Replies: 2 comments
-
Commenting myself: I installed https://github.com/ok2cqr/winkeyer_server instead and it's running on port 6789. It found my K3NG arduino winkeyer without any problems. By choosing "cwdaemon" in the not1mm configuration I can now transmit fine, and I can also change the speed from the not1mm interface. What I can't do is (of course) to use the speed control on the actual K3NG device. Another thing that struck me is that not1mm lacks the ESM function (https://n1mmwp.hamdocs.com/setup/function-keys/#esm-enter-sends-message) which in my view is the first thing you activate in N1MM. I think I've seen requests for this feature somewhere else in the forum. A big step forward for me. No joy with pywinkeyerdaemon.py, but if ESM is activated I would be up and running and ready to take on some contests... |
Beta Was this translation helpful? Give feedback.
-
@awandahl Addressing serial devices: I always use the /dev/serial/by-id/whatever-your-device-shows-as as the device to talk to since it can't get re-enumerated to a random number on the next boot if you have more than one serial device. ESM: I'll think about it. But seems like a lot of trouble to implement for what you get in return. |
Beta Was this translation helpful? Give feedback.
-
PARTLY SOLVED BY WORK-AROUND, SEE MY COMMENT!
I can run https://github.com/mbridak/PyWinKeyerSerial properly (on an Arduino Winkeyer clone) but I have problems with the pywinkeyer. Is it this one I should use? https://github.com/drewarnett/pywinkeyerdaemon I have tried that one, changed it for proper unicode handling, but get this:
I run on a Tinkerboard 2 (Rockchip):
Any hints would be welcome...
Anders SM0HPL 5X7W
Beta Was this translation helpful? Give feedback.
All reactions