|
For quite a while now, I've had issues where all of the sudden, my polling of the Ocelot goes crazy...like the bytes were all offset. I had to put in code to wipe the slate clean and try again. It seemed like, with no warning, I'd suddenly get an extra 7 or 8 bytes of data. But nothing in the protocol doc mentions this, so I just wrote it off as annoying.
I've now come to believe that the bytes are being sent asynchronously from the Ocelot whenever one of the inputs on the Secu16i changes. If so, this would be VASTLY superior to my polling. However, again, my protocol doc (same as available on the website) doesn't mention anything about asynch messages coming across.
Soo...is the ocelot/secu16/secu16i setup to send asynch messages when an input changes? And if so, what is the format of that message? I know I could puzzle it out if I wanted to, but that's a hassle when there should be a document for this, as it's obviously an intended feature.
| 
