bluegaspode;455220 Wrote: > Why do we have 0x20 and 0x0A ? I don't know ... but lets just guess: > In the protocol spec there is a sentence "Each pulse is a 560µs long > 38kHz carrier burst (about 21 cycles)". > If a 'cycle' means one mark and one space > (http://www.sbprojects.com/knowledge/ir/ir.htm) in 21 cycles we will get > 10 marks :) Erm, Not that it really matters but I've just read this a bit more closely and it's not quite right... If a 'cycle' is one mark and one space then in 21 cycles we will get 21 marks (and 21 spaces), not 10. It appears that your detector (or maybe the software) is halving the number of cycles received before outputting them, or maybe the numbers mean something completely different? Your argument is still valid though as it's the relative size of the pule-space combination that was the problem.
As an aside, I know that the Pronto learned codes are in this format (number of cycles rather than time) and that it does report the 'true' number of cycles (eg RC5 is 36000Hz for 889us = 32 cycles, Pronto reports this correctly as 0x0020). I suspect that your setup would show 0x10??? -- indifference_engine ------------------------------------------------------------------------ indifference_engine's Profile: http://forums.slimdevices.com/member.php?userid=20698 View this thread: http://forums.slimdevices.com/showthread.php?t=66795
_______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
