Date   
Re: Nixtracker

Jim Erickson
 

Someone else smarter than me will chime in I’m sure, but for the DRAWS hat, the GPS is located at /dev/ttySC0

I’m not familiar with the Nixtracker, though I am interested.  It looks like your gpsd is correct:

CGroup: /system.slice/gpsd.service
           └─519 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0

There must be a config for Nixtracker to point it at GPS?  In which case /dev/ttySC0 is where the GPS is located, at least for the DRAWS hat.

------
73,
Jim
VA7SHG - Phone
VE7TGZ/VA7TGZ - Other

On Feb 6, 2020, at 12:17, Rich KR4PI <rich.schnieders@...> wrote:

In trying to figure out why the gps is not reporting the info to nixtracker I entered
"sudo systemctl status gpsd" and the result I received is:

gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-02-06 15:09:24 EST; 48s ago
  Process: 511 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
 Main PID: 519 (gpsd)
    Tasks: 3 (limit: 2200)
   Memory: 1.4M
   CGroup: /system.slice/gpsd.service
           └─519 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
 
Feb 06 15:09:24 Draws systemd[1]: Starting GPS (Global Positioning System) Daemon...
Feb 06 15:09:24 Draws systemd[1]: Started GPS (Global Positioning System) Daemon.
Feb 06 15:09:26 Draws gpsd[519]: gpsd:ERROR: response: {"class":"ERROR","message":"No such device as /dev/ttyUSB0"}\x0d\x0a

when I try to cat/Dev/tty/USB0 I receive 
cat: /Dev/ttyUSB0: No such file or directory

any help would be appreciated.

Thanks, 
Rich, KR4PI

Re: Nixtracker

 

In trying to figure out why the gps is not reporting the info to nixtracker I entered
"sudo systemctl status gpsd" and the result I received is:

gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-02-06 15:09:24 EST; 48s ago
  Process: 511 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
 Main PID: 519 (gpsd)
    Tasks: 3 (limit: 2200)
   Memory: 1.4M
   CGroup: /system.slice/gpsd.service
           └─519 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
 
Feb 06 15:09:24 Draws systemd[1]: Starting GPS (Global Positioning System) Daemon...
Feb 06 15:09:24 Draws systemd[1]: Started GPS (Global Positioning System) Daemon.
Feb 06 15:09:26 Draws gpsd[519]: gpsd:ERROR: response: {"class":"ERROR","message":"No such device as /dev/ttyUSB0"}\x0d\x0a

when I try to cat/Dev/tty/USB0 I receive 
cat: /Dev/ttyUSB0: No such file or directory

any help would be appreciated.

Thanks, 
Rich, KR4PI

Re: Nixtracker

 

Good afternoon all,

I have Nixtracker running on my pi 3b with draws hat installed. I have two radios connected. UDR0 is attached to a radio on our local packet freq and runs a Winlink Gateway. UDR1 is connected to a radio on our local aprs freq. I am able to see aprs info on the Nixtracker on another machine. However in the Sats window I have Zero sats. the window reports nodata. gpsd is running on the Pi and has a good lock. I read in this forum that there is something that needs to be done to make this work but it appears those instructions were taken offline.

The other question I have is there a way in the MSG tab to select which port on draws the aprs message goes out?

Thanks for all the help!

Rich, KR4PI

Re: Problems with Winlink handshaking on VHF and no power to transmitter on HF

Dave Christensen
 

I hooked up my Pi3B+ to a Signalink and ran FLDigi, JS8Call, and Direwolf and measured the audio drive levels on transmit.  They were all within 20 mV of each other so the USB Audio Codec (Signalink) is being handled differently than the DRAWS interface for some reason.  I don't know if this simplifies or complicates this issue.

Re: TS-480 Interface #wsjt-x #kenwood #flrig

Charles Blackburn <wx4cb@...>
 

not using a draws yet, but i am using ham radio deluxe on my laptop and i have the settings as below, just remember for it to accept out of the data port, you need to tell it specifically to use the correct TX cat command (there's two). as per page 21 of the command manual: https://www.kenwood.com/i/products/info/amateur/ts_480/pdf/ts_480_pc.pdf

IIRC it's TX1

TX - Sets the transceiver in TX mode.
Parameters: P1 0: Normal (SEND) transmission using MIC input
1: DTS transmission using ANI input
2: TX Tune transmission

If no P1 parameter is specified, P1=0 is used.

radio: HRD

PTT: CAT

TX Audio Source Rear/Data

ModeL None

Split: None


hope this helps

charlie

On 2/5/2020 12:00 AM, Jonathan Visser via Groups.Io wrote:
I am working to test WSJT-s on the latest image of DRAWS image.

I have connected a USB to serial adapter plugged in to the COM port on the radio and have a DIN cable between the UDC0 and the data port on the radio.   I have configured FLRIG and I have seemingly full control of the radio.  I have the ability to transmit and the tune button will tune the antenna.

WSJT-X is configured using FLDIGI as the transmitter.  I can see the waterfalls and the messages are decoded.  I can change the frequency of the radio through WSJT-X.  Th issue I am trying to figure out is WSJT-X will not transmit.  If you press the tune button or enable TX the radio never keys up.  I am sure I am missing something basic, and was hoping someone could point me in the correct direction.

Thanks,
Jonathan N9TJX


TS-480 Interface #wsjt-x #kenwood #flrig

Jonathan Visser
 

I am working to test WSJT-s on the latest image of DRAWS image.

I have connected a USB to serial adapter plugged in to the COM port on the radio and have a DIN cable between the UDC0 and the data port on the radio.   I have configured FLRIG and I have seemingly full control of the radio.  I have the ability to transmit and the tune button will tune the antenna.

WSJT-X is configured using FLDIGI as the transmitter.  I can see the waterfalls and the messages are decoded.  I can change the frequency of the radio through WSJT-X.  Th issue I am trying to figure out is WSJT-X will not transmit.  If you press the tune button or enable TX the radio never keys up.  I am sure I am missing something basic, and was hoping someone could point me in the correct direction.  

Thanks, 
Jonathan N9TJX

Re: #Desktop file manager and screen blanking issues #desktop

Steve, N9VW
 

My suspicions are that since this is a known issue with the Raspian image then they must have fixed the issue and the update/upgrade pulled in the 'fix'...

On 2/2/2020 1:52 PM, f6bvp wrote:

Hi Basil,

By chance the solution of file manager

sudo apt update
sudo apt full-upgrade
sudo reboot

suggesred by david, Ke7rgp

also cured my screen blanking issue !

Anyway, thank you for sharing your solutions.

73 de Bernard, f6bvp


Re: #Desktop file manager and screen blanking issues #desktop

Bernard f6bvp
 

Hi Basil,

By chance the solution of file manager

sudo apt update
sudo apt full-upgrade
sudo reboot

suggesred by david, Ke7rgp

also cured my screen blanking issue !

Anyway, thank you for sharing your solutions.

73 de Bernard, f6bvp

Re: #Desktop file manager and screen blanking issues #desktop

Basil Gunn
 

This means that something should be repaired in nwdr14 and 15 ?
I will not be spinning a new image.

The pcmanfm reinstall has been added to 'app_config.sh core' with this commit:
https://github.com/nwdigitalradio/n7nix/commit/bf885816fe434007f649aaf3ec05d0b253fc9cba

For new installs pcmanfm will automatically get reinstalled if
directions are followed in the "Getting Started Guide" ie. you need to
do a 'git pull' before running 'app_config.sh core'

For those who have already done an install you can fix the symptom, as
previously posted by opening a console running:

apt-get install -y -q --reinstall pcmanfm

I will see if screen blanking issue is also gone.
I think these 2 issues are unrelated.
/Basil n7nix

Re: #Desktop file manager and screen blanking issues #desktop

Bernard f6bvp
 

David,
Thank you for providing a solution that also worked for me.
And thanks to all who confirmed the file manager issue.
It’s  nice to share problems.

This means that something should be repaired in nwdr14 and 15 ?

I will see if screen blanking issue is also gone.

73 de Bernard, f6bvp

Re: #Desktop file manager and screen blanking issues #desktop

Basil Gunn
 

Hi Bernard,

Second issue first: File Manager instantly closes when opened
The solution can be found here:
https://raspberrypi.stackexchange.com/questions/92213/file-manager-instantly-closes-when-opened

The file manager used in Raspbian is called pcmanfm, you must re-install it.

sudo apt-get install --reinstall pcmanfm

First issue:
Disclaimer I do NOT use the raspbian GUI very much so this is my limited
observation.

One of my monitors, Sceptre model E16 (12v monitor), stopped working with
buster running on an RPi 4. I got it displaying again by
putting the following in the /boot/config.txt file.

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
#dtoverlay=vc4-fkms-v3d
max_framebuffers=2
hdmi_force_hotplug:0=1
#hdmi_safe=1
hdmi_group:0=1
hdmi_mode:0=4

What I would do is collect some data to see if you can understand the
problem better. Look at:
- monitor model
- video connector used, ie. HDMI,
- all the hdmi settings in /boot/config.txt,
- raspberry pi model,
- kernel version

This is what I am currently using for testing on my bench:

machine kern RPi video Monitor
plutest 4.19.75 Pi 4 Model B HDMI Sceptre 16"
nwdr15plu2 4.19.93 Pi 3 Model B HDMI Sunfounder 10" touch
ardop2 4.19.75 Pi 3 Model B+ HDMI Sunfounder 10"
mhams 4.14.98 Pi 3 Model B HDMI Sunfounder 10"

Also you will get more eyes looking at your problem if you post your
description on the RaspberryPi-4-HamRadio groups.io site.

/Basil n7nix

f6bvp <f6bvp@...> writes:

Hi,
With nwdr15.img and recently with nwdr14.img I observed same
desktop issues on two different Raspberry Pi models 3B+ and 4 and two
different screen displays models. *These issues are not present on
latest RaspBian distro september 2019 with same 4.19.93 kernel and all
applications updated.*

First issue is with screen blanking. I had to disable it in preference
menu for it was impossible to recover a display after it was
blanked. Sometime unplugging the UDMI plug could recover a normal
display but usually a reboot was needed.

Second issue is with File Manager desktop icon. When clicking on the
icon it opens a file window very briefly and close it right away. At
the same time all desktop icons disappear for a brief moment and
reappear on the desktop.

73 de Bernard, f6bvp

Re: #Desktop file manager and screen blanking issues #desktop

Ruben .
 

Thank you for voicing these issues, I thought it was my inexperience.

Ruben
WA2NBL


On Feb 2, 2020, at 10:17 AM, David Lowry <huskyrunnr@...> wrote:

I had the same problem with file manager. I had a fresh image, nwdr15, the piwiz ran through almost all downloads then failed. Basil had said the core config does the same thing as the piwiz, if I understood correctly, so I left it. After core config, I tried to use the file manager for the first time and noticed the problem.

the problem went away after running

sudo apt update
sudo apt full-upgrade
sudo reboot

david, Ke7rgp 

Re: #Desktop file manager and screen blanking issues #desktop

 

I had the same problem with file manager. I had a fresh image, nwdr15, the piwiz ran through almost all downloads then failed. Basil had said the core config does the same thing as the piwiz, if I understood correctly, so I left it. After core config, I tried to use the file manager for the first time and noticed the problem.

the problem went away after running

sudo apt update
sudo apt full-upgrade
sudo reboot

david, Ke7rgp 

Re: #Desktop file manager and screen blanking issues #desktop

Jonathan Visser
 

Bernard, 

For the file manager I noticed this to.  We did a quick reinstall of the file manager and it took care if it.   When I get back home later today I will look up the command we used and send it over. 

73’s Jonathan N9TJX

On Feb 2, 2020, at 05:31, f6bvp <f6bvp@...> wrote:

Hi,
With nwdr15.img and recently with nwdr14.img I observed same desktop issues on two different Raspberry Pi models 3B+ and 4 and two different screen displays models.
These issues are not present on latest RaspBian distro september 2019 with same 4.19.93 kernel and all applications updated.

First issue is with screen blanking. I had to disable it in preference menu for it was impossible to recover a display after it was blanked. Sometime unplugging the UDMI plug could recover a normal display but usually a reboot was needed.

Second issue is with File Manager desktop icon. When clicking on the icon it opens a file window very briefly and close it right away. At the same time all desktop icons disappear for a brief moment and reappear on the desktop.

73 de Bernard, f6bvp

#Desktop file manager and screen blanking issues #desktop

Bernard f6bvp
 

Hi,
With nwdr15.img and recently with nwdr14.img I observed same desktop issues on two different Raspberry Pi models 3B+ and 4 and two different screen displays models.
These issues are not present on latest RaspBian distro september 2019 with same 4.19.93 kernel and all applications updated.

First issue is with screen blanking. I had to disable it in preference menu for it was impossible to recover a display after it was blanked. Sometime unplugging the UDMI plug could recover a normal display but usually a reboot was needed.

Second issue is with File Manager desktop icon. When clicking on the icon it opens a file window very briefly and close it right away. At the same time all desktop icons disappear for a brief moment and reappear on the desktop.

73 de Bernard, f6bvp

Re: Draws problems

Richard Waller <rewaller@...>
 

I will follow your suggestion but I had been using the ft 817 without removing any pins on mini din and audio was fine.

On Jan 29, 2020, at 10:31 AM, Basil Gunn <@basil860> wrote:


When I last looked at the Yaesu FT-817 over a year ago I had to
disconnect pin 6 on the mDin6 cable which controls squelch on that radio
to get receive audio to work.

See Running FLdigi with the Yaesu FT-817 at this link:
https://github.com/nwdigitalradio/n7nix/blob/master/docs/RADIO_APP_NOTES.md

Also run the measure_deviate.sh script to verify transmit as previously
described.

/Basil

Basil, yes I reimaged the micro sd card. The rPi otherwise is
functioning normally. To be clear, I haven’t tried transmitting. When
I monitor I’m not getting evidence of signals ( which I can hear ) on
the screen. I had been using left minidin. Switched to right in draws
manager, same result. I selected preset for ft 817 af. Audio in out in
wsjt plughwCARD=udrc, DEV=0. Rick
On Jan 29, 2020, at 1:01 AM, Basil Gunn <@basil860> wrote:

Richard Waller via Groups.Io <rewaller=verizon.net@groups.io> writes:

I “crashed” my micro sd card using a non- draws related program.
I reloaded the earlier version of software that I had been using which
had been working on to that sd card.
What exactly did you do? Did you re-image the mSD card?

The wsjt-x program comes up and
runs like before but Now I’m not getting audio from my ft 817 to
wsjt-x program. I’m using the exact same cables and settings I was
using before. I updated the software with the same results.
Is there a way to check the draws hat to see if it is
working?Thanks. Rick Ka4ohm
A basic test is to use the measure_deviate.sh script
https://github.com/nwdigitalradio/n7nix/tree/master/deviation

This will generate a tone and enable PTT. There are options to test left
& right channels.
Use a second radio to hear the generated tone.

/Basil n7nix





Re: Nixtracker

Basil Gunn
 

I got it now Basil. Thanks. My ignorance of Linux is shining
through. Every user including the system gets their own crontab. I was
using the system’s crontab.

time to go read about Linux os
I would suggest to learn about Linux have an idea about something that
you want your Linux system to do then google away until you figure it
out.

got all my wires and coax fished in the truck. Install tomorrow!
Terrific!! Send me a pic when it's done.

i notice in the YouTube you pointed me to, there is no debug panel. Do
you toggle that panel on/off or leave it there all the time?
I currently leave it there all the time. I'll have to look into getting
rid of it.

also, one of the rotating beacon messages indicates a digipeating setting?
That's just a filler I think left over from Dan Smith's configuration
from a number of years ago.

You can easily customize your beacons by looking in the
/etc/tracker/aprs_tracker.ini file in the [comments] section
You set up which beacons you want to rotate through then enable them
with the enabled = line
I would change the #4 beacon to something else.
Variables are defined between pairs of $.

enabled = 1,2,3,4
1=Using nixtracker $ver$, gps sats $sats$
2=https://github.com/n7nix/nixtracker
3=Software $ver$
4=Set path to TEMP1-1,WIDE2-1 to digi
5=Test: Number of sats $sats$, version $ver$, date $date$, time $time$, voltage, $voltage$, index $index$, temperature $temp1$, sig qual $digiq$, call sign $mycall$

/Basil

Re: Nixtracker

 

I got it now Basil. Thanks. My ignorance of Linux is shining through. Every user including the system gets their own crontab. I was using the system’s crontab.

time to go read about Linux os

got all my wires and coax fished in the truck. Install tomorrow!

i notice in the YouTube you pointed me to, there is no debug panel. Do you toggle that panel on/off or leave it there all the time?

also, one of the rotating beacon messages indicates a digipeating setting?

david

Re: Draws problems

Basil Gunn
 

When I last looked at the Yaesu FT-817 over a year ago I had to
disconnect pin 6 on the mDin6 cable which controls squelch on that radio
to get receive audio to work.

See Running FLdigi with the Yaesu FT-817 at this link:
https://github.com/nwdigitalradio/n7nix/blob/master/docs/RADIO_APP_NOTES.md

Also run the measure_deviate.sh script to verify transmit as previously
described.

/Basil

Basil, yes I reimaged the micro sd card. The rPi otherwise is
functioning normally. To be clear, I haven’t tried transmitting. When
I monitor I’m not getting evidence of signals ( which I can hear ) on
the screen. I had been using left minidin. Switched to right in draws
manager, same result. I selected preset for ft 817 af. Audio in out in
wsjt plughwCARD=udrc, DEV=0. Rick
On Jan 29, 2020, at 1:01 AM, Basil Gunn <@basil860> wrote:


Richard Waller via Groups.Io <rewaller=verizon.net@groups.io> writes:

I “crashed” my micro sd card using a non- draws related program.
I reloaded the earlier version of software that I had been using which
had been working on to that sd card.
What exactly did you do? Did you re-image the mSD card?

The wsjt-x program comes up and
runs like before but Now I’m not getting audio from my ft 817 to
wsjt-x program. I’m using the exact same cables and settings I was
using before. I updated the software with the same results.
Is there a way to check the draws hat to see if it is
working?Thanks. Rick Ka4ohm
A basic test is to use the measure_deviate.sh script
https://github.com/nwdigitalradio/n7nix/tree/master/deviation

This will generate a tone and enable PTT. There are options to test left
& right channels.
Use a second radio to hear the generated tone.

/Basil n7nix



Re: Problems with Winlink handshaking on VHF and no power to transmitter on HF

Jack Spitznagel
 

Basil,

 

Thanks for refreshing my memory with the link below – it had been a good while and my focus has been significantly elsewhere since before Dayton/Xenia last year:

 

In a previous post it was mentioned that the contents of that email were captured here:

https://github.com/nwdigitalradio/n7nix/blob/master/docs/RADIO_APP_NOTES.md#alsa-settings-for-ic-7000

Again my very faulty recall was that I did test these settings and found that it still did not allow me to adjust the ALC to the “nil” reading for minimum sig distortion without the noise issue cropping up. OTOH, I am pretty sure I used the discriminator output for receive… but RX was never the issue here. Since I have not tried the new image, I will give it a go and configure from the ground up. If that can be made to work well, then I’ll tackle the 7100 to see if it is different.

 

Thanks,

 

KD4IZ

Jack Spitznagel

FM19oo