Date   
Re: DRAWS

Basil Gunn
 

What could prevent transmitting with DRAWS Hat running NWDR15 on Pi3 B+ ?
Addendum to my last question Why no transmit?
I just did a fresh install to confirm that the text in the "Getting
Started" Guide works consistently.

Thanks for the console output from all the commands. In the future you
can just run the showudrc.sh script which usually gives enough output to
solve problems.

First to answer how to debug transmit problems:

Start from a clean install. Editing any configuration files is
discouraged until you can confirm things are working. In your case
/etc/ax25/axports file has been manually edited and is misconfigured.
The /etc/direwolf.conf file may also be manually edited and misconfigured.

1. Check cable to radio. Is it a custom cable? In your case you should
be using the left hand mDin6 connector.
2. Radio turned on?
-When running scripts btest.sh or measure_deviate.sh
3. Does you radio indicate that it transmits when running either of the
above scripts?
4. Does the transmit led next to the mDin6 connector on the DRAWS card
come on when running either of the above scripts?
5. Tune an HT to the same frequency used by your radio attached to the
DRAWS card. When running the measure_deviate.sh script can you hear a
tone?

Until you get the above tests working I would not try to figure out why
your receive is not working either.

Things from your console output that require fixing:

Either start from a fresh install (recommended) or fix your /etc/ax25/axports file.
Mar 19 19:38:04 ASAwizard bash[564]: axconfig: duplicate callsign KO4BCZ-10 in line 6 of axports file
Mar 19 19:38:04 ASAwizard bash[564]: kissparms: invalid port name - udr1

You said that you did not see any console output from the listen command
yet your direwolf log file sees your beacon test output:

Mar 21 15:08:12 ASAwizard direwolf[479]: [0L]KO4BCZ-11>APUDR1,WIDE1-1::KO4BCZ :21 15:08:11 EDT KO4BCZ mesg_beacon test from host ASAwizard on udr0 Seq: 21

This indicates some ax.25 misconfiguration. Note that if you just follow
the "Getting Started" guide you should NOT have to edit any
configuration files.

Focus on your transmit problem first then look at receive.
Tune your radio to the national 1200 baud APRS frequency (144.390 MHZ),
turn audio up & squelch off. You should hear some/a lot of traffic and
you should see that traffic in your 'listen' console or 'tail -f
/var/log/direwolf/dirwolf.log' console.

Receive problems are usually due to cable mis-wired, incorrect ALSA
parameters or radio misconfigured (AFOUT/DISCriminator).

/Basil n7nix

DRAWS

Paul Noa
 

Addendum to my last question Why no transmit?
~/n7nix/debug $ ax25-status -d
AX25 Debug Status
== failed & loaded but inactive units==
0 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
 
== direwolf ==
  pid: 479
  ver: Dire Wolf DEVELOPMENT version 1.6 D (Jan  6 2020)
== /proc/sys ==
ax25  core  ipv4  ipv6  netfilter  unix
ax0  ax1
 
== Network Interface ax0 & ax1 ==
4: ax0: <BROADCAST,UP,LOWER_UP> mtu 255 qdisc pfifo_fast state UNKNOWN group default qlen 10
    link/ax25 96:9e:68:84:86:b4:14 brd a2:a6:a8:40:40:40:00
    inet 192.168.255.2/32 brd 192.168.255.255 scope global ax0
       valid_lft forever preferred_lft forever
 
5: ax1: <BROADCAST,UP,LOWER_UP> mtu 255 qdisc pfifo_fast state UNKNOWN group default qlen 10
    link/ax25 96:9e:68:84:86:b4:14 brd a2:a6:a8:40:40:40:00
    inet 192.168.255.3/32 brd 192.168.255.255 scope global ax1
       valid_lft forever preferred_lft forever
 
== status networkd services ==
enabled
● systemd-networkd-wait-online.service - Wait for Network to be Configured
   Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled)
   Active: active (exited) since Thu 2020-03-19 19:38:04 EDT; 1 day 19h ago
     Docs: man:systemd-networkd-wait-online.service(8)
  Process: 372 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exited, status=0/SUCCESS)
 Main PID: 372 (code=exited, status=0/SUCCESS)
 
Mar 19 19:38:04 ASAwizard systemd-networkd-wait-online[372]: ignoring: lo
Mar 19 19:38:04 ASAwizard systemd-networkd-wait-online[372]: ignoring: lo
Mar 19 19:38:04 ASAwizard systemd-networkd-wait-online[372]: ignoring: lo
Mar 19 19:38:04 ASAwizard systemd-networkd-wait-online[372]: ignoring: lo
Mar 19 19:38:04 ASAwizard systemd-networkd-wait-online[372]: ignoring: lo
Mar 19 19:38:04 ASAwizard systemd-networkd-wait-online[372]: ignoring: lo
Mar 19 19:38:04 ASAwizard systemd-networkd-wait-online[372]: ignoring: lo
Mar 19 19:38:04 ASAwizard systemd-networkd-wait-online[372]: ignoring: lo
Mar 19 19:38:04 ASAwizard systemd-networkd-wait-online[372]: ignoring: lo
Mar 19 19:38:04 ASAwizard systemd[1]: Started Wait for Network to be Configured.
enabled
● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-03-19 19:38:02 EDT; 1 day 19h ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 317 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 2200)
   Memory: 4.5M
   CGroup: /system.slice/systemd-networkd.service
           └─317 /lib/systemd/systemd-networkd
 
Mar 19 19:38:02 ASAwizard systemd[1]: Starting Network Service...
Mar 19 19:38:02 ASAwizard systemd-networkd[317]: Enumeration completed
Mar 19 19:38:02 ASAwizard systemd[1]: Started Network Service.
Mar 19 19:38:04 ASAwizard systemd-networkd[317]: ax0: Gained carrier
Mar 19 19:38:04 ASAwizard systemd-networkd[317]: ax1: Gained carrier
Mar 19 19:38:10 ASAwizard systemd-networkd[317]: wlan0: Gained carrier
Mar 19 19:38:12 ASAwizard systemd-networkd[317]: wlan0: Gained IPv6LL
Mar 21 14:43:28 ASAwizard systemd-networkd[317]: wlan0: Lost carrier
Mar 21 14:46:53 ASAwizard systemd-networkd[317]: wlan0: Gained carrier
Mar 21 14:47:04 ASAwizard systemd-networkd[317]: wlan0: Gained IPv6LL
 
== status direwolf service ==
enabled
● direwolf.service - Direwolf Daemon
   Loaded: loaded (/etc/systemd/system/direwolf.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-03-19 19:38:03 EDT; 1 day 19h ago
  Process: 470 ExecStartPre=/bin/rm -f /tmp/kisstnc (code=exited, status=0/SUCCESS)
 Main PID: 479 (direwolf)
    Tasks: 15 (limit: 2200)
   Memory: 2.7M
   CGroup: /system.slice/direwolf.service
           └─479 /usr/bin/direwolf -t 0 -c /etc/direwolf.conf -p
 
Mar 21 14:39:07 ASAwizard systemd[1]: /etc/systemd/system/direwolf.service:10: DefaultInstance= only makes sense for template units, ignoring.
Mar 21 14:41:53 ASAwizard direwolf[479]: [ig>tx] WA4TKG>APW290,W4NAS,WIDE2-2,qAR,W4NAS::K6STS-11 :We SEEZ'ya' !{000
Mar 21 15:04:38 ASAwizard direwolf[479]: Error reading from IGate server.  Closing connection.
Mar 21 15:04:52 ASAwizard direwolf[479]: Now connected to IGate server noam.aprs2.net (173.242.239.3)
Mar 21 15:04:52 ASAwizard direwolf[479]: Check server status here http://173.242.239.3:14501
Mar 21 15:04:53 ASAwizard direwolf[479]: [ig] # aprsc 2.1.5-g8af3cdc
Mar 21 15:04:55 ASAwizard direwolf[479]: [ig] # logresp KO4BCZ verified, server T2NALA
Mar 21 15:08:12 ASAwizard direwolf[479]: [0L] KO4BCZ-11>APUDR1,WIDE1-1::KO4BCZ   :21 15:08:11 EDT KO4BCZ mesg_beacon test from host ASAwizard on…dr0 Seq: 21
Mar 21 15:10:10 ASAwizard systemd[1]: /etc/systemd/system/direwolf.service:10: DefaultInstance= only makes sense for template units, ignoring.
Mar 21 15:10:10 ASAwizard systemd[1]: /etc/systemd/system/direwolf.service:10: DefaultInstance= only makes sense for template units, ignoring.
Hint: Some lines were ellipsized, use -l to show in full.
 
== status ax25 service ==
enabled
● ax25dev.service - AX.25 device
   Loaded: loaded (/etc/systemd/system/ax25dev.service; enabled; vendor preset: enabled)
   Active: active (exited) since Thu 2020-03-19 19:38:04 EDT; 1 day 19h ago
  Process: 564 ExecStart=/bin/bash -c /etc/ax25/ax25-upd (code=exited, status=0/SUCCESS)
 Main PID: 564 (code=exited, status=0/SUCCESS)
    Tasks: 3 (limit: 2200)
   Memory: 1.6M
   CGroup: /system.slice/ax25dev.service
           ├─582 /usr/local/sbin/mkiss /tmp/kisstnc /dev/ptmx /dev/ptmx
           ├─598 /usr/local/sbin/kissattach /dev/pts/1 udr0 192.168.255.2
           └─601 /usr/local/sbin/kissattach /dev/pts/2 udr1 192.168.255.3
 
Mar 19 19:38:04 ASAwizard bash[564]: ax25dev-parms finished
Mar 19 19:38:04 ASAwizard bash[564]: Using Device = ax1
Mar 19 19:38:04 ASAwizard bash[564]: ax25dev-parms finished
Mar 19 19:38:04 ASAwizard bash[564]:  Port udr0 attached to ax0
Mar 19 19:38:04 ASAwizard bash[564]:  Port udr1 attached to ax1
Mar 19 19:38:04 ASAwizard bash[564]: axconfig: duplicate callsign KO4BCZ-10 in line 6 of axports file
Mar 19 19:38:04 ASAwizard bash[564]: axconfig: duplicate callsign KO4BCZ-10 in line 6 of axports file
Mar 19 19:38:04 ASAwizard bash[564]: kissparms: invalid port name - udr1
Mar 19 19:38:04 ASAwizard bash[564]: ax25-upd script finished
Mar 19 19:38:04 ASAwizard systemd[1]: Started AX.25 device.
 
-- Logs begin at Thu 2019-02-14 05:11:59 EST, end at Sat 2020-03-21 15:10:10 EDT. --
Mar 19 19:38:03 ASAwizard systemd[1]: Starting AX.25 device...
Mar 19 19:38:03 ASAwizard bash[483]: ax25-upd: Start Port udr0 with device /tmp/kisstnc
Mar 19 19:38:03 ASAwizard bash[483]: Direwolf serial port NOT FOUND
Mar 19 19:38:03 ASAwizard systemd[1]: ax25dev.service: Main process exited, code=exited, status=1/FAILURE
Mar 19 19:38:03 ASAwizard systemd[1]: ax25dev.service: Failed with result 'exit-code'.
Mar 19 19:38:03 ASAwizard systemd[1]: Failed to start AX.25 device.
Mar 19 19:38:04 ASAwizard systemd[1]: Starting AX.25 device...
Mar 19 19:38:04 ASAwizard bash[564]: ax25-upd: Start Port udr0 with device /tmp/kisstnc
Mar 19 19:38:04 ASAwizard bash[564]: Direwolf serial port ready
Mar 19 19:38:04 ASAwizard bash[564]: UDRC_PROD: Digital Radio Amateur Work Station, ID: 4
Mar 19 19:38:04 ASAwizard bash[564]: Product ID match: 4
Mar 19 19:38:04 ASAwizard bash[564]: Found HAT for DRAWS with product ID: 4
Mar 19 19:38:04 ASAwizard bash[564]: UDRC II or DRAWS installed
Mar 19 19:38:04 ASAwizard bash[564]: using mkiss with UDRC II and pseudo term_1: /dev/pts/1 pseudo term_2: /dev/pts/2
Mar 19 19:38:04 ASAwizard bash[564]: kissattach return: 0
Mar 19 19:38:04 ASAwizard bash[564]: Using Device = ax0
Mar 19 19:38:04 ASAwizard bash[564]: ax25dev-parms finished
Mar 19 19:38:04 ASAwizard bash[564]: Using Device = ax1
Mar 19 19:38:04 ASAwizard bash[564]: ax25dev-parms finished
Mar 19 19:38:04 ASAwizard bash[564]:  Port udr0 attached to ax0
Mar 19 19:38:04 ASAwizard bash[564]:  Port udr1 attached to ax1
Mar 19 19:38:04 ASAwizard bash[564]: axconfig: duplicate callsign KO4BCZ-10 in line 6 of axports file
Mar 19 19:38:04 ASAwizard bash[564]: axconfig: duplicate callsign KO4BCZ-10 in line 6 of axports file
Mar 19 19:38:04 ASAwizard bash[564]: kissparms: invalid port name - udr1
Mar 19 19:38:04 ASAwizard bash[564]: ax25-upd script finished
Mar 19 19:38:04 ASAwizard systemd[1]: Started AX.25 device.
 
== status ax25 path ==
enabled
● ax25dev.path
   Loaded: loaded (/etc/systemd/system/ax25dev.path; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-03-19 19:38:02 EDT; 1 day 19h ago
 
Mar 19 19:38:02 ASAwizard systemd[1]: Started ax25dev.path.
 
== status ax25-mheardd ==
enabled
● ax25-mheardd.service - AX.25 mheard daemon
   Loaded: loaded (/etc/systemd/system/ax25-mheardd.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-03-19 19:38:04 EDT; 1 day 19h ago
 Main PID: 624 (mheardd)
    Tasks: 1 (limit: 2200)
   Memory: 204.0K
   CGroup: /system.slice/ax25-mheardd.service
           └─624 /usr/local/sbin/mheardd -f -n 150
 
Mar 19 19:38:04 ASAwizard systemd[1]: Started AX.25 mheard daemon.
Mar 19 19:38:04 ASAwizard mheardd[624]: axconfig: duplicate callsign KO4BCZ-10 in line 6 of axports file
 
== status ax25d ==
enabled
● ax25d.service - General purpose AX.25 daemon
   Loaded: loaded (/etc/systemd/system/ax25d.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-03-19 19:38:04 EDT; 1 day 19h ago
 Main PID: 625 (ax25d)
    Tasks: 1 (limit: 2200)
   Memory: 432.0K
   CGroup: /system.slice/ax25d.service
           └─625 /usr/local/sbin/ax25d -l
 
Mar 19 19:38:04 ASAwizard systemd[1]: Started General purpose AX.25 daemon.
Mar 19 19:38:04 ASAwizard ax25d[625]: axconfig: duplicate callsign KO4BCZ-10 in line 6 of axports file
Mar 19 19:38:04 ASAwizard ax25d[625]: starting
Mar 19 19:38:04 ASAwizard ax25d[625]: ax25d: UID for user 'rmsgw' is unknown, ignoring entry
Mar 19 19:38:04 ASAwizard ax25d[625]: new config file loaded successfuly
 
== netstat ax25 ==
Active AX.25 sockets
Dest       Source     Device  State        Vr/Vs    Send-Q  Recv-Q
*          KO4BCZ-0   ax0     LISTENING    000/000  0       0
*          KO4BCZ-10  ax0     LISTENING    000/000  0       0
pi@ASAwizard:~/n7nix/debug $
 

#draws #draws

Paul Noa
 

What could prevent transmitting with DRAWS Hat running NWDR15 on Pi3 B+ ?

/home/pi/n7nix/debug# ./btest.sh -P udr0
Send a message beacon
 Sent: /usr/local/sbin/beacon -c KO4BCZ-11 -d 'APUDR1 via WIDE1-1' -l -s udr0 :KO4BCZ :21 13:52:56 EDT KO4BCZ mesg_beacon test from host ASAwizard on port udr0 Seq: 20
axconfig: duplicate callsign KO4BCZ-10 in line 6 of axports file

Curiously:  mheard and listen -at return zilch!
$ mheard
Callsign   Port    Packets   Last Heard

pi@ASAwizard:~ $ sudo su
root@ASAwizard:/home/pi# listen -at
axconfig: duplicate callsign KO4BCZ-10 in line 6 of axports file
^C
root@ASAwizard:/home/pi# tail -f /var/log/direwolf/direwolf.log
Mar 21 13:56:57 ASAwizard direwolf[479]: [0.0] K6STS-11>APLIGA,WIDE2-1:/175652h2912.91N/08035.80WO092/022/A=027772 022TxC  24.40C  953.05hPa  7.46V 08S WSPR Pico balloon from Ocala,FL
Mar 21 13:56:57 ASAwizard direwolf[479]: Position with time, Original Balloon (think Ham b
Mar 21 13:56:57 ASAwizard direwolf[479]: N 29 12.9100, W 080 35.8000, 25 MPH, course 92, alt 27772 ft
Mar 21 13:56:57 ASAwizard direwolf[479]:  022TxC  24.40C  953.05hPa  7.46V 08S WSPR Pico balloon from Ocala,FL
Mar 21 14:02:54 ASAwizard direwolf[479]: [ig>tx] WA4TKG>APW290,W4NAS,WIDE2-2,qAR,W4NAS::K6STS-11 :We SEEZ'ya' !{000
Mar 21 14:06:43 ASAwizard direwolf[479]: [ig>tx] WA4TKG>APW290,W4NAS,WIDE2-2,qAR,W4NAS::K6STS-11 :We SEEZ'ya' !{000
Mar 21 14:07:15 ASAwizard direwolf[479]: [ig>tx] WA4TKG>APW290,W4NAS,WIDE2-2,qAR,W4NAS:!3019.88N/08129.06W& WinAPRS QRT @071721z
Mar 21 14:10:04 ASAwizard direwolf[479]: [ig>tx] WA4TKG>APW290,W4NAS,WIDE2-2,qAR,W4NAS::K6STS-11 :We SEEZ'ya' !{000
Mar 21 14:19:02 ASAwizard direwolf[479]: [ig>tx] WA4TKG>APW290,W4NAS,WIDE2-2,qAR,W4NAS:=3019.88N/08129.06W&PHG6176/WinAPRS 2.9.0 -FLDUVJAX     -290-<630>
Mar 21 14:41:53 ASAwizard direwolf[479]: [ig>tx] WA4TKG>APW290,W4NAS,WIDE2-2,qAR,W4NAS::K6STS-11 :We SEEZ'ya' !{000
 
netstat --ax25
Active AX.25 sockets
Dest       Source     Device  State        Vr/Vs    Send-Q  Recv-Q
*          KO4BCZ-0   ax0     LISTENING    000/000  0       0
*          KO4BCZ-10  ax0     LISTENING    000/000  0       0

$ cd n7nix/bin
pi@ASAwizard:~/n7nix/bin $ ./piver.sh
 Pi 3 Model B+, Rev 1.3, Mfg by Sony UK
 Has WiFi
pi@ASAwizard:~/n7nix/bin $ ./udrcver.sh
Found a DRAWS
 
     HAT ID EEPROM
Name:        hat
Product:     Digital Radio Amateur Work Station
Product ID:  0x0004
Product ver: 0x0206
UUID:        80a6c757-5c8f-4ba7-8d95-8ad21990dc7a
Vendor:      NW Digital Radio
pi@ASAwizard:~/n7nix/bin $ cd ~/bin
pi@ASAwizard:~/bin $ ./sndcard.sh
udrc card number line: card 1: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
udrc is sound card #1
pi@ASAwizard:~/bin $ alsa-show.sh
 ===== ALSA Controls for Radio Transmit =====
LO Driver Gain  L:[-2.00dB]     R:[-6.00dB]
PCM             L:[-6.00dB]     R:[-6.00dB]
DAC Playback PT L:[P3]          R:[P3]
LO Playback CM  [Full Chip]
 
 ===== ALSA Controls for Radio Receive =====
ADC Level       L:[8.00dB]      R:[-2.00dB]
IN1             L:[Off]         R:[Off]
IN2             L:[10 kOhm]     R:[10 kOhm]
CM              L:[10 kOhm]     R:[10 kOhm]
pi@ASAwizard:~/bin $ ax25-status
Status for direwolf.service: RUNNING and ENABLED
Status for ax25dev.service: RUNNING and ENABLED
Status for ax25dev.path: RUNNING and ENABLED
Status for ax25-mheardd.service: RUNNING and ENABLED
Status for ax25d.service: RUNNING and ENABLED
AX.25 device: ax0 successfully configured with ip: 192.168.255.2
AX.25 device: ax1 successfully configured with ip: 192.168.255.3


Re: G90 / HamMadeParts Cable / FLDigi

Michael Sharp
 

OK. Thank you...

Re: G90 / HamMadeParts Cable / FLDigi

 

Michael,

Bryan/Sales needs the information -- we are not colocated.

Thanks.

On Thu, Mar 19, 2020 at 2:07 PM Michael Sharp via Groups.Io <nexxusix=yahoo.com@groups.io> wrote:
Hello John,
Thank you for the reply. I have sent an email requesting an RMA. I do not know what my order number is at the moment. I will send you the information with my shipping address for verification.

Thank you,
-Michael



--
John D. Hays
Kingston, WA
K7VE

 

Re: G90 / HamMadeParts Cable / FLDigi

Michael Sharp
 

Hello John,
Thank you for the reply. I have sent an email requesting an RMA. I do not know what my order number is at the moment. I will send you the information with my shipping address for verification.

Thank you,
-Michael

Re: G90 / HamMadeParts Cable / FLDigi

 

Send it to:

NW Digital Radio
150 Cessna Ave
RMA<order number>
Roche Harbor WA 98250


On Mar 19, 2020, at 1:57 PM, Michael Sharp via Groups.Io <nexxusix@...> wrote:

OK. Well, this makes a lot of sense then, and probably the reason why I don’t have the proper output. If you think the wrong components have been installed, then I guess I can request an RMA at this point.

Thank you for responding to this issue.

-Michael

Re: G90 / HamMadeParts Cable / FLDigi

Michael Sharp
 

OK. Well, this makes a lot of sense then, and probably the reason why I don’t have the proper output. If you think the wrong components have been installed, then I guess I can request an RMA at this point.

Thank you for responding to this issue.

-Michael

Re: G90 / HamMadeParts Cable / FLDigi

 

Contact sales@...

On Thu, Mar 19, 2020 at 12:46 PM Michael Sharp via Groups.Io <nexxusix=yahoo.com@groups.io> wrote:
Replying to my own thread here, since I seem to be without any progress. I’m beginning to think I might have been sold a defective DRAWS Hat. When I execute the command: ./measure_deviate.sh -c right, I get only a momentary dip in output voltage from Pin 1. Please see attached oscilloscope image. Something doesn’t seem right here. I would expect a signal at this pin, perhaps a sine wave?



--
John D. Hays
Kingston, WA
K7VE

 

Re: G90 / HamMadeParts Cable / FLDigi

 

Hi Michael,

I’ve been away for a bit but I’m back in the lab.

What you are seeing is the CODEC Turning on and the DC Bias charging up the coupling Cap. At this point yes you should see a sine wave. This at least verifies the connection.

There was an issue with incorrect components being stuffed on some units. You may have one of these.

We can either try to troubleshoot it or just RMA it so I can check it out.

NW Digital Radio
150 Cessna Ave
RMA<order number>
Roche Harbor WA 98250

Thanks,
Bryan K7UDR


On Mar 19, 2020, at 12:46 PM, Michael Sharp via Groups.Io <nexxusix@...> wrote:

Replying to my own thread here, since I seem to be without any progress. I’m beginning to think I might have been sold a defective DRAWS Hat. When I execute the command: ./measure_deviate.sh -c right, I get only a momentary dip in output voltage from Pin 1. Please see attached oscilloscope image. Something doesn’t seem right here. I would expect a signal at this pin, perhaps a sine wave?

<FB8EB6B4-4BC5-4285-94BE-E2ADEB9C7360.jpeg>

Re: G90 / HamMadeParts Cable / FLDigi

Michael Sharp
 

Replying to my own thread here, since I seem to be without any progress. I’m beginning to think I might have been sold a defective DRAWS Hat. When I execute the command: ./measure_deviate.sh -c right, I get only a momentary dip in output voltage from Pin 1. Please see attached oscilloscope image. Something doesn’t seem right here. I would expect a signal at this pin, perhaps a sine wave?

Re: DRAWS Setup ans Operational Manual? #draws #setup

Bailey
 

That would be VERY helpful.

Re: DRAWS Pi HAT and GPS module for sale - $100

 

Hi Jim,

You bought the kit and haven’t received the backordered case, We’ve refunded the difference.

Thanks,
Bryan K7UDR

On Mar 15, 2020, at 7:10 AM, wa9pyh@... wrote:

I have a DRAWS Pi HAT for sale.  Included is the GPS module but no 6 pin to 6 pin DIN cable.  All work but I have lost interest in it.  I paid $200 for it and am asking $100 - a real steal !  First responder gets it.  

Jim Kocsis WA9PYH
South Bend, IN

DRAWS Pi HAT and GPS module for sale - $100

wa9pyh@...
 

I have a DRAWS Pi HAT for sale.  Included is the GPS module but no 6 pin to 6 pin DIN cable.  All work but I have lost interest in it.  I paid $200 for it and am asking $100 - a real steal !  First responder gets it.  

Jim Kocsis WA9PYH
South Bend, IN

Re: G90 / HamMadeParts Cable / FLDigi

Michael Sharp
 

Hello Basil,
I tried running the test. It seems left or right channel still does not have a signal. Being that the Raspberry Pi has at least two sound drivers on it, I made sure that the UDRC soundcard was the default system.

I also use the DRAWs Manager page and set all levels to zero, and also in the Audio driver page (Right Click on speaker icon on RPi task bar) I set all IN2 to 10k. I noticed there was both Positive and Negative, so both were set to 10k. I hope I did this correctly.

Please advise, and thank you for your help,
-Michael

Re: G90 / HamMadeParts Cable / FLDigi

Basil Gunn
 

To rule out left/right port connector problems:

https://github.com/nwdigitalradio/n7nix/tree/master/deviation

Use n7nix/deviation/measure_deviate.sh

This script will put a tone on either left or right connector.
ie.
./measure_deviate.sh -c left
./measure_deviate.sh -c right

Set alsa controls:
LO Driver Gain left & right to 0.00
IN2 left & right to 10 Kohm

Check both left & right mDin6 pin 1 for each of the measure_deviate.sh
runs. Verify that you are using pin 1 of the mDin6 connector.

/Basil n7nix

Michael Sharp <nexxusix@...> writes:

Thank you for the reply Basil,

Just to be fair, I did a fresh install, and I still have the same
results. I also have no audio of any kind coming from pin 1. My 'scope
shows nothing, but interestingly, FLDigi show the waves internally on
it's waterfall. I am only able to make the G90 respond to PTT, but
still with no signal (CW or RTTY) being transmitted from the radio. I
can certainly see received CW on the waterfall, so at least the audio
Input seems to be working properly. Here is the output that you have
requested:

73,
-Michael

pi@drawspi:~ $ udrcver.sh
Found a DRAWS

HAT ID EEPROM
Name: hat
Product: Digital Radio Amateur Work Station
Product ID: 0x0004
Product ver: 0x0106
UUID: 901ce8ed-f8a7-4ae0-bdee-810e43b5e392
Vendor: NW Digital Radio
pi@drawspi:~ $ alsa-show.sh
===== ALSA Controls for Radio Transmit =====
LO Driver Gain L:[-6.00dB] R:[-6.00dB]
PCM L:[24.00dB] R:[24.00dB]
DAC Playback PT L:[P3] R:[P3]
LO Playback CM [Full Chip]

===== ALSA Controls for Radio Receive =====
ADC Level L:[0.00dB] R:[0.00dB]
IN1 L:[Off] R:[Off]
IN2 L:[Off] R:[10 kOhm]
CM L:[10 kOhm] R:[10 kOhm]
pi@drawspi:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Subdevices: 7/7
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 IEC958/HDMI [bcm2835 IEC958/HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: ALSA [bcm2835 ALSA], device 2: bcm2835 IEC958/HDMI1 [bcm2835 IEC958/HDMI1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
Subdevices: 0/1
Subdevice #0: subdevice #0
pi@drawspi:~ $

Re: AX.25 Desktop Icons #a25

Basil Gunn
 

Larry,

Ran split_toggle.sh so that direwolf again controls both channels and
I gather that the AX25-control icon would still be useful in this mode
to start/stop AX25. Is my assumption correct?
Yes. Good assumption.

In the near future you will be able to more easily control each port
ie. on/off 1200/9600 baud.

/Basil n7nix

Re: AX.25 Desktop Icons #a25

Larry W7PAN
 

On Fri, Mar 13, 2020 at 10:22 AM, Basil Gunn wrote:
Fourth, Why aren't you using split-channel
Hadn't looked into it before.  I am now, as of 30 minutes ago, install script worked fine, status looked good, UHF/VHF radios work great, will test HF when I get an antenna back up.

Ran split_toggle.sh so that direwolf again controls both channels and I gather that the AX25-control icon would still be useful in this mode to start/stop AX25.  Is my assumption correct?

73,
Larry W7PAN

Re: AX.25 Desktop Icons #a25

Basil Gunn
 

Four points follow.

First, I am not a gui-guy in the least, so feel free to disregard
anything I have to say about this. Hoop, K9QJS, made an attractive icon &
I took my lead from him. He is a MAC-man so in my domain he had cred.

Second, Thank you Jim VA7SHG. It took my brain a while to come to the same
conclusion you mention.

Third, All my stuff is open source. Just change a script to make it do
what ever you like. I just checked in some changes to
n7nix/systemd/bin/ax25-toggle.sh to make swapping the sense of the icon
easier.

# get updated ax25-toggle.sh script

cd
cd n7nix
git pull

# put script in directory where it gets used

cd config
./bin_refresh.sh

# edit script
cd
cd bin
# edit ax25-toggle.sh script
# Change these two lines at the beginning of the script

ICON_START_FILE="/home/pi/bin/ax25-start.desktop"
ICON_STOP_FILE="/home/pi/bin/ax25-stop.desktop"

ie. do this:

ICON_STOP_FILE="/home/pi/bin/ax25-start.desktop"
ICON_START_FILE="/home/pi/bin/ax25-stop.desktop"

Fourth, Why aren't you using split-channel so that one channel is used
by direwolf for packet & the other is used by some HF program. I will
be checking in a bunch of changes in the next few days to make
split-channel & port baud rate changing a lot easier.

Everyone please stay healthy.

/Basil


Jim Erickson <jim@...> writes:

My two cents on this. I would disagree. I feel that the icon should
represent what the icon is going to do. So if it has an X on it, that
means it’s going to to stop AX25. If it doesn’t have an X, then, the
it’s going to start AX.25.

I also have conky running, which is supposed to represent the current status of things. I don’t feel that an icon is supposed to represent a status. It’s supposed to represent an action.

Just my 2 cents.
------
73,
Jim
VA7SHG - Phone
VE7TGZ/VA7TGZ - Other

On Mar 12, 2020, at 19:25, Larry W7PAN <larryvc@...> wrote:

On Wed, Feb 12, 2020 at 03:02 PM, Basil Gunn wrote:
The icon represents the action that will occur if you click on it.
Hi Basil,

I seem to concur with J P Watters as it is a bit counter intuitive. For those that don't run headless, it seems it would be better in the GUI for the icon to indicate the current state of the AX25 services. I am also using the KM4ACK conky, having the AX25-control icon with an X through it while the conky indicates that the AX25 services are active is just plain confusing. No need to change the scripts, just swapping the start/swap icons does the trick.

Larry W7PAN

Re: AX.25 Desktop Icons #a25

Hoop K9QJS
 

Works for me this way, too.  Used regularly. 

73
Hoop, K9QJS 


On Mar 13, 2020, at 9:17 AM, Jim Erickson <jim@...> wrote:

My two cents on this.  I would disagree.  I feel that the icon should represent what the icon is going to do.  So if it has an X on it, that means it’s going to to stop AX25.  If it doesn’t have an X, then, the it’s going to start AX.25.

I also have conky running, which is supposed to represent the current status of things.  I don’t feel that an icon is supposed to represent a status.  It’s supposed to represent an action.

Just my 2 cents.
------
73,
Jim
VA7SHG - Phone
VE7TGZ/VA7TGZ - Other

On Mar 12, 2020, at 19:25, Larry W7PAN <larryvc@...> wrote:

On Wed, Feb 12, 2020 at 03:02 PM, Basil Gunn wrote:
The icon represents the action that will occur if you click on it.
Hi Basil,

I seem to concur with J P Watters as it is a bit counter intuitive.  For those that don't run headless, it seems it would be better in the GUI for the icon to indicate the current state of the AX25 services.  I am also using the KM4ACK conky, having the AX25-control icon with an X through it while the conky indicates that the AX25 services are active is just plain confusing.  No need to change the scripts, just swapping the start/swap icons does the trick.

Larry W7PAN