Date   

Re: Can't access Draws Manager

Tim Huffaker
 

I have v18 Draws installed most is working well for my APRS activity.  I decided to use draws manager to see how the configure the draws for other modes. When I tried localhost:8080 the browser said the site cannot be reached.  

After that I tried to reinstall draws manager from the gethub site and it failed on https://github.com/nwdigitalradio/draws-manager.git .  It came back saying the draws manager was already installed and failed.  

How do I get the draws manager working?

Tim
KM4ESU


Re: Direwolf/Packet Radio - Audio Settings

Basil Gunn
 

What radio are you using?

Could be cross talk between the two channels. Run some packet spy like
listen (use listen without any options) that will tell you which
interface the packets are being received on.

Also if you are not using both channels, that is you do not have a cable
on each of the mDin6 connections on the DRAWS hat then you can turn off
both the receive inputs (1200/9600 baud) on a particular channel using
ALSA IN1 & IN2 controls. ie. to turn on audio input (not discriminator)
to the left channel and turn off all right connector inputs:

IN1 L:[Off] R:[Off]
IN2 L:[10 kOhm] R:[Off]

Also could be something to do with your LinBPQ configuration.

Jim Erickson <jim@va7shg.ca> writes:

Good Day all. Our local club has started up a small packet network and
I've started to play using my Draws unit. It works fine. I've even
installed linbpq and am working on getting it configured. I've noticed
when looking through the direwolf logs, that it appears that I'm
hearing myself when I transmit. Here's the log entries. I'm
VE7TGZ. You can see my output [0L] and then it appears I hear myself,
with an audio level 2.

Dec 15 07:47:43 ve7tgz direwolf[545]: [0L] VE7TGZ-1>VE7AHH:(SABM cmd, p=1)
Dec 15 07:47:45 ve7tgz direwolf[545]: VE7TGZ-1 audio level = 2(5/2) [NONE] __||||||_
Dec 15 07:47:45 ve7tgz direwolf[545]: [0.4] VE7TGZ-1>VE7AHH:(SABM cmd, p=1)


Re: Direwolf/Packet Radio - Audio Settings

Jim VA7SHG/VE7TGZ
 

Thanks Bryan.  I'm using the Split Mode setup, so both ports are in use, but only one is dedicated to Direwolf/Packet.  The other one is running WSPR, hoping to pick up the W5KUB balloon on 20m wspr.


On 2020-12-15 8:55 a.m., Bryan Hoyer wrote:
Are you using both ports?

If you have an unused port DIREWOLF is capable of decoding from the crosstalk.

You should disable an unused port in /etc/direwolf.conf

Bryan K7UDR

On Dec 15, 2020, at 7:56 AM, Jim Erickson <jim@...> wrote:

Good Day all.  Our local club has started up a small packet network and I've started to play using my Draws unit.  It works fine. I've even installed linbpq and am working on getting it configured.  I've noticed when looking through the direwolf logs, that it appears that I'm hearing myself when I transmit.  Here's the log entries.  I'm VE7TGZ.   You can see my output [0L] and then it appears I hear myself, with an audio level 2.

Dec 15 07:47:43 ve7tgz direwolf[545]: [0L] VE7TGZ-1>VE7AHH:(SABM cmd, p=1)
Dec 15 07:47:45 ve7tgz direwolf[545]: VE7TGZ-1 audio level = 2(5/2)   [NONE]   __||||||_
Dec 15 07:47:45 ve7tgz direwolf[545]: [0.4] VE7TGZ-1>VE7AHH:(SABM cmd, p=1)

Anyone have any thoughts?  I have snap on ferrites on my mini-din6 cables.
73
Jim - VA7SHG/VE7TGZ


Re: Direwolf/Packet Radio - Audio Settings

 

Are you using both ports?

If you have an unused port DIREWOLF is capable of decoding from the crosstalk.

You should disable an unused port in /etc/direwolf.conf

Bryan K7UDR

On Dec 15, 2020, at 7:56 AM, Jim Erickson <jim@...> wrote:

Good Day all.  Our local club has started up a small packet network and I've started to play using my Draws unit.  It works fine. I've even installed linbpq and am working on getting it configured.  I've noticed when looking through the direwolf logs, that it appears that I'm hearing myself when I transmit.  Here's the log entries.  I'm VE7TGZ.   You can see my output [0L] and then it appears I hear myself, with an audio level 2.

Dec 15 07:47:43 ve7tgz direwolf[545]: [0L] VE7TGZ-1>VE7AHH:(SABM cmd, p=1)
Dec 15 07:47:45 ve7tgz direwolf[545]: VE7TGZ-1 audio level = 2(5/2)   [NONE]   __||||||_
Dec 15 07:47:45 ve7tgz direwolf[545]: [0.4] VE7TGZ-1>VE7AHH:(SABM cmd, p=1)

Anyone have any thoughts?  I have snap on ferrites on my mini-din6 cables.
73
Jim - VA7SHG/VE7TGZ


Direwolf/Packet Radio - Audio Settings

Jim VA7SHG/VE7TGZ
 

Good Day all.  Our local club has started up a small packet network and I've started to play using my Draws unit.  It works fine. I've even installed linbpq and am working on getting it configured.  I've noticed when looking through the direwolf logs, that it appears that I'm hearing myself when I transmit.  Here's the log entries.  I'm VE7TGZ.   You can see my output [0L] and then it appears I hear myself, with an audio level 2.

Dec 15 07:47:43 ve7tgz direwolf[545]: [0L] VE7TGZ-1>VE7AHH:(SABM cmd, p=1)
Dec 15 07:47:45 ve7tgz direwolf[545]: VE7TGZ-1 audio level = 2(5/2)   [NONE]   __||||||_
Dec 15 07:47:45 ve7tgz direwolf[545]: [0.4] VE7TGZ-1>VE7AHH:(SABM cmd, p=1)

Anyone have any thoughts?  I have snap on ferrites on my mini-din6 cables.
73
Jim - VA7SHG/VE7TGZ


Re: YAAC/Direwolf PTT missing

Andrew P.
 

Sounds correct to me, since Basil pointed out you should be using port 1.

Now, if you want YAAC in control of digipeating, I-gating, and beaconing, then you have to ensure those items are turned _off_ in the direwolf.conf file (otherwise they will be happing twice as both DireWolf and YAAC, in that order, do everything). Note you will get better digipeater performance if you let DireWolf do it, as it can dynamically change the TNC backoff settings appropriately for digipeated versus locally originated packets, whereas YAAC as a digipeater makes every transmitted packet look locally originated to DireWolf.

Beaconing needs to be enabled in YAAC on the Beacon tab in expert-mode configuration.

In YAAC, digipeating is turned off by default except for the emergency TEMP1-1 alias. So you will have to enable the aliases you want to use application-wide on the expert-mode configuration's Digipeat tab, and then select those same aliases on the AGWPE port. The reason for this is when supporting cross-band digipeating (especially from and to HF bands), you want to be able to control what gets retransmitted out which port.

For I-gating, you will need to create a YAAC APRS-IS or SSL-APRS-IS port, select which APRS-IS server pool you want to connect to, specify your callsign-SSID (should be the same as the RF port for consistent station identification at aprs.fi), specify your authentication information (passcode for APRS-IS, your Logbook of the World certificate and private key for SSL-APRS-IS), and enable the port for transmission.

Since your configuration will now have both RF and APRS-IS ports, YAAC assumes you are operating as a normal I-gate, so you will have to specify APRS-IS filters if you want to receive any traffic from the Internet other than the traffic the APRS-IS backbone expects you should Tx-I-gate to RF.

Hope this helps.

Andrew, KA2DDO
author of YAAC

________________________________________
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> on behalf of Tim Huffaker
Sent: Monday, December 14, 2020 5:18 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] YAAC/Direwolf PTT missing

Andrew,

Thank you for getting back to me. To be more clear I what YAAC to control is digipeating or igate or beaconing need for my system. When I select the AGWPE port the Local Host is set to port 8000. The port name is Port 1 first sound card left. This gets me APRS reception with no issues unfortunately no beaconing.
I went back and ran all the test on the draws board and it passed. I looked for direwolf.conf with no luck to check the port it was using to talk. So can anyone confirm you need Port 8000 from direwolf to give a YAAC a AGWPE port using Port 1 first sound card left.
Basically now I am beaconing and digipeating that was not happing before. I will reboot a few times to work out robustness and get it ready for use.

Tim KM4ESU


Re: YAAC/Direwolf PTT missing

Basil Gunn
 

When I select the AGWPE port the Local Host is set to port 8000. The
port name is Port 1 first sound card left.

This gets me APRS reception with no issues unfortunately no beaconing.

I went back and ran all the test on the draws board and it passed. I
looked for direwolf.conf with no luck to check the port it was using
to talk.
The NWDR image puts the direwolf configuration file here:

/etc/direwolf.conf

which is a Unix/Linux convention where config files should live.

So can anyone confirm you need Port 8000 from direwolf to
give a YAAC a AGWPE port using Port 1 first sound card left.
Direwolf setup for YAAC using AGWPE is in section 4.3.3 on page 15 of
the Direwolf 'User Guide'
https://github.com/wb2osz/direwolf/blob/master/doc/User-Guide.pdf
and yes direwolf defaults to using port 8000 for AGWPE.

Basically now I am beaconing and digipeating
Great!


Re: YAAC/Direwolf PTT missing

Tim Huffaker
 

Andrew,

Thank you for getting back to me. To be more clear I what YAAC to control is digipeating or igate or beaconing need for my system.  When I select the AGWPE port the Local Host is set to port 8000.  The port name is Port 1 first sound card left.  This gets me APRS reception with no issues unfortunately no beaconing.  
I went back and ran all the test on the draws board and it passed.  I looked for direwolf.conf with no luck to check the port it was using to talk.  So can anyone confirm you need Port 8000 from direwolf to give a YAAC a AGWPE port using Port 1 first sound card left.  
Basically now I am beaconing and digipeating that was not happing before.  I will reboot a few times to work out robustness and get it ready for use.  

Tim KM4ESU


Re: YAAC/Direwolf PTT missing

Basil Gunn
 

Tim,
Using the groups.io search function John Hays posted the following on installing YAAC
https://nw-digital-radio.groups.io/g/udrc/message/547?p=,,,20,0,0,0::relevance,,yaac,20,2,0,2519163

When configuring YAAC you can use AGWPE or KISS over TCP.

Basil Gunn <basil@pacabunga.com> writes:

Thanks Andrew.

Andrew P. <andrewemt@hotmail.com> writes:

No, YAAC is not a TNC, so it can't control the radio. You need to have
_DireWolf_ properly configured to do the PTT.
Tim, if you followed the 'Getting Started Guide'
https://nw-digital-radio.groups.io/g/udrc/wiki/8921


Re: YAAC/Direwolf PTT missing

Basil Gunn
 

Thanks Andrew.

Andrew P. <andrewemt@hotmail.com> writes:

No, YAAC is not a TNC, so it can't control the radio. You need to have
_DireWolf_ properly configured to do the PTT.
Tim, if you followed the 'Getting Started Guide'
https://nw-digital-radio.groups.io/g/udrc/wiki/8921

then direwolf is configured to use the proper DRAWS GPIO. Note left
mDin6 connector is port 0 in Direwolf. I'm guessing you will want to add
an AGWPE port in YAAC config. Check out yaac's excellent documentation:
https://www.ka2ddo.org/ka2ddo/YAACdocs/config_agwpe.html

Also you can verify your cable, transmit output, & PTT by running the
measure_deviate.sh script:
https://github.com/nwdigitalradio/n7nix/tree/master/deviation

So, the first question
is: are you PTTing the other radio port on the DRAWS hat? i.e., is
Radio#1 going into transmit when Radio#2 is on the APRS frequency and
connected to DireWolf?

Andrew, KA2DDO
author of YAAC

________________________________________
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> on behalf of Tim Huffaker
Sent: Monday, December 14, 2020 11:56 AM
Subject: [draws and udrc] YAAC/Direwolf PTT missing

I am running the latest Draws release from 2wks. This setup is for
Direwolf and YAAC for aprs support. I see all working well except I
cannot PRT. I have checked my YAAC settings for beaconing but
unfortunately the DRAWs board does not PTT the radio. The Radio is a
TMV71A.

YAAC is controlling the set up with Direwolf acting as the TNC. I am thinking I don’t have sometime enabled to allow YAAC to command a PTT.

Thank you,
Tim
KM4ESU




Re: YAAC/Direwolf PTT missing

Andrew P.
 

No, YAAC is not a TNC, so it can't control the radio. You need to have _DireWolf_ properly configured to do the PTT. So, the first question is: are you PTTing the other radio port on the DRAWS hat? i.e., is Radio#1 going into transmit when Radio#2 is on the APRS frequency and connected to DireWolf?

Andrew, KA2DDO
author of YAAC

________________________________________
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> on behalf of Tim Huffaker
Sent: Monday, December 14, 2020 11:56 AM
Subject: [draws and udrc] YAAC/Direwolf PTT missing

I am running the latest Draws release from 2wks. This setup is for Direwolf and YAAC for aprs support. I see all working well except I cannot PRT. I have checked my YAAC settings for beaconing but unfortunately the DRAWs board does not PTT the radio. The Radio is a TMV71A.

YAAC is controlling the set up with Direwolf acting as the TNC. I am thinking I don’t have sometime enabled to allow YAAC to command a PTT.

Thank you,
Tim
KM4ESU


YAAC/Direwolf PTT missing

Tim Huffaker
 

I am running the latest Draws release from 2wks.  This setup is for Direwolf and YAAC for aprs support.  I see all working well except I cannot PRT.  I have checked my YAAC settings for beaconing but unfortunately the DRAWs board does not PTT the radio.  The Radio is a TMV71A. 

YAAC is controlling the set up with Direwolf acting as the TNC.  I am thinking I don’t have sometime enabled to allow YAAC to command a PTT.

Thank you,
Tim
KM4ESU


Re: DRAWS™ Latest Board Run Defect (Standby) #recall #draws

michael
 

I'm thinking it's this thread:

https://nw-digital-radio.groups.io/g/udrc/topic/68158957#4269

thanks for the heads up.


Re: DRAWS™ Latest Board Run Defect (Standby) #recall #draws

Basil Gunn
 

Right thread, wrong post #. I think this is what you are looking for.

https://nw-digital-radio.groups.io/g/udrc/message/4270

Basil Gunn <basil@pacabunga.com> writes:

Hey Bryan,
Is this what you are talking about:
https://nw-digital-radio.groups.io/g/udrc/topic/68158957#4262

To be clear this is NOT related to the latest DRAWS hats:
Product ver: 0x0108


Bryan Hoyer <bhhoyer@gmail.com> writes:

It’s actually 2 caps and 4 resistors. I’m looking for the thread where it was documented.

Bryan K7UDR


Re: DRAWS™ Latest Board Run Defect (Standby) #recall #draws

Basil Gunn
 

Hey Bryan,
Is this what you are talking about:
https://nw-digital-radio.groups.io/g/udrc/topic/68158957#4262

To be clear this is NOT related to the latest DRAWS hats:
Product ver: 0x0108


Bryan Hoyer <bhhoyer@gmail.com> writes:

It’s actually 2 caps and 4 resistors. I’m looking for the thread where it was documented.

Bryan K7UDR


Re: DRAWS™ Latest Board Run Defect (Standby) #recall #draws

 

It’s actually 2 caps and 4 resistors. I’m looking for the thread where it was documented.

Bryan K7UDR


Re: DRAWS™ Latest Board Run Defect (Standby) #recall #draws

michael
 

Greetings, Is the fix mentioned in this thread still the appropriate course of action?  I have an older board with sma plug adjacent to the power plug.  I will be removing the two capacitors circled in the image below?

I guess this would explain my transmit issues and why the pcm gain needed to be turned up so high for my ft-857d....


Re: HamPi test direwolf /yaac.

 

I just installed HamPi 1.2 on a Pi 400 and attached the DRAWS™ board (via a ribbon cable -- you can plug it directly to the back of the Pi 400 or on the GPIO header of your Pi).  See attached /boot/config.txt 

Note that I clear the dtoverlays (eg. dtoverlay=) ahead of the [pi4] section.  Also the dtparam=audio=0 is a personal choice (my monitor doesn't have speakers)

The gpsd is preconfigured for the DRAWS™ GPS so after you verify --

cat /proc/device-tree/hat/product
Digital Radio Amateur Work Station


cd /dev && ls -l ttySC0 ttySC1 pps0
crw-rw---- 1 root root    241, 0 Jun  8 17:46 pps0
crw-rw---- 1 root dialout 239, 0 Jun  8 17:46 ttySC0
crw-rw---- 1 root dialout 239, 1 Jun  8 17:46 ttySC1


You should be able to run gpsmon or cgps and see gps strings.  The physical gps port is /dev/ttySC0

aplay -l should show the sound card (as udrc)


On Mon, Dec 7, 2020 at 3:59 PM Tim Huffaker <thuffaker@...> wrote:
I wanted to try HamPi with direwolf first to get everything talking.  I followed the document for setting up HamPi with the DRAWs board. After starting direwolf it did not see to find either a Kiss or AGW connection to the codec.  Second I tried to set up the GPS with YAAC and it could not find the GPS.  

Can you point me to debug and let me know what ports the Codec and GPS come in on to the RPI3. From there I should be able to get this working.  

Tim
KM4ESU
_._,_._,_

--
John D. Hays
Kingston, WA
K7VE

 


HamPi test direwolf /yaac.

Tim Huffaker
 

I wanted to try HamPi with direwolf first to get everything talking.  I followed the document for setting up HamPi with the DRAWs board. After starting direwolf it did not see to find either a Kiss or AGW connection to the codec.  Second I tried to set up the GPS with YAAC and it could not find the GPS.  

Can you point me to debug and let me know what ports the Codec and GPS come in on to the RPI3. From there I should be able to get this working.  

Tim
KM4ESU


Re: DRAWS™ Cases have moved to production!

 

Yes, all orders will ship once the cases arrive.

Bryan K7UDR

601 - 620 of 5868