Date   

Re: GPIO Pass through #draws

 

Ed,

There is no current plan for stacked DRAWS boards.

Many of the GPIO pins are dedicated and not available for stacked cards.  However, the DRAWS provides 2 four wire ports (Mini Din-6) and 4 USB ports (plus the 8 pin GPIO brought off the board to the exterior of a case) which allows for a wide variety of configurations. 

Within direwolf, you can configure the 2 radio ports to provide independent 1200 baud and 9600 baud connections.  As we get better support for virtual audio ports, more applications can use these two ports independently as well as running multiple packet modem data rates on a single port.

Because of the Raspberry Pi networking capabilities, building up larger arrays of applications are possible over Ethernet/WiFi/... using multiple Pi + DRAWS.


On Tue, Jan 15, 2019 at 11:25 AM Ed Bloom, KD9FRQ <ewbloom@...> wrote:
Are there plans to have the DRAWS use pass-through GPIO pins so two units can be stacked?  This would allow 1200 & 9600 packet as well as WinMor and ARDOP to all run from one control point.

Just wondering as I am starting work though getting my station active using DRAWS instead of a PC or PI-TNC.
_._,_



--


John D. Hays
Director

  


GPIO Pass through #draws

Ed Bloom, KD9FRQ
 

Are there plans to have the DRAWS use pass-through GPIO pins so two units can be stacked?  This would allow 1200 & 9600 packet as well as WinMor and ARDOP to all run from one control point.

Just wondering as I am starting work though getting my station active using DRAWS instead of a PC or PI-TNC.


Mike - KB0FX
 

Fellow DRAWs Early Adopters,

I am happy to report I am making progress with getting the DRAWS card to work with the Kenwood TS-440S on HF digital modes. I have JS8Call & WSJT-X FT8 Mode decoding signals. I made an adapter cable with a 6 Pin DIN cable and a RJ-45 Jack Block that allows me to use my Signalink USB 13 pin DIN to RJ-45 Plug adapter cable to connect to the DRAWS Pi-Hat. 

I have included a picture below. Once I get everything working I will post the color code and pin out. 

73 - Mike - KB0FX


Re: GPS not working #gps #gpsd

Basil Gunn
 

Please send me the output of showudrc.sh
Look for it in your local bin directory
cd
cd bin
./showudrc.sh

Also send me the console output of:

ls -al /dev/ttySC* /dev/pps*

- Did you follow these instructions?
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started

- Which image are you using: BETA7?

/Basil


oe8bck <christof.bodner@...> writes:

Hi,

I got my DRAWS last week after waiting 4 weeks on customs. Today I wanted to check XAstir, but GPS is not working:
---
pi@draws:~ $ sudo service gpsd status
● gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2019-01-14 21:19:10 CET; 37s ago
Process: 1282 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
Main PID: 1283 (gpsd)
CGroup: /system.slice/gpsd.service
└─1283 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0

Jan 14 21:19:11 draws gpsd[1283]: gpsd:ERROR: SER: read-only device open of /dev/pps0 failed: No such file or directory
Jan 14 21:19:11 draws gpsd[1283]: gpsd:ERROR: initial GPS device /dev/pps0 open failed


GPS not working #gps #gpsd

oe8bck
 

Hi,

I got my DRAWS last week after waiting 4 weeks on customs. Today I wanted to check XAstir, but GPS is not working:
---
pi@draws:~ $ sudo service gpsd status
● gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-01-14 21:19:10 CET; 37s ago
  Process: 1282 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
 Main PID: 1283 (gpsd)
   CGroup: /system.slice/gpsd.service
           └─1283 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0

Jan 14 21:19:11 draws gpsd[1283]: gpsd:ERROR: SER: read-only device open of /dev/pps0 failed: No such file or directory
Jan 14 21:19:11 draws gpsd[1283]: gpsd:ERROR: initial GPS device /dev/pps0 open failed
Jan 14 21:19:11 draws gpsd[1283]: gpsd:ERROR: SER: device open of /dev/ttySC0 failed: No such file or directory - retrying read-only
Jan 14 21:19:11 draws gpsd[1283]: gpsd:ERROR: SER: read-only device open of /dev/ttySC0 failed: No such file or directory
Jan 14 21:19:11 draws gpsd[1283]: gpsd:ERROR: /dev/ttySC0: device activation failed.
Jan 14 21:19:11 draws gpsd[1283]: gpsd:ERROR: /dev/ttySC0: activation failed, freeing device
Jan 14 21:19:11 draws gpsd[1283]: gpsd:ERROR: SER: device open of /dev/pps0 failed: No such file or directory - retrying read-only
Jan 14 21:19:11 draws gpsd[1283]: gpsd:ERROR: SER: read-only device open of /dev/pps0 failed: No such file or directory
Jan 14 21:19:11 draws gpsd[1283]: gpsd:ERROR: /dev/pps0: device activation failed.
Jan 14 21:19:11 draws gpsd[1283]: gpsd:ERROR: /dev/pps0: activation failed, freeing device
pi@draws:~ $ lsmod
Module                  Size  Used by
fuse                  110592  3
rfcomm                 49152  4
bnep                   20480  2
hci_uart               36864  1
btbcm                  16384  1 hci_uart
serdev                 20480  1 hci_uart
bluetooth             368640  29 hci_uart,bnep,btbcm,rfcomm
ecdh_generic           28672  1 bluetooth
xt_tcpudp              16384  4
ip6table_filter        16384  0
ip6_tables             24576  1 ip6table_filter
iptable_filter         16384  1
brcmfmac              307200  0
brcmutil               16384  1 brcmfmac
cfg80211              573440  1 brcmfmac
rfkill                 28672  6 bluetooth,cfg80211
snd_bcm2835            32768  1
snd_pcm                98304  1 snd_bcm2835
snd_timer              32768  1 snd_pcm
snd                    69632  5 snd_timer,snd_bcm2835,snd_pcm
uio_pdrv_genirq        16384  0
fixed                  16384  0
uio                    20480  1 uio_pdrv_genirq
ax25                   69632  0
i2c_dev                16384  0
ip_tables              24576  1 iptable_filter
x_tables               32768  5 ip_tables,iptable_filter,xt_tcpudp,ip6table_filter,ip6_tables
ipv6                  425984  38
---
Any idea what's wrong? I have just the USB plug as power connector. Do I need to attach a 12V supply?

73 de OE8BCK Christof


Re: Beta7 release announcement

Art - KC7SDA
 

awesome! after most of the bugs get worked out I'll do the same thing with my udrc and update everyone up here to the new image =)


Re: Beta7 release announcement

Bernard f6bvp / ai7bg
 

By the way, I wrote a patch for direwolf 1.5-1.6 to give the choice of
channel for sending calibration test signal (option -x).
This may be useful for the default is only on channel 0 that is right
connector (HD15) on UDRC II which is not very convenient when you
prefere to use Din6 wiring for the radio set. With DRAW hat you may also
choose to send calibration signal for level adjustment either on channel
0 or channel 1.

Basil, if interested by this patch I wrote a Direwolf issue here :
https://github.com/wb2osz/direwolf/issues/184
Patch can be downloaded from file :
https://github.com/wb2osz/direwolf/files/2703361/direwolf.patch2.txt

Bernard

Le 13/01/2019 à 00:46, Basil Gunn a écrit :

Art - KC7SDA <@nouse4anick> writes:

semi random question: does this beta work with the original udrc 2? I
think I really really need to update it to the newest drivers and
software.
I have tested the images with a UDRC II. Change /boot/config.txt
from: dtoverlay=draws
to: dtoverlay=udrc

Note *for a UDRC II* that the left & right connectors are swapped from a
DRAWS HAT ie. right connector(HD 15) is chan 0 & uses gpio 12 for PTT,
left connector (mDin6) is chan 1 & uses gpio 23

/Basil


Re: Beta7 release announcement

Basil Gunn
 

Art - KC7SDA <@nouse4anick> writes:

semi random question: does this beta work with the original udrc 2? I
think I really really need to update it to the newest drivers and
software.
I have tested the images with a UDRC II. Change /boot/config.txt
from: dtoverlay=draws
to: dtoverlay=udrc

Note *for a UDRC II* that the left & right connectors are swapped from a
DRAWS HAT ie. right connector(HD 15) is chan 0 & uses gpio 12 for PTT,
left connector (mDin6) is chan 1 & uses gpio 23

/Basil


Re: Beta7 release announcement

Art - KC7SDA
 

semi random question: does this beta work with the original udrc 2? I think I really really need to update it to the newest drivers and software.


Re: Beta7 release announcement

Art - KC7SDA
 

currently testing the beta, so far so good, everything is working great!


Re: JS8Call #js8call

Art - KC7SDA
 

so I did join the js8call group and told them that they need a gpio, the response i got back was to write a script and they might add it later

so the last couple of versions of fldigi had it in there, I think the repository version is too old but the current beta image here has the current build. here's my build script, it should work on any linux box but I did this specifically for this project, you can change the version number to get other versions, I have an update script that I'm working on that will update the fldigi suite (note you need to uncomment the last line in /etc/apt/sources.list to enable source dependency)

sudo apt-get update
sudo apt-get upgrade
#grab any dep we forget:
    sudo apt-get build-dep fldigi -y
    # from http://www.kk5jy.net/fldigi-build/, make sure they are installed
    sudo apt-get install libfltk1.3-dev -y
    sudo apt-get install libjpeg9-dev -y
    sudo apt-get install libxft-dev -y
    sudo apt-get install libxinerama-dev -y
    sudo apt-get install libxcursor-dev -y
    sudo apt-get install libsndfile1-dev -y
    sudo apt-get install libsamplerate0-dev -y
    sudo apt-get install portaudio19-dev -y
    sudo apt-get install libusb-1.0-0-dev -y
    sudo apt-get install libpulse-dev -y
    cd ~
    wget https://sourceforge.net/projects/fldigi/files/fldigi/fldigi-4.0.18.tar.gz
    tar -zxvsf fldigi-4.0.18.tar.gz
    cd fldigi-4.0.18
    ./configure
    make
    sudo make install
    cp data/fldigi.desktop ~/Desktop/
    cp data/flarq.desktop ~/Desktop/

remember you don't have to do this for the current beta, only do this if you are doing it from scratch (in which case you might want to look at my scripts at github.com/nouse4anick/DRAWS)


Re: one stop shop for sound level questions #documentation #draws #beta

Art - KC7SDA
 

as an fyi, I just finished playing around with the verify scripts and tried setting alsa with 'setalsa-default.sh'. right out of the box it works on my boafeng ht after setting the audio input/output in fldigi. I think this will work with most ht's and is a good starting point for base/mobile rigs. If it warms up this weekend I'll set up my hf rig and play around with the sound levels for an ic-718.

Full soundcard/rig settings for fldigi:
for channel 1 (the mini din next to the gps):
- nothing checked in right channel dialog (no swap and no audio on both left and right)
- gpio tab under rig control use bcm 12, 23 is the right mini din.


Re: JS8Call #js8call

K7AZJ <jdawgaz@...>
 

Art.

Did you add an issue to the JS8call issue tracker? I think after v1 Jordan might do something.

Be sure to mention what fldigi did.

What version of fldigi?
And do we have to build it?

Jerry
K7AZJ


On Sat, Jan 12, 2019, 9:40 AM Art - KC7SDA <nouse4anick@...> wrote:
So I just took a quick look at the new update... the only way to do ptt is to write a command file to key the transmitter (I'm not focusing on that right now but i'm sure a script wouldn't be too hard to do)... its a shame they don't do what fldigi did and implement the gpio as check boxes (or even a drop down list)


Re: JS8Call #js8call

Art - KC7SDA
 

So I just took a quick look at the new update... the only way to do ptt is to write a command file to key the transmitter (I'm not focusing on that right now but i'm sure a script wouldn't be too hard to do)... its a shame they don't do what fldigi did and implement the gpio as check boxes (or even a drop down list)


Re: one stop shop for sound level questions #documentation #draws #beta

Art - KC7SDA
 

factory resets are good, however most HT's don't need them as there is little audio adjustment aside from the volume control.

I guess what I'm after is more of to see how people are adjusting them an if there is a common range (high/low/median) that maybe we can come up with something closer that will work with 80% of rigs. I ran the settings at one point and while it received fine i got no audio out for tx until i changed some of the resistor settings (which I think was wrong, but I don't understand enough about the audio chip to make the call on the right and wrong way to set it up).

this will also help assess how much documentation is needed to prevent 'wrong' configurations (ie driving something way too hard when it doesn't need to be), and maybe to help people understand which slide (or value) changes what and why.


Re: Winlink Gateway

Ed Bloom, KD9FRQ
 

Julie,
 
Thank you. That looks nice.
 
Please contact me directly at the address below.  I would like to better understand how some of the other radios are connected via USB (sound modems, USB-serial cables, etc).
 
Ed Bloom, KF9FRQ
ewbloom@...
Sent from Webmail access

-----Original Message-----
From: Julie McGrew via Groups.Io <juliemcgrew@...>
To: udrc <udrc@nw-digital-radio.groups.io>
Sent: Fri, Jan 11, 2019 11:39 am
Subject: Re: [udrc] Winlink Gateway

Hi Ed,

Here's a link to the photo you requested.

https://www.dropbox.com/s/k4z74iro1qkjujp/pilinbpq_rms_gateway.jpeg?dl=0

73,
julie


Re: Winlink Gateway

Julie McGrew
 

Hi Ed,

Here's a link to the photo you requested.

https://www.dropbox.com/s/k4z74iro1qkjujp/pilinbpq_rms_gateway.jpeg?dl=0

73,
julie


Re: #BETA7 performance report #beta7 #config #ft-817 #ic-7000

Jack Spitznagel
 

Hi Tim,

I have played with all of the suggestions you made and many others... I don’t run the 7000 on packet or in digi modes with the Mic connected... period. That is terrible practice with almost any rig.

Point one: Direwolf/Xastir works with the setting in the current Beta... closed issue. I have posted the settings that I have tried and the ones that work in packet in many posts. The ones in the alsamixer setup script are similar to ones I got to work for packet.

I have been struggling with this radio since the DRAWS board was shipped... before the first beta in late Nov/early December. You may not have been following the list since then... if so sorry for wasting your time with a recap of 20+ emails.

Using Betas up thru #5, I had the problem of *USB* overdrive in both the HF digital apps (fldigi and wsjt-x). With Beta #6, fldigi was still having the overdrive issue, but wsjt-x suddenly would not drive the transceiver to any appreciable power. Now in Beta #7, neither app will drive the rig to power. The alsamixer driver system was updated to add the PTM settings at Beta 6.

My control device, a SignaLink, consistently performs properly with the 7000 and the drive level can be adjusted for full power with no ALC. The 7000 is working properly.

When the drive was working, I was never able to find an adjustment point where the DRAWS could be adjusted to produce power with any significant reduction of ALC in SSB mode. I did try reducing Mic gain on the 7000 which did not seem to do anything. What was consistently observed at settings low enough to be in the 100mV range was that the DRAWS produced a noise floor high enough to prevent the level of the TX from dropping any farther. Essentially the tone level fell as noise level came up.

Because of the changes in symptoms with Beta 6 & 7, I am stymied... Basil has found a 7000 for Bryan to work with and I am going to give it a rest. Hopefully they will be able to work it out.

If you want any more background, follow the #ic7000 thread back to early December.

Jack, KD4IZ

On Jan 10, 2019, at 21:59, Tim Ciesluk via Groups.Io <cetpctech=yahoo.com@groups.io> wrote:

I don’t know if you have a way to measure the voltage coming out of DRAWS to compare Direwolf and Fldigi. I would suppose they would be the same. Have you tried adjusting the Mic gain? As odd as it may seem, the mic could be tied to the data port. I was reading the manual for the WMR P&P section on adjusting audio levels into the radio and it mentions this happens in some cases. Default gain is 50 and I saw that mine was set down to 30. Do you see changes with ALC when setting this very low? I don’t remember if you said what output level worked good for Direwolf.
Could you share your settings like power and in what position you placed RF gain/SQL knob?I would like to try to put DRAWS voltage to the minimum recommended level for pocket and use Mic gain control if I can get the chance. I’d also completely disconnect the microphone if this gain setting made any changes. Wish me luck.

Tim - KU1G

On Jan 9, 2019, at 8:23 PM, Jack Spitznagel <@flyingfrawg> wrote:

Thanks for sending that photo. I missed that in the packet section. So in my testing, that seems to be the case for packet on FM (APRS via direwolf) which has been working. Unfortunately when DRAWS TX signal has been at that level it was overdriving the rig in USB using fldigi or wsjt-x.
Jack
On Jan 9, 2019, at 20:34, Tim Ciesluk via Groups.Io <cetpctech=yahoo.com@groups.io> wrote:

Hi Basil and Jack,

Let me preface by saying that I am very interested in the progress you are
making as I too have an IC-7000. I wish I had time to test but we just had a
newborn arrive in December keeping us very busy. You caught me by surprise
saying you’re using the ACC port with FLDigi. I remember some years ago
using Fldigi for HF with a West Mountain Plug&Play attached to the data port
on an IC-7000. The radio was basically default settings and in SSB mode. I
don’t recall anything special being necessary on the radio for settings.
Just to be sure the drive (pc sound card output) wasn’t too much for the
radio. This setup worked modes like JT65, PSK31, and Olivia. If I find any
time, I will try to find out more details about that setup. I want to attach
some details from the user manual regarding voltages for the data port and
describes a way to test the input from the TNC that may be useful.

I hope I’m adding to the conversation. Please let me know if I’m not. I’d
really like to see this succeed.

73,
Tim - KU1G







<image2.jpeg>
<image3.jpeg>

--
J Spitznagel
Science River LLC
KD4IZ


--
J Spitznagel
Science River LLC
KD4IZ


Re: FT891, FT817, Audio Levels, I/O Fail , and Documentation #draws #ft817 #hfmodes

Julian OH8STN <julian@...>
 

Hello everyone.
Unfortunately life happens, so I'm a couple of weeks behind the rest of you. Reading through all the threads, it's awesome to see all the work done by the  NWDR team.
I'm going to jump straight to Beta 7. Let's see if we can pop out a few more viral videos.
73
Julian oh8stn 

Julian OH8STN
www.oh8stn.org
www.youtube.com/c/OH8STN


Re: PC-ALE port to DRAWS?

Julian OH8STN <julian@...>
 

Unless something has changed, PC-ALE is (sadly) Windows only and not open source. So it won't run on a Raspberry Pi. 

Julian OH8STN
www.oh8stn.org
www.youtube.com/c/OH8STN

On 8 Jan 2019 06:57, Doug Yuill <diverdoug@...> wrote:
Is anyone considering a port of PC-ALE to DRAWS? If so, I'm available to help with the testing and validation! 

de VE3OCU in Smith Falls Ontario