Can FlyerChief interfer with Legacy?

I would be inclined to believe it was interference from another nearby layout, rather than the flyerChief.  FlyerChief uses the same 2.4GHz digital radios as LionChief/+, and if that radio signal caused problems for DCC engines then those engines would likely be rather useless in our modern world.  The 2.4GHz band is the same as used by most Wifi devices as well as Bluetooth devices, so in any sort of public setting the band is saturated with countless people's cell phones and other devices sending signals about.

In theory an over-saturation of people using devices on 2.4GHz might cause a Legacy hand held to have trouble communicating with its base, but I find even that to be unlikely, given the way these sorts of devices work, sending messages encoded such that they will only be read by the desired receiver.   Even if there was some heavy bandwidth consuming devices on the "air" it would still only prevent new commands from reaching between a Legacy remote and it's base, it wouldn't cause any new commands to be issued.  

I'm unfamiliar with DCC systems, but it is possible that some of them also use the 2.4GHz band for communication between remote and base, and if they do  they could have the same issue described above for the Legacy remote.  DCS and original TMCC use different radio frequencies, and should be entirely unaffected by FlyerChief/LionChief signals.  As for the track signals that actually talk to the engines, they are at such a low frequency by comparison that the 2.4GHz band is a non-issue.  

JGL

Francine,

As others have already posted, the interference was likely caused by another Legacy / TMCC base somewhere in the hall. The LionChief system (in all its capacities) operates on a completely different set of frequencies from LEGACY. The two can coexist on the same layout without issue. As far as interference with DCC goes, that is even less likely as the DCC signal pulses are carried through the rail and are not RF at all. Much more likely that there were two locomotives of the same address, or the locomotive hadn't been properly dispatched by the last user causing the DCC system to see multiple commands.

Thanks John & Ryan,

It's generally what our club members thought.  However without solid verification, I was not willing to commit with 100% certainty.

Francine