wow, what a great little tool!
ok, i just tried it and it's say data error for most of the time, i doubt it's your app... it'll be my setup for sure.
Data error, expected high nibble to be F 05
Data error, expected high nibble to be F 00
Data error, expected high nibble to be F 02
Data error, expected high nibble to be F C2
RC 08:40:45.0254 F2 41 01 00 F6
Data error, expected high nibble to be F 05
Data error, expected high nibble to be F 00
Data error, expected high nibble to be F 00
Data error, expected high nibble to be F 00
Data error, expected high nibble to be F 00
Data error, expected high nibble to be F 0A
Data error, expected high nibble to be F 00
Data error, expected high nibble to be F 05
Data error, expected high nibble to be F 00
Data error, expected high nibble to be F 04
PB 08:40:45.1190 FF 05 0A 00 05 00 04 FF F2 41 01 00 F6 05 0A 00 05 00
Data error, expected high nibble to be F 06
It makes me wonder if my hantek captures that showed the high nibble of the first byte to always be F might be in error, could you disable that data check so i can do some checking as to why this new method shows different data?
whatever i do i am getting erratic data even using terminal emulators, turning on even parity seems to help though if i use my other terminal emulator but doesn't in the q_capture app, does your app override the default settings for stuff like parity that i set in device mangler?