I think you can already do that.? From memory:
ADEVICE? plughw:1,0 null
I think that was the right syntax. Basically tell DW that there is
no audio device for transmit.?
We used that on a Raspberry Pi 4B as a tattle-tale packet monitor
(*) for our club repeater.? For some reason, allowing DW to open the
audio device for transmit messed up the other audio channels, even
though it never sent anything.? Something unique to the early 4B
models from what I was told.
Greg? KO6TH
(*)? The user interface of some Yaesu radios make it very easy to
misconfigure APRS to beacon on the repeater-assigned VFO.? We kept
hearing "BRRRRRAP" come through every 10 minutes but didn't know who
it was, so added DW and a cheap audio dongle to the existing Pi that
hosted our Echolink / Allstar connection.
Douglas Pervine, N1OBU wrote:
Would it be possible to have DW coded so a single Channel could
have a Receive only mode as well?
For example:
CHANNEL 0
MODEM 9600
RCV_ONLY 1200
If so, I can put a request on the github site.
|
Would it be possible to have DW coded so a single Channel could have a Receive only mode as well?
For example:
CHANNEL 0
MODEM 9600
RCV_ONLY 1200
If so, I can put a request on the github site.
|
Thank you all very much for guiding me toward the rear ports, I think I am well equipped?to head in to the realms of making/purchasing a cable for this.
KK6FPP - I am using this as part of a home config for Raynet... the UK version of ARES.
I just need to get my head around DIGI/iGate and filtering and I'll be away...
73,
Neil - 2E0LNX
On Sun, 7 Apr 2024 at 22:21, Thomas Leibold < leibold@...> wrote: Hi Neil,
We are using Yaesu FT-7900 radios for Packet Communication within our local ARES/RACES group and those radios are a good choice for that purpose.
As others have already mentioned, do use the 6-Pin data connector at the back of the radio. The one pitfall that exists with the 6-pin mini-DIN connector is that it offers two audio output signals (pins 4 and 5). Audio output on the data connector depends on the Menu Setting #26 (PKT.SPD = Packet Speed) which depending on your radio interface cable needs to be set to 1200 (receiver audio on pin 5) or 9600 (discriminator audio on pin 4).
Important: the Packet Speed setting controls the audio output for the data port. It is irrelevant what the actual data rate is that you are using. However high-speed data (9600 baud packet, VARA-FM wide) generally requires bypassing deemphasis and therefore the need to use pin 4. For 1200 baud packet or VARA-FM narrow either audio pin will work.
Again (since this is a common mistake), the menu setting controls the audio output on the data connector and needs to match the way your cable is wired. The radio does not care about the baud rate of your signal.
You may also want to set menu #25 (PKT.MIC = Packet Microphone) to disable the microphone for a radio dedicated to packet use.
You do need to use a proper hardware PTT signal. This can be a GPIO pin from the Raspberry Pi but see the DIrewolf User's Guide? for a number of other ways to produce a good PTT signal. There are DRA models (from Masters Communications) that have mini-DIN6 connectors which means you only need a straight-through cable to connect the radio to any computer with USB port. The DRA uses a GPIO pin on the audio interface to produce PTT for the radio,
This makes the Direwolf configuration easy as well (just "PTT CM108" will do in that case).
73,
Thomas
KK6FPP
|
Hi Neil,
We are using Yaesu FT-7900 radios for Packet Communication within our local ARES/RACES group and those radios are a good choice for that purpose.
As others have already mentioned, do use the 6-Pin data connector at the back of the radio. The one pitfall that exists with the 6-pin mini-DIN connector is that it offers two audio output signals (pins 4 and 5). Audio output on the data connector depends on the Menu Setting #26 (PKT.SPD = Packet Speed) which depending on your radio interface cable needs to be set to 1200 (receiver audio on pin 5) or 9600 (discriminator audio on pin 4).
Important: the Packet Speed setting controls the audio output for the data port. It is irrelevant what the actual data rate is that you are using. However high-speed data (9600 baud packet, VARA-FM wide) generally requires bypassing deemphasis and therefore the need to use pin 4. For 1200 baud packet or VARA-FM narrow either audio pin will work.
Again (since this is a common mistake), the menu setting controls the audio output on the data connector and needs to match the way your cable is wired. The radio does not care about the baud rate of your signal.
You may also want to set menu #25 (PKT.MIC = Packet Microphone) to disable the microphone for a radio dedicated to packet use.
You do need to use a proper hardware PTT signal. This can be a GPIO pin from the Raspberry Pi but see the DIrewolf User's Guide for a number of other ways to produce a good PTT signal. There are DRA models (from Masters Communications) that have mini-DIN6 connectors which means you only need a straight-through cable to connect the radio to any computer with USB port. The DRA uses a GPIO pin on the audio interface to produce PTT for the radio,
This makes the Direwolf configuration easy as well (just "PTT CM108" will do in that case).
73,
Thomas
KK6FPP
|
You might find the direwolf Radio Interface Guide helpful.
73,
John WB2OSZ
|
Hello Neil,
1, Is there any reason why this might not work?
No.. it should work fine.? Both the FT897 and the FT7900 offer a
rear 6pin DIN connection so that should make moving things over
pretty easily.? I would recommend to re-verify the RX and TX audio
levels though.
3, Would I need any specific cables (do I need to hook
in to the mic and speaker or can I use the port on the rear)?
Using the rear 6pin DIN connection is the recommended approach for
both 1200bps AFSK packet radio and especially 9600bps FSK packet
radio.
--David
KI6ZHD
|
>> My questions;
>> 1, Is there any reason why this might not work? ? ? ? ?? The FT7900 would work just fine, especially since it has the 6-pin miniDIN Data jack.? That is the ideal connection for your packet interface .
>> 2, Does anyone have any experience of doing the same, and if so any pointers?
???????? I don't have a FT7900, but hyave worked with the FT7100 and FT8800 (previous, similar models). ???????? You don't say what interface you are using, but these radios do NOT have a CAT PTT command and VOX is not a good idea. ???????? You best bet is to use the Pi GPIO for hardware PTT.
???????? I am a BIG fan of the Nexus DR-X (crosspatch) board for interfacing between the Pi, sound card, and radio. ?????????????? ? ? ? ?? Even if you use a normal USB sound card and only 1 channel of the DR-X, it has some nice advantages. ?? ? ? ? If you decide to buy the Fe-Pi sound card, you can get 2 channels for 2 separate radio interfaces.
>> 3, Would I need any specific cables (do I need to hook in to the mic and speaker or can I use the port on the rear)?
????????? With the Nexus DR-X board you only need a 6-pin miniDIN cable from board to radio.?? ????????? Maybe 2 short stereo cables from sound card to DR-X board.
????????? With aother interface, make sure you have the hardware PTT (either COMM port RTS, DTR, or Pi GPIO).?? ????????? Most, like the DIGIRIG (I believe), have some sort of configuration jumpers for PTT.?? ????????? Just make sure they are hardware pins and NOT CAT.
If you provide more information on the interface, we can provide more details on the cabling.
On Sunday, April 7, 2024 at 11:04:13 AM EDT, Neil Stone - 2E0LNX <neil.stone@...> wrote:
Good afternoon (at least here),
I am considering attaching a Yaesu FT-7900 to a RPi for use with DW as a Digi... I've got it (mostly) working (I think) on a FT897D, but I'd rather not tie up the multi band, multi mode rig if I can help it (I am sure you all understand).
My questions;
1, Is there any reason why this might not work?
2, Does anyone have any experience of doing the same, and if so any pointers?
3, Would I need any specific cables (do I need to hook in to the mic and speaker or can I use the port on the rear)?
Kind regards from a rather sunny southern England.
73,
Neil -?2E0LNX
|
Good afternoon (at least here),
I am considering attaching a Yaesu FT-7900 to a RPi for use with DW as a Digi... I've got it (mostly) working (I think) on a FT897D, but I'd rather not tie up the multi band, multi mode rig if I can help it (I am sure you all understand).
My questions;
1, Is there any reason why this might not work?
2, Does anyone have any experience of doing the same, and if so any pointers?
3, Would I need any specific cables (do I need to hook in to the mic and speaker or can I use the port on the rear)?
Kind regards from a rather sunny southern England.
73,
Neil -?2E0LNX
|
Re: UPDATE...Old school packet radio
Awesome, welcome back to good old command line packet! You live in an area where there is still a lot of on air packet activity. ? If you haven’t joined us on the EastNet groups.io page I would recommend you do. ? ?
? ? Brian N2KGC – President EastNet Packet Group ?
toggle quoted message
Show quoted text
From: [email protected] [mailto:[email protected]] On Behalf Of W2LPC
Sent: Sunday, March 31, 2024 2:15 PM
To: [email protected]
Subject: Re: [direwolf] UPDATE...Old school packet radio ? I hooked up my old PK-232, connected to my serial port 1 and hit "shift+*" and BAM! She came right up. No need for software when I can do it this way!
|
Re: UPDATE...Old school packet radio
I hooked up my old PK-232, connected to my serial port 1 and hit "shift+*" and BAM! She came right up. No need for software when I can do it this way!
|
Re: Old school packet radio
W2LPC,
There has been some good advice but and here is my two cents.
Putty is a good terminal program to use with the type of TNCs you mentioned. I use it with an old MFJ-1270 serial TNC, I also use Outpost Ipserial on Windows 10. Outposs PMM also works with serial modems but is designed just for sernding and retrieving messages for a BBS.
The tricky part is that you will probably need a USB-Serial adaptor (available on Amazon). I like the Gearmo because it has indicator lights. You will also need to figure out how to connect between the TNC and radio, the other tricky part.
Another group that specializes in something besides Direwolf might be better suited. The Direwolf softare and a hardware interface replace the PK-232 modems. I know there is a Facebook page for packet in addition to the resources mentioned here. I would guess there may even be a PK-232 group out there.
Good luck,
Dave
WB9TEN
|
Re: Trouble: DietPi Nano Pi Neo+Direwolf
I noticed that there are a bunch of different OS images, based on the specific Nano Pi model.
Do you have the one for your specific model?
Did you run this to get the latest updates?
sudo apt update
sudo apt upgrade
As David suggested, see if you can record from the audio device to a file.? Find the name of the default audio device being used.
You are running as root, so it should not be a permissions issue.? (i.e. user not in audio group)
Is pulseaudio running??? Early Raspbian releases had a messed up pulseaudio (but it has been OK in recent releases).
Maybe this version has issues and disabling pulseaudio might help.? Just grasping at straws here.
The DietPi forum might have some useful information:??
Would you consider using the OS recommenced by the board manufacturer??? ?
73,
John WB2OSZ
|
Re: Trouble: DietPi Nano Pi Neo+Direwolf
Yes, I tried to play the test file, it plays.I
haven't tried the recording, but it probably works too....
I would recommend not to assume and to try it.? I imagine it won't
work and if it doesn't, this isn't a direwolf issue.? This will
probably be some specific OS issue, OS configuration issue, etc.? I
see you're running the DietPi OS.? Have you tried the official
Raspberry Pi (Bookworm) OS release?
--David
KI6ZHD
|
Re: Trouble: DietPi Nano Pi Neo+Direwolf
John, thank you! But GUHOR:(
Audio device for both receive and transmit: default ?(channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate / 3, DTMF decoder enabled.
... DNS-SD: Avahi: Announcing KISS TCP on port 8001 as 'Dire Wolf on DietPi'
DNS-SD: Avahi: Service 'Dire Wolf on DietPi' successfully registered.
Audio input device 0 error code -5: Input/output error
Audio input device 0 error code -5: Input/output error
Audio input device 0 error code -5: Input/output error
Audio input device 0 error code -5: Input/output error
Audio input device 0 error code -5: Input/output error
Audio input device 0 error code -5: Input/output error
Audio input device 0 error code -5: Input/output error
Audio input device 0 error code -5: Input/output error
Audio input device 0 error code -5: Input/output error
Audio input device 0 error code -5: Input/output error
Audio input device 0 error code -5: Input/output error
Terminating after audio input failure.
Try this:
ADEVICE default
73,
John WB2OSZ
|
Re: Trouble: DietPi Nano Pi Neo+Direwolf
Try this:
ADEVICE default
73,
John WB2OSZ
|
Re: Old school packet radio
Check out EastNet Packet group on Groups.IO you can. Get a lot of help there with what your wanting to do. I'm just starting to get back into it. Originally from Sussex County NJ moved recently into Marshalls Creek PA and there is a bit of packet
activity in your and my area.. feel free to reach out direct.
73 N2KOJ.
Sent from my Verizon, Samsung Galaxy smartphone
Get
toggle quoted message
Show quoted text
Yes, I have been on the SNA node before. I downloaded the Paxon and will try it this weekend. I've had my PK-232's since new in 93' and haven't been on in about 4 years. I can't wait to get back on packet again. Thanks!
|
Re: Trouble: DietPi Nano Pi Neo+Direwolf
David, hello
Yes, I tried to play the test file, it plays. I haven't tried the recording, but it probably works too.... root@DietPi:~# aplay sample-15s.wav
Playing WAVE 'sample-15s.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Next, I tried to install the missing package, and got a little better:
root@DietPi:~# apt-get install avahi-daemon
Now when I run it I get this:
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
DNS-SD: Avahi: Announcing KISS TCP on port 8001 as 'Dire Wolf on DietPi'
DNS-SD: Avahi: Service 'Dire Wolf on DietPi' successfully registered.
Audio input device 0 error code -5: Input/output error
Audio input device 0 error code -5: Input/output error
Audio input device 0 error code -5: Input/output error
What could be causing this error?
Can you do basic audio playback or recording with
tools like aplay and arecord?
--David
KI6ZHD
On 03/13/2024 12:15 PM, Dr. Sergey
Ievkov wrote:
Hello OMs!
Now I’m trying to launch a couple of audio modems on the basis
of a Nanopi single-board computer (I started with direwolf, but
still in terms of ardop), so that I can connect to them via
Wi-Fi from android applications via TCP\IP and work in FX.25 and
Winlink.
The Nano Pi has a built-in audio card with pins to which I
planned to attach an interface and a radio.
While I can’t start the sound, using the direwolf as an example,
I do the following and get an error:
root@DietPi:~# arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 [CDC
PCM Codec-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
root@DietPi:~# cat /proc/asound/cards
0 [Codec ? ? ? ? ?]: H3_Audio_Codec - H3 Audio Codec
H3 Audio Codec
root@DietPi:~# nano /root/direwolf.conf
ADEVICE plughw:0,0
CHANNEL 0
MODEM 1200
root@DietPi:~# direwolf
Dire Wolf DEVELOPMENT version 1.8 A (Mar ?9 2024)
Includes optional support for: ?cm108-ptt dns-sd
Dire Wolf requires only privileges available to ordinary users.
Running this as root is an unnecessary security risk.
…
Audio device for both receive and transmit: plughw:0,0 ?(channel
0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample
rate / 3, DTMF decoder enabled.
…
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
DNS-SD: Avahi: Failed to create Avahi client: Daemon not running
Audio input device 0 error code -5: Input/output error
…
Audio input device 0 error code -5: Input/output error
Terminating after audio input failure.
root@DietPi:~#
Any ideas? Maybe some package is missing?
I would appreciate any help with this project.
73!
|
Hello VE7LTN,
Running Direwolf 1.7, RPi Zero 2W. Digirig, and
Baofeng UV-5R with the Baofeng cable from Digirig.?The direwolf
terminal window shows outgoing packets in pink, but these packets
don't TX.
If you configure say a PBEACON in the direwolf.conf file.. does that
key up your radio when the beacon fires? How does Direwolf key up
your radio?? A GPIO pin?? Say an RTS pine from an RS232 serial
port?? Don't use VOX as it will be both unreliable and it causes
known issues (this is covered in the Direwolf User Guide document).?
Next, for APRS to work proerly with Igating.. your packet station
(direwolf) needs to send it's position.?
?Finally, it's been covered many times here in the Direwolf email
list but many users have issues with using inexpensive radios and
packet radio.? Some people get it working.. others cannot.? for
those who cannot, some move to a better quality radio and all their
issues go away.?
--David
|
Re: Old school packet radio
Yes, I have been on the SNA node before. I downloaded the Paxon and will try it this weekend. I've had my PK-232's since new in 93' and haven't been on in about 4 years. I can't wait to get back on packet again. Thanks!
|
What do you have for PTT in the configuration file?
There are many different options and you need the one matching your radio interface.
|
Neil Stone - 2E0LNX
Brian Webster
W2LPC
