Oh, and for those following along at home...

The command to transmit a test tone is...set a low power and unused freq.

first stop ax25  
in /home/pi/bin/

sudo ./ax25-stop

then in /home/pi/n7nix/deviation/

./measure_deviate.sh -c left

when you are done...  ./ax25-start

-because mine is plugged into the left...the program defaults to the right-

I mean I set the Analog Gain to 0db and the Digital gain to around 15db.   That gave me a good tone through the HT.

I figured it was something obvious...

I still need to tweak the settings, but this is definitely the problem area.

So in my case I have to set the Audio to 0db and Digital to a high number..

I can connect to the winlink node.

with the digital set to high  (15-20db) I get the connections and was able to transmit a message...

...but occasionally I get read udr0: connection timed out. 

This pops up WHILE my radio is still transmitting...in the particular instance it was just a reply to your greeting, so not a long message...but in looking at the reply it generated...there was a whole list of recipients...not sure what was going on...not your fault.

So anyway...seems to be working now thanks to your help.

I really don't understand the audio settings (Draws Manager)...can you explain a bit more about what the settings mean, and what is going on?

Yes I was monitoring the ALC and at low power the ALC is high...but at 50w the ALC is right at the sweet spot...I really don't understand that either.

I don't have a scope adapter yet to monitor the output...but it seems to be fine doing the audio test with my HT.

Thanks again,

Mike
KF5DEY

really! I checked every pin on both connectors while toggling the PTT

I'm out of ideas. Please talk to Bryan.

Basil,
really! I checked every pin on both connectors while toggling the PTT

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

Make sure you are measuring the correct pin.
Also disconnect the cable from your radio in case it's loading that
signal.

http://www.wa8lmf.net/6-Pin-MiniDin-Data-Connector/index.htm

Happy that your setup is working for you!
Have some fun. /Basil n7nix

TG9AOR <qrz@tg9aor.net> writes:

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.

The 6th argument in the axports line is an arbitrary description and
will not affect anything, except as a source of confusion.

The thing to note is the way the scripts set up ax.25 packet is udr0 is
the left mDin6 connector & udr1 is the right mDin6 connector. For your
case I'm assuming you are using the left mDin6 connnector and we will
just ignore udr1, the right connector for the time being.

/Basil n7nix

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@gmail.com> writes:

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

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

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

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. 

Mike B <kf5dey@gmail.com> 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]

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

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

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/

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 <kd4iz@frawg.org> 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 <basil@pacabunga.com> 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 <kd4iz@frawg.org> 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.

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

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 <basil@pacabunga.com> writes: