Re: Changing from Signalink to Easy Digi
Hey All,
Here is a pic of the ¡°interface¡± I build that utilizes the Easy-Digi with a ¡°Soundcard¡± that allows full PTT between the rig if my choosing and a Pi3,4 or whatever.
The 3D printed box I/O¡¯s are phono jacks that allow me to make whatever interface cable I need between the rig of my choosing (Kenwood,Yaesu, etc) and the ¡°box¡±¡then the box plugs into the Pi via a micro usb / usb cable. I run Direwolf and Xastir on the Pi¡¯s for APRS solely. Hope this helps..
73,
Danny NF4J
Sent using the mobile mail app
toggle quoted message
Show quoted text
On 11/20/22 at 19:29, Thomas Leibold wrote: Hi,
David is correct. I was actually looking at the same page he linked to but was mislead by the comments about Vox in the text on that page. I missed the GPIO signal from the Raspberry Pi going to the Easy Digi board, mistaking the red and blue lines as power supply.
This also means that there is a need for a PTT line in the direwolf.conf file. If you followed the example on the openrepeater.com website and used Pin 12 (GPIO 18) on the Raspberry Pi then the corresponding entry in the direwolf.conf file would be PTT GPIO 18.
As for Vox not being recommended that is without question. However there is a difference between the Vox feature inside many radios (which is intended for Voice communication only) and a fast-acting Vox circuit inside a computer-radio interface (such as Signalink and some DRA models which can indeed be used for digital communication).
A real PTT signal under software control will always be superior to a Vox circuit.
73,
Thomas
KK6FPP
|
Re: Changing from Signalink to Easy Digi
Hi,
This thread caught me eye as I have two SignaLinks (along with cables and modules for Yaesu 8900, Alinco DR-235, Baofengs/Kenwood/etc, Anyone 778UV, etc) and usd to use one for APRS/digipeater/igate stuff, but now using just one of the EasyDigi¡¯s. Have three EasyDigi¡¯s, the two shown here and one in current use with s FT60R going into an amplifier and out a jpole (that one also has the blue USB PTT cable). I¡¯m using just a RPi02W for DireWolf and triggering the USB by ¡°PTT /dev/ttyUSB0 RTS DTR¡± in direwolf.conf. For audio, I¡¯m using a ¡°Fe-Pi¡± audio hat (well, actually it is WB7FHC¡¯s clone since the Fe-Pi is no longer made), and it works great. Google ¡°Nexus DR-X¡± and then look at part listing if anyone is interested in getting one of those boards. I have two and they work a treat. They don¡¯t get disconnected by RF like sometimes the USB sound dongles do.
The EasyDigi on the left is just a VOX one. I don¡¯t really care to use just VOX, but sometimes it is convenient, especially with just a cheap Baofeng or such. I have a few of the BTech K1-APRS cables, but found the EasyDigi to work much better. Also have a MobiLinkD TNC3 that is part of my WinLink Gateway. That¡¯s a great device too, but currently on hold due to world chip shortage. Hoping the MobiLink is sold again soon as been patiently waiting to get a second one.
Anyway, just saw the post about switching from using a SignaLink to EasyDigi and thought I¡¯d chime in as I did the same. When I was using the SignaLink, it was able to trigger PTT on my mobile and didn¡¯t have to use VOX.
EasyDigi¡¯s are great devices to have also though.
Cheers,
Jerry
Sent from my iPhone 13 Pro Max
toggle quoted message
Show quoted text
On Nov 20, 2022, at 8:29 PM, Thomas Leibold <leibold@...> wrote:
?Hi,
David is correct. I was actually looking at the same page he linked to but was mislead by the comments about Vox in the text on that page. I missed the GPIO signal from the Raspberry Pi going to the Easy Digi board, mistaking the red and blue lines as power supply.
This also means that there is a need for a PTT line in the direwolf.conf file. If you followed the example on the openrepeater.com website and used Pin 12 (GPIO 18) on the Raspberry Pi then the corresponding entry in the direwolf.conf file would be PTT GPIO 18.
As for Vox not being recommended that is without question. However there is a difference between the Vox feature inside many radios (which is intended for Voice communication only) and a fast-acting Vox circuit inside a computer-radio interface (such as Signalink and some DRA models which can indeed be used for digital communication).
A real PTT signal under software control will always be superior to a Vox circuit.
73,
Thomas
KK6FPP
|
Re: Changing from Signalink to Easy Digi
Hi,
David is correct. I was actually looking at the same page he linked to but was mislead by the comments about Vox in the text on that page. I missed the GPIO signal from the Raspberry Pi going to the Easy Digi board, mistaking the red and blue lines as power supply.
This also means that there is a need for a PTT line in the direwolf.conf file. If you followed the example on the openrepeater.com website and used Pin 12 (GPIO 18) on the Raspberry Pi then the corresponding entry in the direwolf.conf file would be PTT GPIO 18.
As for Vox not being recommended that is without question. However there is a difference between the Vox feature inside many radios (which is intended for Voice communication only) and a fast-acting Vox circuit inside a computer-radio interface (such as Signalink and some DRA models which can indeed be used for digital communication).
A real PTT signal under software control will always be superior to a Vox circuit.
73,
Thomas
KK6FPP
|
Re: Changing from Signalink to Easy Digi
The Easy Digi isolation boards that I'm aware of do
NOT support any form of PTT control.? To function, they get wired
up something like this:
??
Please note... the use of VOX is NOT recommended for Packet
Radio.? Please read section 9.2.13.1 of the Direwolf User Guide:
??
--David
KI6ZHD
On 11/20/2022 04:00 PM, Thomas Leibold
wrote:
toggle quoted message
Show quoted text
Hi Fred,
The first thing to check is that you wired the connections from the Easy Digi interface and the Kenwood radio properly. In particular it is important that both the Mic Gnd and the PTT Gnd connections from the Easy Digi are connected to the radio ground.
The Easy Digi implements a Vox interface for PTT. In order for this circuit to work, there has to be sufficient output volume on the Sabrent USB sound fob/dongle. Try turning up the speaker volume for the USB sound interface to see if this helps to generate PTT.
No PTT configuration is needed in direwolf.conf when using Vox, so these commented out PTT lines are fine.
73,
Thomas
KK6FPP
|
Re: Changing from Signalink to Easy Digi
Hi Fred,
The first thing to check is that you wired the connections from the Easy Digi interface and the Kenwood radio properly. In particular it is important that both the Mic Gnd and the PTT Gnd connections from the Easy Digi are connected to the radio ground.
The Easy Digi implements a Vox interface for PTT. In order for this circuit to work, there has to be sufficient output volume on the Sabrent USB sound fob/dongle. Try turning up the speaker volume for the USB sound interface to see if this helps to generate PTT.
No PTT configuration is needed in direwolf.conf when using Vox, so these commented out PTT lines are fine.
73,
Thomas
KK6FPP
|
Re: Changing from Signalink to Easy Digi
Hello Fred,
When you say a Sabrent USB adapter, do you mean a Sabrent sound
device?? If so, that device will only support *sound* out of the
box.? Depending on your specific sound device, some can be opened
up and you can add a PTT circuit to it if you're willing to try:
??
If you don't want to do that, you can use a GPIO pin off your
Raspberry Pi itself and with a simple transistor circuit, you can
use that:
??
--David
KI6ZHD
On 11/20/2022 03:30 PM, Fred Bouwman
wrote:
toggle quoted message
Show quoted text
Hello all. My APRS station is a Pi 3B, Signalink, and
Kenwood TM-281a running Direwolf and YAAC. Runs great. I replaced
the Signalink with an Easy Digi and a Sabrent USB adapter. I
cannot get the system to transmit. Is there a change I need to
make in direwolf.conf? I tried making changes in the lines below
with no success. Thanks for your help.?
#PTT COM1 RTS
#PTT COM1 RTS -DTR
#PTT /dev/ttyUSB0 RTS
|
Re: Changing from Signalink to Easy Digi
Hello Fred,
Assuming you added a USB sound adapter and a USB to serial adapter, the PTT line should look like this:
PTT /dev/ttyUSB0 RTS DTR
If that doesn't work, try this:
PTT /dev/ttyUSB0 DTR RTS
I don't recall exactly which one of the two worked for me when I was using an EasyDigi board.
73, Lee K5DAT
On Sun, Nov 20, 2022 at 5:30 PM Fred Bouwman < bouwmanf@...> wrote: Hello all. My APRS station is a Pi 3B, Signalink, and Kenwood TM-281a running Direwolf and YAAC. Runs great. I replaced the Signalink with an Easy Digi and a Sabrent USB adapter. I cannot get the system to transmit. Is there a change I need to make in direwolf.conf? I tried making changes in the lines below with no success. Thanks for your help.?
#PTT COM1 RTS
#PTT COM1 RTS -DTR
#PTT /dev/ttyUSB0 RTS
|
Changing from Signalink to Easy Digi
Hello all. My APRS station is a Pi 3B, Signalink, and Kenwood TM-281a running Direwolf and YAAC. Runs great. I replaced the Signalink with an Easy Digi and a Sabrent USB adapter. I cannot get the system to transmit. Is there a change I need to make in direwolf.conf? I tried making changes in the lines below with no success. Thanks for your help.?
#PTT COM1 RTS
#PTT COM1 RTS -DTR
#PTT /dev/ttyUSB0 RTS
|
Re: Kiss format vs direwolf.conf format
There was a pass last night and I was repeated. So the line below does work.
toggle quoted message
Show quoted text
On 2022-11-19 20:40, Robert Bower wrote: Good evening everyone,
I am attempting to get digipeted by the ISS. I am able to get
digipeated if I have the following in my direwolf.conf
PBEACON delay=00:01 every=00:10 symbol="/-" lat=41.6814784N
long=86.2034467W power=5 height=10 gain=0 comment="Hello, from Robert"
via=ARISS
I since have setup direwolf to be a satgate so I took that statement
out since I have a radio always listening.
I wrote a little script that using kissutil to interject a beacon on
demand for a specified amount of time. The script works and is sent
out via radio but I never get digipeated.
I think I don't wrote the kissutil statement correctly. I have tried
several. I think the previous ones had too much in them and didn't
have the CQ.
I think this one is correct.
W9RWB-1>CQ,ARISS,WIDE2-1:!4140.89NI08612.21W#PHG2000 Hello from Robert
Is there anything missing or needs to be taken out.
Thanks for your help.
--
Thanks,
Robert Bower
W9RWB
WRPH745
--
Thanks,
Robert Bower
W9RWB
WRPH745
|
Kiss format vs direwolf.conf format
Good evening everyone,
I am attempting to get digipeted by the ISS. I am able to get digipeated if I have the following in my direwolf.conf
PBEACON delay=00:01 every=00:10 symbol="/-" lat=41.6814784N long=86.2034467W power=5 height=10 gain=0 comment="Hello, from Robert" via=ARISS
I since have setup direwolf to be a satgate so I took that statement out since I have a radio always listening.
I wrote a little script that using kissutil to interject a beacon on demand for a specified amount of time. The script works and is sent out via radio but I never get digipeated.
I think I don't wrote the kissutil statement correctly. I have tried several. I think the previous ones had too much in them and didn't have the CQ.
I think this one is correct.
W9RWB-1>CQ,ARISS,WIDE2-1:!4140.89NI08612.21W#PHG2000 Hello from Robert
Is there anything missing or needs to be taken out.
Thanks for your help.
--
Thanks,
Robert Bower
W9RWB
WRPH745
|
Re: lm_data_request NULL packet pointer
Do you recommend the current HEAD of the dev branch?
I'll try building that for Windows.
Correct.
I don't see a tag 1.7-dev-E nor a release 1.7e
Direwolf v1.7 is not released yet and there isn't a clear ETA yet of
when it would be.? It should be stable and it has lots of
improvements over v1.6 but it's still a WIP.
Regarding tagging, that's correct, WB2OSZ didn't create a git tag
for his intermediate beta releases.?? If you want to track the
changes to the Beta versioning yourself, you can do a search for
"MAJOR_VERSION, MINOR_VERSION" on this git view:
and of course there are numerous commits (including
HEAD) with "E" in that dw_printf line. It would be helpful to
publish an occasional tag, pre-release or release that you're
confident works well.
Agreed and WB2OSZ reads this list so maybe he would be willing to
add additional tags as he continues his development.? To your other
point, I have had good luck with v1.7E but your specific issue here
was it about an issue due to a misconfiguration that you have since
fixed.? That's a corner case for sure but it's possible it's now
caught in the newer Beta code.
--David
KI6ZHD
|
Re: lm_data_request NULL packet pointer
The same problem occurs with source code commit v8913a852fd (version 1.7 E). A log file is attached.
toggle quoted message
Show quoted text
On Thu, Nov 17, 2022 at 10:52 AM, David Ranch wrote:
If possible, can you compile the new version and see if you can reproduce the issue?
|
Re: lm_data_request NULL packet pointer
Do you recommend the current HEAD of the dev branch? I'll try building that for Windows.
I don't see a tag 1.7-dev-E nor a release 1.7e, and of course there are numerous commits (including HEAD) with "E" in that dw_printf line. It would be helpful to publish an occasional tag, pre-release or release that you're confident works well.
toggle quoted message
Show quoted text
On Thu, Nov 17, 2022 at 10:52 AM, David Ranch wrote:
The current version found in the DEV branch on Git as of today is v1.7E ...
|
Re: Winlink Packet connection issue via Direwolf
Hello Marcel,
Problem is that this setup does not connect to any
remote stations. Signalink keys PTT but the remote station doesn't
answer.
Ok.
However, if I move the USB connection to the Windows PC and
connect via UZ7HO Soundmodem, everything is fine.
Don't let that fool you, that's all irrelevant.
The obvious stuff first:
- sound levels are adjusted and verified - not muted - more to
that a bit below
Define how you verified?? Did you verify both TX and RX?? Are the
transmitted signals clean?? Please read
to learn how to
do this pretty easily for 1200bps AFSK packet.
- sound levels are +/- 0.8V and also trigger PTT of
the Signalink, Radio goes into transmit in either case
Ok though voltage levels only matter to what specific radio you're
using.
- receive level is adjusted to satisfy soundmodem
Irrelevant.? If you want Direwolf to work.. tune for Direwolf's
required levels
- I can receive APRS messages with Direwolf and see
them on the console/log
What are the heard "tone" levels according to the Direwolf console
output?? The goal should be to get as many of them close to
reporting a value of 50.?
- I see the SABM message in Direwolf? and Radio goes
to TX.
Ok
- with soundmodem I get a connection within 1-2
connection attempts
How close is this other remote packet station?? Is the signal strong
and clean?? If so, the connection attempt should work first try
- I'm only moving the USB cable between the Pi and the
PC for the two scenarios
Irrelevant.? You have two entirely different operating systems,
sound drivers, and mixers between the two systems.? You need to tune
the entire stack to get an optimal setup.
Connected a scope to the MONI Port on the Signalink and observed
the following difference between the two setups
Working - Soundmodem talking to Signalink
This is what I expected. Mark and space +/- at 1200/2200
Doing the same with Direwolf gives a different result:
That Direwolf screen shot seems to be rather dirty with a lot of
harmonics in there.? how does it sound via a set of earbuds?? There
could be bus noise, ground hum, etc. getting introduced when using
the Rpi.
Also the waveform is much different
The top one look saturated.? Lower the TX audio level on the
Signalink
direwolf is started with -p - nothing else
Since you're using AGW to connect from a Windows machine, I assume
you did not configure the Raspberry Pi's AX25 stack.? If so, you
should not start Direwolf with "-p" as it will eventually crash.?
This is mention in the Direwolf User Guide.
ADEVICE plughw:2,0
ACHANNELS 1
MODEM 1200 1200:2200 E+??
(also tried with just MODEM 1200)
AGWPORT 0
KISSPORT 8001
LOGDIR
/home/pi/ham/logs/direwolf
This config doesn't match what you said above.? You said you were
using AGW but the above config shows it's disabled.? Maybe you're
using TCPKISS on the Winlink Windows application?
Do I need to specify AFSK 1200 somewhere specifically?
You did.. it's the " MODEM 1200"
part of that one line.?
--David
KI6ZHD
|
Re: Winlink Packet connection issue via Direwolf
At first glance, the output from direwolf looks so hi it is severely clipped and distorted, which would explain the spectal view.
Can you verify deviation on the transmitter?
From: "Marcel, VA3UKW" <tinkernut@...> To: [email protected]Sent: Thursday, November 17, 2022 4:59:09 PM Subject: [direwolf] Winlink Packet connection issue via Direwolf
Greetings, I'm trying to connect with Winlink (Windows App) via Winlink Packet to a local node. Setup: - Windows PC is Windows 10 - Direwolf (latest dev) runs on a Pi. - Both units are in the same network. - I'm using a Signalink to connect to a TM-271a. Problem is that this setup does not connect to any remote stations. Signalink keys PTT but the remote station doesn't answer. However, if I move the USB connection to the Windows PC and connect via UZ7HO Soundmodem, everything is fine. The obvious stuff first: - sound levels are adjusted and verified - not muted - more to that a bit below - sound levels are +/- 0.8V and also trigger PTT of the Signalink, Radio goes into transmit in either case - receive level is adjusted to satisfy soundmodem. - I can receive APRS messages with Direwolf and see them on the console/log - I see the SABM message in Direwolf? and Radio goes to TX. - with soundmodem I get a connection within 1-2 connection attempts. - I'm only moving the USB cable between the Pi and the PC for the two scenarios. Connected a scope to the MONI Port on the Signalink and observed the following difference between the two setups Working - Soundmodem talking to Signalink  This is what I expected. Mark and space +/- at 1200/2200 Doing the same with Direwolf gives a different result:  Also the waveform is much different  And the working version  direwolf is started with -p - nothing else direwolf.conf - omitting comments and default values ADEVICE plughw:2,0
ACHANNELS 1
MODEM 1200 1200:2200 E+?? (also tried with just MODEM 1200)
AGWPORT 0
KISSPORT 8001
LOGDIR /home/pi/ham/logs/direwolf
Any idea where I go wrong or why this doesn't work? Do I need to specify AFSK 1200 somewhere specifically? Thanks 73, Marcel
|
Winlink Packet connection issue via Direwolf
Greetings, I'm trying to connect with Winlink (Windows App) via Winlink Packet to a local node. Setup: - Windows PC is Windows 10 - Direwolf (latest dev) runs on a Pi. - Both units are in the same network. - I'm using a Signalink to connect to a TM-271a. Problem is that this setup does not connect to any remote stations. Signalink keys PTT but the remote station doesn't answer. However, if I move the USB connection to the Windows PC and connect via UZ7HO Soundmodem, everything is fine. The obvious stuff first: - sound levels are adjusted and verified - not muted - more to that a bit below - sound levels are +/- 0.8V and also trigger PTT of the Signalink, Radio goes into transmit in either case - receive level is adjusted to satisfy soundmodem. - I can receive APRS messages with Direwolf and see them on the console/log - I see the SABM message in Direwolf? and Radio goes to TX. - with soundmodem I get a connection within 1-2 connection attempts. - I'm only moving the USB cable between the Pi and the PC for the two scenarios. Connected a scope to the MONI Port on the Signalink and observed the following difference between the two setups Working - Soundmodem talking to Signalink  This is what I expected. Mark and space +/- at 1200/2200 Doing the same with Direwolf gives a different result:  Also the waveform is much different  And the working version  direwolf is started with -p - nothing else direwolf.conf - omitting comments and default values ADEVICE plughw:2,0
ACHANNELS 1
MODEM 1200 1200:2200 E+?? (also tried with just MODEM 1200)
AGWPORT 0
KISSPORT 8001
LOGDIR /home/pi/ham/logs/direwolf
Any idea where I go wrong or why this doesn't work? Do I need to specify AFSK 1200 somewhere specifically? Thanks 73, Marcel
|
Re: lm_data_request NULL packet pointer
Hello John,
Per your report, you are running Direwolf Beta version 1.7A which is
rather old.?? The current version found in the DEV branch on Git as
of today is v1.7E:
--
$ grep "Dire Wolf DEVELOPMENT" src/direwolf.c
??? dw_printf ("Dire Wolf DEVELOPMENT version %d.%d %s (%s)\n",
MAJOR_VERSION, MINOR_VERSION, "E",
__DATE__);
--
If possible, can you compile the new version and see if you can
reproduce the issue?
--David
KI6ZHD
On 11/16/2022 04:18 PM, John Kristian
wrote:
toggle quoted message
Show quoted text
I saw Direwolf log:
INTERNAL ERROR:? lm_data_request NULL packet pointer.
Please report this!
So I'm reporting it. A more complete log file is attached.
Arguably this is a client problem: I didn't configure a target
address in the client (QtTermTCP). The problem doesn't occur with
a non-empty target address.
|
Re: ic7100 on Win10 won't transmit
David,
???? Thank you for all that.? All my searches yield Linux systems.? Your info will certainly get my situation resolved.? Thnx.
73? Rory? W4RJG
|
lm_data_request NULL packet pointer
I saw Direwolf log:
INTERNAL ERROR:? lm_data_request NULL packet pointer. Please report this!
So I'm reporting it. A more complete log file is attached. Arguably this is a client problem: I didn't configure a target address in the client (QtTermTCP). The problem doesn't occur with a non-empty target address.
|
Re: ic7100 on Win10 won't transmit
Hello Rory,
If I'm reading you correctly, you got UZ70HO Soundmodem for
Windows to key up your radio but you've been unable to get
Direwolf for Windows to key up the radio?? What is the "PTT" line
configured to in your direwolf.conf file?? The syntax should look
like:
?? # Per Direwolf User Guide section 9.2.9.4
?? # Hamlib 3.x style for IC7100
?? # Change COM3 to be the correct serial port per Windows Device
Manager
?? PTT RIG 370 COM3
Btw, doing a search on the Direwolf email list archives for
"IC7100 Windows" gave hits like:
?? #Newer style using Direwolf's native CAT support
??
?? #Using the older style solution of using the CAT7200
intermediate program
?? /g/direwolf/topic/34951885
You also should be able to assert PTT using the secondary serial
port presented by the Icom IC7100 which is a bit simpler than
using CAT command.? The solution choice is yours.
--David
KI6ZHD
On 11/15/2022 01:40 PM, Rory Griffin,
W4RJG wrote:
toggle quoted message
Show quoted text
Hi all,
????? Thanking in advance for the solution needed.? This is a
Win10, with ic7100 working with lots of other software.? Even
soundmodem regarding transmit.? But I need Direwolf for receieve
diagnosis.? But to trigger my Winlink server in packet, direwolf
wont get the radio into Tx mode.? I tried PTT CAT9 (-rts|rts)
(-dts|dts) combinations, or so I think I did.? What else am i
missing.? Thank you.
73? Rory? W4RJG
|
Danny NF4J
Fred Bouwman
John Kristian
Danny K5CG