Quote:
I did some more experimenting with EEHack and the CCM in a parking garage today at work. It turned out that the five seconds I was experiencing while experimenting with Flashhack was actually due to Flashhack's timeout period. So with Flashhack, if I send a command, it first connects to the bus, then sends the command, then after a certain amount of time (~5 seconds?) with no further commands, it disconnects from the bus and returns everything to normal operation. This disconnection process resets the CCM, which cancels the Mode 04 command. EEHack on the other hand connects first and stays connected until you disconnect it. As such, sending a command will cause that to continue to run until you send an opposing command (such as 00) or reset the CCM or the bus.
flashhack doesn't really have a timeout period. eehack does have a keep-alive feature that keeps twiddling the bus keep it asleep. what's happening is the CCM times out with no activity on the bus in flashhack and resuming normal traffic. i might add a keepalive thing to help with testing like this but as a flash tool it's probably not necessary, we just start our operation, and when it's done, it's done. there should be no idle time.
Quote:
Interestingly, attempting to do something like "000000FF" does nothing. It seems that if the first four bits are 0, nothing happens. At least one of the first four bits must be nonzero. I only tested F, but considering the combinations of lights that came on, I'm guessing that this is actually based on number values somehow.
ah yeah that's something we've seen before. sometimes there's bits/bytes for 'enable override' then bits/bytes for 'on/off'.