Date   
Re: Draws manager - 'successful' configurations #drawsmanager #draws-manager

 

Added to git repository

On Thu, Apr 2, 2020 at 12:46 PM Mike B <kf5dey@...> wrote:
./usr/local/var/draws-manager/webapp/radios.json

{
        "radio":"FT-857D FM AX25",
        "audiorx":"af",
        "negresistor":"10 kOhm",
        "powertune":"PTM_P3",
        "pcmvol":"15.00db",
        "lodigvol":"0.00db",
        "adcvol":"0.0db",
        "dacswitch":"on",
        "dacplaysw":"on",
        "comments":""
    }



--
John D. Hays
Kingston, WA
K7VE

 

Re: Draws manager - 'successful' configurations #drawsmanager #draws-manager

Mike B
 

./usr/local/var/draws-manager/webapp/radios.json

{
        "radio":"FT-857D FM AX25",
        "audiorx":"af",
        "negresistor":"10 kOhm",
        "powertune":"PTM_P3",
        "pcmvol":"15.00db",
        "lodigvol":"0.00db",
        "adcvol":"0.0db",
        "dacswitch":"on",
        "dacplaysw":"on",
        "comments":""
    }

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

Basil Gunn
 

Hi Jack,
Taking your responses out of order.

it ain't worth fretting about. Solution found.
Yep, totally agree. Get another RPi and continue having some fun. A
friend of mine had exactly the same symptom on a Pi 3B. I have 6 RPi's
on my bench running 24/7 and haven't seen the problem with any yet. At
least two of the RPi's are RMS Gateways that have been running for a
couple of years.

I am going to add a cron job to all my RPis that check's being throttle
& over temperature as in the case you had where vcgencmd get_throttled
returned 0xd0005.

vcgencmd get_throttled
https://www.raspberrypi.org/documentation/raspbian/applications/vcgencmd.md

// Is it OK to run a Pi4 off the DRAWS buck regulator? - I vaguely remember
discussion concluding it was.
Yep. I have 2 RPi 4's (2GB, 4GB) running powered by the DRAWS 12 V buck
regulator with no problem. Actually all my RPi's run from 12 V. I never
have problems with under voltage & it is a lot easier to manage a bunch
of power pole connectors than a bunch of wall warts plugged into a power
strip.

// it is on all 40 pins correctly - that is one of my personal QC checks -
burnt up my first pi making that error
You are not an RPi expert unless you burn at least one up.
I killed two due to mDin6 control cable laying on antenna coax. Didn't
learn my lesson the first time.

Glad to hear you are back up & running.
/Basil n7nix

Jack Spitznagel <@flyingfrawg> writes:

Hi Basil,

Good news/bad news story:
DRAWS hat appears to be OK, the Pi3B+ is a sick puppy. Silver lining:
discovered just how fast everything DRAWS seems to respond with a Pi4. That
may be the replacement board I pick. The 1GB versions have gotten fairly
cheap.

See inline after your suggestions below:

* Keep a continuous eye on the temperature In a console window cd cd
n7nix/debug watch ./pitemp.sh
// never bothered with pitemp.sh - just used vcgencmd measure_temp to start
with & GPU temp
// kept rising, so removed the DRAWS board, let the Pi cool, booted vanilla
Rasbian Buster
// and the GPU temp headed toward 65C very quickly. Both GPU and CPU sinks
were very hot to touch so
// shut it down so not to waste time to create pitemp.sh on the sick Pi in
vanilla buster.
// AT this point I decided the Pi3B+ board was ailing and did not push it.
* Using pitemp.sh note the temperature at boot & after 1/2 hour
// Skipped this as noted above
* Removed the DRAWS hat, boot, note the temperature & after a 1/2 hour
// Skipped, see above
* When you re-install DRAWS hat check for being off by one on the 40pin
connector.
// it is on all 40 pins correctly - that is one of my personal QC checks -
burnt up my first pi making that error

* 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.
// I did this and the symptoms were the same, nothing in alsa-show.sh
output and nothing
// from gpsmon other than it "could not find the device at localhost port
2XXX" whatever.

* Do a close visual inspection of the DRAWS hat & RPi.
* Anything look charred?
// Nope! Just two very hot to touch processors - both have heat sinks on
them too! That may have
// been what prevented a total meltdown.
* Feel the USB cable powering your RPi does it feel warm?
// Neither power cable configuration got 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?
// wired the buck regulator feed to the display power line and saw the same
symptoms with the Pi3B+
// THEN I subbed in a Pi4 (4GB) that I have been playing with and it fired
right up. DRAWS came up and
// behaved normally for alsa-show and gpsmon including no lightning bolt
while running off the buck
// regulator on the DRAWS board.
QUESTION:
// Is it OK to run a Pi4 off the DRAWS buck regulator? - I vaguely remember
discussion concluding it was.

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.
SO: The Pi4 is good with the DRAWS but the Pi3 is the second I have
consigned to the junk bin. Something probably munged up the GPIO lines
needed by the sound and GPS subsystems - have no idea what and @ <$30 for a
replacement, it ain't worth fretting about. Solution found.

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

Jack Spitznagel
 

Hi Basil,

Good news/bad news story:
DRAWS hat appears to be OK, the Pi3B+ is a sick puppy. Silver lining:
discovered just how fast everything DRAWS seems to respond with a Pi4. That
may be the replacement board I pick. The 1GB versions have gotten fairly
cheap.

See inline after your suggestions below:

* Keep a continuous eye on the temperature In a console window cd cd
n7nix/debug watch ./pitemp.sh
// never bothered with pitemp.sh - just used vcgencmd measure_temp to start
with & GPU temp
// kept rising, so removed the DRAWS board, let the Pi cool, booted vanilla
Rasbian Buster
// and the GPU temp headed toward 65C very quickly. Both GPU and CPU sinks
were very hot to touch so
// shut it down so not to waste time to create pitemp.sh on the sick Pi in
vanilla buster.
// AT this point I decided the Pi3B+ board was ailing and did not push it.
* Using pitemp.sh note the temperature at boot & after 1/2 hour
// Skipped this as noted above
* Removed the DRAWS hat, boot, note the temperature & after a 1/2 hour
// Skipped, see above
* When you re-install DRAWS hat check for being off by one on the 40pin
connector.
// it is on all 40 pins correctly - that is one of my personal QC checks -
burnt up my first pi making that error

* 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.
// I did this and the symptoms were the same, nothing in alsa-show.sh
output and nothing
// from gpsmon other than it "could not find the device at localhost port
2XXX" whatever.

* Do a close visual inspection of the DRAWS hat & RPi.
* Anything look charred?
// Nope! Just two very hot to touch processors - both have heat sinks on
them too! That may have
// been what prevented a total meltdown.
* Feel the USB cable powering your RPi does it feel warm?
// Neither power cable configuration got 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?
// wired the buck regulator feed to the display power line and saw the same
symptoms with the Pi3B+
// THEN I subbed in a Pi4 (4GB) that I have been playing with and it fired
right up. DRAWS came up and
// behaved normally for alsa-show and gpsmon including no lightning bolt
while running off the buck
// regulator on the DRAWS board.
QUESTION:
// Is it OK to run a Pi4 off the DRAWS buck regulator? - I vaguely remember
discussion concluding it was.

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.
SO: The Pi4 is good with the DRAWS but the Pi3 is the second I have
consigned to the junk bin. Something probably munged up the GPIO lines
needed by the sound and GPS subsystems - have no idea what and @ <$30 for a
replacement, it ain't worth fretting about. Solution found.

Re: Update WSJTX #draws #wsjt-x

TG9AOR
 

Hello Basil. I went ahead and updated as you instruct in this thread. As I did this, this message came up:
authentication required to restart 'dphys-swapfile.service
multiple identities can be used for authentication:
1,,,(pi)
2 root


I did not pick one, it went with user pi. Hopefully I did the right thing. Thanks.

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

Mike B
 

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-

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

Mike B
 

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.

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

Mike B
 

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

Re: DRAWS

Basil Gunn
 

really! I checked every pin on both connectors while toggling the PTT
I'm out of ideas. Please talk to Bryan.

Re: DRAWS

Paul Noa
 

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

Re: DRAWS

Basil Gunn
 

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

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
 

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

TG9AOR <@TG9AOR> writes:

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: PAT with DRAWS on VHF

Basil Gunn
 

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

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