elksmart/ccrustar NEC commands #2
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I've captured this
And decoded nec command matches https://ircodefinder.wasiliysoft.ru/page/rcbyuser/rcDetail.php?id=2e0d91cf-00f9-463d-be6d-6bdc766c54e4&label=RUBIN+RB-19SE9T2S (POWER)
yet, when i'm trying to send NEC command my tv doesn't seem react
for captured command, pulses are
But for NEC they are
Any help is appreciated, as i'm trying to make an app and driver for portable console, and there are a lot of databases for NEC codes, but, obviously, nothing for Ocrustar
Try different computers and USB ports, the gadget can be annoying. It has to quite visibly flash green when transmitting.
Also remember to use the --nec switch. If it is actually NEC-coded.
Otherwise I have no idea.
I mean, yeah, light is flashing. And transmitting captured command as-is succeeds (so it isn't pc / port issue. plus dumped with debug flag pulses differ between captured command and decoded one).
Mkay, looking closely at the code it makes sense why NEC pulses don't match captured pulses (because their values are fixed)
Guess i'm out of luck then
Another piece of information: those numbers are (light on, light off) pairs and receivers are very tolerant.
If you can graph these, that's how you should compare them.
The NEC protocol is rather well defined.
Try cutting off trailing pulses until it no longer works. You can take the encoded string as you got it, including any ff prefix pairs.
Oh, in learned sequence there's no inverted bytes (except that 0x57 is an inverted 0xA8), so it's just NEC variation (NECx2 ?), i guess.
And indeed, after rewriting encoding as
it now works