I got my DCS Commander this week, too. I had a Supersnap figure 8 setup for my daughter's "science experiment" adding weight and seeing how much each additional pound of weight slowed the train down. Hooked up the Commander and I couldn't get the thing to recognize my FA-2. Got the "Er" message. Then when I switched back to the CW-80 for a check, the horn went off and it took off in reverse!!!
Fearing I had done expensive damage to the ALCO, I took it back upstairs to the Fastrack loop powered by a CW-80 where I had been running it before. When I first applied power the horn beeped again and it backed up again. I let it sit for a bit and then it resumed normal operations for a PS2 under conventional control.
So I tried removing the Supersnap terminal from the loop thinking maybe there was an anomaly somewhere in the figure 8 that was not affecting the conventional. Identical behavior "Er" on screen, and when back to the CW-80 horn and reverse on power up!!
Swapped in a 30" Fastrack straight connected to the DCS and Bazinga! engine added. Ran through some of the basic commands, everything worked fine.
So, what's the deal? The only things that changed was the track type and the hookup wire. The Supersnap runs conventional fine but the DCS, not at all. Fastrack runs both just fine.
I may be selling a pile of Supersnap in a bit.