Hello Guys.
It's my first post here so I'd like to say "hi" to all of you and express my excitment regarding CQR Log software. I'm using it shortly as well as Linux OS in general so it gives me a lot of fun.
I purchased G4ZLP Dig Master Cw Keyer recently to work with CQR Log. And i stucked:) I'm not familiar with my OS (Lubuntu 14.04) so it is general help question reather then a bug report.
G4ZLP device is not visible to CQR Log. I downloaded server UDP program here https://www.cqrlog.com/?q=node/149 and it shows "error 9" and "Keyer offline" message.
I also runned trough drivers for winkeyer and cwdaemon.
My computer got USB ports functional (usb memory sticks loads up automaticly.
Same device works fine with windows so it is pretty much the case od detecting this device in my Lubuntu computer (excetp i don't know linux at all..)
Is there any way i can figure out what is wrong and run this keyer with CQR Log?
regards
Tom
Hi Tom,
it is not a Winkeyer problem, because G4ZLP DigiMaster CW Interface is not a Winkeyer ... :-)
Ubuntu as well as its clones has already built-in support of FTDI chips so your device must be visible as USB port. Check it using this script
#!/bin/bash
for sysdevpath in $(find /sys/bus/usb/devices/usb*/ -name dev); do
(
syspath="${sysdevpath%/dev}"
devname="$(udevadm info -q name -p $syspath)"
[[ "$devname" == "bus/"* ]] && continue
eval "$(udevadm info -q property --export -p $syspath)"
[[ -z "$ID_SERIAL" ]] && continue
echo "/dev/$devname - $ID_SERIAL"
)
done
Just copy the script and save it as "devcheck.sh". Make it executable and run it in a terminal window. You should see an output similar to this:
martin@doma:~$ ./devcheck.sh
/dev/ttyUSB0 - FTDI_FT232R_USB_UART_AD02DTQX
/dev/input/event11 - 1bcf_USB_Optical_Mouse
/dev/input/mouse0 - 1bcf_USB_Optical_Mouse
/dev/ttyUSB1 - FTDI_FT232R_USB_UART_A8007V22
/dev/ttyUSB2 - 1a86_USB2.0-Serial
You see that I have two USB ports with FTDI FT232 chips (ttyUSB0, ttyUSB1) ... and another USB port marked as 1a86_USB2.0-Serial (ttyUSB2) which is the chinese CH340G in an Arduino as a new prototype of my TinyKeyer. You should see at least one USB port with FTDI chip.
Don't hesitate to paste your output from devcheck.sh here, it will help to diagnose what happened to your system.
73, Martin, OK1RR
Thank you Martin.
You are right - it is now winkeyer - it is just G4ZLP who advertises his device as working with all winkeyer apps.
I was able to list mounted (or connected) usb devices yesterday and FTDI was present. I runned your script (thank you) and it returned as below:
/dev/ttyHS0 - Option_N.V._Globetrotter_HSUPA_Modem
/dev/ttyHS1 - Option_N.V._Globetrotter_HSUPA_Modem
/dev/ttyHS2 - Option_N.V._Globetrotter_HSUPA_Modem
/dev/ttyHS3 - Option_N.V._Globetrotter_HSUPA_Modem
/dev/ttyHS4 - Option_N.V._Globetrotter_HSUPA_Modem
/dev/ttyHS5 - Option_N.V._Globetrotter_HSUPA_Modem
/dev/input/event5 - Sonix_Technology_Co.__Ltd._USB_2.0_Camera
/dev/media0 - Sonix_Technology_Co.__Ltd._USB_2.0_Camera
/dev/video0 - Sonix_Technology_Co.__Ltd._USB_2.0_Camera
/dev/ttyUSB0 - FTDI_FT232R_USB_UART_A104VLLV
tomek@booklet:~$
any clue?
Tomek
sp5xo.net
meanwhile...
running : "sudo cwdaemon" gives back
"cwdaemon: bad keyer device: parport0"
sp5xo.net
Tomek,
I see that you have only one USB port, there is FTDI FT232R so I assume that this is the right one. So, in CQRLOG go to File -> Preferences -> CW interface, select from the first pulldown menu 'Interfaces type' the Winkeyer USB and set the port to /dev/ttyUSB0. If the G4ZLP device is compatible with Wineyer USB by K1EL, it must go. If not, there is another problem.
Forget the cwdaemon, your machine has no parallel port! This daemon is built for another purpose, it has nothing to do with Winkeyer!
BTW I would highly recommend to learn a bit about devices in Linux. It saves a lot of problems :-)
73,
Martin, OK1RR
Ok. So wheter this device is based on WinKeyer or not (first you told me it is not winkeyer device it does not comunicate with CQR Log.
Ofcourse i did what you adviced me and it brings no result at all.
I'm surely not familiar with linux as i admit in first post but what i figured out is that FTDI chipset is no longer recognized as "trusted" by ubuntu 14.04 and later. This results with some awkward procedure to make those devices trusted for the system.
After three days of seeking the way to make it go, crawling trough hilarious user setings in linux i just changed to win XP and n1mm. Thats why i was able to do some /p qsos flawlessly - including one with OK2CQR - thanks for calling me!
Maybe i'll have better luck next time or i need some more patience/knowlage to this intersting but wierd OS.
Thank you Peter.
CUL
sp5xo.net