Keyboard Shortcuts
Likes
- Direwolf
- Messages
Search
|
Re: Other Stations don't decode
--
Very interesting this device has native 32000 support.? I don't think I've seen that before. -- No idea, I didn't even know how to pull the data from the devices to figure that out, so thank you! -- I'm not sure why you're seeing TWO of these though.? That's unusual if not wrong unless you have two of these unit connected -- Yes, I do have two of this connected to this machine. One for my 857 and one for the 300DR -- Your previous email said you were using "ADEVICE plughw:CARD=CODEC,DEV=0" aka.. you ARE using the "plughw" aspect of the ALSA sound system.? Anyway.. can provide some sound captures of direwolf running your SCU-17 at say 44100 and 48000 which DON'T decode on your other station?? This shouldn't be happening. Btw.. what is your other station using for a soundcard, TNC, etc? -- Yea, I realized I already had plughw set correctly after I sent that massage but I was in a hurry and didn't want to blow up people's emails with the same message. My other stations that are listening are a Raspberry Pi using a CMedia sound fob running direwolf connected to a old Kenwood commercial radio that was repurposed just to act as a iGate for the local area. We had a very large gap here in N Idaho that we filled back in. The other radio is a Yeasu FT3D hand held, neither of them would decode at 44100 or 48000 48000 sample rate gave me the following... Dire Wolf DEVELOPMENT version 1.7 E (May? 1 2022) Includes optional support for:? gpsd hamlib cm108-ptt Reading config file direwolf.conf Audio device for both receive and transmit: plughw:CARD=CODEC,DEV=0? (channel 0) Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 48000 sample rate. Warning: Calculated pre filter size of 417 is too large. Decrease the audio sample rate or increase the decimation factor. You can use -D2 or -D3, on the command line, to down-sample the audio rate before demodulating.? This greatly decreases the CPU requirements with little impact on the decoding performance.? This is useful for a slow ARM processor, such as with a Raspberry Pi model 1. Ready to accept AGW client application 0 on port 8000 ... Ready to accept KISS TCP client application 0 on port 8001 ... Interestingly enough 48000 worked for some reason this time. I've tried it before and it didn't. Got a 100% response 44100 on the other hand is attached as a wave file recorded from my iGate using FLDigi, it decoded once out of many tries. The iGate is using a CMedia sound fob -- Btw.. for your compiler errors on v1.7, this is an issue with gpsd and it's ever changing libraries.? If you can DISABLE the support for gpsd at compile time just for this test, I think that will get you going. -- Ahh, good to know, but how do I disable support for gpsd? As I'm just using direwolf as a TNC in this case I don't need it enabled but I'll add it to my notes in case I ever need to recompile and add it back in. -- Ugh.. sorry.. I was forgetting that the unit here is 10s of milliseconds.?? What you should shoot for here is say 120 to 200ms.? In Direwolf syntax, that should be a "12" to a "20". Start at "20" and see if everything works in communicating to remote packet stations (not just home packet stations).? Then slowly work your way down in say 25ms increments.? Since the FTM300 is a digital radio, I would think it can support faster than average key up times of about 150ms but you'll just have to experiment here -- Adjusted! I'll give it some testing later on but 20 sounds nice, there's not a lot of lag between key up and actual packet sending and decoding was working well. 100% success. Only small issue I see is I can't seem to get my audio level below about 70 to 80. Any lower and the pot on the SCU-17 goes quiet and adjusting it via alsamixer does nothing. -- See the Direwolf User Guide in the "MODEM" section. -- I'm content with /1. This machine is perfectly capable and is capable of running Windows 10 in a virtual environment while running everything else. Sure it slows a small bit but nothing that bothers me Between being a quad core 3.2Ghz w/HT and 32GB of RAM it should be fine Think I should add E+ or since it's default I presume it's assumed? -- I have it all written down: -- Wow, that's a heck of a guide! Looks like I've got some reading to do. I can't say I'll read it all right now but I am saving it to PDF for reference offline. Thanks a ton! |
|
Re: Headaches with direwolf + linpac
Hey Neil -
Maybe I have badly estimated what 5W can deliver on packet radio.I have run my APRS mobile tracker N7UV-9 for at least the last 12-15 years using an HT or other 5 W max VHF output radio. Fortunately, for me out west there are a reasonable (but not sufficient) number of high-level digis that provide pretty good service even for my wimpy 5 w radio. I first used a Yaesu Vertex VX-150 but there was something funky about the 4-circuit 3.5 mm plug that would occasionally put the radio in constant TX mode. Yeah, it'd time out, but then it seemed to need to pull and replace the 3.5 mm plug to get it to work again. For the past 10 years I've been using a Friendcom VHF "industrial" radio that I bought from ArgentData way back in the day. It's been bulletproof. The TNC right now is an ArgentData Tracker4, but soon will likely switch to a Microsat TNC.? Never underestimate what 5 W can do! Cheers and 73 - Jon N7UV ? |
|
Re: LoRa APRS & DW
Hi Tom and the others on this thread:
I have several LoRA-enabled 900 MHz USB-connected radios that are flashed to be stand-alone KISS serial TNCs. Two are unsigned.io RNodes and the other two are TTGO LoRA V2.1 radios. They're all flashed with the unsigned.io rnodeconf tool. In linux-land, the RNodes present as /dev/ttyUSB0 and the TTGO units as /dev/ttyACM0. (I don't know why they behave differently, except maybe cause of the USB chips they use.) When connected to a Windows box the RNodes run without any USB serial driver, while the TTGO nodes require a serial port driver available on git-hub?). I have a node set up at my house, on an antenna in the window, and it connects just fine via USB to APRSIS32 running on a Windows 7 box. It presents as a KISS serial modem. I have the LoRA radio set up for approximately 1100 baud to maximize the range. Like you and others have discussed, it'd be great to plug at least one of these into a RPi running direwolf, and get "cross-band" connectivity. Couldn't I set up direwolf to recognize a kiss connection from a serial port within the same RPi, and pass packets between the LoRA radio and the radio natively connected to direwolf? I'm mildly interested in this since my tests at +17 dBm tx out (the max that the Semtech SX1276 does) has done over 10 km in typical suburban terrain. (Note that my house is about 200' higher than my part of town, so maybe that's cheating...) The other end is another of those radios, connected to a Windows PC in my truck via USB, with the win pc running APRSIS32 as well.? Anyway, I would like to be able to use these LoRA radios as an adjunct, or backhaul, or just another band radio that gets packets from 2m and spits them out on 900, and vice-versa. Cheers and 73 - Jon N7UV |
|
Re: Headaches with direwolf + linpac
Neil H. Gray
I've been blown away by the attention everyone on this group has given me.? As a thank-you I will share my modest success after following everyone's advice.
As far as I can tell direwolf + linpac had been working from the very beginning.? I think most of you suspected as much.? But empirically testing my setup is difficult because I am located in an area with few packet stations(none closer than 15 miles). I was able to confirm my working setup with a variety of local hardware and aprs. Variety of working setups where there was decoding: 1. linpac+direwolf+radio over the air to radio+direwolf+linpac 2. linpac+direwolf+radio over the air to radio+aea-pk900+terminal interface a. The transmit level of the pk900 is messed up.? It's too low, and the calibration procedure in the manual doesn't work. b. The pk900 was able to easily decode packets from direwolf even if it couldn't respond. 3. linpac+direwolf+radio over the air to radio+mfj-1274+linpac a. This appeared to work as well as direwolf for my tests. b. Eventually this tnc stopped working like the other 30+ year old tnc that I could find. c. Things broke down before I could estimate a bit error rate. 4. Using a slightly more powerful transmitter(10W) and using Xastir+direwolf to send some position data to aprs via wide-2, one aprs station(k8gps-10) did successfully decode my signal.? That station was the closest to me at 38 miles. And then there is stuff that still doesn't work.? I cannot connect to some of the local digipeaters even though the operators of those stations have assured me that they accept connections. I'm going to have a chance to meet some of them in person soon. I'll get to the bottom of this. Maybe I have badly estimated what 5W can deliver on packet radio. Maybe everyone else's noise floor is way higher than it used to be. Maybe the old tnc hardware needs a very strong signal to decode direwolf. But I can play with packet radio just through my own nearby stations for now.? There are some new features(at least new compared to 1992 when I last used packet radio) that I can test. And I think that I can convince some of my neighboring hams to get on packet radio due to direwolf's lowering the barrier/cost of entry.? A lot of people have raspberry pi's. I appreciate the outpouring of help.? Now I'm going to go bug the guys at the linpac sourceforge site over a few issues.? Regardless of what help they might offer they're not going to be as cool of a bunch as you guys on the direwolf forum(unless of course they also frequent the direwolf forum). Neil H. Gray (n8ssw) |
|
Re: Other Stations don't decode
开云体育Hello Patrick,
Very interesting this device has native 32000 support.? I don't think I've seen that before.
I'm not sure why you're seeing TWO of these though.? That's unusual if not wrong unless you have two of these unit connected
Your previous email said you were using "ADEVICE plughw:CARD=CODEC,DEV=0" aka.. you ARE using the "plughw" aspect of the ALSA sound system.? Anyway.. can provide some sound captures of direwolf running your SCU-17 at say 44100 and 48000 which DON'T decode on your other station?? This shouldn't be happening.? Btw.. what is your other station using for a soundcard, TNC, etc?
I'll have to look to see what might be going on here on v1.7 and v1.6.?? Btw.. for your compiler errors on v1.7, this is an issue with gpsd and it's ever changing libraries.? If you can DISABLE the support for gpsd at compile time just for this test, I think that will get you going.
Ok.. that looks all reasonable.
You're correct.. I forgot about that syntax.
Ugh.. sorry.. I was forgetting that the unit here is 10s of milliseconds.?? What you should shoot for here is say 120 to 200ms.? In Direwolf syntax, that should be a "12" to a "20".?? Start at "20" and see if everything works in communicating to remote packet stations (not just home packet stations).? Then slowly work your way down in say 25ms increments.? Since the FTM300 is a digital radio, I would think it can support faster than average key up times of about 150ms but you'll just have to experiment here.
See the Direwolf User Guide in the "MODEM" section.
I have it all written down:? ?? --David KI6ZHD |
|
Re: Other Stations don't decode
-- |
|
Re: Other Stations don't decode
开云体育Hello Patrick, OK, I think I've got it figured out. This has been my obsession for a bit to long now and I'm glad to have it figured out. Good to hear. The SCU-17 can not and does not handle a 44100 sampling rate nor a 48000 sampling rate.? The sampling rates I have found that works are between 22,000 (might be lower) and 38,000 Hz at most. I tried 40,000, 44,100, 48,000 and they didn't work. That doesn't sound right at all.? Try this command to display what sampling rates this SCU-17 device offers: ?? bash <(wget -q -O - ) -l usb -s You will want to use the NATIVE sampling rate offered by the card because if you don't and you use the "plughw" prefix in your direwolf.conf's "ADEVICE" line, this will make ALSA take the native sampling rate from the hardware and then interpolate it into the rate you specify.? That's MORE work for the computer to do and will yield poorer audio. I have my sample rate set as follows.... What makes you think that 38000 is better than say 48000 or 44100?
I think your observation here needs some more troubleshooting in the Direwolf code.? The way I interpret "-DTR" is that DTR should *never* be asserted on that serial port.? Curious, if you shutdown Direwolf and any other programs that might use the SCU-17.. now UNPLUG it's USB cable, wait 5 seconds, plug it's USB cable back in, and then run the "dmesg" command in a terminal window, what do the last 10 lines or so show about the USB device being detected by the kernel?? Hopefully someone else using a SCU-17 finds this thread useful. --David KI6ZHD |
|
Re: Other Stations don't decode
Nice write-up! I am sure anyone working with the SCU-17 that comes across this will appreciate your sharing. A couple of quick comments on the configuration. 1. Interestingly you specify "PERSIST 63" (at its DEFAULT setting), but comment out "#SLOTTIME 10" (also at its DEFAULT setting). ??? These 2 KISS settings setting work together to determine whether to TX when the channel is deemed open. ??? As a suggestion, since the 2 work together, I recommend either comment both out, or specify both. ??? Since they are at their default, it will make no difference. 2. You chose ARATE 38000.? This is a nonstandard value and may not scale well. ??? Most often users go with multiples (or whole divisions) of the 44,100 and 48,000.? So 22,050 or 24,000. ??? Again, not any sort of fix, just a little more standard. 3. The SCU-17 has 2 "key ports": PTT and FSK (interestingly on the same jack). ??? So it kind of makes sense that it would key both when requesting TX. ??? It also makes sense that you would have to disable the unused pin of the serial port. ??? Thank Goodness Dire Wolf takes multiple parameters so you can specify -DTR RTS ?????? DTR LOW and RTS HIGH on TX ??? Many interface applications like ire Wolf only allow 1 parameter which would probably force user of the ??? SCU-17 (and similar devices) to 'live with' the FSK activating. Robert Giuliano
On Monday, May 2, 2022, 11:48:46 PM EDT, Patrick <kd7wpq@...> wrote:
OK, I think I've got it figured out. This has been my obsession for a bit to long now and I'm glad to have it figured out. I do apologize if I've offended anyone on my other threads. My frustration sometimes gets the best of me. Anyhow, if anyone runs across this thread regarding the SCU-17 here is what I have found. The SCU-17 can not and does not handle a 44100 sampling rate nor a 48000 sampling rate. The sampling rates I have found that works are between 22,000 (might be lower) and 38,000 Hz at most. I tried 40,000, 44,100, 48,000 and they didn't work. I have my sample rate set as follows.... ARATE 38000 The SCU-17 with Direwolf will trigger FSK and PTT at the same time depending on how you have it set. The default setting for the SCU are... DTR - FSK RTS - PTT To get the SCU to trigger PTT without FSK on you have to set PTT to -DTR RTS. This will turn FSK on when receiving but off when transmitting. This appears to not affect receiving in any way that I've noticed. Example:..... PTT /dev/ttyUSB1 -DTR RTS FSK and PTT on during transmit.... PTT /dev/ttyUSB1 DTR RTS Setting to RTS only will also work but will leave FSK stuck on. This does not seem to affect the transmitted signal and DTR RTS doesn't seem to affect receive either as far as I can see. Unfortunately when I was observing my radio's behavior I was only watching the lights. Just because FSK comes on does NOT mean the radio is keyed. To my detriment and many, MANY hours later I have figured this out so hopefully if someone else runs across these problems they can avoid wasting as much time as I have and can hopefully get on the air and enjoy what they have quickly! I do also want to thank the makers of Direwolf. They have put a LOT of time and effort into making it work. Though the serial signaling does need to be tuned to not grab a signal that has not been specified it does work and it works quite well. Direwolf has a lot of features that are easily configured via the config file and it works quit well with very little overhead. A very impressive application indeed! Hopefully someone else using a SCU-17 finds this thread useful. Here is my config file for reference and for software TNC use only ACHANNELS 1 ARATE 38000 #ARATE 44100 #ADEVICE plughw:CARD=CODEC,DEV=0 hw:CARD=CODEC,DEV=0 ADEVICE plughw:CARD=CODEC,DEV=0 DWAIT 0 #SLOTTIME 10 PERSIST 63 TXDELAY 50 #TXTAIL 10 FULLDUP OFF CHANNEL 0 MYCALL replace-me-with-your-call MODEM 1200 #MODEM 2400 #MODEM 4800 #MODEM 9600 # PTT Notes for the SCU-17 # DTR Triggers FSK, RTS Triggers PTT, -DTR will leave FSK on until TX is triggered #PTT COM1 RTS #PTT COM1 RTS -DTR #PTT /dev/ttyUSB1 RTS PTT /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00F8CEC3-if01-port0 DTR RTS AGWPORT 8000 KISSPORT 8001 FIX_BITS 1 |
|
Re: Direwolf as a TNC Help
Got it all working. I updated this thread on this group... /g/direwolf/topic/other_stations_don_t_decode/90829585?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,90829585,previd%3D1651549724754083416,nextid%3D1649302366690394507&previd=1651549724754083416&nextid=1649302366690394507 I do apologize of I have offended anyone, my frustration has a tenancy to get the best of me at times. |
|
Re: Other Stations don't decode
OK, I think I've got it figured out. This has been my obsession for a bit to long now and I'm glad to have it figured out.
I do apologize if I've offended anyone on my other threads. My frustration sometimes gets the best of me. Anyhow, if anyone runs across this thread regarding the SCU-17 here is what I have found. The SCU-17 can not and does not handle a 44100 sampling rate nor a 48000 sampling rate. The sampling rates I have found that works are between 22,000 (might be lower) and 38,000 Hz at most. I tried 40,000, 44,100, 48,000 and they didn't work. I have my sample rate set as follows.... ARATE 38000 The SCU-17 with Direwolf will trigger FSK and PTT at the same time depending on how you have it set. The default setting for the SCU are... DTR - FSK RTS - PTT To get the SCU to trigger PTT without FSK on you have to set PTT to -DTR RTS. This will turn FSK on when receiving but off when transmitting. This appears to not affect receiving in any way that I've noticed. Example:..... PTT /dev/ttyUSB1 -DTR RTS FSK and PTT on during transmit.... PTT /dev/ttyUSB1 DTR RTS Setting to RTS only will also work but will leave FSK stuck on. This does not seem to affect the transmitted signal and DTR RTS doesn't seem to affect receive either as far as I can see. Unfortunately when I was observing my radio's behavior I was only watching the lights. Just because FSK comes on does NOT mean the radio is keyed. To my detriment and many, MANY hours later I have figured this out so hopefully if someone else runs across these problems they can avoid wasting as much time as I have and can hopefully get on the air and enjoy what they have quickly! I do also want to thank the makers of Direwolf. They have put a LOT of time and effort into making it work. Though the serial signaling does need to be tuned to not grab a signal that has not been specified it does work and it works quite well. Direwolf has a lot of features that are easily configured via the config file and it works quit well with very little overhead. A very impressive application indeed! Hopefully someone else using a SCU-17 finds this thread useful. Here is my config file for reference and for software TNC use only ACHANNELS 1 ARATE 38000 #ARATE 44100 #ADEVICE plughw:CARD=CODEC,DEV=0 hw:CARD=CODEC,DEV=0 ADEVICE plughw:CARD=CODEC,DEV=0 DWAIT 0 #SLOTTIME 10 PERSIST 63 TXDELAY 50 #TXTAIL 10 FULLDUP OFF CHANNEL 0 MYCALL replace-me-with-your-call MODEM 1200 #MODEM 2400 #MODEM 4800 #MODEM 9600 # PTT Notes for the SCU-17 # DTR Triggers FSK, RTS Triggers PTT, -DTR will leave FSK on until TX is triggered #PTT COM1 RTS #PTT COM1 RTS -DTR #PTT /dev/ttyUSB1 RTS PTT /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00F8CEC3-if01-port0 DTR RTS AGWPORT 8000 KISSPORT 8001 FIX_BITS 1 |
|
Re: Add Bluetooth…
开云体育Hello Armando, Please don't hijack a thread about Bluetooth for your SDR question.? Please create a new thread.? In that new thread. you can mention any questions you might have after reading: ?? --David On 05/01/2022 03:23 PM, Armando
Rodriguez wrote:
Good afternoon. I am currently running a Digipeater using a uv5r, raspberry pi 4 B, an audio card and the corresponding connections. Now i would like to use a SDR to feed the digipeater. I am a new ham and would like to get some help in this matter. I forgot, the pi is running build a pi. Any ideas. Best Regards. Armando Rodriguez On May 1, 2022, at 5:19 PM, Patrick <kd7wpq@...> wrote: ?Think this will help....? |
|
Re: Add Bluetooth…
Good afternoon. I am currently running a Digipeater using a uv5r, raspberry pi 4 B, an audio card and the corresponding connections.
toggle quoted message
Show quoted text
Now i would like to use a SDR to feed the digipeater. I am a new ham and would like to get some help in this matter. I forgot, the pi is running build a pi. Any ideas. Best Regards. Armando Rodriguez On May 1, 2022, at 5:19 PM, Patrick <kd7wpq@...> wrote:
?Think this will help....? |
|
Re: Direwolf as a TNC Help
开云体育-- Yes... I think, if I understand the question correctly. Let me elaborate... The SCU hase 3 LED indicator lights, FSK, PTT and Power... Direwolf not running, FSK off, PTT off, Power on Direwolf running, FSK on, PTT off, Power on YAAC sends message, Direwolf triggers PTT then, FSK off, PTT on, Power on Direwolf drops PTT, FSK on, PTT off, Power on Exit Direwolf application, FSK off, PTT off, Power on -- The only documentation I know of for the SCU-17 is this... But yea, they don't break things down all the way. -- Oh, I agree for sure! The CPU in the machine is by far more
powerful than any TNC and would for sure have better error
correcting! -- You're
right, I very likely missed that with the FSK light on it wasn't
keying. I am by no means perfect or infallible so therefor I do
make mistake and I'll own. As for rolling back to 1.6 it seems I've run into a issue compiling it. I get the following..... dwgpsd.c:64:2:
error: #error libgps API version might be incompatible.
If I git checkout dev then it compiles just fine and starts out with... -- Dire
Wolf Version: 1.7.0-c9ffbd7 I know
this message was very long, sorry about that, just trying to be
thorough.
|
|
Other Stations don't decode
One problem after another here. |
|
Re: Direwolf as a TNC Help
开云体育Hello Patrick,
I also see on the LInuxHams list, you mentioned: -- PTT /dev/ttyUSB1 -DTR RTS then the FSK light comes on and when it transmits it flips from FSK to PTT without a dead key. -- Are you saying that Direwolf keys up SCU-17 and it's "FSK" indicator lights up but Direwolf stays playing audio (AFSK modem tones), the SCU-17's turns off the FSK light and then turns on the PTT light?? If so, that does NOT sound right at all.? If you would, please try Direwolf v1.6.?? I would expect Direwolf v1.7* as very stable now but it's NOT released code and it's still undergoing change.
The vew fellow HAMs who have had issue have been either using unusual sound devices, using unusual isolation devices, etc.? Direwolf can be made to work with any of them but you have to determine what the right signal is for each of them.? In your circumstance, the SCU-17 documentation is non-existent which makes it extra hard.?
Of course the choice is yours but I can nearly guarantee you that Direwolf will out perform *any* hardware TNC you buy.? TNCs like a KPC3+ or PK96 can come close but most of the PIC/Arduino based units will have significantly poor decode rates.
Well.. I hear the frustration here but Direwolf has recommend hardware mentioned in the User Guide but you're not using that.? You also were doing a lot of testing and you might have actually missed the test that either "-DTR RTS" or "-DTR RTS" was actually working for you (ignore whatever the LED lights are as there is no FSK signal here in AFSK1200 packet).? FSK from an SCU-17 perspective is used for things like "real" RTTY or CW on HF radios. --David KI6ZHD |
|
Re: Add Bluetooth…
开云体育Completely agreed, direwolf+bluetooth is a great combo, extend it to the ax.25 network stack on the pi as well,?? cool, -craig KM6LYW On 5/1/22 2:52 PM, J K via groups.io
wrote:
|
|
Re: Direwolf as a TNC Help
So I have found if I set direwolf to
PTT /dev/ttyUSB1 -DTR RTS That I find functional. Now to figure out why nothing else understands it when it transmits. |
|
Re: Add Bluetooth…
Lynn Deffenbaugh
开云体育I'm running Bluetooth to a Pi 2 Zero W
with Direwolf as KJ4OVQ-9.? I connect to it from my
APRSISMO/TestHost Android application when I'm in the vehicle to
become a mobile IGate.? It only does SPP and not BLE, so iPhones
don't even try it.
Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 5/1/2022 5:52 PM, J K via groups.io
wrote:
|
|
Re: Direwolf as a TNC Help
It's definitely got to be a application issue. I've found threads where others have had the issue and worked around the problem but quite frankly I shouldn't have to work around the problem, that's why I bought a sound serial interface device, to minimize the clutter and optimize space and power consumption. |