USB connection to radio does not function in Fldigi, QSSTV or WSJT-X in V22b. It works perfectly in V17 with same cable on same computer. I get the message: "HamLib: IO error in opening connection to radio. Check read/write permissions.", when starting WSJT-X and serial PTT connection does not work. I have checked permissions where I could find them with no success. I have run dmesg and lsusb and find cable is there and activated to "ttyUSB0", but still no function. Any Help ?............................Carl, WA0RLY
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Andy,
Mon.Jan.13,2020
I found your post on the "dialout group" and that worked ! WSJT-X and QSSTV function now. It
also worked in Puppy Linux for getting the T/R button to work in Fldigi in the Windows
Emulator(WINE). Excellent compilation of Ubuntu, Andy ! I use it for Fldigi emergency comms
practice nets and find it to be better than Windows because it is stable. Settings stay the same, so my
machine works when others are suffering from Windows Updates. The shutdown Logout is good so
that the computer would stay running in an EOC if unauthorized persons tried to stop Fldigi message
traffic. Thank You for a fine dependable OS with apps.......73s and Best
DX !........................................................Carl, WA0RLY
On 01/12/2020 12:56 PM, Andy Stewart wrote:
Carl: Are you a member of the dialout group? Does it work when you are root? Are you sure that the device is actually at /dev/ttyUSB0 and not USB1?
Hello Andy, Mon.Jan.13,2020
I found your post on the "dialout group" and that worked ! WSJT-X and QSSTV function now. It also worked in Puppy Linux for getting the T/R button to work in Fldigi in the Windows Emulator(WINE). Excellent compilation of Ubuntu, Andy ! I use it for Fldigi emergency comms practice nets and find it to be better than Windows because it is stable. Settings stay the same, so my machine works when others are suffering from Windows Updates. The shutdown Logout is good so that the computer would stay running in an EOC if unauthorized persons tried to stop Fldigi message traffic. Thank You for a fine dependable OS with apps.......73s and Best DX !........................................................Carl, WA0RLY
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To say "not working" is not helpful. WHAT isn't working?
Did you try what I suggested?
Which step in that process failed?
Did you verify that the driver is loaded?
Did you verify that your device is seen by the kernel after you plug it in?
Were there any error messages?
Did you do a Google search for more information?
73,
Andy
KB1OIQ
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
USB connection to radio does not function in Fldigi, QSSTV or WSJT-X in V22b. It works perfectly in V17 with same cable on same computer. I get the message: "HamLib: IO error in opening connection to radio. Check read/write permissions.", when starting WSJT-X and serial PTT connection does not work. I have checked permissions where I could find them with no success. I have run dmesg and lsusb and find cable is there and activated to "ttyUSB0", but still no function. Any Help ?............................Carl, WA0RLY
Carl: Are you a member of the dialout group? Does it work when you are root? Are you sure that the device is actually at /dev/ttyUSB0 and not USB1?
73,
Andy
KB1OIQ
Hello Andy,
Mon.Jan.13,2020
I found your post on the "dialout group" and that worked ! WSJT-X and QSSTV function now. It
also worked in Puppy Linux for getting the T/R button to work in Fldigi in the Windows
Emulator(WINE). Excellent compilation of Ubuntu, Andy ! I use it for Fldigi emergency comms
practice nets and find it to be better than Windows because it is stable. Settings stay the same, so my
machine works when others are suffering from Windows Updates. The shutdown Logout is good so
that the computer would stay running in an EOC if unauthorized persons tried to stop Fldigi message
traffic. Thank You for a fine dependable OS with apps.......73s and Best
DX !........................................................Carl, WA0RLY
On 01/12/2020 12:56 PM, Andy Stewart wrote:
Carl: Are you a member of the dialout group? Does it work when you are root? Are you sure that the device is actually at /dev/ttyUSB0 and not USB1?
73,
Andy
KB1OIQ
USB to Serial Adapter Not Workinghttps://sourceforge.net/p/kb1oiq-andysham/discussion/1789006/thread/f6d5f73cbf/?limit=25#0a9d
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/kb1oiq-andysham/discussion/1789006/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Hello Andy, Mon.Jan.13,2020
I found your post on the "dialout group" and that worked ! WSJT-X and QSSTV function now. It also worked in Puppy Linux for getting the T/R button to work in Fldigi in the Windows Emulator(WINE). Excellent compilation of Ubuntu, Andy ! I use it for Fldigi emergency comms practice nets and find it to be better than Windows because it is stable. Settings stay the same, so my machine works when others are suffering from Windows Updates. The shutdown Logout is good so that the computer would stay running in an EOC if unauthorized persons tried to stop Fldigi message traffic. Thank You for a fine dependable OS with apps.......73s and Best DX !........................................................Carl, WA0RLY
Hi Carl,
I'm glad that this information helped you to get things working correctly. Many thanks for your kind words.
73,
Andy
KB1OIQ
Hi Andy
NOT SAVE USB-SERIAL CH340 driver .Tthe computershuts down ehen four met off .THANK YUO. JUSTAS.
Hello Justinas,
Here are the stept to load the module on every boot:
1) as root, edit /etc/modules
2) Add "ch341"
3) Save the file
4) Reboot
5) Verify that the module has been loaded: lsmod | grep ch341
6) Enjoy!
73,
Andy
KB1OIQ
HI.
Not working.thank yuo.73
2020-07-12, sk, 19:19 Andy Stewart andystewart@users.sourceforge.net rašė:
2020-07-16, kt, 20:52 justinas justinas90@users.sourceforge.net rašė:
Hi Justinas,
To say "not working" is not helpful. WHAT isn't working?
Did you try what I suggested?
Which step in that process failed?
Did you verify that the driver is loaded?
Did you verify that your device is seen by the kernel after you plug it in?
Were there any error messages?
Did you do a Google search for more information?
73,
Andy
KB1OIQ