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
|
Re: Packet (TNC) or PC Serial I/O (for Dummies)
Thanks, Rob. I'll check it out. I didn't realize pins 1 & 5 (or 4) were audio.
Also, according to the manual, pin 3 (PKS) says '"L" is transmitted and microphone is muted' What the heck do they mean by "L" is transmitted? ?
? ? ?…doug
?
Doug Kaye, K6DRK
DMR ID: 3196950
doug@...
?
? |
|
Re: Packet (TNC) or PC Serial I/O (for Dummies)
At a glance, it looks like the serial interface is for programming - not "packet". Therefore, I'd suggest a sound card interface using the 8-pin data jack information on page 23 of the manual. Pin 1 - TX audio from sound card headphones/line out Pin 2 Gnd Pin 3 PTT Pin 5 RX audio to sound card Mic/line in ???????? Could use Pin 4 for high baud rates. Personally, I never use the SQL line (pin 6) - use open squelch and let Direwolf handle that part. Don't know anything more about the radio, like TX/RX turnaround, etc. Robert Giuliano
On Thursday, October 5, 2023 at 08:18:22 PM EDT, Doug Kaye (K6DRK) <doug@...> wrote:
I've built a few iGates and digipeaters using Direwolf on Linux with USB sound cards. No problem. Now I want to make a digipeater for a Btech UV-50X3 xcvr. It offers two interfaces via a DIN-8 connector. Which do I want to use:
And then, how do I configure direwolf for the selected interface? It's probably obvious, but I haven't found this easily. |
|
Packet (TNC) or PC Serial I/O (for Dummies)
I've built a few iGates and digipeaters using Direwolf on Linux with USB sound cards. No problem.
Now I want to make a digipeater for a Btech UV-50X3 xcvr. It offers two interfaces via a DIN-8 connector. Which do I want to use:
And then, how do I configure direwolf for the selected interface? It's probably obvious, but I haven't found this easily. |
|
Re: Raspberry pi Build (cmake ...) error after upgrading from Buster to Bullseye
Thanks for sharing - makes sense! Robert Giuliano
On Thursday, October 5, 2023 at 09:50:30 AM EDT, f1mhv <f1mhv@...> wrote:
Hi Robert, I did previously sudo apt install cmake libasound2-dev libudev-dev but no success. Fix was provided by Geoffrey F4FXL: deleting build directory and starting agin from mkdir build && cd build and so on… build was error-less. 73 de Cyril - DF1CHB - F1MHV > Le 5 oct. 2023 à 15:04, Rob Giuliano via groups.io <kb8rco@...> a écrit : > > I have built Direwolf on Bullseye many time, so you must be missing something fairly simple. > > Did you update the dependencies after updating the OS? > You may want to run >? sudo apt install cmake libasound2-dev libudev-dev > As these may need to be restore / readdressed after the OS update. >? ? I see libudev listed, so it is a good bet. > > > > Robert Giuliano > KB8RCO > > > On Thursday, October 5, 2023 at 03:32:19 AM EDT, f1mhv <f1mhv@...> wrote: > > > Gi Group, > > I decided to upgrade my RPi running Direwolf from Buster to Bullseye by changing /etc/apt/sources.list (yes i know it’s the dirty way but i didn’t want to re-install EVERYTHING). Luckily it worked with minimum damages (old G4KLX GMSK Dstar modem & F4FXL’s Dsatrgateway ok) but Direwolf was hit. > > - make clean done > > - cmake -DUNITTEST=1 .. > -- Dire Wolf Version: 1.7.0-ab834f3 > -- Build type set to: Release > CMake system: Linux > -- Target architecture: ARM > -- Use NEON SIMD instructions > -- Checking for module 'hamlib' > --? No package 'hamlib' found > -- Could NOT find hamlib (missing: HAMLIB_LIBRARY HAMLIB_INCLUDE_DIR) > -- Build unit test binaries > -- Configuring done > -- Generating done > -- Build files have been written to: /home/pi/direwolf/build > > then make -j4 with following errors: > > -? 26%] Building C object src/CMakeFiles/gen_packets.dir/fcs_calc.c.o > make[2]: *** No rule to make target '/lib/arm-linux-gnueabihf/libudev.so', needed by 'src/cm108'.? Stop. > make[2]: *** Waiting for unfinished jobs…. > > [ 28%] Building C object src/CMakeFiles/cm108.dir/textcolor.c.o > make[1]: *** [CMakeFiles/Makefile2:1555: src/CMakeFiles/cm108.dir/all] Error 2 > make[1]: *** Waiting for unfinished jobs…. > > - [ 62%] Building C object src/CMakeFiles/direwolf.dir/dns_sd_common.c.o > make[2]: *** No rule to make target '/lib/arm-linux-gnueabihf/libudev.so', needed by 'src/direwolf'.? Stop. > make[2]: *** Waiting for unfinished jobs.... > [ 63%] Building C object src/CMakeFiles/direwolf.dir/dns_sd_avahi.c.o > make[1]: *** [CMakeFiles/Makefile2:1310: src/CMakeFiles/direwolf.dir/all] Error 2 > make: *** [Makefile:182: all] Error 2 > > about libudev-dev: > > dpkg -l | grep libudev > ii? libgudev-1.0-0:armhf? ? ? ? ? ? ? ? 234-1? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? armhf? ? ? ? GObject-based wrapper library for libudev > ii? libudev-dev:armhf? ? ? ? ? ? ? ? ? ? 247.3-7+rpi1+deb11u2? ? ? ? ? ? ? ? ? ? armhf? ? ? ? libudev development files > ii? libudev0:armhf? ? ? ? ? ? ? ? ? ? ? 200-1? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? armhf? ? ? ? compatibility wrapper for libudev version 0 > ii? libudev1:armhf? ? ? ? ? ? ? ? ? ? ? 247.3-7+rpi1+deb11u2? ? ? ? ? ? ? ? ? ? armhf? ? ? ? libudev shared library > > pkg-config is installed as well. > > Of course prior dropping this email i went thru groups.io messages search but i couldn’t figured-out a fix. > > 73 de Cyril - DF1CHB - F1MHV > > > > > > > > > > |
|
Re: Raspberry pi Build (cmake ...) error after upgrading from Buster to Bullseye
Hi Robert,
toggle quoted message
Show quoted text
I did previously sudo apt install cmake libasound2-dev libudev-dev but no success. Fix was provided by Geoffrey F4FXL: deleting build directory and starting agin from mkdir build && cd build and so on… build was error-less. 73 de Cyril - DF1CHB - F1MHV Le 5 oct. 2023 à 15:04, Rob Giuliano via groups.io <kb8rco@...> a écrit : |
|
Re: Raspberry pi Build (cmake ...) error after upgrading from Buster to Bullseye
I have built Direwolf on Bullseye many time, so you must be missing something fairly simple. Did you update the dependencies after updating the OS? You may want to run ? sudo apt install cmake libas ound2-dev libudev-devAs these may need to be restore / readdressed after the OS update. ?? I see libudev listed, so it is a good bet. Robert Giuliano KB8RCO
On Thursday, October 5, 2023 at 03:32:19 AM EDT, f1mhv <f1mhv@...> wrote:
Gi Group, I decided to upgrade my RPi running Direwolf from Buster to Bullseye by changing /etc/apt/sources.list (yes i know it’s the dirty way but i didn’t want to re-install EVERYTHING). Luckily it worked with minimum damages (old G4KLX GMSK Dstar modem & F4FXL’s Dsatrgateway ok) but Direwolf was hit. - make clean done - cmake -DUNITTEST=1 .. -- Dire Wolf Version: 1.7.0-ab834f3 -- Build type set to: Release CMake system: Linux -- Target architecture: ARM -- Use NEON SIMD instructions -- Checking for module 'hamlib' --? No package 'hamlib' found -- Could NOT find hamlib (missing: HAMLIB_LIBRARY HAMLIB_INCLUDE_DIR) -- Build unit test binaries -- Configuring done -- Generating done -- Build files have been written to: /home/pi/direwolf/build then make -j4 with following errors: -? 26%] Building C object src/CMakeFiles/gen_packets.dir/fcs_calc.c.o make[2]: *** No rule to make target '/lib/arm-linux-gnueabihf/libudev.so', needed by 'src/cm108'.? Stop. make[2]: *** Waiting for unfinished jobs…. [ 28%] Building C object src/CMakeFiles/cm108.dir/textcolor.c.o make[1]: *** [CMakeFiles/Makefile2:1555: src/CMakeFiles/cm108.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs…. - [ 62%] Building C object src/CMakeFiles/direwolf.dir/dns_sd_common.c.o make[2]: *** No rule to make target '/lib/arm-linux-gnueabihf/libudev.so', needed by 'src/direwolf'.? Stop. make[2]: *** Waiting for unfinished jobs.... [ 63%] Building C object src/CMakeFiles/direwolf.dir/dns_sd_avahi.c.o make[1]: *** [CMakeFiles/Makefile2:1310: src/CMakeFiles/direwolf.dir/all] Error 2 make: *** [Makefile:182: all] Error 2 about libudev-dev: dpkg -l | grep libudev ii? libgudev-1.0-0:armhf? ? ? ? ? ? ? ? 234-1? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? armhf? ? ? ? GObject-based wrapper library for libudev ii? libudev-dev:armhf? ? ? ? ? ? ? ? ? ? 247.3-7+rpi1+deb11u2? ? ? ? ? ? ? ? ? ? armhf? ? ? ? libudev development files ii? libudev0:armhf? ? ? ? ? ? ? ? ? ? ? 200-1? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? armhf? ? ? ? compatibility wrapper for libudev version 0 ii? libudev1:armhf? ? ? ? ? ? ? ? ? ? ? 247.3-7+rpi1+deb11u2? ? ? ? ? ? ? ? ? ? armhf? ? ? ? libudev shared library pkg-config is installed as well. Of course prior dropping this email i went thru groups.io messages search but i couldn’t figured-out a fix. 73 de Cyril - DF1CHB - F1MHV |
|
Raspberry pi Build (cmake ...) error after upgrading from Buster to Bullseye
Gi Group,
I decided to upgrade my RPi running Direwolf from Buster to Bullseye by changing /etc/apt/sources.list (yes i know it’s the dirty way but i didn’t want to re-install EVERYTHING). Luckily it worked with minimum damages (old G4KLX GMSK Dstar modem & F4FXL’s Dsatrgateway ok) but Direwolf was hit. - make clean done - cmake -DUNITTEST=1 .. -- Dire Wolf Version: 1.7.0-ab834f3 -- Build type set to: Release CMake system: Linux -- Target architecture: ARM -- Use NEON SIMD instructions -- Checking for module 'hamlib' -- No package 'hamlib' found -- Could NOT find hamlib (missing: HAMLIB_LIBRARY HAMLIB_INCLUDE_DIR) -- Build unit test binaries -- Configuring done -- Generating done -- Build files have been written to: /home/pi/direwolf/build then make -j4 with following errors: - 26%] Building C object src/CMakeFiles/gen_packets.dir/fcs_calc.c.o make[2]: *** No rule to make target '/lib/arm-linux-gnueabihf/libudev.so', needed by 'src/cm108'. Stop. make[2]: *** Waiting for unfinished jobs…. [ 28%] Building C object src/CMakeFiles/cm108.dir/textcolor.c.o make[1]: *** [CMakeFiles/Makefile2:1555: src/CMakeFiles/cm108.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs…. - [ 62%] Building C object src/CMakeFiles/direwolf.dir/dns_sd_common.c.o make[2]: *** No rule to make target '/lib/arm-linux-gnueabihf/libudev.so', needed by 'src/direwolf'. Stop. make[2]: *** Waiting for unfinished jobs.... [ 63%] Building C object src/CMakeFiles/direwolf.dir/dns_sd_avahi.c.o make[1]: *** [CMakeFiles/Makefile2:1310: src/CMakeFiles/direwolf.dir/all] Error 2 make: *** [Makefile:182: all] Error 2 about libudev-dev: dpkg -l | grep libudev ii libgudev-1.0-0:armhf 234-1 armhf GObject-based wrapper library for libudev ii libudev-dev:armhf 247.3-7+rpi1+deb11u2 armhf libudev development files ii libudev0:armhf 200-1 armhf compatibility wrapper for libudev version 0 ii libudev1:armhf 247.3-7+rpi1+deb11u2 armhf libudev shared library pkg-config is installed as well. Of course prior dropping this email i went thru groups.io messages search but i couldn’t figured-out a fix. 73 de Cyril - DF1CHB - F1MHV |
|
Re: RPi Direwolf packet station.
Mike Berg
For a simple packet station using a Raspberry Pi with a sound card interface like Signalink USB, I found Direwolf and QtTermTCP got the job done.
|
|
Re: "Timeout waiting for input from audio device 0" on Windows
On Mon, Oct 2, 2023 at 06:52 AM, Peter G. Viscarola wrote:
Can anyone suggest a "known to work without problems on Windows" USB sound device? Masters Communications ?but old models had limited bandwidth |
|
Re: "Timeout waiting for input from audio device 0" on Windows
toggle quoted message
Show quoted text
On Tue, Oct 3, 2023 at 1:09?PM Rob Giuliano via <kb8rco=[email protected]> wrote:
|
|
Re: "Timeout waiting for input from audio device 0" on Windows
Not in the config file.? The command line is the Windows command prompt or a Linux terminal. In Windows search on "cmd", or modify the "Target:" information in a Windows shortcut. ?? <Right-click>on the shortcut and look at "Properties" for "Target:" In Linux, the terminal is typically an icon "of >_ " or under the Accessories menu >Terminal (on a Raspberry Pi).? Other Linux distros may have it under different menu items. Robert Giuliano KB8RCO
|
|
Re: "Timeout waiting for input from audio device 0" on Windows
hi guys. I have been reading the post re this matter, Great stuff. This is outside of this, BUT how and where do you put the Command Line in the config file to bring up? the timestamps. I have tried?this so many times and i can't?get it the read it. >Put "-T %H:%M:%S" on the command line to get timestamps. any help here.. Thanks? ? ? ? ? ? ? ? ?Pete VK2BLO On Tue, Oct 3, 2023 at 4:51?AM Peter G. Viscarola <PeterVisc@...> wrote:
|
|
Re: "Timeout waiting for input from audio device 0" on Windows
开云体育
>Put "-T
%H:%M:%S" on the command line to get timestamps.
Oh, that's terrific.? Thanks for that!? That works great!
>Are you
using a USB hub?
No, I'm not.? I
am? using an extender cable, though ("a" type female to "a" type male).? I guess that could be causing some problems.? Hmmm...
Thanks again, and very much, to everyone for the suggestions so far.
(Interesting note: Since changing the sampling rate to 48000, I haven't seen the timeout problem. I don't really understand why this would fix the problem, but....)
VY 73 de Peter K1PGV
|
|
Re: "Timeout waiting for input from audio device 0" on Windows
On Mon, Oct 2, 2023 at 11:01 AM, Peter G. Viscarola wrote:
I was just bemoaning the fact that direwolf didn't timestamp any output Put "-T %H:%M:%S" on the command line to get timestamps. Are you using a USB hub?? There have been cases where plugging the USB Audio adapter into a USB hub was less reliable. How about trying a different USB port on the computer? 73, John WB2OSZ |
|
Re: "Timeout waiting for input from audio device 0" on Windows
开云体育
David KI6ZHD wrote:
>?Consider
running direwolf from a batch file that after the direwolf line is run, then run a "date /t" and a "time /t" command.? Now, when you run Direwolf and it then exits, it will print out WHEN exactly it crashed out.? At that point, go look a the the Windows Event
Viewer aka the system logs and look around those timestamps to see what the OS says.
Thank
you, David.? That's another very excellent suggestion... and one I had not thought of at all (I was just bemoaning the fact that direwolf didn't timestamp any output; I didn't even THINK of using a batch file to log the time/date).
SO,
thanks for that... I'll create that simple batch file and try that again right now.
Many
thanks to all so far...
vy 73 de Peter K1PGV
|
|
Re: "Timeout waiting for input from audio device 0" on Windows
开云体育Hello Peter, Consider running direwolf from a batch file that after the direwolf line is run, then run a "date /t" and a "time /t" command.? Now, when you run Direwolf and it then exits, it will print out WHEN exactly it crashed out.? At that point, go look a the the Windows Event Viewer aka the system logs and look around those timestamps to see what the OS says.? At that point, report back to the email list with what you've found and maybe someone can give you some more ideas what to do next. --David KI6ZHD On 10/02/2023 07:13 AM, Peter G.
Viscarola wrote:
|
|
Re: "Timeout waiting for input from audio device 0" on Windows
开云体育
Jeff KP3FT suggested:
>?Try changing
the default sampling rate of 44100? to 48000 by using the -r switch
Thanks!? I'm trying that right now.? I'll report back.
In the meantime, I'd love to hear other thoughts/suggestions/ideas/recommendations.
vy 73 de Peter K1PGV
|
Jerry Rogich AA2T
John Kristian
N9PNO
to navigate to use esc to dismiss