Re: Rasberry Pi 3, Direwolf, USB soundcard doesn't digipeat packets.
David,
I did not do rpi-update, apparently the installer thought? did not have enough HD room
I have reinstalled pulse audio.
I did not compile direwolf, I installed it from the standard repository.
AFAIK, I am the only igate in the area and the one APRS "repeater" in our area is only beaconing, not repeating.
I have seen the messages from direwolf to try to get the recognized audio level to 50. With he Signalink, it's not too bad to get working, the usb soundcard is a PITA. I haven't been able to get that to work.
I already have Xastir using Open Street Maps on the Pi, bit I rarely use Xastir on the Pi, and so not use it to digipeat.
The autostartup is a simple script executed from the session/startup module in XF4CE.
Of the main problems I am having is that they system does not transmit the APRS data packet. Direwolf will beacon position packets, as will Xastir. The system igates.
If I can get the system working, I'll only be beaconing every 30 minutes, if that. And, as I said, I'm the only igate in the area.
Also. I am using a 5 watt UV5R, 5 watts into a dual band 450 jpole that is hanging inside my first floor condo which had stucco over wiring for the? outside wall covering.
Thanks,
Rick, KK4GGL
.
|
Re: Rasberry Pi 3, Direwolf, USB soundcard doesn't digipeat packets.
Hello Rick,
The directions, which I posted, said to delete
pulseaudio.
Looking at the instructions at
, I can say the following:
?? - I agree with the statement "Due to the less than desirable
receiving and transmitting qualities of a Baofeng, especially with
the stock antenna, your range and APRS usefulness will be limited."
though I would argue he should emphasize the lack of reliability and
the real possibility that the final setup may never work with some
Baofeng radios.? It really can be hit and miss with those low
quality radios.
?? - The use of "rpi-update" to consume beta class Linux kernels is
not a good idea for most users.? It should only be used as a last
resort if something isn't working right
?? - This statement of "Lets remove pulseaudio from the system if
its installed by default. Although it works fine on most systems, it
does not play well with ARM based devices such as the RaspberryPi."
is very old and removing it will cause a LOT more harm than good.??
Since he references a YouTube video from "Retro Tech &
Electronics", I have to assume that video is giving old information
as well.? If this is a brand new setup and you haven't invested a
whole lot of work into it, I recommend to START OVER with a fresh
copy of the Raspberry Pi OS which didn't have PulseAudio removed.
?? - Compiling Direwolf from source code is not required as those
instructions will still only get you Direwolf v1.6 (via the Master
branch) which is the same version as available in the current
Raspberry Pi OS repos using "apt install direwolf"
?? - Depending on your location like if you're in a suburban area,
you should NOT configure your RF or APRS-IF beacons to use WIDE2-1.?
Using WIDE1-1 is far more appropriate to avoid over-flooding the
APRS RF network
?? - You should set the Baofeng's squelch to be wide open for best
operation.? I assume a setting of "1" is enabling some level of
squelch which might stop your station from decoding some weak
packets
?? - This documentation does NOT make any mention of tuning the
audio levels which is bad.? You should shoot for a receive level
according to Direwolf of 50 and this should be a combination of the
audio output from your radio and the microphone gain on the sound
device.?? For transmit audio tuning, there are lots of guides out
there such as this one:
.?? The Direwolf
User Guide gives some details here and I have a recommended approach
here as well:??
?? - It's unfortunate that the Xastir section of the guide makes no
mention of enabling some better maps such as OpenStreetMap, etc.?
?? - I would argue it's not a good idea to configure Xastir to
enable digipeating by default.
?? - I would argue it's not a good idea to configure Xastir to use
WIDE2-2 by default.? As mentioned above and depending on your area,
All Urban and most likely suburban areas should only use WIDE1-1.
?? - I would argue that no mention of Xastir's TXDELAY, TXTAIL, etc.
is bad.? See below for more details on say TXDELAY and a TXTAIL of
30ms is way too long.? Many would ague that it's not needed at all
but you will have to experiment with your setup to see if you need
it.? If you do, nothing more than 10ms should be required.
?? - In the "Final Thoughts" section where the author states "I?m
also unclear if it is counterproductive having both Direwolf and
Xastir set to transmit and digipeat, or if Direwolf must be
configured that way to grant Xastir that capability."? He is correct
that it's counter productive.? You should only configure the beacons
and digipeating in one place.? I personally recommend Direwolf to
keep things simpler and your beacons will go out even if Xastir
isn't running
Finally, this article makes no mention to the user of how to have
the APRS setup automatically start.? I don't think the article has
to tell the user everything but he/she should have at least hinted
at it and where to go to learn how to do it.
?
? Next, which Btech cable are you using here?? Is it
this one?
??
Yes
If so, what kinda of a sound card are you using with
it because it's just an audio adapter cable with a simple
circuit to support PTT.
?
and
As pointed out on this thread, this setup uses VOX instead of a real
PTT setup which is not great.? Another major gap in this article is
that they aren't configuring the TXDELAY parameter.? Per the BTECH
documentation, they state:
?? "In your Application for your device locate the transmit
settings; and allow a 3-4 second preamble/delay on AFSK (so VOX has
a chance to initiate on the radio)"
That would translate to a Direwolf setting of "TXDELAY 3000" or
"TXDELAY 4000" which would create a three to four second DEAD-AIR
transmission before each of your packets are sent.? That kind of
delay is is absolutely terrible for the local APRS RF channel.? A
good amateur radio APRS setup should only need 150-250ms of a
TXDELAY and an excellent one is more like 20-50ms!?? What this means
in the real world is that when your radio wants to transmit, it's
going to be hogging the air waves with dead air way more than anyone
else.? As such, if you still really want to run this setup 24/7, I
*highly* recommend you do NOT enable digipeating or send many
beacons as you'll be directly reducing the overall capacity of the
local APRS network.
--David
KI6ZHD
|
Re: Rasberry Pi 3, Direwolf, USB soundcard doesn't digipeat packets.
On Sat, Jun 11, 2022 at 03:39 PM, Lee Bengston wrote:
It appears the instructions above include enabling VOX in the Baofeng radio. Relying on VOX in a radio for PTT is not recommended, and I believe it states that in the Direwolf user guide.
?
Yes the Signalink uses its own fast VOX implementation for PTT, so it keys the radio using the standard PTT input. One guess is that Baofeng radios have variable quality in terms of how well the VOX works. Also I would expect poorly performing VOX to impact digipeating more than beacons. One possibility is it may be possible to tweak some settings such as TX delay and see if it works better.
?
If the intent is to use something smaller and less expensive than a Signalink, you could potentially use a DINAH or equivalent, but the cabling would have to be adapted to the radio's audio in/out and PTT in.
?
73,
Lee K5DAT
Thanks for the info.
?
|
Re: Rasberry Pi 3, Direwolf, USB soundcard doesn't digipeat packets.
On Sat, Jun 11, 2022 at 03:06 PM, David Ranch wrote:
Why are you removing PulseAudio?? Technically speaking, there is no reason to do so though a very long time ago, an older version of Raspbian did have an issue with it.? There is no reason to remove it in modern versions of the Raspberry Pi OS and any documentation recommending this is old.
The directions, which I posted, said to delete pulseaudio.
? Next, which Btech cable are you using here?? Is it this one?
??
Yes
If so, what kinda of a sound card are you using with it because it's just an audio adapter cable with a simple circuit to support PTT.
? and
Regarding your audio levels, ever sound card will have it's own behavior.? As such, you'll have to re-turn the playback and microphone levels appropriately.? Also be aware that some sound devices also have advanced features like "Gain Boost" toggles, AGC toggles, etc. so you'll need to enable/disable them to provide proper audio levels to properly work with your radio.
--David
KI6ZHD
|
Re: Rasberry Pi 3, Direwolf, USB soundcard doesn't digipeat packets.
I am attempting to construct an APRS digipeater/igate using a Raspbery Pi 3 running Bullseye and Direwolf a Baofeng UV5R and a USB sound card following directions: from . I am using a btech APRS cable to interface the radio to the soundcard.
It appears the instructions above include enabling VOX in the Baofeng radio. Relying on VOX in a radio for PTT is not recommended, and I believe it states that in the Direwolf user guide.
I was successfully using a SignaLink, without the Baofeng on vox.
Yes the Signalink uses its own fast VOX implementation for PTT, so it keys the radio using the standard PTT input. One guess is that Baofeng radios have variable quality in terms of how well the VOX works. Also I would expect poorly performing VOX to impact digipeating more than beacons. One possibility is it may be possible to tweak some settings such as TX delay and see if it works better.
The system successfully beacons on air and igates. I can use Xastir to beacon, but when the system attempts to digipeat, the UV5R will key but it doesn't transmit any packets... sounding something like an open mic.
If the intent is to use something smaller and less expensive than a Signalink, you could potentially use a DINAH or equivalent, but the cabling would have to be adapted to the radio's audio in/out and PTT in.
73, Lee K5DAT
|
Re: Rasberry Pi 3, Direwolf, USB soundcard doesn't digipeat packets.
Why are you removing PulseAudio?? Technically
speaking, there is no reason to do so though a very long time ago,
an older version of Raspbian did have an issue with it.? There is
no reason to remove it in modern versions of the Raspberry Pi OS
and any documentation recommending this is old.? Next, which Btech
cable are you using here?? Is it this one?
??
If so, what kinda of a sound card are you using with it because
it's just an audio adapter cable with a simple circuit to support
PTT.
Regarding your audio levels, ever sound card will have it's own
behavior.? As such, you'll have to re-turn the playback and
microphone levels appropriately.? Also be aware that some sound
devices also have advanced features like "Gain Boost" toggles, AGC
toggles, etc. so you'll need to enable/disable them to provide
proper audio levels to properly work with your radio.
--David
KI6ZHD
On 06/11/2022 06:08 AM, Rick Hatton
wrote:
toggle quoted message
Show quoted text
I swapped the Signalink back in and reinstalled Pulse
Audio. The system digipeated.
I swapped the btech cable back in and there was no data out on
digipeat.
The SignaLink is back in for now .. digipeating.
With the usb sound card and btech cable, the audio levels were low
when beaconing.
|
Re: RTL-SDR / Direwolf IGate Start-up Configuration
Also the WorkingDirectory needs to be where the direwolf.conf file is located, which may not necessarily be /home/pi.
On Sat, Jun 11, 2022 at 12:53 PM Lee D Bengston < kilo5dat@...> wrote: I use systemd.? Just dug this up from a previous post.
Below is one way to do it.
Install screen: sudo apt install screen
Create a text file named direwolf.service and put it in?the /etc/systemd/system directory. The contents of the file are shown below:
Description=Direwolf After=network.target
[Service] Type=forking WorkingDirectory=/home/pi User=pi Group=pi ExecStart=/usr/bin/screen -S dw -d -m /usr/bin/direwolf SyslogIdentifier=Direwolf
[Install] WantedBy=multi-user.target
The
above should work in a Raspberry Pi assuming the pi user applies. If
running a compiled version of Direwolf, the ExecStart line should use
/usr/local/bin/direwolf instead of /usr/bin/direwolf.? The above line in
blue applies to using Direwolf as installed from the software
repository.
After adding the text file to the specified directory, issue the following command: sudo systemctl daemon-reload
To test the new service issue the following command: sudo systemctl start direwolf
To verify direwolf started, issue the following screen -r dw?
to detach from the screen session... "Ctrl-a" followed by the letter "d"
To make the service start at boot sudo systemctl enable direwolf
Note
- if preferred it is also possible to create a small shell script that
launches direwolf - including with options in the command line, then
call the shell script in the systemd service -
something like the example below where direwolf.sh is a shell script
that launches direwolf and is located in /home/pi.
ExecStart=/usr/bin/screen -S dw -d -m /home/pi/direwolf.sh
On Sat, Jun 11, 2022 at 11:52 AM Eric Struble < eric@...> wrote: I've put together a simple Igate setup using a Raspberry Pi, running bullseye (headless), and a RTL-SDR for a receiver. It is up and running fine but I was wondering if there is a simple way to get it to run in the background and without user interaction? I would like a way to start and stop it from the command line then have it remember that setting during a re-boot.
The Direwolf manual for Raspberry Pi SDR IGate document explains how to start it from the command line and also how to add it to the /etc/rc.local file but then goes on to say that is not a good idea. It follows up with using dw_start.sh file to enable it.?
If I need to, I can edit the dw_start.sh file but I was wondering if someone has come up with a better way to enable the IGate application through Direwolf with a rtf-sdr. If this isn't a good method to create a fill-in IGate, I could always scrap the plan and just use an old mobile rig with a RA-45 interface.?
Just looking for ideas on what people have found that works and what doesn't.
Thanks,
Eric, W7CSD
|
Re: RTL-SDR / Direwolf IGate Start-up Configuration
I use systemd.? Just dug this up from a previous post.
Below is one way to do it.
Install screen: sudo apt install screen
Create a text file named direwolf.service and put it in?the /etc/systemd/system directory. The contents of the file are shown below:
Description=Direwolf After=network.target
[Service] Type=forking WorkingDirectory=/home/pi User=pi Group=pi ExecStart=/usr/bin/screen -S dw -d -m /usr/bin/direwolf SyslogIdentifier=Direwolf
[Install] WantedBy=multi-user.target
The
above should work in a Raspberry Pi assuming the pi user applies. If
running a compiled version of Direwolf, the ExecStart line should use
/usr/local/bin/direwolf instead of /usr/bin/direwolf.? The above line in
blue applies to using Direwolf as installed from the software
repository.
After adding the text file to the specified directory, issue the following command: sudo systemctl daemon-reload
To test the new service issue the following command: sudo systemctl start direwolf
To verify direwolf started, issue the following screen -r dw?
to detach from the screen session... "Ctrl-a" followed by the letter "d"
To make the service start at boot sudo systemctl enable direwolf
Note
- if preferred it is also possible to create a small shell script that
launches direwolf - including with options in the command line, then
call the shell script in the systemd service -
something like the example below where direwolf.sh is a shell script
that launches direwolf and is located in /home/pi.
ExecStart=/usr/bin/screen -S dw -d -m /home/pi/direwolf.sh
On Sat, Jun 11, 2022 at 11:52 AM Eric Struble < eric@...> wrote: I've put together a simple Igate setup using a Raspberry Pi, running bullseye (headless), and a RTL-SDR for a receiver. It is up and running fine but I was wondering if there is a simple way to get it to run in the background and without user interaction? I would like a way to start and stop it from the command line then have it remember that setting during a re-boot.
The Direwolf manual for Raspberry Pi SDR IGate document explains how to start it from the command line and also how to add it to the /etc/rc.local file but then goes on to say that is not a good idea. It follows up with using dw_start.sh file to enable it.?
If I need to, I can edit the dw_start.sh file but I was wondering if someone has come up with a better way to enable the IGate application through Direwolf with a rtf-sdr. If this isn't a good method to create a fill-in IGate, I could always scrap the plan and just use an old mobile rig with a RA-45 interface.?
Just looking for ideas on what people have found that works and what doesn't.
Thanks,
Eric, W7CSD
|
RTL-SDR / Direwolf IGate Start-up Configuration
I've put together a simple Igate setup using a Raspberry Pi, running bullseye (headless), and a RTL-SDR for a receiver. It is up and running fine but I was wondering if there is a simple way to get it to run in the background and without user interaction? I would like a way to start and stop it from the command line then have it remember that setting during a re-boot.
The Direwolf manual for Raspberry Pi SDR IGate document explains how to start it from the command line and also how to add it to the /etc/rc.local file but then goes on to say that is not a good idea. It follows up with using dw_start.sh file to enable it.?
If I need to, I can edit the dw_start.sh file but I was wondering if someone has come up with a better way to enable the IGate application through Direwolf with a rtf-sdr. If this isn't a good method to create a fill-in IGate, I could always scrap the plan and just use an old mobile rig with a RA-45 interface.?
Just looking for ideas on what people have found that works and what doesn't.
Thanks,
Eric, W7CSD
|
Re: Rasberry Pi 3, Direwolf, USB soundcard doesn't digipeat packets.
I swapped the Signalink back in and reinstalled Pulse Audio. The system digipeated.
I swapped the btech cable back in and there was no data out on digipeat.
The SignaLink is back in for now .. digipeating.
With the usb sound card and btech cable, the audio levels were low when beaconing.
|
Re: Rasberry Pi 3, Direwolf, USB soundcard doesn't digipeat packets.
The splitter is for a headset, splitting mic and headphones.
The system does transmit data on beacon from direwolf and Xastir, but there is not data when digipeating. Direwolf does hear incoming traffic and does gate it.
|
Re: FT60R PTT EasyDigi [SOLVED]
Ok,?
I have it working. ?Thanks for reminding me about the CT-44. ?I actually have three of them that built up (I do a bit of Wires-X), so had a spare one. ?Apparently the FT60R’s mic input isn’t a standard TRRS, but the CT-44 works great with it. ? Of course, since I just had one combined line coming out of the EasyDig and the CT-44 has two inputs (speaker and mic), I had to use a splitter first. Then, since one of them is a 2.5mm input, I had to use a 3.5mm to 2.5mm adapter as well, but it all works.
Thanks for the CT-43 reminder!
toggle quoted message
Show quoted text
On Jun 10, 2022, at 5:50 PM, J K <kuhnje@...> wrote:
? It’s the cable. ?I have to do the same thing to get it to work with my FT70DR. ?Problem with pulpy the cable slight out is that audio goes both out the speaker and RX cable. ?Obviously I don’t want audio going out the speaker. ?Looks like new to get this cable fixed. 13 Pro Max On Jun 10, 2022, at 5:47 PM, David Ranch <direwolf-groupsio@...> wrote:
?
Oh interesting.. similar to this is a common issue
with Baofeng radios with programming cables and the issue is on
the Baofeng radio itself.? I've never heard this on Yaesu radios.?
Regardless, good to hear you got things working but you might have
a failing radio or a improperly made cable and this "iffyness"
will probably lead to unreliable packet connections.
--David
KI6ZHD
On 06/10/2022 02:33 PM, J K via
groups.io wrote:
I got it to work. ?I can’t push the audio cable fully in the
FT60R. ?I have to pull it back out s little then it works.
13 Pro Max
?
There is a schematic posted here (bottom image
on the right):
??
To me, it seems like your Direwolf configuration using "DTR
RTS" should work.? Are you *sure* that /dev/ttyUSB0 is the
correct device for this blue USB to serial port cable?
--David
KI6ZHD
On 06/10/2022 02:26 PM, J K via
groups.io wrote:
It’s an EasyDigi with USB PTT cable.
13 Pro Max
On Jun 10, 2022, at 5:16 PM,
Martin Cooper via groups.io <kd6yam@...>
wrote:
?
You
didn't say how you're connecting between the Easy
Digi and the FT-60R. Whatever cable you're using
needs to be carrying the PTT signal to the radio,
in addition to the audio signal.
Martin.
KD6YAM
Hi,
Is anyone else using a FT60R and EasyDigi?
I just received one.?It
receives well, but can’t get it to TX. I’m
using a Raspberry Pi running DireWolf. I
know the audio is getting out of the sound
device because if I plug in a set of
headphones, I can hear the burst. I’m
thinking it must by the PTT (?). In
direwolf.conf, I have the following line for
PTT:
PTT
/dev/ttyUSB0 RTS DTR
This
is exactly what I used with the K2-2pin
EasyDigi with USB and it worked great. I
tried every variation of RTS, -RTS, DTR,
-DTR also and nothing worked.? Ie, i tried:
PTT
/dev/USB0 RTS DTR
PTT
/dev/USB0 -RTS DTR
PTT
/dev/USB0 RTS -DTR
PTT
/dev/USB0 -RTS -DTR
Any
help would be most appreciated.
Thanks!
13 Pro Max
|
Re: Rasberry Pi 3, Direwolf, USB soundcard doesn't digipeat packets.
Be sure that you have a headphone/mic splitter and not a headphone sharing device.? ?One is tip/ring/sleeve other is tip/ring/ring/sleeve.? ?You can do all kinds of things using that uv5 vox mode that don't? require fast switching to rx....mumble, echolink,allstar,etc but won't do varafm Herbert KD5PQJ?
|
Rasberry Pi 3, Direwolf, USB soundcard doesn't digipeat packets.
I am attempting to construct an APRS digipeater/igate using a Raspbery Pi 3 running Bullseye and Direwolf a Baofeng UV5R and a USB sound card following directions: from https://n1aae.com/raspberry-pi-aprs-direwolf-linux-igate-digipeater/. I am using a btech APRS cable to interface the radio to the soundcard.
I was successfully using a SignaLink, without the Baofeng on vox.
The system successfully beacons on air and igates. I can use Xastir to beacon, but when the system attempts to digipeat, the UV5R will key but it doesn't transmit any packets... sounding something like an open mic.
Does anyone have an idea what I might look at to fix this?
|
Thanks! ?That is extremely helpful. I will likely send this back and get one with two audio cables (transmit/receive) and use a CT-44 (I have two of those here).
Thanks again, Jerry
13 Pro Max
toggle quoted message
Show quoted text
On Jun 10, 2022, at 7:53 PM, J K via groups.io <kuhnje@...> wrote:
? Thanks! ?That is extremely helpful. I will likely send this back and get one with two audio cables (transmit/receive) and use a CT-41 (I have two of those here).
Thanks again, Jerry 13 Pro Max On Jun 10, 2022, at 7:40 PM, Rob Giuliano via groups.io <kb8rco@...> wrote:
? I have an FT60R HT and have used it for packet. The biggest issue is the SRRT (Sleeve, Ring, Ring, Tip) Mic jack.? I tried all kinds of electronics store plugs, but none worked.? I finally bought the Yaesu CT-44 interface cable.? That was the only one that actually matched the jack.
Next, you have to configure the interface so that the Mic Audio goes through a 10uF cap, and there is a 2k2 resistor to the PTT.? When the PTT pin goes low, the Mic input sees 2k2 ohms impedance.? Without the 2k2 resistor, you are shorting the TNC audio to ground.? That also means you need -DTR (so the DTR pin is grounded when you request TX).
On Friday, June 10, 2022 at 05:16:47 PM EDT, Martin Cooper via groups.io <kd6yam@...> wrote:
You didn't say how you're connecting between the Easy Digi and the FT-60R. Whatever cable you're using needs to be carrying the PTT signal to the radio, in addition to the audio signal.
Martin. KD6YAM Hi,
Is anyone else using a FT60R and EasyDigi? I just received one.?It receives well, but can’t get it to TX. I’m using a Raspberry Pi running DireWolf. I know the audio is getting out of the sound device because if I plug in a set of headphones, I can hear the burst. I’m thinking it must by the PTT (?). In direwolf.conf, I have the following line for PTT:
PTT /dev/ttyUSB0 RTS DTR
This is exactly what I used with the K2-2pin EasyDigi with USB and it worked great. I tried every variation of RTS, -RTS, DTR, -DTR also and nothing worked.? Ie, i tried:
PTT /dev/USB0 RTS DTR PTT /dev/USB0 -RTS DTR PTT /dev/USB0 RTS -DTR PTT /dev/USB0 -RTS -DTR
Any help would be most appreciated.Thanks!13 Pro Max
|
Thanks! ?That is extremely helpful. I will likely send this back and get one with two audio cables (transmit/receive) and use a CT-41 (I have two of those here).
Thanks again,
toggle quoted message
Show quoted text
On Jun 10, 2022, at 7:40 PM, Rob Giuliano via groups.io <kb8rco@...> wrote:
? I have an FT60R HT and have used it for packet. The biggest issue is the SRRT (Sleeve, Ring, Ring, Tip) Mic jack.? I tried all kinds of electronics store plugs, but none worked.? I finally bought the Yaesu CT-44 interface cable.? That was the only one that actually matched the jack.
Next, you have to configure the interface so that the Mic Audio goes through a 10uF cap, and there is a 2k2 resistor to the PTT.? When the PTT pin goes low, the Mic input sees 2k2 ohms impedance.? Without the 2k2 resistor, you are shorting the TNC audio to ground.? That also means you need -DTR (so the DTR pin is grounded when you request TX).
On Friday, June 10, 2022 at 05:16:47 PM EDT, Martin Cooper via groups.io <kd6yam@...> wrote:
You didn't say how you're connecting between the Easy Digi and the FT-60R. Whatever cable you're using needs to be carrying the PTT signal to the radio, in addition to the audio signal.
Martin. KD6YAM Hi,
Is anyone else using a FT60R and EasyDigi? I just received one.?It receives well, but can’t get it to TX. I’m using a Raspberry Pi running DireWolf. I know the audio is getting out of the sound device because if I plug in a set of headphones, I can hear the burst. I’m thinking it must by the PTT (?). In direwolf.conf, I have the following line for PTT:
PTT /dev/ttyUSB0 RTS DTR
This is exactly what I used with the K2-2pin EasyDigi with USB and it worked great. I tried every variation of RTS, -RTS, DTR, -DTR also and nothing worked.? Ie, i tried:
PTT /dev/USB0 RTS DTR PTT /dev/USB0 -RTS DTR PTT /dev/USB0 RTS -DTR PTT /dev/USB0 -RTS -DTR
Any help would be most appreciated.Thanks!13 Pro Max
|
I have an FT60R HT and have used it for packet. The biggest issue is the SRRT (Sleeve, Ring, Ring, Tip) Mic jack.? I tried all kinds of electronics store plugs, but none worked.? I finally bought the Yaesu CT-44 interface cable.? That was the only one that actually matched the jack.
Next, you have to configure the interface so that the Mic Audio goes through a 10uF cap, and there is a 2k2 resistor to the PTT.? When the PTT pin goes low, the Mic input sees 2k2 ohms impedance.? Without the 2k2 resistor, you are shorting the TNC audio to ground.? That also means you need -DTR (so the DTR pin is grounded when you request TX).
On Friday, June 10, 2022 at 05:16:47 PM EDT, Martin Cooper via groups.io <kd6yam@...> wrote:
You didn't say how you're connecting between the Easy Digi and the FT-60R. Whatever cable you're using needs to be carrying the PTT signal to the radio, in addition to the audio signal.
Martin. KD6YAM
Hi,
Is anyone else using a FT60R and EasyDigi? I just received one.?It receives well, but can’t get it to TX. I’m using a Raspberry Pi running DireWolf. I know the audio is getting out of the sound device because if I plug in a set of headphones, I can hear the burst. I’m thinking it must by the PTT (?). In direwolf.conf, I have the following line for PTT:
PTT /dev/ttyUSB0 RTS DTR
This is exactly what I used with the K2-2pin EasyDigi with USB and it worked great. I tried every variation of RTS, -RTS, DTR, -DTR also and nothing worked.? Ie, i tried:
PTT /dev/USB0 RTS DTR PTT /dev/USB0 -RTS DTR PTT /dev/USB0 RTS -DTR PTT /dev/USB0 -RTS -DTR
Any help would be most appreciated.Thanks!13 Pro Max
|
Baofeng radios also have terrible TX audio flatness.
On 11/06/2022 7:47 am, David Ranch
wrote:
toggle quoted message
Show quoted text
Oh interesting.. similar to this is a common issue
with Baofeng radios with programming cables and the issue is on
the Baofeng radio itself.? I've never heard this on Yaesu
radios.? Regardless, good to hear you got things working but you
might have a failing radio or a improperly made cable and this
"iffyness" will probably lead to unreliable packet connections.
--David
|
It’s the cable. ?I have to do the same thing to get it to work with my FT70DR. ?Problem with pulling the cable slight out is that audio goes both out the speaker and RX cable. ?Obviously I don’t want audio going out the speaker. ?Looks like need to get this cable fixed.
toggle quoted message
Show quoted text
On Jun 10, 2022, at 5:50 PM, J K <kuhnje@...> wrote:
? It’s the cable. ?I have to do the same thing to get it to work with my FT70DR. ?Problem with pulpy the cable slight out is that audio goes both out the speaker and RX cable. ?Obviously I don’t want audio going out the speaker. ?Looks like new to get this cable fixed. 13 Pro Max On Jun 10, 2022, at 5:47 PM, David Ranch <direwolf-groupsio@...> wrote:
?
Oh interesting.. similar to this is a common issue
with Baofeng radios with programming cables and the issue is on
the Baofeng radio itself.? I've never heard this on Yaesu radios.?
Regardless, good to hear you got things working but you might have
a failing radio or a improperly made cable and this "iffyness"
will probably lead to unreliable packet connections.
--David
KI6ZHD
On 06/10/2022 02:33 PM, J K via
groups.io wrote:
I got it to work. ?I can’t push the audio cable fully in the
FT60R. ?I have to pull it back out s little then it works.
13 Pro Max
?
There is a schematic posted here (bottom image
on the right):
??
To me, it seems like your Direwolf configuration using "DTR
RTS" should work.? Are you *sure* that /dev/ttyUSB0 is the
correct device for this blue USB to serial port cable?
--David
KI6ZHD
On 06/10/2022 02:26 PM, J K via
groups.io wrote:
It’s an EasyDigi with USB PTT cable.
13 Pro Max
On Jun 10, 2022, at 5:16 PM,
Martin Cooper via groups.io <kd6yam@...>
wrote:
?
You
didn't say how you're connecting between the Easy
Digi and the FT-60R. Whatever cable you're using
needs to be carrying the PTT signal to the radio,
in addition to the audio signal.
Martin.
KD6YAM
Hi,
Is anyone else using a FT60R and EasyDigi?
I just received one.?It
receives well, but can’t get it to TX. I’m
using a Raspberry Pi running DireWolf. I
know the audio is getting out of the sound
device because if I plug in a set of
headphones, I can hear the burst. I’m
thinking it must by the PTT (?). In
direwolf.conf, I have the following line for
PTT:
PTT
/dev/ttyUSB0 RTS DTR
This
is exactly what I used with the K2-2pin
EasyDigi with USB and it worked great. I
tried every variation of RTS, -RTS, DTR,
-DTR also and nothing worked.? Ie, i tried:
PTT
/dev/USB0 RTS DTR
PTT
/dev/USB0 -RTS DTR
PTT
/dev/USB0 RTS -DTR
PTT
/dev/USB0 -RTS -DTR
Any
help would be most appreciated.
Thanks!
13 Pro Max
|
It’s the cable. ?I have to do the same thing to get it to work with my FT70DR. ?Problem with pulpy the cable slight out is that audio goes both out the speaker and RX cable. ?Obviously I don’t want audio going out the speaker. ?Looks like new to get this cable fixed. 13 Pro Max
toggle quoted message
Show quoted text
On Jun 10, 2022, at 5:47 PM, David Ranch <direwolf-groupsio@...> wrote:
?
Oh interesting.. similar to this is a common issue
with Baofeng radios with programming cables and the issue is on
the Baofeng radio itself.? I've never heard this on Yaesu radios.?
Regardless, good to hear you got things working but you might have
a failing radio or a improperly made cable and this "iffyness"
will probably lead to unreliable packet connections.
--David
KI6ZHD
On 06/10/2022 02:33 PM, J K via
groups.io wrote:
I got it to work. ?I can’t push the audio cable fully in the
FT60R. ?I have to pull it back out s little then it works.
13 Pro Max
?
There is a schematic posted here (bottom image
on the right):
??
To me, it seems like your Direwolf configuration using "DTR
RTS" should work.? Are you *sure* that /dev/ttyUSB0 is the
correct device for this blue USB to serial port cable?
--David
KI6ZHD
On 06/10/2022 02:26 PM, J K via
groups.io wrote:
It’s an EasyDigi with USB PTT cable.
13 Pro Max
On Jun 10, 2022, at 5:16 PM,
Martin Cooper via groups.io <kd6yam@...>
wrote:
?
You
didn't say how you're connecting between the Easy
Digi and the FT-60R. Whatever cable you're using
needs to be carrying the PTT signal to the radio,
in addition to the audio signal.
Martin.
KD6YAM
Hi,
Is anyone else using a FT60R and EasyDigi?
I just received one.?It
receives well, but can’t get it to TX. I’m
using a Raspberry Pi running DireWolf. I
know the audio is getting out of the sound
device because if I plug in a set of
headphones, I can hear the burst. I’m
thinking it must by the PTT (?). In
direwolf.conf, I have the following line for
PTT:
PTT
/dev/ttyUSB0 RTS DTR
This
is exactly what I used with the K2-2pin
EasyDigi with USB and it worked great. I
tried every variation of RTS, -RTS, DTR,
-DTR also and nothing worked.? Ie, i tried:
PTT
/dev/USB0 RTS DTR
PTT
/dev/USB0 -RTS DTR
PTT
/dev/USB0 RTS -DTR
PTT
/dev/USB0 -RTS -DTR
Any
help would be most appreciated.
Thanks!
13 Pro Max
|
Eric Struble