RCModelReviews wrote:I've also asked Eva to tell us whether this is a newly introduced issue or if it's always been there.
I suspect it's relatively new -- otherwise 2-way systems would have been shooting each other down all over the place when used in 1-way mode.
if that's the case, then if you have a unit that's not affected by the problem, your GUID was already set in the 1-way mode anyway so you didn't/won't need to do the 2-way bind and, if you do, nothing will change but you won't have a zero GUID.
I'm thinking...speculating, One of two things is happening.
1) The current batch just recently sold (Earlier ones not affected) were sent out with a step in manufacturing / QC missed or skipped and some modules were shipped without ever being initialized properly once at the factory.
2) That a lot of people mistakenly (or while playing with new toy) tried to bind their new 2-way modules in two-way mode the first time and then realized that need to set the switches for their one-way receivers. This mistake actually triggered the first GUID change to be locked in and saved them from the current problem.
7SP