Date   

Re: DRAWS

Basil Gunn
 

A brief look at the ICOM F521 manual indicates that it does NOT have
discriminator output so do NOT route IN1 ALSA control ie. your left
channel is currently configured to use discriminator out & it shouldn't be.
This assumes that you have a properly wired cable with discriminator out
on pin 4 & AFOUT on pin 5 referencing the mDin6 cable.

Paul Noa <pauljnoa@...> writes:

~/n7nix/debug $ ./ax25-showcfg.sh -d
Debug mode on
===== ALSA Controls for Radio Transmit =====
LO Driver Gain L:[-6.00dB] R:[-6.00dB]
PCM L:[-6.00dB] R:[-25.00dB]
DAC Playback PT L:[P3] R:[P3]
LO Playback CM [Full Chip]

===== ALSA Controls for Radio Receive =====
ADC Level L:[-6.00dB] R:[2.00dB]
IN1 L:[10 kOhm] R:[Off]
IN2 L:[Off] R:[10 kOhm]
CM L:[10 kOhm] R:[10 kOhm]


Re: DRAWS

Paul Noa
 

~/n7nix/debug $ ./ax25-showcfg.sh -d
Debug mode on
 
 === Display kissparms & ax25dev-parms
Debug: portname=udr0, portcfg=port0
AX.25: udr0 speed: 1200
parse baud_1200 section for udr0
port: 0, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: 3000, t2 timeout: 1000
Debug: portname=udr1, portcfg=port1
AX.25: udr1 speed: 1200
parse baud_1200 section for udr1
port: 1, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: 3000, t2 timeout: 1000
 == kissparms from /etc/ax25/ax25-upd
        $KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
            $KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
            $KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
            $KISSPARMS -p ${PORTNAME_2} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
        $KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
 
 ===== ax.25 config
Found directory: /proc/sys/net/ax25/ax0
ax25_default_mode: 0
backoff_type: 0
connect_mode: 2
dama_slave_timeout: 180000
extended_window_size: 32
idle_timeout: 900000
ip_default_mode: 0
maximum_packet_length: 255
maximum_retry_count: 6
protocol: 0
standard_window_size: 2
t1_timeout: 3000
t2_timeout: 1000
t3_timeout: 300000
 
Found directory: /proc/sys/net/ax25/ax1
ax25_default_mode: 0
backoff_type: 0
connect_mode: 2
dama_slave_timeout: 180000
extended_window_size: 32
idle_timeout: 900000
ip_default_mode: 0
maximum_packet_length: 255
maximum_retry_count: 6
protocol: 0
standard_window_size: 2
t1_timeout: 3000
t2_timeout: 1000
t3_timeout: 300000
 
 
 ===== ALSA Controls for Radio Transmit =====
LO Driver Gain  L:[-6.00dB]     R:[-6.00dB]
PCM             L:[-6.00dB]     R:[-25.00dB]
DAC Playback PT L:[P3]          R:[P3]
LO Playback CM  [Full Chip]
 
 ===== ALSA Controls for Radio Receive =====
ADC Level       L:[-6.00dB]     R:[2.00dB]
IN1             L:[10 kOhm]     R:[Off]
IN2             L:[Off]         R:[10 kOhm]
CM              L:[10 kOhm]     R:[10 kOhm]
 
===== Port baudrate
DireWolf: udr0 speed: 1200, udr1 speed: 1200
AX.25:    udr0 speed: 1200, udr1 speed: 1200
 
===== axports
udr0        KO4BCZ-10            9600    255     2       Winlink port
udr1        KO4BCZ-1             9600    255     2       Direwolf port
 
 ===== ax25d.conf
[KO4BCZ-10 VIA udr0]
NOCALL   * * * * * *  L
default  * * * * * *  - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U
#
[KO4BCZ VIA udr0]
NOCALL   * * * * * *  L
default  * * * * * *  - pi /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d
 
 ===== wl2k.conf
paclink-unix not configured.


Re: UDRCII with RT Systems Cable for CAT Control & mini 6DIN and Yaesu FT-450D --PTT engaged but 0 Watts transmitted #wsjt-x #ft-8

Basil Gunn
 

Looking at my notes to see what might be relevant because I do not own
an FT-450.

* Re: FT-817, I could only get this radio to work by disconnecting pin 6
(squelch) on the mDin6 cable.
https://github.com/nwdigitalradio/n7nix/blob/master/docs/RADIO_APP_NOTES.md

* From your config you are using the left DRAWS connector.
* Adjust the power output slider on the right side of the wsjt-x screen?
* Verify using draws manager
* Input from Receiver: AF (pin5) for your left channel.
* Verify the setting in the Radio that tells it to use the Data
connector for transmit audio, instead of from the Microphone.
* You want MODE = DAT(a) instead of MODE = SSB.
* The serial settings are for configuring rig control which most likely
has no effect on the DRAWS hat configuration.
Make sure rig control is affecting the left channel.
* Look at pertinent ALSA settings alsa-show.sh
* Check out Steve McGrane's video #5 DRAWS GPS & FT8
https://www.youtube.com/watch?v=5lxvVD1-0lk&feature=youtu.be
* In the groups.io forum for this group use the search option for wsjt
/Basil n7nix


TG9AOR <@TG9AOR> writes:

Hello Friends. I have this setup on WSJT-X that came with the DRAWS Image (WSJT-X v2.0.1 7ddcb7)
Radio Tab Audio Tab
Rig: FT-450 Input plughw:CARD=udrc,DEV=0 Mono
Serial Port /dev/ttyUSB0 Output plughw:CARD=udrc,DEV=0 Mono
Baud Rate 38400
Data Bits Default
Stop Bits Default
HandShake Default
Force Control Lines DTR Blank
Force Control Lines RTS Blank
PTT Method CAT
Mode DATA/PKT
Split Operation None

I am able to decode. Curiously, with this same cable, on the FT817(I
am referring to the UDRC cable) I cannot hear the static, maybe
because of the squelch pin John told me back in 2018, must behave
differently on the 817/857.

So with this setup the PTT activates, but 0 watts are transmitted.
Thanks for reading my message and God Bless everyone. 73 de TG9AOR


Re: Compass image V15, XASTIR, Missing Library?

Basil Gunn
 

Mike,
Thanks for the feedback.
I have an nwdr16.img candidate in testing that has those libraries
installed.
/Basil

Mike B <kf5dey@...> writes:

I used your recommended sudo apt-get install shapelib libshp-dev libgeotiff-dev libwebp-dev libgraphicsmagick1-dev

The following additional packages will be installed:
libbz2-dev libexif-dev libexif-doc libgeotiff2 libjbig-dev libjpeg-dev
libjpeg62-turbo-dev liblcms2-dev liblzma-dev libtiff-dev libtiffxx5
libwmf-dev libzstd-dev

And that solved it...I hope the list of packages helps.

Mike
KF5DEY


Re: Compass image V15, XASTIR, Missing Library?

Mike B
 

I used your recommended   sudo apt-get install shapelib libshp-dev libgeotiff-dev libwebp-dev libgraphicsmagick1-dev

The following additional packages will be installed:                                                      
libbz2-dev libexif-dev libexif-doc libgeotiff2 libjbig-dev libjpeg-dev                                  
libjpeg62-turbo-dev liblcms2-dev liblzma-dev libtiff-dev libtiffxx5                                     
libwmf-dev libzstd-dev

And that solved it...I hope the list of packages helps.

Mike
KF5DEY


UDRCII with RT Systems Cable for CAT Control & mini 6DIN and Yaesu FT-450D --PTT engaged but 0 Watts transmitted #wsjt-x #ft-8

TG9AOR
 

Hello Friends. I have this setup on  WSJT-X that came with the DRAWS Image (WSJT-X v2.0.1 7ddcb7)
Radio Tab                                                                         Audio Tab
Rig: FT-450                                                                       Input plughw:CARD=udrc,DEV=0 Mono
Serial Port /dev/ttyUSB0                                                    Output plughw:CARD=udrc,DEV=0 Mono
Baud Rate 38400
Data Bits Default
Stop Bits Default
HandShake Default
Force Control Lines DTR Blank
Force Control Lines RTS Blank
PTT Method CAT
Mode DATA/PKT
Split Operation None

I am able to decode. Curiously, with this same cable, on the FT817(I am referring to the UDRC cable) I cannot hear the static, maybe because of the squelch pin John told me back in 2018, must behave differently on the 817/857.

So with this setup the PTT activates, but 0 watts are transmitted.
Thanks for reading my message and God Bless everyone. 73 de TG9AOR


Re: Setting Up AARDOP with the #draws

Basil Gunn
 

I assume that is for a two radio setup? Or are you saying one radio
and easily switch between ax25?
Two radios, but running packet & some HF program at the same time on your
RPi. I run packet using my vhf/uhf radio & some HF program (FLdigi) on my
HF rig. The way I use it is for convenience of leaving things cabled up
between the two modes. The port.conf file also allows easily setting up
9600 baud packet.

Because my head still hurts from the build and getting ARDOP setup :)
If your head isn't hurting you are probably not doing enough stuff :)

Mike KF5DEY


Re: Setting Up AARDOP with the #draws

Mike B
 

I assume that is for a two radio setup?  Or are you saying one radio and easily switch between ax25?

Because my head still hurts from the build and getting ARDOP setup :)

Mike
KF5DEY


Re: Setting Up AARDOP with the #draws

Basil Gunn
 

Mike,

Happy to hear you have an HF ARDOP setup running on an RPi. Nice work!

Just to let you know it is possible to run direwolf on one port (left) &
ARDOP on the right port. I recently checked-in some scripts that allow
configuring the left & right connectors in split-channel mode using
/etc/ax25/port.conf file. I have some preliminary documentation here:

https://github.com/nwdigitalradio/n7nix/blob/master/docs/PORT_CONFIG.md

/Basil


Mike B <kf5dey@...> writes:

I will give big thanks to the developers and especially others like KM4ACK.

For those wishing to attempt this, do the KM4ACK videos...very easy to follow and understand...but

Do them in this order... Big exception to his instructions... use the settings in the post above... (I use left audio connector)
"For a DRAWS hat left = gpio 12, right = gpio 23. Make sure that direwolf is NOT running."

*./piardopc 8515 plughw:1,0 plughw:1,0 -p GPIO=12*

(if you don't put plughw:1,0 in twice, you will get an error)

Added this to *. asoundrc*
ref: ARDOPC.txt

*pcm.ARDOP {*
*type rate*
*slave {*
*pcm "hw:1,0"*
*rate 12000*
*}*
*}*

Install Winlink on Raspberry Pi 4 Part 1 2019 (also applies to a 3) https://www.youtube.com/watch?v=oZJJLfVz23k

Install Winlink on Raspberry Pi 4 Part 2 2019 (only first bit, he tells you where to stop for DRAWS) https://www.youtube.com/watch?v=BgqsTbxzR4E

THEN

Pat Winlink on DRAWS https://www.youtube.com/watch?v=LnJQv6rDpss

Final thoughts are I had to really crank up the output volume from the default to get any radio output.

127.0.0.1:8080 on your Pi or 'ip_address':8080 on networked computer to start the Web GUI "DRAWS Manager" to set your audio levels.

For me on an FT-857 the radio displays ALC levels, and I have an power meter connected to show the radio ouput wattage...I dial up the digital volume in the "DRAWS Manager" bit by bit until the ALC level is at the 3/4 mark (example in your radio manual) and output power should be close to what was set on the radio.

But I did log into a winlink station, send and receive email over HF, all while using a networked computer's web browser.

So for me, it is working 100%

Mike
KF5DEY


Re: Setting Up AARDOP with the #draws

Mike B
 

I will give big thanks to the developers and especially others like  KM4ACK.

For those wishing to attempt this, do the KM4ACK videos...very easy to follow and understand...but

Do them in this order... Big exception to his instructions... use the settings in the post above... (I use left audio connector)
"For a DRAWS hat left = gpio 12, right = gpio 23. Make sure that direwolf is NOT running."

./piardopc 8515 plughw:1,0 plughw:1,0 -p GPIO=12

(if you don't put plughw:1,0 in twice, you will get an error)

Added this to .asoundrc
ref: ARDOPC.txt

pcm.ARDOP {
type rate
slave {
pcm "hw:1,0"
rate 12000
}
}

Install Winlink on Raspberry Pi 4 Part 1 2019 (also applies to a 3)  https://www.youtube.com/watch?v=oZJJLfVz23k

Install Winlink on Raspberry Pi 4 Part 2 2019  (only first bit, he tells you where to stop for DRAWS)  https://www.youtube.com/watch?v=BgqsTbxzR4E

THEN

Pat Winlink on DRAWS  https://www.youtube.com/watch?v=LnJQv6rDpss

Final thoughts are I had to really crank up the output volume from the default to get any radio output.

127.0.0.1:8080 on your Pi or 'ip_address':8080 on networked computer to start the Web GUI "DRAWS Manager" to set your audio levels.

For me on an FT-857 the radio displays ALC levels, and I have an power meter connected to show the radio ouput wattage...I dial up the digital volume in the "DRAWS Manager" bit by bit until the ALC level is at the 3/4 mark (example in your radio manual) and output power should be close to what was set on the radio.

But I did log into a winlink station, send and receive email over HF, all while using a networked computer's web browser.

So for me, it is working 100%

Mike
KF5DEY


Re: RTC time: n/a

Mike B
 

Yup on for 24  hours, brand new out of the package battery.

Now I have had GPS lock since last night, so I think I may have solved the reception issue (put gps antenna on an empty altoids tin at same location as before...)  or just got lucky...

Mike
KF5DEY

pi@draws:~/n7nix/gps $ ./verify_time.sh

        timedatectl

               Local time: Sun 2020-03-29 10:50:59 CDT
           Universal time: Sun 2020-03-29 15:50:59 UTC
                 RTC time: n/a
                Time zone: America/Chicago (CDT, -0500)
System clock synchronized: yes
              NTP service: inactive
          RTC in local TZ: no

        chronyc sources

210 Number of sources = 6
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
#? GPS                           0   3     0   979   -337ms[ -337ms] +/-  106ms
#* PPS                           0   3     0   978  +3032ns[+3025ns] +/-   11us
^- clock.sjc.he.net              1  10    37   980  -6892us[-6892us] +/-   32ms
^- tick.srs1.ntfo.org            3  10   377   366  -8714us[-8714us] +/-  134ms
^- ntp1.wiktel.com               1  10   357   23m    -14ms[  -14ms] +/-   35ms
^- linode227395.stevemeacha>     3  10   275   40m  -5000us[-7211ns] +/-   58ms

        chronyc sourcestats

210 Number of sources = 6
Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
==============================================================================
GPS                         6   3   151   -408.037   3835.704   -709ms    22ms
PPS                        10   4   526     +0.000      0.055   +120ns  7808ns
clock.sjc.he.net           27  17   84m     -0.263      1.181  -6134us  1752us
tick.srs1.ntfo.org         60  33   10h     +0.003      0.097  -6130us  2668us
ntp1.wiktel.com            24  10  500m     -0.094      0.201  -9183us  2122us
linode227395.stevemeacha>  44  24  589m     -0.060      0.089  -8188us  1766us

        chronyc tracking

Reference ID    : 50505300 (PPS)
Stratum         : 1
Ref time (UTC)  : Sun Mar 29 15:34:40 2020
System time     : 0.000000002 seconds fast of NTP time
Last offset     : -0.000000004 seconds
RMS offset      : 0.000075341 seconds
Frequency       : 5.940 ppm fast
Residual freq   : +0.000 ppm
Skew            : 0.058 ppm
Root delay      : 0.000000001 seconds
Root dispersion : 0.001043428 seconds
Update interval : 8.0 seconds
Leap status     : Normal

        chronyc activity

200 OK
4 sources online
0 sources offline
0 sources doing burst (return to online)
0 sources doing burst (return to offline)
0 sources with unknown address

        chronyd systemctl status

● chrony.service - chrony, an NTP client/server
   Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2020-03-29 00:21:08 CDT; 10h ago
     Docs: man:chronyd(8)
           man:chronyc(1)
           man:chrony.conf(5)
  Process: 478 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=0/SUCCESS)
  Process: 499 ExecStartPost=/usr/lib/chrony/chrony-helper update-daemon (code=exited, status=0/SUCCESS)
 Main PID: 494 (chronyd)
    Tasks: 2 (limit: 2200)
   Memory: 3.4M
   CGroup: /system.slice/chrony.service
           ├─494 /usr/sbin/chronyd -F -1
           └─497 /usr/sbin/chronyd -F -1

Mar 29 00:21:31 draws chronyd[494]: Selected source GPS
Mar 29 00:21:31 draws chronyd[494]: System clock wrong by 9.604035 seconds,…rted
Mar 29 00:21:41 draws chronyd[494]: System clock was stepped by 9.604035 seconds
Mar 29 00:21:51 draws chronyd[494]: Selected source 69.89.207.99
Mar 29 00:21:53 draws chronyd[494]: Selected source 208.79.89.249
Mar 29 00:21:53 draws chronyd[494]: Selected source 69.89.207.99
Mar 29 00:25:33 draws chronyd[494]: Selected source GPS
Mar 29 00:26:11 draws chronyd[494]: Source 208.79.89.249 replaced with 148.…3.91
Mar 29 00:26:21 draws chronyd[494]: Selected source PPS
Mar 29 09:09:25 draws chronyd[494]: Source 148.251.183.91 replaced with 216….202
Hint: Some lines were ellipsized, use -l to show in full.

        gpsd systemctl status

● gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2020-03-29 00:21:08 CDT; 10h ago
  Process: 513 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
 Main PID: 516 (gpsd)
    Tasks: 3 (limit: 2200)
   Memory: 1.4M
   CGroup: /system.slice/gpsd.service
           └─516 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0

Mar 29 00:21:08 draws systemd[1]: Starting GPS (Global Positioning System) …n...
Mar 29 00:21:08 draws systemd[1]: Started GPS (Global Positioning System) D…mon.
Hint: Some lines were ellipsized, use -l to show in full.
gpsd: 3.20 (revision 3.20)
pi@draws:~/n7nix/gps $


Re: RTC time: n/a

Basil Gunn
 

The GPS device on the DRAWS hat is an S1216 Family GNSS Module.
http://www.skytraq.com.tw/datasheet/S1216V8_v0.9.pdf

This device is not a traditional RTC so there is no RTC wired up to the
Device Tree Source Files loaded by the Linux kernel. What it does provide is a
battery backed-up time source that operates with chronyd like an RTC
device.
To verify that your time source (GPS) is working, run the verify_time.sh
script which checks the chronyd & gpsd daemons to verify the S1216 GNSS
module is working and providing an accurate time source. For example
from 'chronyc tracking' which is run from the verify_time.sh script.

Ref time (UTC) : Sun Mar 29 14:26:55 2020
System time : 0.000000172 seconds fast of NTP time

I can see my time source is stunningly accurate.

To confirm that your time source is working properly I would need to see
the output of the verify_time.sh script.

/Basil n7nix

Mike B <kf5dey@...> writes:

First I would like to say, thanks to the documentation and how to
videos spread throughout the inter-tubes I have my DRAWS setup mostly
working.

A continual problem I have is the GPS...and it might even be
associated a bit with RFI...tbd.

However in troubleshooting, I run verify_time.sh (in the n7nix/gps folder)

RTC time always shows n/a. Is that because the pi doesn't see the RTC?
Is there any way to see if the RTC is working and has the correct
time?


Re: RTC time: n/a

 

The RTC on DRAWS™ is really a backup clock for the GPS. 

It is set by the GPS when the GPS is locked on a sufficient number of satellites. 

It keeps running as long as the HAT has power. If the DRAWS™ looses power, the backup battery can keep the RTC running for a cumulative 40 days (Subtract the time the power is removed), then the battery must be replaced and the GPS  must reset the clock. 

Are you getting GPS lock?  Are you leaving the DRAWS™ powered at all times?  Is your backup battery good?

On Sun, Mar 29, 2020, 07:17 Mike B <kf5dey@...> wrote:
First I would like to say, thanks to the documentation and how to videos spread throughout the inter-tubes I have my DRAWS setup mostly working.

A continual problem I have is the GPS...and it might even be associated a bit with RFI...tbd.

However in troubleshooting, I run verify_time.sh (in the n7nix/gps folder)

RTC time always shows n/a.   Is that because the pi doesn't see the RTC?   Is there any way to see if the RTC is working and has the correct time? 


RTC time: n/a

Mike B
 

First I would like to say, thanks to the documentation and how to videos spread throughout the inter-tubes I have my DRAWS setup mostly working.

A continual problem I have is the GPS...and it might even be associated a bit with RFI...tbd.

However in troubleshooting, I run verify_time.sh (in the n7nix/gps folder)

RTC time always shows n/a.   Is that because the pi doesn't see the RTC?   Is there any way to see if the RTC is working and has the correct time? 


DummyRepeater for DRAWS #dtarrepeater #dummyrepeater #draws

Geoffrey Merck
 

Hi All,

So being in quarantine I have some extra time on my hands.
I took on DummyRepeater and made it work with DRAWS. In the mean time I fixed some issues like resources not always being released or the program not properly exiting.
I also improved audio filtering as users were reporting audio had too much low.

While this is still work in progress, anyone interested can pull it from my feature/DRAWS branch at https://github.com/F4FXL/DummyRepeater/tree/feature/Draws
libboost-all-dev is required to build.

Comments are welcome !

73
Geoffrey F4FXL / KC3FRA


Re: DRAWS

Basil Gunn
 

# From your console output I do not see the mis-configuration I saw
before. To confirm you could also provide console output from
~/n7nix/debug/ax25-showcfg.sh -d

# From the direwolf User-Guide.pdf doc to invert the gpio output pin
sense: https://raw.githubusercontent.com/wb2osz/direwolf/master/doc/User-Guide.pdf

9.2.8.2 PTT with General Purpose I/O (GPIO)
On Linux you can use General Purpose I/O (GPIO) pins if available. This is mostly applicable to a
microprocessor board, such as a Raspberry Pi or BeagleBone, not a general purpose PC. Precede the pin
number with “-“ to invert the signal.
PTT GPIO [-]pin-number

# In directory ~/n7nix/bin there is a script to test just the PTT gpio
pins used by UDRC/DRAWS hat.

./ptt_ctrl.sh -h
Usage: ptt_ctrl.sh [-l][-r][-on][-off][-c][-h]
-l | --left Select left connector gpio
-r | --right Select right connector gpio
-on | on Turn selected gpio ON
-off | off Turn selected gpio OFF
-t | --toggle Toggle PTT state
-c | --check Check gpio state ie. read gpio
-d | --debug Turn debug on
-h display this message

# With just a quick look at the the IC-F21 Service manual I don't
believe it provides discriminator output so nothing will be connected
to mDin6 connector pin 4 and you should configure ALSA to not route on
IN1. You are currently doing this:

IN1 L:[10 kOhm]     R:[Off]
IN2 L:[Off]         R:[10 kOhm]


# The mDin6 data connector is somewhat of a standard used by Japanese
ham equipment manufacturers.
http://wa8lmf.net/miscinfo/MiniDIN6-Packet.pdf
For pin numbers look at a Kenwood TM-v71a manual page 83.

I am still looking for a clarification on the pin outs, when I ring out the Cable, Male Plug, Looking into the connector (at the Pins) flat portion on top:
pin 1 is bottom left, TX
pin 2 bottom right GND
pin 3 middle left PTT
pin 4 middle right LN1
pin 5 top left LN2
pin 6 top right SQL

What I have learned scoping the outputs is PTT is low going high on pin 3;

On the IC F-521, when I pull the respective pin on the accessory connector low I xmit! I will search for the specs on the interface again to verify.

Is there a way in software to invert this ?

I do see the AFSK out haven't got to adjust yet trying to resolve XMIT issue

Paul


#draws #draws

Paul Noa
 

Basil,
I edited axport file here is the current output from Showudrc

 showudrc.sh
==== Sound Card ====
udrc card number line: card 0: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
udrc is sound card #0
==== ALSA Controls for Radio Tansmit ====
LO Driver Gain  L:[0.00dB]      R:[-6.00dB]
PCM             L:[-3.00dB]     R:[-25.00dB]
DAC Playback PT L:[P3]  R:[P3]
LO Playback CM  [Full Chip]
==== ALSA Controls for Radio Receive ====
ADC Level       L:[-6.00dB]     R:[0.00dB]
IN1             L:[10 kOhm]     R:[Off]
IN2             L:[Off]         R:[10 kOhm]
==== Pi Ver ====
 Pi 3 Model B+, Rev 1.3, Mfg by Sony UK
 Has WiFi
==== udrc Ver ====
Found a DRAWS
 
     HAT ID EEPROM
Name:        hat
Product:     Digital Radio Amateur Work Station
Product ID:  0x0004
Product ver: 0x0206
UUID:        709b5761-81d1-452a-9709-8e1626c29c26
Vendor:      NW Digital Radio
 
==== sys Ver ====
----- image version
2020 01 23 09:25:01 PST: SD image version: nwdr15
----- /proc/version
Linux version 4.19.97-v7+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1294 SMP Thu Jan 30 13:15:58 GMT 2020
 
----- /etc/*version: 10.3
 
----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
 
----- lsb_release
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 10 (buster)
Release:        10
Codename:       buster
 
---- systemd
   Static hostname: asawizard
         Icon name: computer
        Machine ID: 27ac1f0c20904cb7a960920e966db545
           Boot ID: 8a4bb8c1524f445381df95e98fa862d8
  Operating System: Raspbian GNU/Linux 10 (buster)
            Kernel: Linux 4.19.97-v7+
      Architecture: arm
 
---- modules
snd_soc_tlv320aic32x4_i2c    16384  27
snd_soc_tlv320aic32x4    40960  1 snd_soc_tlv320aic32x4_i2c
snd_soc_core          192512  4 snd_soc_simple_card_utils,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_soc_simple_card
snd_pcm               102400  6 snd_pcm_dmaengine,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_soc_core
snd                    73728  11 snd_compress,snd_timer,snd_soc_tlv320aic32x4,snd_soc_core,snd_pcm
 
---- kernel
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name               Version      Architecture Description
+++-==================-============-============-=================================
ii  raspberrypi-kernel 1.20200212-1 armhf        Raspberry Pi bootloader
 
---- Codec drivers
Found: snd-soc-tlv320aic32x4-i2c.ko, OK
Found: snd-soc-tlv320aic32x4.ko, OK
Directory: /proc/device-tree/soc/i2c@7e804000/tlv320aic32x4@18 exists and status is okay
 
---- syslog
 
---- dmesg
 
 
----- Dire Wolf DEVELOPMENT version 1.6 D (Jan  6 2020)
 
==== Filesystem ====
/dev/root        29G  5.3G   23G  19% /
 
==== boot config ====
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
 
[all]
#dtoverlay=vc4-fkms-v3d
 
# Flush all overlays, ie. deprecated overlays loaded from eeprom
dtoverlay=
# enable udrc/draws if no eeprom
dtoverlay=draws,alsaname=udrc
force_turbo=1
# Enable audio (loads snd_bcm2835)
#dtparam=audio=on
 
---- gpsd
/usr/local/sbin/gpsd
gpsd: 3.20 (revision 3.20)
● gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2020-03-27 18:44:14 EDT; 16h ago
  Process: 514 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
 Main PID: 521 (gpsd)
    Tasks: 3 (limit: 2200)
   Memory: 1.4M
   CGroup: /system.slice/gpsd.service
           └─521 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
 
Mar 27 18:44:14 asawizard systemd[1]: Starting GPS (Global Positioning System) Daemon...
Mar 27 18:44:14 asawizard systemd[1]: Started GPS (Global Positioning System) Daemon.
 
---- chrony
crw-rw---- 1 root root    241, 0 Mar 27 18:44 /dev/pps0
crw------- 1 root root    241, 1 Mar 27 18:44 /dev/pps1
crw-rw---- 1 root dialout 239, 0 Mar 27 18:44 /dev/ttySC0
crw-rw---- 1 root dialout 239, 1 Mar 27 18:44 /dev/ttySC1
-- chrony sources
210 Number of sources = 6
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
#- GPS                           0   3   377     6    -73ms[  -73ms] +/-  104ms
#* PPS                           0   3   377     6    -36ns[ -245ns] +/-  501ns
^- ntp.jtsage.com                2   6    17    39    -11ms[  -11ms] +/-  103ms
^- jikan.ae7.st                  2   6    17    39  -4532us[-4534us] +/-   83ms
^- y.ns.gin.ntt.net              2   6    17    40  -3766us[-3768us] +/-   65ms
^- t2.time.bf1.yahoo.com         3   6    17    39  -6671us[-6673us] +/-   74ms
-- chrony tracking
Reference ID    : 50505300 (PPS)
Stratum         : 1
Ref time (UTC)  : Sat Mar 28 15:06:24 2020
System time     : 0.000000212 seconds slow of NTP time
Last offset     : -0.000000256 seconds
RMS offset      : 0.018753026 seconds
Frequency       : 1.507 ppm fast
Residual freq   : -0.003 ppm
Skew            : 0.135 ppm
Root delay      : 0.000000001 seconds
Root dispersion : 0.000009062 seconds
Update interval : 8.0 seconds
Leap status     : Normal
-- chrony sourcestats
210 Number of sources = 6
Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
==============================================================================
GPS                        12   9    88   +176.256    183.237    -76ms  4014us
PPS                         6   3    41     -0.003      0.124     -8ns   485ns
ntp.jtsage.com              4   3     6   +156.375  24667.115  -5644us  4045us
jikan.ae7.st                4   3     6  -1681.325  13177.292    -73ms  1435us
y.ns.gin.ntt.net            4   4     6   +109.014   7221.111   +176us   995us
t2.time.bf1.yahoo.com       4   3     6   -517.597  15332.971    -27ms  1864us
 
---- sensors
-rw-r--r-- 1 root root 171 Sep 19  2019 /etc/sensors.d/draws
rpi_volt-isa-0000
Adapter: ISA adapter
in0:              N/A
 
ads1015-i2c-1-48
Adapter: bcm2835 I2C adapter
+12V:         +0.00 V
in5:          +2.47 V
User ADC 1:   +0.00 V
User ADC 2:   +0.00 V
 
 
---- throttle
temp=41.3'C
throttled=0x0
 
---- locale
Locale country codes consistent among WiFi cfg file, iw reg & X11: US
core_config.sh has been run 1 time(s)

I am still looking for a clarification on the pin outs,  when I ring out the Cable, Male Plug, Looking into the connector (at the Pins) flat portion on top:
pin 1 is bottom left,  TX   
pin 2 bottom right    GND
pin 3 middle left       PTT
pin 4 middle right     LN1
pin 5 top left             LN2
pin 6 top right           SQL

What I have learned scoping the outputs is PTT is low going high on pin 3;

On the IC F-521, when I pull the respective pin on the accessory connector low I xmit!  I will search for the specs on the interface again to verify.

Is there a way in software to invert this ?

I do see the AFSK out haven't got to adjust yet trying to resolve XMIT issue

Paul


Re: DRAWS

Paul Noa
 

Basil,
I edited axport file here is the current output from Showudrc

 showudrc.sh
==== Sound Card ====
udrc card number line: card 0: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
udrc is sound card #0
==== ALSA Controls for Radio Tansmit ====
LO Driver Gain  L:[0.00dB]      R:[-6.00dB]
PCM             L:[-3.00dB]     R:[-25.00dB]
DAC Playback PT L:[P3]  R:[P3]
LO Playback CM  [Full Chip]
==== ALSA Controls for Radio Receive ====
ADC Level       L:[-6.00dB]     R:[0.00dB]
IN1             L:[10 kOhm]     R:[Off]
IN2             L:[Off]         R:[10 kOhm]
==== Pi Ver ====
 Pi 3 Model B+, Rev 1.3, Mfg by Sony UK
 Has WiFi
==== udrc Ver ====
Found a DRAWS
 
     HAT ID EEPROM
Name:        hat
Product:     Digital Radio Amateur Work Station
Product ID:  0x0004
Product ver: 0x0206
UUID:        709b5761-81d1-452a-9709-8e1626c29c26
Vendor:      NW Digital Radio
 
==== sys Ver ====
----- image version
2020 01 23 09:25:01 PST: SD image version: nwdr15
----- /proc/version
Linux version 4.19.97-v7+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1294 SMP Thu Jan 30 13:15:58 GMT 2020
 
----- /etc/*version: 10.3
 
----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
 
----- lsb_release
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 10 (buster)
Release:        10
Codename:       buster
 
---- systemd
   Static hostname: asawizard
         Icon name: computer
        Machine ID: 27ac1f0c20904cb7a960920e966db545
           Boot ID: 8a4bb8c1524f445381df95e98fa862d8
  Operating System: Raspbian GNU/Linux 10 (buster)
            Kernel: Linux 4.19.97-v7+
      Architecture: arm
 
---- modules
snd_soc_tlv320aic32x4_i2c    16384  27
snd_soc_tlv320aic32x4    40960  1 snd_soc_tlv320aic32x4_i2c
snd_soc_core          192512  4 snd_soc_simple_card_utils,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_soc_simple_card
snd_pcm               102400  6 snd_pcm_dmaengine,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_soc_core
snd                    73728  11 snd_compress,snd_timer,snd_soc_tlv320aic32x4,snd_soc_core,snd_pcm
 
---- kernel
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name               Version      Architecture Description
+++-==================-============-============-=================================
ii  raspberrypi-kernel 1.20200212-1 armhf        Raspberry Pi bootloader
 
---- Codec drivers
Found: snd-soc-tlv320aic32x4-i2c.ko, OK
Found: snd-soc-tlv320aic32x4.ko, OK
Directory: /proc/device-tree/soc/i2c@7e804000/tlv320aic32x4@18 exists and status is okay
 
---- syslog
 
---- dmesg
 
 
----- Dire Wolf DEVELOPMENT version 1.6 D (Jan  6 2020)
 
==== Filesystem ====
/dev/root        29G  5.3G   23G  19% /
 
==== boot config ====
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
 
[all]
#dtoverlay=vc4-fkms-v3d
 
# Flush all overlays, ie. deprecated overlays loaded from eeprom
dtoverlay=
# enable udrc/draws if no eeprom
dtoverlay=draws,alsaname=udrc
force_turbo=1
# Enable audio (loads snd_bcm2835)
#dtparam=audio=on
 
---- gpsd
/usr/local/sbin/gpsd
gpsd: 3.20 (revision 3.20)
● gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2020-03-27 18:44:14 EDT; 16h ago
  Process: 514 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
 Main PID: 521 (gpsd)
    Tasks: 3 (limit: 2200)
   Memory: 1.4M
   CGroup: /system.slice/gpsd.service
           └─521 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
 
Mar 27 18:44:14 asawizard systemd[1]: Starting GPS (Global Positioning System) Daemon...
Mar 27 18:44:14 asawizard systemd[1]: Started GPS (Global Positioning System) Daemon.
 
---- chrony
crw-rw---- 1 root root    241, 0 Mar 27 18:44 /dev/pps0
crw------- 1 root root    241, 1 Mar 27 18:44 /dev/pps1
crw-rw---- 1 root dialout 239, 0 Mar 27 18:44 /dev/ttySC0
crw-rw---- 1 root dialout 239, 1 Mar 27 18:44 /dev/ttySC1
-- chrony sources
210 Number of sources = 6
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
#- GPS                           0   3   377     6    -73ms[  -73ms] +/-  104ms
#* PPS                           0   3   377     6    -36ns[ -245ns] +/-  501ns
^- ntp.jtsage.com                2   6    17    39    -11ms[  -11ms] +/-  103ms
^- jikan.ae7.st                  2   6    17    39  -4532us[-4534us] +/-   83ms
^- y.ns.gin.ntt.net              2   6    17    40  -3766us[-3768us] +/-   65ms
^- t2.time.bf1.yahoo.com         3   6    17    39  -6671us[-6673us] +/-   74ms
-- chrony tracking
Reference ID    : 50505300 (PPS)
Stratum         : 1
Ref time (UTC)  : Sat Mar 28 15:06:24 2020
System time     : 0.000000212 seconds slow of NTP time
Last offset     : -0.000000256 seconds
RMS offset      : 0.018753026 seconds
Frequency       : 1.507 ppm fast
Residual freq   : -0.003 ppm
Skew            : 0.135 ppm
Root delay      : 0.000000001 seconds
Root dispersion : 0.000009062 seconds
Update interval : 8.0 seconds
Leap status     : Normal
-- chrony sourcestats
210 Number of sources = 6
Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
==============================================================================
GPS                        12   9    88   +176.256    183.237    -76ms  4014us
PPS                         6   3    41     -0.003      0.124     -8ns   485ns
ntp.jtsage.com              4   3     6   +156.375  24667.115  -5644us  4045us
jikan.ae7.st                4   3     6  -1681.325  13177.292    -73ms  1435us
y.ns.gin.ntt.net            4   4     6   +109.014   7221.111   +176us   995us
t2.time.bf1.yahoo.com       4   3     6   -517.597  15332.971    -27ms  1864us
 
---- sensors
-rw-r--r-- 1 root root 171 Sep 19  2019 /etc/sensors.d/draws
rpi_volt-isa-0000
Adapter: ISA adapter
in0:              N/A
 
ads1015-i2c-1-48
Adapter: bcm2835 I2C adapter
+12V:         +0.00 V
in5:          +2.47 V
User ADC 1:   +0.00 V
User ADC 2:   +0.00 V
 
 
---- throttle
temp=41.3'C
throttled=0x0
 
---- locale
Locale country codes consistent among WiFi cfg file, iw reg & X11: US
core_config.sh has been run 1 time(s)

I am still looking for a clarification on the pin outs,  when I ring out the Cable, Male Plug, Looking into the connector (at the Pins) flat portion on top:
pin 1 is bottom left,  TX   
pin 2 bottom right    GND
pin 3 middle left       PTT
pin 4 middle right     LN1
pin 5 top left             LN2
pin 6 top right           SQL

What I have learned scoping the outputs is PTT is low going high on pin 3;

On the IC F-521, when I pull the respective pin on the accessory connector low I xmit!  I will search for the specs on the interface again to verify.

Is there a way in software to invert this ?

I do see the AFSK out haven't got to adjust yet trying to resolve XMIT issue

Paul


Re: app_config.sh

Basil Gunn
 

J P,
I need to clean-up app_config.sh a little.

The 'messenger' config was to bring up a web interface for both Winlink
& APRS messages. The goal was to be able to run Winlink & APRS in my
truck from a web browser on my Android tablet.

What happened was the default paclink-unix config now installs the
paclink-unix winlink web app & SMTP mail server. There is an option in
app_config.sh, plumin, to just install minimum paclink-unix and a
console based email client. Last year I switched the defualt
paclink-unix install to be a complete web app install.

To get the messenger application I originally envisioned you need to
install paclink-unix then nixtracker (forked from dantracker). Nixtracker has a modified web app (from the paclink-unix
only web app) that supports both APRS & winlink messaging. To compose a
winlink message you use Rainloop (https://www.rainloop.net/) webmail
then send it with the paclink-unix web interface. The APRS messaging is
pretty basic but it supports acks.

Hope this makes sense.

/Basil n7nix


J P Watters via Groups.Io <kc9kko=mac.com@groups.io> writes:

What does *app_config.sh messenger* do? I searched the WIKI without sucess.

I ran *app_config.sh without any parameters and it shows command line* *Usage: app_config.sh [-d][-h][core][plu][rmsgw][messanger]*
*core MUST be run before any other config*


app_config.sh

J P Watters <kc9kko@...>
 

What does app_config.sh messenger do? I searched the WIKI without sucess.

I ran app_config.sh without any parameters and it shows  command line Usage: app_config.sh [-d][-h][core][plu][rmsgw][messanger]
   core      MUST be run before any other config
   plu       Configures paclink-unix & email applications
   rmsgw     Configures Linux RMS Gateway
   messanger Configures messanger appliance
   -d        set debug flag
   -h        no arg, display this message