Date   
Re: ax25 transmitting but output is incorrect apparently so no connection

Basil Gunn
 

Mike, Replying to your last 2 posts Let's just focus on getting APRS
working first which may also fix your wl2kax25 problem as well. The
console output for wl2ktelnet you previously posted looks OK. Also looks
like you are receiving packets OK (from mheard).

Get used to starting up a packet spy in a console window.
sudo su
listen -a

Deviation:
Incorrect deviation is most likely the reason you could not connect to W0UO-10.

How did you determine these ALSA settings?
I think you were monitoring 'ALC'. If possible put PCM closer to zero
and change LO Driver to adjust for proper deviation.
- 'Lo Driver Gain' is the analog control and the preferred way to set level.
- 'PCM' is the digital control & will set how many bits the DAC will use.

LO Driver Gain  L:[-6.00dB]     R:[-6.00dB]
PCM             L:[-33.00dB]    R:[-25.00dB]

These above settings will vary depending on your radio settings.

To set deviation output a tone, see measure_deviate.sh utility.
https://github.com/nwdigitalradio/n7nix/tree/master/deviation
If you have a handy talky use it to listen to the tones transmitted by
the FT-857D

From FT-857D Operating Manual:
You can adjust DATA input level using Menu Item No-037 [DIG GAIN].

See manual starting on page 66 of FT-857D Operating Manual for setting
up digital transmitter operation. There are a LOT of settings on this
radio that affect digital modes. Try searching for "deviation".

GPS:
Try to put your GPS antenna close to a window especially if your shack
is in your basement or you have a metal roof. I put the magnetic antenna
on the roof of my truck cab when I'm mobile. The btest.sh script should
work without an operational GPS ie. should transmit packets

APRS.FI
I have only seen 1 packet at the aprs.fi site and that was from a couple
of days ago (which is encouraging). Could you please tune your radio to
the 2M APRS frequency, 144.390 and run the btest.sh script again 3 times
with no arguments ie. message beacon mode.

I know it's April Fool's Day but this post is sincere.
/Basil n7nix


Mike B <kf5dey@...> writes:

So doing some more testing...ran the mheard command and got a surprising result...

Now some of these are APRS packets I am sure...but the first one is the station I am trying to reach with the wl2kax25 command. So that tells me I am hearing it... I can't tell if it is replying to my queries...the time date stamp doesn't match...

---
pi@draws:/ $ mheard
Callsign Port Packets Last Heard
W0UO-10 udr0 27 2020-03-31 23:06:07
KB5RLJ-4 udr0 1 2020-03-31 21:27:58
KE5UCT-5 udr0 5 2020-03-31 21:27:51
W5WFR-8 udr0 1 2020-03-31 21:27:24
WD5RP-2 udr0 6 2020-03-31 21:27:17
K5LOL-9 udr0 5 2020-03-31 21:27:08
KS5S udr0 3 2020-03-31 21:26:52
KI4SSU udr0 1 2020-03-31 21:26:42
KD5UIG-10 udr0 4 2020-03-31 21:26:37
DCARA-9 udr0 2 2020-03-31 21:26:25
KC5TIL-3 udr0 2 2020-03-31 21:25:31
KC5TIL-4 udr0 1 2020-03-31 21:25:02

Re: PAT with DRAWS on VHF

Mike B
 

I am checking my configs do to a similar problem...(in a different thread)

But in this thread I noticed that Dave Christensen had..
    "ax25": {
    "port": "udr0",
   
    udr0        KD7UM-6         9600    255     2       Direwolf port

My axports has udr0 as the Winlink port, and that is the one selected in the wl2k.conf and in .wl2k/config.json

Is that correct?   Just trying to troubleshoot.

Mike
KF5DEY

Re: ax25 transmitting but output is incorrect apparently so no connection

Mike B
 

So doing some more testing...ran the mheard command and got a surprising result...

Now some of these are APRS packets I am sure...but the first one is the station I am trying to reach with the wl2kax25 command.   So that tells me I am hearing it... I can't tell if it is replying to my queries...the time date stamp doesn't match...

---
pi@draws:/ $ mheard
Callsign   Port    Packets   Last Heard
W0UO-10    udr0         27   2020-03-31 23:06:07
KB5RLJ-4   udr0          1   2020-03-31 21:27:58
KE5UCT-5   udr0          5   2020-03-31 21:27:51
W5WFR-8    udr0          1   2020-03-31 21:27:24
WD5RP-2    udr0          6   2020-03-31 21:27:17
K5LOL-9    udr0          5   2020-03-31 21:27:08
KS5S       udr0          3   2020-03-31 21:26:52
KI4SSU     udr0          1   2020-03-31 21:26:42
KD5UIG-10  udr0          4   2020-03-31 21:26:37
DCARA-9    udr0          2   2020-03-31 21:26:25
KC5TIL-3   udr0          2   2020-03-31 21:25:31
KC5TIL-4   udr0          1   2020-03-31 21:25:02

Re: ax25 transmitting but output is incorrect apparently so no connection

Mike B
 

As far as the GPS goes...it is up and down all the time...I am in a non optimal location...

Re: UDRCII with RT Systems Cable for CAT Control & mini 6DIN and Yaesu FT-450D --PTT engaged but 0 Watts transmitted #wsjt-x #ft-8

TG9AOR
 

Basil, thank you for your response. I cycled the PWR slider: no change. I cycled the Output device on my audio tab, from plughw:CARD=udrc,DEV=0 Mono to default, and to Left on the drop down list box next to it, no change. Reverted back to plughw:CARD=udrc,DEV=0 Mono and selected Both on the drop down list box, and that solved it. I am now able to transmit and adjust ALC leves with the power slider. Thank you very much. 

Re: ax25 transmitting but output is incorrect apparently so no connection

Basil Gunn
 

Mike B <kf5dey@...> writes:

BTW as I always I appreciate the info available...sometimes it is just out of my league...
No problem, stick with it, it will become 2nd nature after a while.

As far as APRS, thanks, I search on aprs.fi and it says doesn't exist
in database. I still can't see that particular one on aprs.fi...I
guess you can't just go to the website and type in a callsign like for
everyone else. So I will have to take your word on that...and that
narrows down the trouble a bit.
Go to aprs.fi
click on raw packets
set Originating callsign to KF5DEY*
which says look for KF5DEY all SSIDs

I don't see any of your position beacons and gps is NOT getting a fix.

Left connector from DRAWS to FT-857D
I'll send more info tomorrow.

---

---
pi@draws:~/n7nix/debug $ wl2kax25 -c w0uo-10
connect(): Connection timed out

pi@draws:~ $ sudo listen -a
udr0: fm KF5DEY to W0UO-10 ctl SABM+ 21:28:28.637932
udr0: fm KF5DEY to W0UO-10 ctl SABM+ 21:28:31.703698
udr0: fm KF5DEY to W0UO-10 ctl SABM+ 21:28:34.743701
udr0: fm KF5DEY to W0UO-10 ctl SABM+ 21:28:37.783687
udr0: fm KF5DEY to W0UO-10 ctl SABM+ 21:28:40.823686
udr0: fm KF5DEY to W0UO-10 ctl SABM+ 21:28:43.863681
udr0: fm KF5DEY to W0UO-10 ctl SABM+ 21:28:46.903694
---

pi@draws:~/n7nix/bin $ ./alsa-show.sh
===== ALSA Controls for Radio Transmit =====
LO Driver Gain L:[-6.00dB] R:[-6.00dB]
PCM L:[-33.00dB] R:[-25.00dB]
DAC Playback PT L:[P3] R:[P3]
LO Playback CM [Full Chip]

===== ALSA Controls for Radio Receive =====
ADC Level L:[-2.00dB] R:[0.00dB]
IN1 L:[Off] R:[Off]
IN2 L:[10 kOhm] R:[Off]
CM L:[10 kOhm] R:[10 kOhm]

Re: ax25 transmitting but output is incorrect apparently so no connection

Mike B
 

BTW as I always I appreciate the info available...sometimes it is just out of my league...

As far as APRS, thanks, I search on aprs.fi and it says doesn't exist in database.  I still can't see that particular one on aprs.fi...I guess you can't just go to the website and type in a callsign like for everyone else.  So I will have to take your word on that...and that narrows down the trouble a bit.

Left connector from DRAWS to FT-857D

---

---
pi@draws:~/n7nix/debug $ wl2kax25 -c w0uo-10
connect(): Connection timed out

pi@draws:~ $ sudo listen -a
udr0: fm KF5DEY to W0UO-10 ctl SABM+ 21:28:28.637932
udr0: fm KF5DEY to W0UO-10 ctl SABM+ 21:28:31.703698
udr0: fm KF5DEY to W0UO-10 ctl SABM+ 21:28:34.743701
udr0: fm KF5DEY to W0UO-10 ctl SABM+ 21:28:37.783687
udr0: fm KF5DEY to W0UO-10 ctl SABM+ 21:28:40.823686
udr0: fm KF5DEY to W0UO-10 ctl SABM+ 21:28:43.863681
udr0: fm KF5DEY to W0UO-10 ctl SABM+ 21:28:46.903694
---

pi@draws:~/n7nix/bin $ ./alsa-show.sh
 ===== ALSA Controls for Radio Transmit =====
LO Driver Gain  L:[-6.00dB]     R:[-6.00dB]
PCM             L:[-33.00dB]    R:[-25.00dB]
DAC Playback PT L:[P3]          R:[P3]
LO Playback CM  [Full Chip]

 ===== ALSA Controls for Radio Receive =====
ADC Level       L:[-2.00dB]     R:[0.00dB]
IN1             L:[Off]         R:[Off]
IN2             L:[10 kOhm]     R:[Off]
CM              L:[10 kOhm]     R:[10 kOhm]

--
On FT-857D there is a menu entry to monitor 'ALC' when transmitting data...mine  shows right at the correct point (according to description in manual), and power output is what is expected.  So something is getting modulated.

Mike
KF5DEY

Re: ax25 transmitting but output is incorrect apparently so no connection

Basil Gunn
 

Tried APRS beaconing and winlink packet.
APRS beaconing test does not send out a beacon...it transmits, but
noting worth hearing apparently...(other than obvoius test, second
test was HT outside with unobstructed view of antenna...lots of other
APRS beacons, but none from my station.
What are you using to come to this conclusion?
As root run listen -a to see what packets are being sent.

No errors, I have run the ./btest.sh it keys the transmitter and sends
out some kind of modulated signal...but it is not APRS.
Yet your beacon packet appears in aprs.fi as an APRS message beacon
2020-03-30 11:35:04 PDT: KF5DEY-11>APUDR1,AC5V-15*,qAO,KF5DEY-1::KF5DEY :30 13:34:58 CDT KF5DEY mesg_beacon test from host draws on port udr0 Seq: 0

run ./btest.sh -h
To see possible arguments to use ie. to send an APRS position beacon use
-p
./btest.sh -p

I can see the input meter to the radio, and the output power, so it is
attempting to transmit something...but whatever it is sending is bad.
I don't think an APRS message packet is bad. Also run ./btest.sh -p at
least 3 times so I can take a look (at aprs.fi) at your APRS packets
that are getting gated back to aprs.fi

No connection using wl2kax -c (node). monitoring output with SDR, it
is transmitting...Using a laptop winlink express and a Signalink using
the exact same radio/freq/mode/ and node I get an immediate
connection.
I can't comment unless I see the console output & preferably a packet
spy trace using listen -a

Using telnet I get a good connection and transfer of data.
Only error is 'Connection timed out"
Once again I need to see console output to see what's happening.

Where can I start troubleshooting/
Send console output of all commands you are using.
Which mDin6 connector (left or right) is the cable going to your radio
connected to. Should be left.

Also would like to see output of alsa-show.sh

/Basil n7nix

ax25 transmitting but output is incorrect apparently so no connection

Mike B
 

I fear there are a few threads on this topic, but they are labeled random things.

For the record.  All transmit and receive in modes not using ax25 work just fine.

ax25 reception/decoding works fine.

ax25 transmission is the problem.

Tried APRS beaconing and winlink packet.  

APRS beaconing test does not send out a beacon...it transmits, but noting worth hearing apparently...(other than obvoius test, second test was HT outside with unobstructed view of antenna...lots of other APRS beacons, but none from my station.

No errors, I have run the ./btest.sh  it keys the transmitter and sends out some kind of modulated signal...but it is not APRS.

I can see the input meter to the radio, and the output power, so it is attempting to transmit something...but whatever it is sending is bad.

No connection using wl2kax -c (node). monitoring output with SDR, it is transmitting...Using a laptop winlink express and a Signalink using the exact same radio/freq/mode/ and node I get an immediate connection.   

Using telnet I get a good connection and transfer of data.

Only error is 'Connection timed out"

Where can I start troubleshooting/

Re: #DRAWS oddity, GPS and ALSA headaches #draws

Basil Gunn
 

So things to do to help triage the problem:

* Keep a continuous eye on the temperature
In a console window
cd
cd n7nix/debug
watch ./pitemp.sh

* Using pitemp.sh note the temperature at boot & after 1/2 hour
* Remove the DRAWS hat, boot, note the temperature & after a 1/2 hour

* When you re-install DRAWS hat check for being off by one on the
40pin connector.
* Power down RPi with DRAWS hat, let RPi cool down
At cool power up is the DRAWS hat working?
* just run alsa-show.sh and look for something reasonable.
* Do a close visual inspection of the DRAWS hat & RPi.
* Anything look charred?

* Feel the USB cable powering your RPi does it feel warm?

More things to try as you suggested.

The Pi did not seem to be acting sick by itself.
Could it be the power source or should I not trust the PI at all?
It is suspicious to me that the RPi gives the low voltage symptom
(lightning bolt). Is it the power supply or is the DRAWS card loading
the RPi voltage source?

The following is not a bad idea but I would confirm that there is not
something seriously fried on the DRAWS hat first.

If you think I can trust the Pi, I could always take a different power
supply tactic and use the buck supply line in the DRAWs card for the Pi and
feed the display from a separate line.
/Basil

Jack Spitznagel <@flyingfrawg> writes:

Hmmm... and Pi was feeding the DRAWS card, not visa-versa... but that should
not be causing the CPU to overheat!
-Jack

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On
Behalf Of Basil Gunn
Sent: Tuesday, March 31, 2020 18:49
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] #DRAWS oddity, GPS and ALSA headaches


Ya that was a little too dramatic. While your RPi is running much hotter
than any of mine on the bench @ 69C it won't catch fire. It looks like the
"official" operating limit is around 85C and will start to thermally
throttle at around 82C which your RPi has already hit.

So yes your RPi is running suspiciously hot and no it probably won't catch
fire.
/Basil

Basil Gunn <@basil860> writes:

Hi Jack,
If I could give out prizes for most interesting symptoms you would
definitely get a prize.

First Pass at your console output.
Drivers are loading fine, no software faults, hardware is definitely
stressed, gps not working, codec not working

Second Pass at your console output.
Your RPI is running at over 150F and will soon catch fire if you don't
DISCONNECT THE POWER. From vcgencmd throttled=0xd0005

- Temperature limit has occurred
- Throttling has occurred
- Under voltage has occurred
The RPi is currently running throttled & under-voltage

Just recently I have seen someone else's RPi start running really hot.
Also check your 5V RPi wall wart. Is it warm/hot?

/Basil n7nix

See embedded below.

Jack Spitznagel <@flyingfrawg> writes:

Hi Basil,

Just when I thought everything was pretty stable, I started to get
protests from xastir that my GPS wasn't behaving.
... snip...
---- sensors
-rw-r--r-- 1 root root 171 Sep 19 2019 /etc/sensors.d/draws
rpi_volt-isa-0000
Adapter: ISA adapter
in0: N/A ALARM (LCRIT)

ads1015-i2c-1-48
Adapter: bcm2835 I2C adapter
+12V: +0.00 V
in5: +0.53 V
User ADC 1: +0.01 V
User ADC 2: +0.00 V


---- throttle
temp=69.3'C
throttled=0xd0005

SO:
Should I wait for image 16, try another install then?
Nope.

Do you see something that got flipped the wrong way by me when
running ./app_config.sh core?
Software config looks OK.




Re: #DRAWS oddity, GPS and ALSA headaches #draws

Jack Spitznagel
 

Hmmm... and Pi was feeding the DRAWS card, not visa-versa... but that should
not be causing the CPU to overheat!
-Jack

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On
Behalf Of Basil Gunn
Sent: Tuesday, March 31, 2020 18:49
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] #DRAWS oddity, GPS and ALSA headaches


Ya that was a little too dramatic. While your RPi is running much hotter
than any of mine on the bench @ 69C it won't catch fire. It looks like the
"official" operating limit is around 85C and will start to thermally
throttle at around 82C which your RPi has already hit.

So yes your RPi is running suspiciously hot and no it probably won't catch
fire.
/Basil

Basil Gunn <@basil860> writes:

Hi Jack,
If I could give out prizes for most interesting symptoms you would
definitely get a prize.

First Pass at your console output.
Drivers are loading fine, no software faults, hardware is definitely
stressed, gps not working, codec not working

Second Pass at your console output.
Your RPI is running at over 150F and will soon catch fire if you don't
DISCONNECT THE POWER. From vcgencmd throttled=0xd0005

- Temperature limit has occurred
- Throttling has occurred
- Under voltage has occurred
The RPi is currently running throttled & under-voltage

Just recently I have seen someone else's RPi start running really hot.
Also check your 5V RPi wall wart. Is it warm/hot?

/Basil n7nix

See embedded below.

Jack Spitznagel <@flyingfrawg> writes:

Hi Basil,

Just when I thought everything was pretty stable, I started to get
protests from xastir that my GPS wasn't behaving.
... snip...
---- sensors
-rw-r--r-- 1 root root 171 Sep 19 2019 /etc/sensors.d/draws
rpi_volt-isa-0000
Adapter: ISA adapter
in0: N/A ALARM (LCRIT)

ads1015-i2c-1-48
Adapter: bcm2835 I2C adapter
+12V: +0.00 V
in5: +0.53 V
User ADC 1: +0.01 V
User ADC 2: +0.00 V


---- throttle
temp=69.3'C
throttled=0xd0005

SO:
Should I wait for image 16, try another install then?
Nope.

Do you see something that got flipped the wrong way by me when
running ./app_config.sh core?
Software config looks OK.

Re: #DRAWS oddity, GPS and ALSA headaches #draws

Basil Gunn
 

Ya that was a little too dramatic. While your RPi is running much hotter
than any of mine on the bench @ 69C it won't catch fire. It looks like
the "official" operating limit is around 85C and will start to thermally
throttle at around 82C which your RPi has already hit.

So yes your RPi is running suspiciously hot and no it probably won't
catch fire.
/Basil

Basil Gunn <@basil860> writes:

Hi Jack,
If I could give out prizes for most interesting symptoms you would
definitely get a prize.

First Pass at your console output.
Drivers are loading fine, no software faults, hardware is definitely
stressed, gps not working, codec not working

Second Pass at your console output.
Your RPI is running at over 150F and will soon catch fire if you don't
DISCONNECT THE POWER. From vcgencmd throttled=0xd0005

- Temperature limit has occurred
- Throttling has occurred
- Under voltage has occurred
The RPi is currently running throttled & under-voltage

Just recently I have seen someone else's RPi start running really hot.
Also check your 5V RPi wall wart. Is it warm/hot?

/Basil n7nix

See embedded below.

Jack Spitznagel <@flyingfrawg> writes:

Hi Basil,

Just when I thought everything was pretty stable, I started to get protests
from xastir that my GPS wasn't behaving.
... snip...
---- sensors
-rw-r--r-- 1 root root 171 Sep 19 2019 /etc/sensors.d/draws
rpi_volt-isa-0000
Adapter: ISA adapter
in0: N/A ALARM (LCRIT)

ads1015-i2c-1-48
Adapter: bcm2835 I2C adapter
+12V: +0.00 V
in5: +0.53 V
User ADC 1: +0.01 V
User ADC 2: +0.00 V


---- throttle
temp=69.3'C
throttled=0xd0005

SO:
Should I wait for image 16, try another install then?
Nope.

Do you see something that got flipped the wrong way by me when running
./app_config.sh core?
Software config looks OK.

Re: #DRAWS oddity, GPS and ALSA headaches #draws

Jack Spitznagel
 

Ok.... now, I did not notice that set of TEMP lines in the output because I
was so focused on the sound device/ALSA and GPS lines. I have heatsinks on
the Pi. I have not heard that lack of ventilation of the Pi on a Sunfounder
display is an issue even with hats in place... I do not use a wallwart.

The Pi has seemed to run happily off the aux 5V USB power out from the
Sunfounder 10' display. The display is fed from a 25A 13.9V power supply via
3A fused line from a multi-powerpole type distro panel. No problems in over
a year 'til now. I did notice the undervoltage lightning bolt on the X
display however. A crappy old DVM says the voltage is 13.77 at the plug to
the display with all other devices on the buss operating. I don't have a USB
voltage monitor around, so I don't know what the display USB line is putting
out but obviously the Pi thinks it is low.

The Pi did not seem to be acting sick by itself. Could it be the power
source or should I not trust the PI at all?

If you think I can trust the Pi, I could always take a different power
supply tactic and use the buck supply line in the DRAWs card for the Pi and
feed the display from a separate line.

Thanks for playing Doc!

Jack - KD4IZ

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On
Behalf Of Basil Gunn
Sent: Tuesday, March 31, 2020 18:16
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] #DRAWS oddity, GPS and ALSA headaches


Hi Jack,
If I could give out prizes for most interesting symptoms you would
definitely get a prize.

First Pass at your console output.
Drivers are loading fine, no software faults, hardware is definitely
stressed, gps not working, codec not working

Second Pass at your console output.
Your RPI is running at over 150F and will soon catch fire if you don't
DISCONNECT THE POWER. From vcgencmd throttled=0xd0005

- Temperature limit has occurred
- Throttling has occurred
- Under voltage has occurred
The RPi is currently running throttled & under-voltage

Just recently I have seen someone else's RPi start running really hot.
Also check your 5V RPi wall wart. Is it warm/hot?

/Basil n7nix

See embedded below.

Jack Spitznagel <@flyingfrawg> writes:

Hi Basil,

Just when I thought everything was pretty stable, I started to get
protests from xastir that my GPS wasn't behaving.
... snip...
---- sensors
-rw-r--r-- 1 root root 171 Sep 19 2019 /etc/sensors.d/draws
rpi_volt-isa-0000
Adapter: ISA adapter
in0: N/A ALARM (LCRIT)

ads1015-i2c-1-48
Adapter: bcm2835 I2C adapter
+12V: +0.00 V
in5: +0.53 V
User ADC 1: +0.01 V
User ADC 2: +0.00 V


---- throttle
temp=69.3'C
throttled=0xd0005

SO:
Should I wait for image 16, try another install then?
Nope.

Do you see something that got flipped the wrong way by me when running
./app_config.sh core?
Software config looks OK.

Re: #DRAWS oddity, GPS and ALSA headaches #draws

Basil Gunn
 

Hi Jack,
If I could give out prizes for most interesting symptoms you would
definitely get a prize.

First Pass at your console output.
Drivers are loading fine, no software faults, hardware is definitely
stressed, gps not working, codec not working

Second Pass at your console output.
Your RPI is running at over 150F and will soon catch fire if you don't
DISCONNECT THE POWER. From vcgencmd throttled=0xd0005

- Temperature limit has occurred
- Throttling has occurred
- Under voltage has occurred
The RPi is currently running throttled & under-voltage

Just recently I have seen someone else's RPi start running really hot.
Also check your 5V RPi wall wart. Is it warm/hot?

/Basil n7nix

See embedded below.

Jack Spitznagel <@flyingfrawg> writes:

Hi Basil,

Just when I thought everything was pretty stable, I started to get protests
from xastir that my GPS wasn't behaving.
... snip...
---- sensors
-rw-r--r-- 1 root root 171 Sep 19 2019 /etc/sensors.d/draws
rpi_volt-isa-0000
Adapter: ISA adapter
in0: N/A ALARM (LCRIT)

ads1015-i2c-1-48
Adapter: bcm2835 I2C adapter
+12V: +0.00 V
in5: +0.53 V
User ADC 1: +0.01 V
User ADC 2: +0.00 V


---- throttle
temp=69.3'C
throttled=0xd0005

SO:
Should I wait for image 16, try another install then?
Nope.

Do you see something that got flipped the wrong way by me when running
./app_config.sh core?
Software config looks OK.

Re: #DRAWS oddity, GPS and ALSA headaches #draws

Jack Spitznagel
 

Hi Basil,

Just when I thought everything was pretty stable, I started to get protests
from xastir that my GPS wasn't behaving. Dropped out of xastir and ran
gpsmon only receive a blank stare... Unfortunately did not check to see that
the alsa config was recognized... but for some 23:59EDT reason put a new SSD
with image 15 in and did a core config. (I do have the old microSD card
saved).

Well - things seemed to be OK as I followed the setup steps until I ran
alsa-show.sh and it gave a matrix of nothing entries, then gpsmon gave me a
blank stare.

I then ran showudrc.sh and got the following which seems to indicate that I
hosed the configuration somehow or the DRAWS card is behaving abnormally:
-----------------------------------------------------------------------
pi@kd4izdraws1:~/n7nix/config $ showudrc.sh
==== Sound Card ====
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
==== ALSA Controls for Radio Tansmit ====
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
LO Driver Gain L: R:
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
PCM L: R:
amixer: Mixer hw:1 load error: Remote I/O error
==== ALSA Controls for Radio Receive ====
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
ADC Level L: R:
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
IN1 L:[] R:[]
IN2 L:[] R:[]
==== Pi Ver ====
Pi 3 Model B+, Rev 1.3, Mfg by Sony UK
Has WiFi
==== udrc Ver ====
Found a DRAWS

HAT ID EEPROM
Name: hat
Product: Digital Radio Amateur Work Station
Product ID: 0x0004
Product ver: 0x0405
UUID: 6170bac5-b90e-462b-8dec-8f564d9cbbe5
Vendor: NW Digital Radio

==== sys Ver ====
----- image version
2020 01 23 09:25:01 PST: SD image version: nwdr15
----- /proc/version
Linux version 4.19.97-v7+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG
crosstool-ng-1.22.0-88-g8460611)) #1294 SMP Thu Jan 30 13:15:58 GMT 2020

----- /etc/*version: 10.3

----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

----- lsb_release
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 10 (buster)
Release: 10
Codename: buster

---- systemd
Static hostname: kd4izdraws1
Icon name: computer
Machine ID: 27ac1f0c20904cb7a960920e966db545
Boot ID: 5c158adeda3043cda9402f8dc718f6d3
Operating System: Raspbian GNU/Linux 10 (buster)
Kernel: Linux 4.19.97-v7+
Architecture: arm

---- modules
snd_soc_tlv320aic32x4_i2c 16384 48
snd_soc_tlv320aic32x4 40960 1 snd_soc_tlv320aic32x4_i2c
snd_soc_core 192512 4
snd_soc_simple_card_utils,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_soc_
simple_card
snd_pcm 102400 5
snd_pcm_dmaengine,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_bcm2835,snd_
soc_core
snd 73728 12
snd_compress,snd_timer,snd_soc_tlv320aic32x4,snd_bcm2835,snd_soc_core,snd_pc
m

---- kernel
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==================-============-============-===========================
======
ii raspberrypi-kernel 1.20200212-1 armhf Raspberry Pi bootloader

---- Codec drivers
Found: snd-soc-tlv320aic32x4-i2c.ko, OK
Found: snd-soc-tlv320aic32x4.ko, OK
Directory: /proc/device-tree/soc/i2c@7e804000/tlv320aic32x4@18 exists and
status is okay

---- syslog

---- dmesg


----- Dire Wolf DEVELOPMENT version 1.6 D (Jan 6 2020)

==== Filesystem ====
/dev/root 29G 5.3G 22G 20% /

==== boot config ====
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d

# Flush all overlays, ie. deprecated overlays loaded from eeprom
dtoverlay=
# enable udrc/draws if no eeprom
dtoverlay=draws,alsaname=udrc
force_turbo=1
# Enable audio (loads snd_bcm2835)
dtparam=audio=on

---- gpsd
/usr/local/sbin/gpsd
gpsd: 3.20 (revision 3.20)
● gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset:
enabled)
Active: active (running) since Tue 2020-03-31 16:36:26 EDT; 4min 41s ago
Process: 509 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS
$DEVICES (code=exited, status=0/SUCCESS)
Main PID: 511 (gpsd)
Tasks: 1 (limit: 2200)
Memory: 1.1M
CGroup: /system.slice/gpsd.service
└─511 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0

Mar 31 16:36:26 kd4izdraws1 systemd[1]: Starting GPS (Global Positioning Sy
…n...
Mar 31 16:36:26 kd4izdraws1 systemd[1]: Started GPS (Global Positioning Sys
…mon.
Hint: Some lines were ellipsized, use -l to show in full.

---- chrony
crw------- 1 root root 241, 0 Mar 31 16:36 /dev/pps0
crw-rw---- 1 root dialout 239, 0 Mar 31 16:36 /dev/ttySC0
crw-rw---- 1 root dialout 239, 1 Mar 31 16:36 /dev/ttySC1
-- chrony sources
210 Number of sources = 6
MS Name/IP address Stratum Poll Reach LastRx Last sample

============================================================================
===
#? GPS 0 3 0 - +0ns[ +0ns] +/-
0ns
#? PPS 0 3 0 - +0ns[ +0ns] +/-
0ns
^- darwin.kenyonralph.com 2 6 77 107 -2007us[-3418us] +/-
79ms
^- atl1.ntp7.mattnordhoff.n> 2 6 177 43 -1306us[-1697us] +/-
54ms
^* ellone.fdisk.io 2 6 177 41 -249us[ -641us] +/-
14ms
^- fin.mattnordhoff.net 2 6 177 42 +270us[ -122us] +/-
50ms
-- chrony tracking
Reference ID : 30FED930 (ellone.fdisk.io)
Stratum : 3
Ref time (UTC) : Tue Mar 31 20:40:26 2020
System time : 0.000266782 seconds slow of NTP time
Last offset : -0.000392392 seconds
RMS offset : 0.001072069 seconds
Frequency : 2.079 ppm fast
Residual freq : -2.085 ppm
Skew : 17.376 ppm
Root delay : 0.027547063 seconds
Root dispersion : 0.001782908 seconds
Update interval : 64.9 seconds
Leap status : Normal
-- chrony sourcestats
210 Number of sources = 6
Name/IP Address NP NR Span Frequency Freq Skew Offset Std
Dev
============================================================================
==
GPS 0 0 0 +0.000 2000.000 +0ns
4000ms
PPS 0 0 0 +0.000 2000.000 +0ns
4000ms
darwin.kenyonralph.com 6 4 136 +3.546 18.414 -1660us
337us
atl1.ntp7.mattnordhoff.n> 7 3 200 +0.169 7.690 -1323us
211us
ellone.fdisk.io 7 5 201 -2.085 21.671 -87us
586us
fin.mattnordhoff.net 7 4 201 -0.646 19.456 +210us
437us

---- sensors
-rw-r--r-- 1 root root 171 Sep 19 2019 /etc/sensors.d/draws
rpi_volt-isa-0000
Adapter: ISA adapter
in0: N/A ALARM (LCRIT)

ads1015-i2c-1-48
Adapter: bcm2835 I2C adapter
+12V: +0.00 V
in5: +0.53 V
User ADC 1: +0.01 V
User ADC 2: +0.00 V


---- throttle
temp=69.3'C
throttled=0xd0005

---- locale
Locale country codes consistent among WiFi cfg file, iw reg & X11: US
core_config.sh has been run 1 time(s)
pi@kd4izdraws1:~/n7nix/config $
-----------------------------------------------------------------------

I've tried my best to follow the output above to troubleshoot, but have a
bit of difficulty with what I see other than the obvious.

SO:
Should I wait for image 16, try another install then?
Do you see something that got flipped the wrong way by me when running
./app_config.sh core?

Re: DRAWS

Paul Noa
 

Thanks Basil,

I know I have not  changed to LN2 yet,  as I am troubleshooting NO XMIT.

I am using your handy script: ptt_ctrl, thank you. I see the  respective LEDs for L or R PTT come on and go off when I toggle them,

I see the respective GPIO pins ie io12 & io23 go high when I toggle them.

However I do not get an output on either MiniDin6 connector at anytime with the exception of SQL which is high all the time.

I suspect I might have killed Q1 when I was mis-wired but I have never touched the right connector before today (and only with a scope probe) and therefore would expect Q2 to still be good.

What say you?

Paul

Re: DRAWS

Basil Gunn
 

A brief look at the ICOM F521 manual indicates that it does NOT have
discriminator output so do NOT route IN1 ALSA control ie. your left
channel is currently configured to use discriminator out & it shouldn't be.
This assumes that you have a properly wired cable with discriminator out
on pin 4 & AFOUT on pin 5 referencing the mDin6 cable.

Paul Noa <pauljnoa@...> writes:

~/n7nix/debug $ ./ax25-showcfg.sh -d
Debug mode on
===== ALSA Controls for Radio Transmit =====
LO Driver Gain L:[-6.00dB] R:[-6.00dB]
PCM L:[-6.00dB] R:[-25.00dB]
DAC Playback PT L:[P3] R:[P3]
LO Playback CM [Full Chip]

===== ALSA Controls for Radio Receive =====
ADC Level L:[-6.00dB] R:[2.00dB]
IN1 L:[10 kOhm] R:[Off]
IN2 L:[Off] R:[10 kOhm]
CM L:[10 kOhm] R:[10 kOhm]

Re: DRAWS

Paul Noa
 

~/n7nix/debug $ ./ax25-showcfg.sh -d
Debug mode on
 
 === Display kissparms & ax25dev-parms
Debug: portname=udr0, portcfg=port0
AX.25: udr0 speed: 1200
parse baud_1200 section for udr0
port: 0, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: 3000, t2 timeout: 1000
Debug: portname=udr1, portcfg=port1
AX.25: udr1 speed: 1200
parse baud_1200 section for udr1
port: 1, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: 3000, t2 timeout: 1000
 == kissparms from /etc/ax25/ax25-upd
        $KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
            $KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
            $KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
            $KISSPARMS -p ${PORTNAME_2} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
        $KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
 
 ===== ax.25 config
Found directory: /proc/sys/net/ax25/ax0
ax25_default_mode: 0
backoff_type: 0
connect_mode: 2
dama_slave_timeout: 180000
extended_window_size: 32
idle_timeout: 900000
ip_default_mode: 0
maximum_packet_length: 255
maximum_retry_count: 6
protocol: 0
standard_window_size: 2
t1_timeout: 3000
t2_timeout: 1000
t3_timeout: 300000
 
Found directory: /proc/sys/net/ax25/ax1
ax25_default_mode: 0
backoff_type: 0
connect_mode: 2
dama_slave_timeout: 180000
extended_window_size: 32
idle_timeout: 900000
ip_default_mode: 0
maximum_packet_length: 255
maximum_retry_count: 6
protocol: 0
standard_window_size: 2
t1_timeout: 3000
t2_timeout: 1000
t3_timeout: 300000
 
 
 ===== ALSA Controls for Radio Transmit =====
LO Driver Gain  L:[-6.00dB]     R:[-6.00dB]
PCM             L:[-6.00dB]     R:[-25.00dB]
DAC Playback PT L:[P3]          R:[P3]
LO Playback CM  [Full Chip]
 
 ===== ALSA Controls for Radio Receive =====
ADC Level       L:[-6.00dB]     R:[2.00dB]
IN1             L:[10 kOhm]     R:[Off]
IN2             L:[Off]         R:[10 kOhm]
CM              L:[10 kOhm]     R:[10 kOhm]
 
===== Port baudrate
DireWolf: udr0 speed: 1200, udr1 speed: 1200
AX.25:    udr0 speed: 1200, udr1 speed: 1200
 
===== axports
udr0        KO4BCZ-10            9600    255     2       Winlink port
udr1        KO4BCZ-1             9600    255     2       Direwolf port
 
 ===== ax25d.conf
[KO4BCZ-10 VIA udr0]
NOCALL   * * * * * *  L
default  * * * * * *  - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U
#
[KO4BCZ VIA udr0]
NOCALL   * * * * * *  L
default  * * * * * *  - pi /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d
 
 ===== wl2k.conf
paclink-unix not configured.

Re: UDRCII with RT Systems Cable for CAT Control & mini 6DIN and Yaesu FT-450D --PTT engaged but 0 Watts transmitted #wsjt-x #ft-8

Basil Gunn
 

Looking at my notes to see what might be relevant because I do not own
an FT-450.

* Re: FT-817, I could only get this radio to work by disconnecting pin 6
(squelch) on the mDin6 cable.
https://github.com/nwdigitalradio/n7nix/blob/master/docs/RADIO_APP_NOTES.md

* From your config you are using the left DRAWS connector.
* Adjust the power output slider on the right side of the wsjt-x screen?
* Verify using draws manager
* Input from Receiver: AF (pin5) for your left channel.
* Verify the setting in the Radio that tells it to use the Data
connector for transmit audio, instead of from the Microphone.
* You want MODE = DAT(a) instead of MODE = SSB.
* The serial settings are for configuring rig control which most likely
has no effect on the DRAWS hat configuration.
Make sure rig control is affecting the left channel.
* Look at pertinent ALSA settings alsa-show.sh
* Check out Steve McGrane's video #5 DRAWS GPS & FT8
https://www.youtube.com/watch?v=5lxvVD1-0lk&feature=youtu.be
* In the groups.io forum for this group use the search option for wsjt
/Basil n7nix


TG9AOR <@TG9AOR> writes:

Hello Friends. I have this setup on WSJT-X that came with the DRAWS Image (WSJT-X v2.0.1 7ddcb7)
Radio Tab Audio Tab
Rig: FT-450 Input plughw:CARD=udrc,DEV=0 Mono
Serial Port /dev/ttyUSB0 Output plughw:CARD=udrc,DEV=0 Mono
Baud Rate 38400
Data Bits Default
Stop Bits Default
HandShake Default
Force Control Lines DTR Blank
Force Control Lines RTS Blank
PTT Method CAT
Mode DATA/PKT
Split Operation None

I am able to decode. Curiously, with this same cable, on the FT817(I
am referring to the UDRC cable) I cannot hear the static, maybe
because of the squelch pin John told me back in 2018, must behave
differently on the 817/857.

So with this setup the PTT activates, but 0 watts are transmitted.
Thanks for reading my message and God Bless everyone. 73 de TG9AOR

Re: Compass image V15, XASTIR, Missing Library?

Basil Gunn
 

Mike,
Thanks for the feedback.
I have an nwdr16.img candidate in testing that has those libraries
installed.
/Basil

Mike B <kf5dey@...> writes:

I used your recommended sudo apt-get install shapelib libshp-dev libgeotiff-dev libwebp-dev libgraphicsmagick1-dev

The following additional packages will be installed:
libbz2-dev libexif-dev libexif-doc libgeotiff2 libjbig-dev libjpeg-dev
libjpeg62-turbo-dev liblcms2-dev liblzma-dev libtiff-dev libtiffxx5
libwmf-dev libzstd-dev

And that solved it...I hope the list of packages helps.

Mike
KF5DEY