开云体育

Good to hear you got it working. Just to clarify, what ADEVICE are you using in your direwolf.conf? Also, any specific reason why you used qasmixer? I had never heard of it before and had to look

Hi Marc, obviously I know the 6-pin DIN PKT connector is used for FM data but the DATA IN/OUT connected jack doesn't disturb although it isn't used in this case. I only quoted for additional

David, I've got it working this morning with some fine tuning the input level with the help of Qasmixer under my Gnome GUI. It was far too loud and had to be drastically reduced to get a response,

David, here are some short answers to your requests. a) Squelch: is wide open, the audio signal can be traced directly at pin #27 of CM108 with more than 100mVpp b) Output from 'uname -a' Linux

I set up a raspberry pi 3 with Direwolf. It's uses a Baofeng Uv-R5 and aprs cable and usb sound card. They all work and settings are correct for everything. Everything seems to be working. I can see

Though somewhat off-topic, I wouldn't recommend to troubleshoot Direwolf input audio level issues with the very old Thomas Sailer soundmodem soft-TNC (not to be confused with the UZ7HO soundmodem for

Ok, with seeing the trailing zero in "receive audio level CH0 0" means no audio is being routed to Direwolf. In the beginning of this thread, you mentioned you're running Linux. - Make sure that

That is a great explanation Chris. Yes WA8DED and the better TF2.7b still handles the AX.25 stack, but allows the application to select multiple connections at once via streams. You can still

This thread was started a long time ago? but has some recent activity. The original TAPR TNC was designed for a human operator sitting at a? dumb terminal.??Text going to the TNC could be either

John, thank you for this (-a 10) trick. The output is always: ADEVICE0: Sample rate approx. 44.1 k, 0 errors, receive audio level CH0 0 Best regards. Karl, DK7AL

Try adding "-a 10" to the direwolf command line. This will print the audio input level periodically. 73, John WB2OSZ

It sounds like both the softmodem (direwolf) configuration and audio path are suspect at this point. Maybe try the kernal soundmodem module instead of direwolf and see if it decodes packets?? ?If

I believe this is your problem. I? also use an FT-847 for packet....with audio to/from the 6-pin DIN PKT connector.....not the Data IN/OUT phono. The DIN jack must be used for FM data.? ?The Data

I'm probably missing something here, but are you looking for 'kissattach' here ..... which reads from the the direwolf pty (if launched with -p) and creates the network interface you specified in

Almost sounds like you're configured for 9600baud or over rather than the 1200 baud usually used for APRS? Maybe try these settings: direwolf.conf (copy in your home directory or root home

I run it in KISS mode, use a bash script to grab the pty names (the BASH_REMATCH variable), and feed those to kissattach: regex = " Virtual KISS TNC is available

Because your oscilloscope is not looking at the point inside the integrated circuit after the analog mike preamp stage, nor is it looking at the output of the A/D converter. The clipping would be

Andrew, thank you for your suggestion. I have my scope directly soldered at pin #27 of CM108 and can directly monitor the incoming signal. There is no clipping or distortion to be seen from the

Note that turning down the digital gain of the mike input won't help if the signal was already distorted from overloading the analog mike preamp and A/D converter on the CM108. I recommend installing

There is no difference in case I use DW1.7S