PPDMI, or others that are experiencing this issue, I have some questions or things to to test out just out of curiosity. I have all my engines compatible with the remote in storage right now so can't check it out on my own right now.
With the test above, where the remote must be reset at about the 7 minute mark, is this only when you make no adjustments at all over that time, or will it happen even when changing speed and such on the first engine throughout the time, then try to switch engines?
Also, if you switch back and forth through the engines, say every minute, does the problem still happen? Like if every 60 seconds you switch to the next engine and keep rotating through them? Or is it only if you don't switch engines over the whole time?
Lastly, if you do not switch engines, say only running one engine, is there any problem?
Some random thoughts:
Seven minutes is a weird number. It doesn't matter for the end users, but I think I have an idea how it is that the fault happens at 7 minutes. At first glance it doesn't seem to be an amount of time that neatly breaks down into one of the number limits a micro-processor would have. After some thought, though, it does roughly break down, if the processor's clock, for some reason, is counting in tenth's of a microsecond. That is if once every 1/10,000,000 of a second the clock is advanced a step. If the clock is stored in an unsigned long integer format, that type of number can get to 4,294,967,295 before it rolls over to zero. That breaks down to roughly 7 minutes and 9.5 seconds of .1 microsecond counts. So, not that it matters for folks that are having problems, but my theory on the cause of the problem is that the clock is rolling over to zero, and when it does so the remote thinks it has been reset. Sort of like the infamous Y2K bug with two digit years in dates.
JGL
