The onboarding process with the third (renumbered) Atlas/ESU V BN RS-3 got a little involved, when I decided to try using some of the advanced features of their new LokSound ESU-V decoders. I had already standardized on using F9 for "brake", but the ESU-V's have three different braking rates, called, cleverly, "Brake 1", "Brake 2" and "Brake 3". After some experiments, I decided to go with Brake 1 (CV179=200) mapped to my usual F9, Brake 2 (CV180=220) mapped to F10, and Brake 3 (CV181=240) mapped to F11. While I was at it, just for kicks, I mapped "drive hold" to F12. All of this is "ok", but not ideal, because functions above F9 are only available by double clicks on most of my NCE throttles. I use F9 for the brake mainly because it is in the lower left-hand corner of the throttle face, and easy to find when you're in a hurry to apply brakes to a moving locomotive.
I mainly use the LokProgrammer to set the CV's in ESU LokSound decoders, but I've heard that the JMRI interface is getting good enough to do this without using the LokProgrammer. It would be more convenient to use JMRI, because then my locomotive roster would all be on one computer, and accessible during op sessions by WiThrottles, among other advantages. I got into this hobby to run trains, not to become an electronics and database technician.
Once I had the three locomotives programmed with the three braking rates, mapped to F9, 10 and 11, I took them down and tested them on the layout. At first it seemed ok, but then once in a while, each locomotive, for no obvious reason, would randomly (and independently) come to a stop and wait about 13 seconds before resuming speed. The sound continued to be on, so it didn't seem like it was related to dirty wheels or track (although I did clean the wheels again just to make sure).
I didn't know what to do. I poured over the LokProgrammer windows, looking for ideas. I made sure all the DC modes and functions were turned off (since this is a DCC layout), in case the decoders were getting erroneous voltage spikes. Suddenly, about two hours into the hunt, I came across a section at the bottom of the "function settings" window in the LokProgrammer, where there was a section on "random functions". It turns out that the ESU V decoders come from the factory with a default setting which, when you press F11, causes the locomotive to randomly come to a stop in the middle of running! Since I had remapped F11 to be "Brake 3", as soon as I tested Brake 3 by pressing F11, the locomotive would thereafter be subject to random stoppages!
Can you imagine such a thing?! Shipping a new decoder to customers with a function activated by default which would cause the locomotive to randomly stop?! Someone back in ESU headquarters apparently thinks they're very clever. I think they owe me two hours. This is what is meant by "the learning curve". Sure, I was messing with their plans by remapping F11 to Brake 3. I get that. I should have spent another two hours studying the manual before doing it.
That said, the three locomotives are now running beautifully together in a lash-up. First generation Alco's are still alive and well, here on the Burrlington Northern in 1973.
No comments:
Post a Comment