So far I have been working on 14bit "Shot" messages and things have been going fine.
But, a few days ago I started working on some of their system messages starting with their "Reload" command which is a 2400 header followed by a 3 byte command (24 bits) and I have been seeing some really strange signals very much like some of those on the AC threads with some random long bursts.
Anyway, I went back to basics and I wrote this simple sketch using IRRemote - basically it keeps sending a 24 bit code (FFFFFF) every 5 seconds or so
Code: Select all
#include <IRremote.h>
IRsend irsend;
void setup()
{}
void loop()
{
irsend.sendSony(0xFFFFFFFF, 24); // Sony TV power code
delay(5000);
}
I have attached a screenshot of the trace below - notice the very long pulse in the middle as well as the single spike shortly after.
I exported the data which is
0000 006D 0000 0018 0060 0014 0030 0018 002F 0016 0032 0014 0030 0016 0032 0015 0030 0016 0031 0015 0030 0017 01C3 0018 002F 0017 0015 002F 0017 0030 0016 0030 0017 0030 0015 0030 0017 0031 0014 0030 0016 0030 0016 0031 0016 0031 0014 0030 0018 002F 0017 002F 0026
I have also attached a screenshot of the signal I measured on the data leg of the TSOP2238 - clear header pulse followed by 24 data pulses.
From my testing so far I am seeing this problem once the data contains more than 20 bits - 20 bits works fine and is analysed as a 20 bit Sony code, but after that it is coming up as raw with these differing signals in AnalysisIR
Any light that you could shed on this would be great