Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Direwolf
- Messages
Search
|
Digipeating Path
I have noticed what I feel may be a bug or a simple newbie error. I'm unable to have my station digipeat stations that it hears like the following, NA7Q,APX202,MEGLER*,WIDE1,WIDE2-1:=........ My settings?DIGIPEAT 0 0 ^WIDE[3-7]-[1-7]$ ^WIDE[12]-[12]$ TRACE Am I missing something? It will repeat if the WIDE1 is not present. I'm not the latest updates of Jessie and Direwolf dev. |
|
Re: Getting PTT working
David Ranch
开云体育Hello Lee, ? Ok.. but now you know that the Rpi and Direwolf are working.? That's key!
Is this the PTT LED on James N7SET's RPi-WD-Packet_Interface board (good picture of a built unit -and a printable case: ). Is that with just the +3.3v and ground line connected?? No radio or audio connections connected?? Btw, per the main readme at Github: -- Selectable single-wire handheld PTT or 'Kenwood' dedicated PTT wire method ??? Most HTs use a resistor to ground on the microphone input to trigger PTT. Kenwood/Baofeng and some others have to be different and ground the mic shield to trigger. You can set a jumper to select whatever method you need. -- That's the JP6.? Do you see any different behavior with the jumper on/off?
Right.? Curious, have you adjusted the TX timeout pot to see if the PTT LED will go OUT after a period of time?
Beyond that, only two ideas: ? 1. Are you absolutely sure you used a CMOS 555 timer - not a TTL level part - This is critical - ? 2. You're going to need to trace the connections through the PCB and see why either Q1 or the 555 is making things behave like this. --David KI6ZHD |
|
Re: Getting PTT working
David,
Thanks for your response to my question. ?I took your suggestion and wired up a LED with the 1K resistor. Using some proper RPi jumper cables, I did get a response on GPIO 25; i.e. the LED lit up. I think the biggest issue here was trying to cobble together a cable that I thought would work and it didn't. With that out of the way I hooked up RPi-WD-Packet_Interface. ?What I noticed is that the LED for the PTT stays high (even with just the power and ground connected), while the DCD LED responds to the RPi when the Beacon signal is sent. I did solder the PCB myself (actually 2 of them because I thought the first one didn't work) and they both respond the same way with the PTT LED being constantly high. ?I assume that is why when I remove the jumper from J6, the radio stays in transmit mode (I'm just guessing now). Any thoughts? Thanks again David for your help. ? Lee |
|
Re: Getting PTT working
David Ranch
开云体育Hello Lee, ? Few questions here: ?? 1. What OS did and version is running on your Rpi v1 B+? ?? 2. What USB sound card are you using with the Rpi? 1 B+ ?? 3. Is the USB sound card directly connected to your Rpi (that's recommended) What pin on the GPIO header are you using for PTT?? Is there a specific reason why your trying to use some of the alternative GPIO mappings?? Just use the stock GPIO setup. Per the Direwolf documentation, it has the following recommendations: ?? Raspberry Pi pin 11 - GPIO 17 ?? Raspberry Pi pin 15 - GPIO 22 ?? Raspberry Pi pin 16 - GPIO 23 ?? Raspberry Pi pin 18 - GPIO 24 ?? Raspberry Pi pin 22 - GPIO 25 Check out for a helpful interactive tool to see the pinouts, functions, etc.? Once you have that, I would recommend to wire up an LED through a 1K resistor between ground and your chosen PTT GPIO pin.? Now go into the Direwolf configuration and setup a beacon to run every minute so you can observe the PTT in action: ?? #An object beacon that will be located north of Boston, MA ?? OBEACON delay=0:01 every=1 overlay=S symbol="digi" lat=42^37.00N long=071^00.00W power=50 height=20 gain=4 OBJNAME=TESTBCN comment="test beacon" via=WIDE1-1 You should see the LED light up just after Direwolf starts up and every 60 seconds after that.? If you don't, reverse the connections to the LED (you might have mixed up the anode and cathode): ????? - connect to cathode of LED (short lead / smaller metal inside LED) to GPIO pin ????? - connect to anode of LED (long lead / larger metal inside LED) to GND pin Once you can confirm that the PTT signal is being asserted, then you have to troubleshoot things through the RPi-WD-Packet-Interface.?? Did you have that board made for you or did you solder it together yourself?? It's a very nice board but it's a bit complicated as it has a 555 timer on it to shutdown your radio on PTT issues from the Rpi, etc.? --David KI6ZHD |
|
Getting PTT working
? I’m having a terrible time getting my Raspberry Pi, Dire Wolf and the RPi-WD-Packet-Interface (https://github.com/jaymzx/RPi-WD-Packet-Interface) to all cooperate.? I’m running Dire Wolf Version 1.3 on a model B+ Pi with a USB sound dongle.? I’ m trying to transmit through a iCom 2300H. ??The system works beautifully receiving APRS packets.? Where I can’t get it to run is sending out anything through the packet interface board.? The Pi does send information out through the sound dongle but that’s where it stops. I’ve followed the steps to release the serial port on the Pi and reassign a couple of GPIO pins to ALT3.? If I remove the jumper from JP6 ?(PTT Resistor) the radio does go into transmit mode. Not sure what the next step to troubleshoot the problem is. ?
Kind’a new at all this stuff so bear with me. Thanks Lee |
|
direwolf 1.4 beta test
direwolf version 1.4 beta test is now available.?
You can find a list of new features and bug fixes here:
If no significant issues are reported, it will soon become the 1.4 release and the default download version. On Linux, you can get the most recent version with these commands:? git clone cd direwolf git checkout dev make sudo make install For Windows, go to the releases page and download?. ? |
|
Re: Q-construct difference between two versions of Dire Wolf?
From comments in source file igate.c.
/* ?* It seems that the specification has changed recently. ?* http://www.tapr.org/pipermail/aprssig/2016-December/046456.html ?* ?* We can see the history at the Internet Archive Wayback Machine. ?* ?* http://www.aprs-is.net/Connecting.aspx ?* captured Oct 19, 2016: ?* ... Only the qAR construct may be generated by a client (IGate) on APRS-IS. ?* Captured Dec 1, 2016: ?* ... Only the qAR and qAO constructs may be generated by a client (IGate) on APRS-IS. ?* ?* http://www.aprs-is.net/q.aspx ?* Captured April 23, 2016: ?* (no mention of client generating qAO.) ?* Captured July 19, 2016: ?* qAO - (letter O) Packet is placed on APRS-IS by a receive-only IGate from RF. ?* The callSSID following the qAO is the callSSID of the IGate. Note that receive-only ?* IGates are discouraged on standard APRS frequencies. Please consider a bidirectional ?* IGate that only gates to RF messages for stations heard directly. ?*/ The previous version of Dire Wolf always used qAR when sending to the APRS-IS server. The current version uses qAO when configured as a receive only IGate. ?I suppose this would inform the server that it would be wasting its time by by asking the IGate station to transmit something. As for keying the transmitter each time something is received, more details are needed to figure out what is going on. ?configuration file? ?screen capture? |
|
Re: Q-construct difference between two versions of Dire Wolf?
Also here is the qAR construct descriptions
Server Generated: qAR - Packet was received directly (via a verified connection) from an IGate using the ,I construct. The callSSID following the qAR it the callSSID of the IGate. Client Generated: qAR - Packet is placed on APRS-IS by an IGate from RF. The callSSID following the qAR is the callSSID of the IGate. One other thing is that Version 1.4 keys the tranceiver with every received packet as if it is a digipeter. I don't understand why it is doing that either.? Is there something that I need to configure in the config file? Any insight would be appreciated. 73, Mike, NA5SS |
|
Q-construct difference between two versions of Dire Wolf?
The strings below are from findu.com today.? I don't understand why the Q construct is different for these two versions of Dire Wolf..
I first noticed this yesterday when I downloaded the latest Windows version. Server Generated: qAO - (letter O) Packet was received via a client-only port and the FROMCALL does not match the login. Client generated: qAO - (letter O) Packet is placed on APRS-IS by a receive-only IGate from RF. The callSSID following the qAO is the callSSID of the IGate. Note that receive-only IGates are discouraged on standard APRS frequencies. Please consider a bidirectional IGate that only gates to RF messages for stations heard directly. Maybe there is no problem.? I guess that I just don't understand why the difference. 73, Mike, NA5SS Dire Wolf Version 1.4 (Apr 2 2017) Beta test 00:00:00:16 : N0VWX]CQ,RS0ISS*,qAO,NA5SS-10:=3821.15N/10547.30W-+3821.15N110547.30W Hello from Colorado {UISS54} 00:00:00:23 : W7QL]CQ,RS0ISS*,qAO,NA5SS-10::WD9EWK :ack02 00:00:00:25 : N0VWX]CQ,RS0ISS*,qAO,NA5SS-10:+3821.15N110547.30W UISS Ver 5.40 Dire Wolf-1.3.1 00:11:10:03 : PSAT-1]APOFF,ARISS,qAR,NA5SS-10:T#155,810,073,948,552,812,00011100 00:11:10:22 : PSAT-1]APOFF,ARISS,qAR,NA5SS-10:s#005525,0z001 00:11:11:04 : PSAT-1]APOFF,ARISS,qAR,NA5SS-10:T#154,821,073,950,566,811,00011100 |
|
Re: Transmit Audio Sending Over Wring Sound Card
David Ranch
开云体育Hello Ronnie, Ok.. everything looks good.? I would next recommend to install the final Direwolf 1.4 Beta available at: ?? I have also posted a .deb of it here for Rasbian 8/Jessie if you wish (not an official binary): ?? This new code might still have the issue but it's a key starting point to make sure the issue still exists. --David KI6ZHD |
|
Re: Transmit Audio Sending Over Wring Sound Card
Hi David, thanks for the reply.
Linux raspberrypi 4.4.38-v7+ #938 SMP Thu Dec 15 15:22:21 GMT 2016 armv7l GNU/Linux PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)" NAME="Raspbian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" DW Version 1.3 Pulseaudio, no, not installed... sudo apt-get remove --purge pulseaudio ... Package 'pulseaudio' is not installed, so not removed |
|
Re: Direwolf 1.4 developer Raspbian
开云体育Thank you David! Nick Ellson - from iPhone (forgive typos) CCIE #20018; VCIX-NV, CNSE Network Hobbyist "Educating Layer 8, one user at a time." On Apr 8, 2017, at 4:31 PM, David Ranch dranch@... [direwolf_packet] <direwolf_packet@...> wrote:
|
|
Re: Audio "Feedback"
David Ranch
开云体育Hello Mike, ? Ok, if you have a digital volt meter (DVM), measure the voltage from the radio's mic line to ground.? Do the same measuring the sound card's mic line to ground.? You'll probably observe +5 volts on those lines.? If you see this and you're not using a basic/small 10uF cap on those mic lines, you're sending that voltage right into your respective radio or sound cards which can damage them.? I would highly recommend you get those small capacitors installed.
I would recommend a variable resistor if you need it though many radios offer variable output and you can usually use the "alsamixer" program to change your sound card levels too.? If you use alsamixer, please remember that the setting is only temporary.? If you want to store and recall those settings, you need to use the alsactl program and manually save the levels.? To restore them upon every boot, again use "alsactl restore" in a script that runs at boot (such as rc.local). --David |
|
Re: Audio "Feedback"
With the simple setups im using only resistors in line with the outgoing and incoming wires to the sound card. No pots, capacitors, chokes or anything else. The wires are no more than a foot long. I'm using various types of cables, most from speaker mics and shielded aux cables.
Mic/mic ground wires go from the radio to the sound card speaker tip and sleeve with a 50K resistor for audio leveling. Identical setup from the speaker to sound card mic. Using a 100k resistor in line on the mic wire removes the heard packets but then drops the audio too low to the radio. So this is where I've found the issue to be, the speaker sound card output. Shorting them, ?y just hooking them up directly, bleeds the audio to the mic.? |
|
Re: Audio "Feedback"
David Ranch
开云体育Hello Mike, How are you wiring your sound card to your radios?? What kind of wiring (POTS phone grade wire, cat5 twisted pair, etc)?? How long are the wires?? Do you have coupling capacitors connected between both the radio's microphone input line and the soundcard's input line?? Do you have any ferrite chokes on ALL ends of all the cables? --David KI6ZHD On 04/08/2017 09:14 PM,
mike_ph4@... [direwolf_packet] wrote:
? |
|
Re: Direwolf 1.4 developer Raspbian
David Ranch
开云体育Hello Nick, All the steps required to build on Raspian is in the Direwolf docs: ?? I also have it documented in my Raspberry Pi Packet + hardening doc: ?? Anyway.. I have posted Direwolf-1.4Beta packages for Centos5 and Raspbian8/Jessie here: ?? Please note these are NOT official or signed packages.. Just built by me and packaged using either rpmbuild (for Centos) or checkinstall (for Raspbian) --David |
to navigate to use esc to dismiss