|
David Nussdorfer <davesworld06@...>
Thanks for replying Basil.
The instructions do not call for a play -l until configuring the sound card. The instructions link you posted is the one I used twice to configure the Draws Hat on a rPi 3b. I ran the ax25-start, then ax25-status and ax25-status -d per the instructions on a fresh install and got the errors in my first post. Both attempts were connected to a FT-857d, using my wireless connection found by the ifconfig command. I used the image labeled draws-beta13.img, and received my Draws Hat on July 6th. On another rPi with a Signalink USB (without the Hat), I had no problems setting up Direwolf. Dave Nussdorfer WD4VE
|
|
|
|
Re: Using the DRAWS hat with a Raspberry Pi 4
#yaac
#replacecompass
#draws
#install
#js8call
Frank Ivan
Hi Lars
You can fix the loading of js8call and wsjtx by using sudo apt-get install ./$findname instead to sudo dpkg -I $filename. Apt will resolve the missing dependencies. It just needs to know it is working with a local file - thus the ./ prefix. I have followed this but can't get the drivers enabled. When I have dtoverlay=vc4-fkms-v3d or dtoverlay=draws,alsaname=udrc enabled in /boot/config.txt my Task Bar on the screen goes away and aplay -l says aplay: device_list:272: no soundcards found... Maybe the drivers aren't compatible with the new SOC. 73 - Frank - K0FEI
|
|
|
|
If you read the Getting Started Guide
toggle quoted messageShow quoted text
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started you will see all you need to do after the initial config is to run: ``` ./ax25-start ``` This assumes that the draws device has been enumerated. Check this by running: ``` aplay -l ``` If you do not see a udrc device from the output of the above command card 1: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [] then you need to fix that first. Running showudrc.sh will give a hint as to what the problem is. Hopefully John can help you with that as I'm away from any computer device for about a week. /Basil n7nix David Nussdorfer <davesworld06@gmail.com> writes:
Not sure how to set up the IPTables for AX.25, so I used my wireless access to my router during the config setup I used the IP address twice during the setup. Unfortunately, the information to set up ports are sparse, and I am a noob here. Below is the results:
|
|
|
|
David Nussdorfer <davesworld06@...>
Not sure how to set up the IPTables for AX.25, so I used my wireless access to my router during the config setup I used the IP address twice during the setup. Unfortunately, the information to set up ports are sparse, and I am a noob here. Below is the results:
pi@WD4VE_Draws:~ $ ax25-status
Status for direwolf.service: RUNNING and ENABLED
Status for ax25dev.service: NOT RUNNING and ENABLED
Status for ax25dev.path: RUNNING and ENABLED
Status for ax25-mheardd.service: NOT RUNNING and ENABLED
Status for ax25d.service: NOT RUNNING and ENABLED
AX.25 device: ax0 not configured
AX.25 device: ax1 not configured
pi@WD4VE_Draws:~ $ ax25-status -d
AX25 Debug Status
== failed & loaded but inactive units==
UNIT LOAD ACTIVE SUB DESCRIPTION
● ax25dev.service loaded failed failed AX.25 device
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
== direwolf ==
pid: 396
ver: Dire Wolf DEVELOPMENT version 1.6 B (Feb 27 2019)
== /proc/sys ==
core ipv4 ipv6 netfilter unix
ls: cannot access '/proc/sys/net/ax25': No such file or directory
== Network Interface ax0 & ax1 ==
Device "ax0" does not exist.
Device "ax1" does not exist.
== 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 Sun 2019-07-07 16:25:09 PDT; 42s ago
Docs: man:systemd-networkd-wait-online.service(8)
Process: 324 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exited, status=0/SUCCESS)
Main PID: 324 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/systemd-networkd-wait-online.service
Jul 07 16:25:07 WD4VE_Draws systemd-networkd-wait-online[324]: ignoring: lo
Jul 07 16:25:07 WD4VE_Draws systemd-networkd-wait-online[324]: ignoring: lo
Jul 07 16:25:07 WD4VE_Draws systemd-networkd-wait-online[324]: ignoring: lo
Jul 07 16:25:07 WD4VE_Draws systemd-networkd-wait-online[324]: ignoring: lo
Jul 07 16:25:07 WD4VE_Draws systemd-networkd-wait-online[324]: ignoring: lo
Jul 07 16:25:07 WD4VE_Draws systemd-networkd-wait-online[324]: ignoring: lo
Jul 07 16:25:07 WD4VE_Draws systemd-networkd-wait-online[324]: ignoring: lo
Jul 07 16:25:07 WD4VE_Draws systemd-networkd-wait-online[324]: ignoring: lo
Jul 07 16:25:09 WD4VE_Draws systemd-networkd-wait-online[324]: ignoring: lo
Jul 07 16:25:09 WD4VE_Draws systemd[1]: Started Wait for Network to be Confi…ed.
Hint: Some lines were ellipsized, use -l to show in full.
enabled
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2019-07-07 16:25:04 PDT; 46s ago
Docs: man:systemd-networkd.service(8)
Main PID: 309 (systemd-network)
Status: "Processing requests..."
CGroup: /system.slice/systemd-networkd.service
└─309 /lib/systemd/systemd-networkd
Jul 07 16:25:04 WD4VE_Draws systemd[1]: Starting Network Service...
Jul 07 16:25:04 WD4VE_Draws systemd-networkd[309]: Enumeration completed
Jul 07 16:25:04 WD4VE_Draws systemd[1]: Started Network Service.
Jul 07 16:25:07 WD4VE_Draws systemd-networkd[309]: wlan0: Gained carrier
Jul 07 16:25:09 WD4VE_Draws systemd-networkd[309]: 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 Sun 2019-07-07 16:25:05 PDT; 45s ago
Process: 353 ExecStartPre=/bin/rm -f /tmp/kisstnc (code=exited, status=0/SUCCESS)
Main PID: 396 (direwolf)
CGroup: /system.slice/direwolf.service
└─396 /usr/bin/direwolf -t 0 -c /etc/direwolf.conf -p
Jul 07 16:25:31 WD4VE_Draws direwolf[396]: [ig] # logresp WD4VE verified, se…2PR
Jul 07 16:25:46 WD4VE_Draws direwolf[396]: Digipeater N6EX-1 audio level = 5…___
Jul 07 16:25:46 WD4VE_Draws direwolf[396]: [0.3] WA6MHA-15>APOTU0,N6EX-1*:!3…20>
Jul 07 16:25:46 WD4VE_Draws direwolf[396]: Didn't find wind direction in for…99.
Jul 07 16:25:46 WD4VE_Draws direwolf[396]: Didn't find wind speed in form s999.
Jul 07 16:25:46 WD4VE_Draws direwolf[396]: Didn't find wind gust in form g999.
Jul 07 16:25:46 WD4VE_Draws direwolf[396]: Didn't find temperature in form t999.
Jul 07 16:25:46 WD4VE_Draws direwolf[396]: Weather Report, WEATHER Station (…ack
Jul 07 16:25:46 WD4VE_Draws direwolf[396]: N 34 11.2000, W 118 13.0200
Jul 07 16:25:46 WD4VE_Draws direwolf[396]: , " 12.6V 83F "
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: failed (Result: exit-code) since Sun 2019-07-07 16:25:06 PDT; 45s ago
Process: 493 ExecStart=/bin/bash -c /etc/ax25/ax25-upd (code=exited, status=1/FAILURE)
Main PID: 493 (code=exited, status=1/FAILURE)
Jul 07 16:25:06 WD4VE_Draws systemd[1]: Starting AX.25 device...
Jul 07 16:25:06 WD4VE_Draws bash[493]: ax25-upd: Start Port udr0 with devic…stnc
Jul 07 16:25:06 WD4VE_Draws bash[493]: Direwolf serial port ready
Jul 07 16:25:06 WD4VE_Draws bash[493]: No UDRC found, exiting
Jul 07 16:25:06 WD4VE_Draws systemd[1]: ax25dev.service: Main process exited…URE
Jul 07 16:25:06 WD4VE_Draws systemd[1]: Failed to start AX.25 device.
Jul 07 16:25:06 WD4VE_Draws systemd[1]: ax25dev.service: Unit entered failed…te.
Jul 07 16:25:06 WD4VE_Draws systemd[1]: ax25dev.service: Failed with result …e'.
Hint: Some lines were ellipsized, use -l to show in full.
-- Logs begin at Thu 2016-11-03 10:16:43 PDT, end at Sun 2019-07-07 16:25:51 PDT. --
Jul 07 16:25:05 WD4VE_Draws systemd[1]: Starting AX.25 device...
Jul 07 16:25:06 WD4VE_Draws bash[429]: ax25-upd: Start Port udr0 with device /tmp/kisstnc
Jul 07 16:25:06 WD4VE_Draws bash[429]: Direwolf serial port NOT FOUND
Jul 07 16:25:06 WD4VE_Draws systemd[1]: ax25dev.service: Main process exited, code=exited, status=1/FAILURE
Jul 07 16:25:06 WD4VE_Draws systemd[1]: Failed to start AX.25 device.
Jul 07 16:25:06 WD4VE_Draws systemd[1]: ax25dev.service: Unit entered failed state.
Jul 07 16:25:06 WD4VE_Draws systemd[1]: ax25dev.service: Failed with result 'exit-code'.
Jul 07 16:25:06 WD4VE_Draws systemd[1]: Starting AX.25 device...
Jul 07 16:25:06 WD4VE_Draws bash[493]: ax25-upd: Start Port udr0 with device /tmp/kisstnc
Jul 07 16:25:06 WD4VE_Draws bash[493]: Direwolf serial port ready
Jul 07 16:25:06 WD4VE_Draws bash[493]: No UDRC found, exiting
Jul 07 16:25:06 WD4VE_Draws systemd[1]: ax25dev.service: Main process exited, code=exited, status=1/FAILURE
Jul 07 16:25:06 WD4VE_Draws systemd[1]: Failed to start AX.25 device.
Jul 07 16:25:06 WD4VE_Draws systemd[1]: ax25dev.service: Unit entered failed state.
Jul 07 16:25:06 WD4VE_Draws systemd[1]: ax25dev.service: Failed with result 'exit-code'.
== status ax25 path ==
enabled
● ax25dev.path
Loaded: loaded (/etc/systemd/system/ax25dev.path; enabled; vendor preset: enabled)
Active: active (waiting) since Sun 2019-07-07 16:25:05 PDT; 46s ago
Jul 07 16:25:05 WD4VE_Draws 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: inactive (dead)
== status ax25d ==
enabled
● ax25d.service - General purpose AX.25 daemon
Loaded: loaded (/etc/systemd/system/ax25d.service; enabled; vendor preset: enabled)
Active: inactive (dead)
== netstat ax25 ==
Active AX.25 sockets
Dest Source Device State Vr/Vs Send-Q Recv-Q
|
|
|
|
Re: What am I missing?
Thanks John.
|
|
|
|
Re: What am I missing?
I don't have an 857 but the settings for 8x7 radios seem to be about the same. In DRAWS™ Manager, try the default settings for the FT-817 and make small changes from there.
On Sun, Jul 7, 2019 at 10:12 AM km4ack <jason.oleham@...> wrote: Running JS8Call and monitoring on a station in the adjacent town via VNC. Remote station is ~15 miles away. Operating on 40M. --
John D. Hays Kingston, WA K7VE
|
|
|
|
What am I missing?
Running JS8Call and monitoring on a station in the adjacent town via VNC. Remote station is ~15 miles away. Operating on 40M.
Beta13 Yaesu 857D Before I moved to the DRAWS unit, I ran a test with my primary pi with signalink. Remote station shows -03db SNR. Now for the DRAWS unit: If I turn the analog/digital gain down to where there is little/no ALC showing on the meter, nothing is heard on the remote station. I have to turn up the analog/digital gain to where ALC is half before being heard (-16db SNR) and then there is splatter all over the band. I have tried moving the sliders all over in DRAWS manager and playing with digital gain on the radio itself. All to no avail. There has to be something I either don't know or am overlooking. I have never seen this with any other soundcard that I have worked with. What am I missing? 73, Jason KM4ACK
|
|
|
|
Michael Starling
Be aware that the 2.1.0 rc7 version does not now transmit data on my Mac. Apparently has some built-in switch to turn it off during some periods. Version 2.0.1 does work on the Mac and the 3B+ under Stretch..
|
|
|
|
Richard Waller <rewaller@...>
Have you looked at the output settings in draws manager and tried to adjust those? Have you confirmed that the audio settings are correct for transmit in the wsjt-x program? Lastly, have you adjusted the power output slider on the right side of the wsjt-x screen? Rick Ka4ohm.
toggle quoted messageShow quoted text
On Jul 6, 2019, at 10:05 PM, Matt N7ROO <n7roo@...> wrote:
|
|
|
|
Hi Matt. Make sure the radio is getting the input from the 6-pin data port. I don't have a FT-891, but look into mode. Could be called USB-D, DIG or similar. Try whistling into the mic while WSJT-X keys your radio and look at the power meter then. Karl
|
|
|
|
Hello,
I've been trying to set up my DRAWS and FT-891 to use FT8 via WSJT-X. I've been following the videos and settings from Julian and Steve, and can receive messages ok, however whenever I transmit the radio lights up but the power output meter never changes. Almost as if there is no data aside from the PTT notification being send from the DRAWS unit. If anyone has some insight on what may be causing this please let me know. Happy to run any commands / dump console outputs if it will help. 73 Matt N7ROO
|
|
|
|
Re: Raspberry Pi 4
LA4RHA / Lars
I have amended the document with the comments from John regarding the file. Have also added some comments about installing DRAWS Manager ("Follow the instructions at...") /Lars - LA4RHA
|
|
|
|
Re: Raspberry Pi 4
LA4RHA / Lars
Thank you for the heads up, Basil !
|
|
|
|
Re: Raspberry Pi 4
One additional item, add the attached file to /etc/sensors.d And don't forget https://github.com/nwdigitalradio/draws-manager
On Fri, Jul 5, 2019 at 9:20 AM Basil Gunn <basil@...> wrote:
--
John D. Hays Kingston, WA K7VE
|
|
|
|
Re: Raspberry Pi 4
While Anna's tlv320aic32x4 driver for DRAWS is in Raspbian kernel
toggle quoted messageShow quoted text
4.19.50, all of her i2c timer patches are not yet in this kernel. From Anna: Check this directory for a clock entry marked as i2c_div in the output /sys/kernel/debug/clk/clk_summary I've done some preliminary testing with Raspbian 4.19.50 as well and so far I haven't come across anything but be aware that all of Anna's recent patches have not made it into the current Raspbian kernel. /Basil n7nix LA9KOA - Karl <oyoygard@gmail.com> writes:
Annaliese's driver is included in kernel 4.19.50 that is shipped with Rasbian Buster.
|
|
|
|
Re: Using the DRAWS hat with a Raspberry Pi 4
#yaac
#replacecompass
#draws
#install
#js8call
Lars,
Great work. To your question, yes you should build fldigi and flrig from source. John
|
|
|
|
Re: Raspberry Pi 4
JT Croteau <jt.tobit@...>
Thanks for this early work Lars and Karl. I've been trying to decide whether to go with the 4 now or get a e for my new build. This early work is encouraging. N1ESE
On Fri, Jul 5, 2019, 09:20 LA9KOA - Karl <oyoygard@...> wrote:
|
|
|
|
Re: Raspberry Pi 4
Annaliese's driver is included in kernel 4.19.50 that is shipped with Rasbian Buster. https://nw-digital-radio.groups.io/g/udrc/message/3641 Karl
|
|
|
|
Using the DRAWS hat with a Raspberry Pi 4
#yaac
#replacecompass
#draws
#install
#js8call
LA4RHA / Lars
Hi all, Not sure if this is the correct group, mods: please feel free to move this to another group if it belongs there ! FLDigi is installed, but not yet tested If you want to set this up yourselves, our notes/worklog is here: https://docs.google.com/document/d/1Wq-jNLXYuREIOcr0OVu1FxPNhDFGuCOu6dX5OQ2BVxA/edit?usp=sharing We appreciate any comments, both here, and in the google document 73, de
|
|
|
|
Re: piardopc?
I had piardopc working with arim on the original UDRC & UDRC II hats
about a year ago. Should work with DRAWS hat as well. Set you gpio depending on which mDin6 connector you are using. For a DRAWS hat left = gpio 12, right = gpio 23. Make sure that direwolf is NOT running. Command line I used: ./piardopc 8515 plughw:1,0 plughw:1,0 -p GPIO=23 Added this to .asoundrc pcm.ARDOP { type rate slave { pcm "hw:1,0" rate 12000 } } I found that using arim was useful in getting piardopc going because of its debug facilities. https://www.whitemesa.net/arim/arim.html /Basil n7nix
|
|
|