Date   

Re: Building Fldigi

 


Use a converter cable for your rig (CI-V, CAT, etc.) plugged into one of the USB ports on the Pi.
_._,

>>

... And encourage the NWDR folks to add the 3 or so resistors needed to DRAWS on the next rev so it will also have the CTT/CI-V cable functionality.

Bill, wa7nwp



Building Fldigi and Flrig for DRAWS #fldigi #draws

 

While the beta image is being prepared, I recommend the directions  at http://www.kk5jy.net/fldigi-build/ for building fldigi and flrig.  I have done this build and it works fine on the left DIN-6 port.

Use a converter cable for your rig (CI-V, CAT, etc.) plugged into one of the USB ports on the Pi.


Re: DRAWS downloadable Image? #setup #compassimage #draws #earlyadopters

 



On Thu, Nov 29, 2018 at 9:00 PM Brian Badger <brian@...> wrote:
The muting is great for packet but once we get fldigi working I’m going to need that RX audio to find signals.  If we can’t do it in software then I’ll have to savage one of these cables to inline a switch.

I find the waterfall on fldigi and wsjt-x work better than my ears for finding signals.

All in all, very happy with draws so far.  The only complaint I have is the power connector.  Hopefully once I get a case built I’ll be able to mount a proper one on it (5mm barrel or powerpole)

The idea of the pigtail is to be able to put whatever you want on the other end.  The 9-15 VDC input to the pigtail is the better way to power the DRAWS Hat and Pi, but they can also be powered off the 5.1 VDC 2.5+ A microUSB port on the Pi.

 
Brian N0KZ



--


John D. Hays
Edmonds, WA
K7VE

   


Re: DRAWS downloadable Image? #setup #compassimage #draws #earlyadopters

 



On Thu, Nov 29, 2018 at 8:27 PM Brian Badger <brian@...> wrote:
I have Direwolf running now, but I couldn't deduce which of these three parameters was "input sensitivity" -- instead I changed the impedance from 10 kOhm to 20kOhm to get the levels right.  What is the recommended procedure?  

Please leave the 10 KOhm settings in place.  ADC (Analog Digital) is the control for setting the level from the receiver.  In packet with Direwolf, you can tweak it until received signals are indicated around level 50 (using a reliable transmit source, a lot of people run their TNCs/Digipeaters hot).  The procedure is similar to what is described here https://nw-digital-radio.groups.io/g/udrc/wiki/UDRC%E2%84%A2-For-Simplex-Hotspots-and-Converted-Analog-Repeaters#Troubleshooting

The example ~/my-setup-script.sh (see above link) should be very close for an FT-8x7


--


John D. Hays
Edmonds, WA
K7VE

   


Re: DRAWS downloadable Image? #setup #compassimage #draws #earlyadopters

Brian Badger
 

The muting is great for packet but once we get fldigi working I’m going to need that RX audio to find signals.  If we can’t do it in software then I’ll have to savage one of these cables to inline a switch.

All in all, very happy with draws so far.  The only complaint I have is the power connector.  Hopefully once I get a case built I’ll be able to mount a proper one on it (5mm barrel or powerpole)

Brian N0KZ


On Nov 29, 2018, at 9:36 PM, Jack Spitznagel <kd4iz@...> wrote:

Hi Brian,

 

My testbed FT-817 does the same muting (but I like it). I am listening to transmitted audio with a TH D74A. DRAWS receive audio was basically fine after I ran the bash script for setting up the soundcard. The system has run flawlessly with Xastir all evening. DRAWS makes the 817 key up and make noise (with the 9600 port volume at 70), but I still need to adjust the DRAWS transmit audio level and change the timing parameter (hangtime, etc) so my other APRS gear will decode it… something for tomorrow.

 

KD4IZ

Jack Spitznagel

FM19oo

 

 

 

From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of Brian Badger
Sent: Thursday, November 29, 2018 23:28
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] DRAWS downloadable Image? #draws #earlyadopters #setup #compassimage

 

I have Direwolf running now, but I couldn't deduce which of these three parameters was "input sensitivity" -- instead I changed the impedance from 10 kOhm to 20kOhm to get the levels right.  What is the recommended procedure?  

Is there any way to set these impedance values in software to get a Yaesu to stop muting audio?  I have no idea what pin causes a Yaesu to decide it is no longer going to output audio to the speaker, but I can't use it like this.  If I keep plugging and unplugging the mini-din I'm going to break the connector off the board.

Is there a way instead to enable the Raspberry Pi onboard audio and route the RX audio via mixer to it?
--
Brian N0KZ


--
J Spitznagel
Science River LLC
KD4IZ


Re: DRAWS downloadable Image? #setup #compassimage #draws #earlyadopters

Jack Spitznagel
 

Hi Brian,

 

My testbed FT-817 does the same muting (but I like it). I am listening to transmitted audio with a TH D74A. DRAWS receive audio was basically fine after I ran the bash script for setting up the soundcard. The system has run flawlessly with Xastir all evening. DRAWS makes the 817 key up and make noise (with the 9600 port volume at 70), but I still need to adjust the DRAWS transmit audio level and change the timing parameter (hangtime, etc) so my other APRS gear will decode it… something for tomorrow.

 

KD4IZ

Jack Spitznagel

FM19oo

 

 

 

From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of Brian Badger
Sent: Thursday, November 29, 2018 23:28
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] DRAWS downloadable Image? #draws #earlyadopters #setup #compassimage

 

I have Direwolf running now, but I couldn't deduce which of these three parameters was "input sensitivity" -- instead I changed the impedance from 10 kOhm to 20kOhm to get the levels right.  What is the recommended procedure?  

Is there any way to set these impedance values in software to get a Yaesu to stop muting audio?  I have no idea what pin causes a Yaesu to decide it is no longer going to output audio to the speaker, but I can't use it like this.  If I keep plugging and unplugging the mini-din I'm going to break the connector off the board.

Is there a way instead to enable the Raspberry Pi onboard audio and route the RX audio via mixer to it?
--
Brian N0KZ


--
J Spitznagel
Science River LLC
KD4IZ


Re: DRAWS downloadable Image? #setup #compassimage #draws #earlyadopters

Brian Badger
 

I have Direwolf running now, but I couldn't deduce which of these three parameters was "input sensitivity" -- instead I changed the impedance from 10 kOhm to 20kOhm to get the levels right.  What is the recommended procedure?  

Is there any way to set these impedance values in software to get a Yaesu to stop muting audio?  I have no idea what pin causes a Yaesu to decide it is no longer going to output audio to the speaker, but I can't use it like this.  If I keep plugging and unplugging the mini-din I'm going to break the connector off the board.

Is there a way instead to enable the Raspberry Pi onboard audio and route the RX audio via mixer to it?
--
Brian N0KZ


Re: DRAWS downloadable Image? #setup #compassimage #draws #earlyadopters

 

On Fri, Nov 23, 2018 at 09:40 PM, John D Hays - K7VE wrote:
sset 'ADC Level' -2.0dB
sset 'LO Driver Gain' 0dB
sset 'PCM' 0.0dB
When you create the script (put in ~/draws-setup.sh or similar) then you can execute it anytime you want to set values for the sound chip.  If you find you need to modify the 3 above values in alsamixer, just edit them in the shell script and keep for your radio.


Setting up Xastir for DRAWS™ #draws #direwolf #compass #xastir

Jack Spitznagel
 

All DRAWS owners,

 

Setting up xastir for the DRAWS board was not a slam dunk! This message is longish but my discoveries and explanations here may help if you are relatively Raspbian naieve. If you hate reading and want to risk it,  just “fly the doghouse”, skip to the short “how to” section at the bottom. Warning – this was my solution, you may or may not find it works for you.

 

Below you will find a clip that may or may not help someone new to DRAWS getting xastir configured. I was able to bring the Compass install up and change it as in John’s instructions so the DRAWS board features are in the device list with the GPS and PPS0 outputs available. Also quickly got DireWolf working in receive with a venerable FT-817 (original model, not ND). I am playing with transmit next… but I had trouble getting xastir installed, configured, and working. I thought a “sudo apt-get install” approach would be a cakewalk… but it wasn’t. Here is the outcome as reported in a thread in the Compass subgroup:

Nota Bene: Please Please Please remember that NW Digital is not the author of the application software that you want to install on Compass for your new DRAWS/RPi system. You will need to 1) go to the specific application website/wiki to understand and perform an install 2) ask the authors/contributors on their email support groups if 1) does not help you.

I must give some explanation for what came before success finally happened: xastir was not installing properly with the usual tools – in addition, the online info about xastir on Raspbian was most unhelpful. I had to flash a new copy of Compass after doing what the when the online instructions said to do: that is to use the “startx” command to bring up the X environment, period. It did not say “if you are in the CLI”. I was already in the GUI. Running startx in a terminal window bombed the OS and left it stuck asking for my log in repeatedly, even after a reboot. My password would not work.  I sent the issue to the NW Digital Compass group where after some discussion, John reminded me that the Compass/Stretch GUI is an X environment. My “X problem” was really just a PEBCAK situation.

------ snip from the Compass subgroup thread “Compass image 2018-11-18 X issue on #raspberrypi”  -----

- Learning some obvious points and walking the following steps has now got xastir “mostly working”:

  1. When using the GUI, “startx” already is done for you. Thanks John! I had not remembered that the GUI is X.<headsmack> I built a new Compass install and got the Dire Wolf baying again.
  2. After attempting xastir installs using both the graphical “Add/Remove software” app and the command line “sudo apt-get install xastir” – I could not find any proper trace of xastir files where they should be and nothing was added to the menu. I conclude those installations were botched by something in the package install tool or associated scripts even though I received no apparent error.
  3. I then “removed” xastir using the Add/Remove app and reinstalled using Synaptic Package Manager (this needs to be installed). This time I had files and menu entries… BUT (always a but…)

The menu entries point to a xastir.desktop file in /home/pi/.local/share/applications that throws an “Invalid desktop entry file:” error.

Looking at the original xastir.desktop file pointed to by the graphical menu entry:

[Desktop Entry]

Name=Xastir

Comment=X Amateur Station Tracking and Information Reporting

Exec=xastir

Terminal=false

Type=Application

Categories=Network;HamRadio

Keywords=APRS;AX.25;HamRadio

StartupNotify=false

Path=/usr/bin

 

I did not see anything obvious, but after comparing with the direwolf.desktop file that does work, I created a backup and began to tweak things until the file and an executable worked. First, I copied the xastir executable to a non-protected Exec path, then changed its execution permission to “all”.  It was set to “owner only” in /usr/bin. I also took out any mention of a Path in the .desktop file.

[Desktop Entry]

Type=Application

Exec=/usr/bin/xastir

Name=Xastir

Comment=X Amateur Station Tracking and Information Reporting

Terminal=false

Categories=Network;HamRadio

Keywords=APRS;AX.25;HamRadio

StartupNotify=false

Path=

 

With that mod, the xastir started working in receive with direwolf. So, I went back to the /usr/bin/xastir file and used “sudo chmod a+x xastir” to set execute permissions to “all”. Why this was not the case after installation, I don’t know.

 

I still have to set the DRAWS board up to transmit using the keyline in the miniDIN cable.

 

For the sake of those who have no Linux skills at all, I hope the software in the forthcoming DRAWS Compass image will be less challenging to set up.

 

Here is a “short” version for those who are too impatient to understand what is going on:

  1. Install Compass and configure DRAWS drivers as John has instructed in his emails and support pages at NW Digital. See https://nw-digital-radio.groups.io/g/udrc/message/2023.
  2. Install and use the Synaptic Package Manager to install Dire Wolf and xastir the email reference above is a good start.
  3. Configure and get Dire Wolf working as instructed by John’s help emails in this group
  4. Open and use Geany or nano to change /home/pi/.local/share/applications/xastir.desktop file in to read:

[Desktop Entry]

Type=Application

Exec=/usr/bin/xastir

Name=Xastir

Comment=X Amateur Station Tracking and Information Reporting

Terminal=false

Categories=Network;HamRadio

Keywords=APRS;AX.25;HamRadio

StartupNotify=false

Path=

  1. If clicking on the xastir icon in the Internet or HamRadio GUI menus does not work, open a terminal window and do a sudo chmod a+x /usr/bin/xastir so that xastir may be executed by any user.

That should do it.

 

KD4IZ

Jack Spitznagel

FM19oo

 

 


--
J Spitznagel
Science River LLC
KD4IZ


Re: Setting up your DRAWS™ GPS #draws #gpsd #gps #setup

Brian Badger
 

gpsd is up.  Thank you for adding this to the wiki so quickly.

Brian N0KZ


On Nov 29, 2018, at 12:15 PM, John D Hays - K7VE <john@...> wrote:

I updated the Wiki page to note this requirement.

On Thu, Nov 29, 2018 at 11:11 AM John D. Hays <john@...> wrote:
There is no separate GPS driver.  If you are not seeing /dev/ttySC0 then check the last line of /boot/config.txt  and make sure it indicates draws instead of udrc.  If you need to change it, you will need to reboot for it to take effect.

"edit /boot/config.txt and change the last line from dtoverlay=udrc to dtoverlay=draws"  -- from https://nw-digital-radio.groups.io/g/udrc/message/2023




On Thu, Nov 29, 2018 at 11:03 AM Brian Badger <brian@...> wrote:
Ensure that the device tree and driver have been installed on your Raspberry Pi image.  There should be a filename of /dev/ttySC0, which is the serial port for the GPS receiver and /dev/pps0, which is the pulse per second port from the receiver.

These device files do not exist.

If these files are not visible, then review your operating system (Compass Linux or Raspbian with updates) install.

I am using the latest version of Compass, fully updated.

What is the gps kernel module I should be looking for?

Brian N0KZ



--


John D. Hays
Edmonds, WA
K7VE

   



--


John D. Hays
Edmonds, WA
K7VE

   


Re: Setting up your DRAWS™ GPS #draws #gpsd #gps #setup

 

I updated the Wiki page to note this requirement.

On Thu, Nov 29, 2018 at 11:11 AM John D. Hays <john@...> wrote:
There is no separate GPS driver.  If you are not seeing /dev/ttySC0 then check the last line of /boot/config.txt  and make sure it indicates draws instead of udrc.  If you need to change it, you will need to reboot for it to take effect.

"edit /boot/config.txt and change the last line from dtoverlay=udrc to dtoverlay=draws"  -- from https://nw-digital-radio.groups.io/g/udrc/message/2023




On Thu, Nov 29, 2018 at 11:03 AM Brian Badger <brian@...> wrote:
Ensure that the device tree and driver have been installed on your Raspberry Pi image.  There should be a filename of /dev/ttySC0, which is the serial port for the GPS receiver and /dev/pps0, which is the pulse per second port from the receiver.

These device files do not exist.

If these files are not visible, then review your operating system (Compass Linux or Raspbian with updates) install.

I am using the latest version of Compass, fully updated.

What is the gps kernel module I should be looking for?

Brian N0KZ



--


John D. Hays
Edmonds, WA
K7VE

   



--


John D. Hays
Edmonds, WA
K7VE

   


Re: Setting up your DRAWS™ GPS #draws #gpsd #gps #setup

 

There is no separate GPS driver.  If you are not seeing /dev/ttySC0 then check the last line of /boot/config.txt  and make sure it indicates draws instead of udrc.  If you need to change it, you will need to reboot for it to take effect.

"edit /boot/config.txt and change the last line from dtoverlay=udrc to dtoverlay=draws"  -- from https://nw-digital-radio.groups.io/g/udrc/message/2023




On Thu, Nov 29, 2018 at 11:03 AM Brian Badger <brian@...> wrote:
Ensure that the device tree and driver have been installed on your Raspberry Pi image.  There should be a filename of /dev/ttySC0, which is the serial port for the GPS receiver and /dev/pps0, which is the pulse per second port from the receiver.

These device files do not exist.

If these files are not visible, then review your operating system (Compass Linux or Raspbian with updates) install.

I am using the latest version of Compass, fully updated.

What is the gps kernel module I should be looking for?

Brian N0KZ



--


John D. Hays
Edmonds, WA
K7VE

   


Re: Setting up your DRAWS™ GPS #draws #gpsd #gps #setup

Brian Badger
 

Ensure that the device tree and driver have been installed on your Raspberry Pi image.  There should be a filename of /dev/ttySC0, which is the serial port for the GPS receiver and /dev/pps0, which is the pulse per second port from the receiver.

These device files do not exist.

If these files are not visible, then review your operating system (Compass Linux or Raspbian with updates) install.

I am using the latest version of Compass, fully updated.

What is the gps kernel module I should be looking for?

Brian N0KZ


Re: UDRC II, no TX? Other questions

Matt Trull
 

Thanks all,

I will go back through and rerun the initial setup scripts to be sure everything is set back to defaults and see if that makes a difference.

Thanks,
Matt


On Wed, Nov 28, 2018 at 2:15 PM John D Hays - K7VE <john@...> wrote:
Also, always start with the values in this script https://nw-digital-radio.groups.io/g/udrc/wiki/UDRC%E2%84%A2-Setup-for-the-Yaesu-DR-1X-Repeater#Basic-Configuration  -- there are additional settings that the script sets that have an affect on input and output.

On Wed, Nov 28, 2018 at 11:10 AM Matt Trull <Oxyacetylene@...> wrote:
Thanks for the suggestion, but I have tried varying PCM, ADC and Lo levels up to the max and the output signal isn't changing. I think the signal I am seeing on my SDR is just carrier or noise. I also emailed you directly so we can compare a few things.

Thanks!
Matt

On Wed, Nov 28, 2018 at 1:58 PM VE3MIC via Groups.Io <ve3mic=yahoo.com@groups.io> wrote:
Hi Matt,

On rare occasions (which to this date, I still don't know the cause) my DR-1x TX(PCM) audio level on the UDRC gets reset to zero.
Check yours. In my case, I set both audio levels to 48, If this isn`t it, and would like to compare notes. Drop me an email> ve3mic at rac dot ca.
Inline image



--


John D. Hays
Edmonds, WA
K7VE

   


Re: UDRC II, no TX? Other questions

 

It can be anywhere, but following those instructions that is where it ends up.

On Wed, Nov 28, 2018 at 11:25 AM VE3MIC via Groups.Io <ve3mic=yahoo.com@groups.io> wrote:
John.  The script you are referring to is the set-udrc-dr1x.sh file in the home/pi directory correct?
de Mike



--


John D. Hays
Edmonds, WA
K7VE

   


Re: UDRC II, no TX? Other questions

VE3MIC
 

John.  The script you are referring to is the set-udrc-dr1x.sh file in the home/pi directory correct?
de Mike


Re: UDRC II, no TX? Other questions

 

Also, always start with the values in this script https://nw-digital-radio.groups.io/g/udrc/wiki/UDRC%E2%84%A2-Setup-for-the-Yaesu-DR-1X-Repeater#Basic-Configuration  -- there are additional settings that the script sets that have an affect on input and output.


On Wed, Nov 28, 2018 at 11:10 AM Matt Trull <Oxyacetylene@...> wrote:
Thanks for the suggestion, but I have tried varying PCM, ADC and Lo levels up to the max and the output signal isn't changing. I think the signal I am seeing on my SDR is just carrier or noise. I also emailed you directly so we can compare a few things.

Thanks!
Matt

On Wed, Nov 28, 2018 at 1:58 PM VE3MIC via Groups.Io <ve3mic=yahoo.com@groups.io> wrote:
Hi Matt,

On rare occasions (which to this date, I still don't know the cause) my DR-1x TX(PCM) audio level on the UDRC gets reset to zero.
Check yours. In my case, I set both audio levels to 48, If this isn`t it, and would like to compare notes. Drop me an email> ve3mic at rac dot ca.
Inline image



--


John D. Hays
Edmonds, WA
K7VE

   


Re: UDRC II, no TX? Other questions

Matt Trull
 

Thanks for the suggestion, but I have tried varying PCM, ADC and Lo levels up to the max and the output signal isn't changing. I think the signal I am seeing on my SDR is just carrier or noise. I also emailed you directly so we can compare a few things.

Thanks!
Matt


On Wed, Nov 28, 2018 at 1:58 PM VE3MIC via Groups.Io <ve3mic=yahoo.com@groups.io> wrote:
Hi Matt,

On rare occasions (which to this date, I still don't know the cause) my DR-1x TX(PCM) audio level on the UDRC gets reset to zero.
Check yours. In my case, I set both audio levels to 48, If this isn`t it, and would like to compare notes. Drop me an email> ve3mic at rac dot ca.



Re: UDRC II, no TX? Other questions

VE3MIC
 

Hi Matt,

On rare occasions (which to this date, I still don't know the cause) my DR-1x TX(PCM) audio level on the UDRC gets reset to zero.
Check yours. In my case, I set both audio levels to 48, If this isn`t it, and would like to compare notes. Drop me an email> ve3mic at rac dot ca.
Inline image


UDRC II, no TX? Other questions

Matt Trull
 

I am configuring a UDRC II with DR-1X repeater. Looking at the dstarrepeaterd_1.log file I see my HT's transmission being received/decoded, but I do not see it being repeated or TX. For normal RF traffic should you see the "Transmit To" in the log? I went through the config file but I might be missing something. I went back through the Wiki and compared all of the settings there in the linked initial config file to what I have, mostly paying attention to PTT, RX, TX invert and such.

Another question on adjusting the audio levels. I found the n7nix measure_deviate.sh script. In order to use the sound device (UDRC) I stop the dstarrepeater daemon and run the script. It runs, but doesn't appear to be TX anything. I'll do some more testing and make sure the PTT is being triggered, but I think the script should be doing that as well?

Thanks,
Matt KX4GG