开云体育

Doh! Missed that message, ya beat me to it.

Think this will help....? https://github.com/wb2osz/direwolf/blob/master/doc/Bluetooth-KISS-TNC.pdf

Well dad gum, I could have SWORE for the life of me I tried that I swapped RTS and DTR back and fourth and they both worked though it is triggering FKS and PTT at the same time it is working and I've

Looks straightforward. https://github.com/wb2osz/direwolf/blob/master/doc/Bluetooth-KISS-TNC.pdf Sent from my iPhone 13 Pro Max

Anyone add Bluetooth support? I have a RPi02W with Fe-Pi audio board and even though have a Moblink TNC3 was thinking about getting a second TNC3, but then thought why not just add

I had a similar problem when using a USB to serial adapter and an EasyDigi board. Both the RTS and DTR pins are wired to the EasyDigi - presumably so that either one can be selected for PTT by the

Understood, but toggling the switch should only switch the PTT method whether that by PTT or FSK in accordance to the signal it receives, be that RTS or DTR, but I digress, if my buddy and I have no

Hello Patrick, It's a pretty remote possibility that this is a code bug since 1000s of people are successfully using Direwolf. The unique thing here is that you're using the Yaesu SCU-17 device

Hopefully I haven't baffled or stumped everyone. Granted I'm a bit stumped as to why it's not working. Is it possible it's a application bug and if so what do I need to do to request it be fixed?

Nope, I have FLRig and FLDigi configured to use my 857 by default. FLRig is pointed to /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00AC0110-if00-port0 Firewolf

What about Flrig? Are you using that with Fldigi? If so, Flrig is the program that is owning the serial port, not Fldigi, so it is what has to be shut down before starting DireWolf. Andrew,

Great question to be sure I'm not pointing two applications to the same device :) A easy mistake to make for sure, but no. I opened FLDigi and ran it without direwolf running to see if it would key

I'll ask the obvious question:?? You aren't trying to use /dev/ttyUSB1 when both FLDigi and Direwolf are running??? Being more specific, you are sure FLDigi is 'dropping' its connection to

OK, I've done a bit more testing and have verified that FLDigi has no problem keying the SCU-17 but direwolf is having problems. If I set FLDigi's Hardware PTT to /dev/ttyUSB1 RTS then I can trigger

Danny, thank you for the reply. There is a way to find the device, yes Basically instead of using /dev/ttyUSB0 or 1 I'm targeting it by ID by using /dev/serial/by-id/............ I had not however

Patrick, The following is the entire contents of my direwolf.conf running on a Raspberry pi. ADEVICE plughw:1,0 plughw:1,0 ACHANNELS 1 CHANNEL 0 MYCALL K5CG MODEM 1200 PTT /dev/ttyUSB0 RTS

Anyone have an insite on how to get PTT working or some things I can test to get it working? I've tried ending the first un-commented PTT line with RTS, RTS DTR, RTS -DTR, -DTR and DTR and it will

I'll jump over there and see what I can get figured out. I have the radio connected via USB to a SCU-17 ( http://yaesu.com/jp/manuals/yaesu_m/SCU-17_OM_ENG_JPN.pdf ) via a CT-163 (

Rob is right here (sorry for the confusion). I did have them reversed BUT it's the "DATA IN" signal that also needs the ability to enable or disable the application of pre-emphasis if your radio

The Data Jack (6-pin mini-DIN) on radios does NOT have a 9600 baud TX pin.There are 6 pins in the jack:1??? PKD (Data In) 2??? GND3??? PTT4??? RX96005??? RX12006??? SQL The TC path