I had a closer look at the boards. Everywhere there is a 101 on the old board, there is a 104 on the new board. Even on what must be audio in. Is this part of the revision?

Brendan O'Neill <km4hrr@gmail.com> writes:

I was asked thia moring if the gateway config on DRAWS is running RMS
packet and/or RMS Relay. I am unsure how to answer that

RMS Packet and RMS Relay are Windows programs so no to both of those.
If you look on the https://winlink.org/RMSChannels site & click on
Gateway Versions, search for KM4HRR-10 you are running (Linux) RMS Gateway.

Also, you mentioned offering directions on how to update the
advertised freq my gateway is monitoring. Please so so.

Edit file /etc/rmsgw/channels.xml <frequency field>
Frequency is in Hertz.

/Basil n7nix

I was asked thia moring if the gateway config on DRAWS is running RMS packet and/or RMS Relay. I am unsure how to answer that

Also, you mentioned offering directions on how to update the advertised freq my gateway is monitoring. Please so so.

Respectfully,
Brendan
km4hrr@gmail.com

Hello,
I, too, tried to use the support form on the website, but i received no answer.

Is it working?

What deviation should I shoot for on the tm-v71a?

From page 83 of the Kenwood TM-V71a manual
Select 1200 or 9600 bps for the data transfer rate, depending on your TNC.
1200 bps: Transmit data input (PKD) sensitivity is 40 mV p-p , input impedance is 10 kΩ.
9600 bps: Transmit data input (PKD) sensitivity is 2 V p-p , input impedance is 10 kΩ.

I use the 9600 bps connection even with 1200 baud data which just selects the
Kenwood discriminator output (PR9 Output 9600 (bps)) ie. pin 4 on the
mDin6 connector is selected by ALSA setting IN1.

Then you can control your packet data speed with a single setting in
/etc/direwolf.conf MODEM 1200 or MODEM 9600. Make sure your Kenwood
Menu 518 is set to DATSPD 9600.

/Basil n7nix

David Lowry <huskyrunnr@msn.com> writes:

Well, I must have done something to the first board during my cable fiasco a year ago.

I’ve had a tm-v71a since the first of last summer, new-in-box until this morning. I set it up. This eliminates my mad cable skills and gives me some known ALSA parameters from setalsa-tmv71a.sh. PCM for the old hat needs to be set much lower. PCM for the new hat is much closer to the script values, not sure what deviation the script is shooting for. Audio In looks right for the new board as well.

Bryan, is it possible to fubar that ti chip in a way that increases sensitivity? Because that is what it appears I have done. In any case, both hats work reliably on both xmit and rev.

What deviation should I shoot for on the tm-v71a?

Rcv, not rev. Thanks spellcheck.

Well, I must have done something to the first board during my cable fiasco a year ago.

I’ve had a tm-v71a since the first of last summer, new-in-box until this morning. I set it up. This eliminates my mad cable skills and gives me some known ALSA parameters from setalsa-tmv71a.sh. PCM for the old hat needs to be set much lower. PCM for the new hat is much closer to the script values, not sure what deviation the script is shooting for. Audio In looks right for the new board as well.

Bryan, is it possible to fubar that ti chip in a way that increases sensitivity? Because that is what it appears I have done. In any case, both hats work reliably on both xmit and rev.

What deviation should I shoot for on the tm-v71a?

Hi Basil,

Thanks Basil,

 

“Things to try for more data points.
1. swap RPi SD cards
2. swap DRAWS hat”

I’ll try these things.

“One unit has a power-down switch?
dtoverlay=gpio-shutdown,gpio_pin=6,gpio_pull=up”

Correct, on my old hardware, I loaded nwdr14 and then added my embellishments. No embellishments with the new hardware.

“What radio (make, model) are you using?”

Yaesu FT-2980.

“You set the lowest level (PTM_P1) for the DAC PowerTune control (DAC
Playback PT) which drops the LO Drive output voltage down to 330mv
P-P. What happens if you use PTM_P2?”

For the following, showudrc attached, I used only the RPi3, a single sd card with new nwdr14 image updated by piwiz and git pull on n7nix directory. The mic gain on the radio was set to 5. I swapped DRAWS hats. I still get a large difference in sensitivity to Audio In from the radio. For Audio Out, LO was -6 dB in all cases. I nulled the carrier for both hats at PT_P1, PT_P2, and PT_P3. I used

measure_deviate.sh –f 1042 –c left

PT_P3:

Old DRAWS; PCM_-35.5 dB, New DRAWS; PCM_-13.5 dB

PT_P2:

Old DRAWS; PCM_-30.5 dB, New DRAWS; PCM_-9 dB

PT_P1

Old DRAWS; PCM_-21 dB, New DRAWS; PCM_1 dB

I still worry about my DIY cable. I had problems making it correctly, got what I thought was correct and everything worked fine. Then, the new board came and the different audio levels blew my confidence. The Audio In level for the KPC3+ is closer to the old draws board. But I made that cable too.

David

The libjpeg.so.9 requirement issue for fldigi was fixed in the
installation scripts some time ago.

If you give me something to work with, like the console output of
showudrc.sh, I may be able to help you with your direwolf problem.
If fldigi does not start, then run it from a console and send me the
output.

/Basil

Chris Robinson KF6NFW DMR ID 3153250 <kf6nfw@gmail.com> writes:

David,

Trying to understand differences between the two units you are
using.

Things to try for more data points.
1. swap RPi SD cards
2. swap DRAWS hat

One unit has a power-down switch?
dtoverlay=gpio-shutdown,gpio_pin=6,gpio_pull=up

What radio (make, model) are you using?

You set the lowest level (PTM_P1) for the DAC PowerTune control (DAC
Playback PT) which drops the LO Drive output voltage down to 330mv
P-P. What happens if you use PTM_P2?

See comment below.

David Lowry <huskyrunnr@msn.com> writes:

An RPi3 plus an older draws hat is running with nwdr14 and adc gain
set to 0 dB. Audio knob from the radio is set to give an average level
of 50 in received direwolf packets.

An RPi4 plus the new draws hat with all else equal, I have to either
crank the audio knob up a quarter turn or leave it and adjust adc gain
to +7 dB in alsamixer to get the same average level 50 in direwolf.

Both sets of hardware were updated through piwiz and git pull on the
n7nix dir.

direwolf is decoding equally well in either case so this may be a
non-issue from a practical perspective. But should this be a concern?
If not, I’ll happily move on.

Thanks for any insight. I will not be able to respond with any
requested console output until this evening. There are some snd_card_*
differences between the boards from showudrc if that could be
relevant.

BTW, thank you Basil for your scripts. My students studied fm side
band theory and ultimately used measure_deviate along with gnu radio
and rtf-sdr to put it into practice. The project was well received.

Thanks and happy to hear that you found the script useful. Appreciate
the feedback.
/Basil n7nix

Once again I thank you very much for your invaluable help for
progressing into RaspBerry Pi and DRAWS usage with AX.25.

You are welcome & thanks for all your feedback.

Reading doc files is quite easy but it does not preclude some
missinterpretations by me as you have noticed.

Documentation is not my forte.

I want to achieve a complete set up of an FPAC NODE using DRAWS based on
nwdr image that should simplify considerably the configuration with your
scripts help. However I am not yet finished !

Sounds cool. Let me know how it goes.

I still need ax25ipd configuration for AX25<-->UDP encapsulation of
ROSE/FPAC and LinFBB frames toward Internet. I guess this should be
added into ax25-start or built into a kind of ax25ipd-start. Then I will
need something like uronode conf and install for FPAC node utilities.

Look forward to seeing your result!

Meanwhile I found an error when trying to use measure deviation script.
The first case of failure is when direwolf is started and prevents using
sound device as you noticed. You already wrote instructions in order to
remove direwolf with stop AX.25.

The measure_deviate.sh script checks if direwolf is running & if it is
runs the ax25-stop script which should free up the audio device.

The second cause of failure is when
user is sudo and your scripts fails finding /home/root/bin/ax25-stop
script for $USER= root

Yes that is a bug, thanks!
To fix I made measure_deviate.sh, ax25-start & ax25-stop root agnostic

Changes for fix are checked into n7nix repo.

6025db1ab55b997d935fc31c75d7fd4b266988de Make running script root agnostic.
M deviation/README.md
M deviation/measure_deviate.sh
00dc61dcb2b4084288735c970c0cba7cd72412a6 Make consistent with ax25-start, root agnostic.
M systemd/bin/ax25-stop

To take advantage of these changes:
cd
cd n7nix
git pull
cd config
./bin_refresh.sh

Thanks again Bernard,
/Basil n7nix

Hi Basil,

Once again I thank you very much for your invaluable help for progressing into RaspBerry Pi and DRAWS usage with AX.25.

Reading doc files is quite easy but it does not preclude some missinterpretations by me as you have noticed.

I want to achieve a complete set up of an FPAC NODE using DRAWS based on nwdr image that should simplify considerably the configuration with your scripts help. However I am not yet finished !

I still  need ax25ipd configuration for AX25<-->UDP encapsulation of ROSE/FPAC and LinFBB frames toward Internet. I guess this should be added into ax25-start or built into a kind of ax25ipd-start. Then I will need something like uronode conf and install for FPAC node utilities.

Meanwhile I found an error when trying to use measure deviation script.  The first case of failure is when direwolf is started and prevents using sound device as you noticed. You already wrote instructions in order to remove direwolf with stop AX.25. The second cause of failure is when user is sudo and your scripts fails finding /home/root/bin/ax25-stop script for $USER= root

I suggest you could add the following lines borrowed from other scripts from you.

These lines should be just before the USER check paragraph where ax25-stop is called.

# Don't be root
if [[ $EUID == 0 ]] ; then
   echo "Don't be root"
   exit 1
fi


73 de Bernard, f6bvp

Yes Dave,

Hi David,

There should be no difference in Audio Input between the revisions.

6dB sounds suspiciously like the resistor settings. Run Basil’s Script and let us know.

Bryan

However there is a complete discrepancy between what you suggest and
what is explained in the

"Getting Started Guide"
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started

In the above guide is written to execute script app_config.sh core in Initial Configuration.
On the contrary you wrote

https://github.com/nwdigitalradio/n7nix/blob/master/docs/IMAGE_README.md)
come pre-installed on the nwdr14.img. Running the install scripts on
this image is not necessary and most likely will break things.

The nwdr14.img comes with installed software. You must do the initial
configuration. app_config.sh is a configuration script not an
installation script. Do not run the install scripts over the
pre-installation on the image.

You can see a log of what is already installed here:
cat /var/log/udr_install.log

However, direwolf is not installed in nwdr14 image.

Direwolf is part of the core install and is on the nwdr14.img.
From log file:
2019 09 19 11:03:22 PDT: core_install.sh: core install script FINISHED
Run sudo ax25-start to enable it as specified in the 'Getting Started Guide'

direwolf -v 2>/dev/null | grep -m 1 -i version
Dire Wolf DEVELOPMENT version 1.6 C (Sep 19 2019)

Immediately after first initial distro configuration ax25-status shows
that AX.25 pplications are not RUNNING and NOT ENABLED.

Yes, by design. The image will run HF programs by default unless you
run ax25-start.

Executing ./ax25-start fails with error code due to direwolf port not
found. There are a few reasons for this. First /etc/direwolf.conf is
not configured for DRAWS device is commented together with PTT GPIO is
not set to 12 (default left DRAWS plug).

Because you haven't run ./app_config.sh core
See 'Getting Started Guide'

In order to check if AX.25 is now correctly set up I started YAAC
application and listening to APRS frequency.

No stations could be decoded.

I had to execute setalsa-udrc-din6.sh script.

See 'Getting Started Guide'
* You must set your ALSA configuration for your particular radio at this time

At this step, to be able to get a functioning APRS application I found
it is abolutely necessary to switch Raspberry Pi power OFF and ON to
reboot. Otherwise, direwolf is not getting DRAWS audio.

ax25-stop followed by ax25-start will also work.

After these mandatory successive procedures, measure-deviate script was
found to be working correctly and beacon application could also be
activated.

The udrc port assignments are defaulting to a udrc II. You can fix that
by running the chk_port.sh script. The latest config scripts should do a
better job of setting the udr ports. ie when starting from a fresh image
always do a 'cd n7nix ; git pull' first. For the DRAWS hat the default
is to set the left mDin6 connector as udr0 for packet (winlink)
connections. You can change the config files to use the right mDin6
connector by running chk_ports.sh -n 1 -e

~/n7nix/bin $ ./chk_ports.sh -h
Usage: chk_ports.sh [-d][-e][-h]
Displays or edits: axports, ax25d.conf, channels.xml, wl2k.conf
No command line args, will display port names in above files.
-d set debug flag
-e set edit files flag
-n 0 or 1 set winlink device number, only used with -e option.
-p print files with port names.
-h no arg, display this message

pi@checkcfg:~/n7nix/bin $ ./chk_ports.sh
== AX.25 network ports check
Device ax0 OK, and up
Device ax1 OK, and up

== file: /usr/local/etc/ax25/axports check
axport: found device: udr0, with call sign N7NIX-10
axport: found device: udr1, with call sign N7NIX-1

== file: /usr/local/etc/ax25/ax25d.conf check
ax25d: found device: udr0, with call sign N7NIX-10
ax25d: found device: udr0, with call sign N7NIX

== file: /etc/rmsgw/channels.xml check
RMS gateway: chan_name: udr0, call sign: N7NIX-10

== file: /usr/local/etc/wl2k.conf check
plu: ax25port: udr0, call sign: N7NIX

/Basil