selector Assuming the under-F2 contacts aren't a little tired, or even defective, Tom, I'd say you have a communication problem, and yes, it might very well be a glitch in the programming.
Assuming the under-F2 contacts aren't a little tired, or even defective, Tom, I'd say you have a communication problem, and yes, it might very well be a glitch in the programming.
There aren't any function contact(s) on the Lokprogrammer itself, Crandell. I'm using a Windows tablet as the interface. So, I'm guessing it has to be a firmware issue of some kind. I may try posting the above on the Loksound Groups forum and see what they suggest.
Tom
https://tstage9.wixsite.com/nyc-modeling
Time...It marches on...without ever turning around to see if anyone is even keeping in step.
I've had the opposite happen, no F2 with the power cab but it works with the lokprogrammer. DCC poltergeists.
Henry
COB Potomac & Northern
Shenandoah Valley
Assuming the under-F2 contacts aren't a little tired, or even defective, Tom, I'd say you have a communication problem, and yes, it might very well be a glitch in the programming. Maybe format, or something like it, and start brand new with the newest version again, and see if this doesn't correct the problem? If not, I'd be on the blower to the techs at LokSound.
Greetings all,
I was using my Lokprogrammer this past evening to upgrade the firmware of my Select decoders and ran across an issue that has me scratching my head. When using the Lokprogrammer built-in throttle with two of the locomotives, the horn would not activate when pressing F2 but would if activated with my NCE Power Cab.
Is this a possible glitch with the Lokprogrammer firmware? I updated that firmware before upgrading the firmware of my Select decoders. It's not a huge deal. I'm just curious why it might be happening.
Thanks,