And this is how it looks like;)
Yes they are very useful!
Did you try pressing every button in case I have the order reversed?
Phil
Yes, tried all buttons and in debug. Nothing catches.
OK try now, I wonder if the first byte on your list (255) isnât actually received and the data starts at the second byte? That would make sense and would be 16 bytes of data.
Phil
Well now I continously have PTT on/off in debug log;)
2023-02-07 21:56:41.144 DBG usbcontrol: On Button event: âPTT Onâ
2023-02-07 21:56:41.144 DBG usbcontrol: Off Button event: âPTT Offâ
2023-02-07 21:56:41.169 DBG usbcontrol: On Button event: âPTT Onâ
2023-02-07 21:56:41.169 DBG usbcontrol: Off Button event: âPTT Offâ
2023-02-07 21:56:41.195 DBG usbcontrol: On Button event: âPTT Onâ
2023-02-07 21:56:41.195 DBG usbcontrol: Off Button event: âPTT Offâ
2023-02-07 21:56:41.220 DBG usbcontrol: On Button event: âPTT Onâ
2023-02-07 21:56:41.220 DBG usbcontrol: Off Button event: âPTT Offâ
2023-02-07 21:56:41.245 DBG usbcontrol: On Button event: âPTT Onâ
2023-02-07 21:56:41.245 DBG usbcontrol: Off Button event: âPTT Offâ
2023-02-07 21:56:41.270 DBG usbcontrol: On Button event: âPTT Onâ
2023-02-07 21:56:41.271 DBG usbcontrol: Off Button event: âPTT Offâ
2023-02-07 21:56:41.296 DBG usbcontrol: On Button event: âPTT Onâ
OK so that guess was wrong 
Data is composed of 17 bytes data[0] - data[16]
data[0] is 255 all the time
example from wireshark:
âusbhid.dataâ: âff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00â
OK try it now, hopefully that should be it?
Now its betterâŚ
ButâŚ;\
There is a difference between RC28 and eCoder.
RC28 is sending data ONLY if there is a change, while eCoder is sending data all the time even without the changeâŚ
For some reason it is continously on/off still.
aa.log (372.9 KB)
debug.log attached.
Here you have output from my python debugger.
I just pressed PTT foot switch (JACK) and button1 (top left).
python.log (300.3 KB)
You can see the data on data[1] and data[3]
It shouldnât matter as the code only reacts on a change of the button values rather than each time it is received. As long as it isnât sending an empty value in-between or something?
Let me check it again.
It does not send any data in between. Debounce is done correctly;)
OK try that now, it now only reacts if the first byte is 0xff.
You are my hero;)
Buttons are correctly recognized;)
PTT from JACK does not work.
Nor VFO.
Give me a chance I havenât even looked at those yet and need to eat now!
Smacznego @phil !
Regarding, the VFO knobâŚ
I think it was just not designed to spin the VFO wheel that fastâŚ
Observations/tests on ExpertSDR3 shows they have the same issue.
I would just suggest to make an assumption that:
1-127 means increase by 10Hz * data[13]
255-129 means decrease by 10Hz * (256 - data[13])
Try the VFO knob now.
Works great!, but on default 100Hz its to fast - the same as RC28.
It seems that dedicated knobs, like RC28, eCoder have way higher resolution then non-radio world.
eCoder has 1024 resolution encoder, for RC28 I have no clue but something close to that number too.
Try the new sensitivity slider underneath the controller image.
