-
-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kato FL12 #279
Comments
It could be that the FL12 still is "stuck in last century" and requires paged mode programming which DCC-EX CS can not do. Some things I read on the Internet sugest this. This would be the first decoder I know of sold in 2022 which can not do direct byte programming but considering what I have heard about the FL12 I would not be surprised. The ZIMO MX605SL is a drop in replacement for the Kato (OEM Digitrax?) FL12. Zimo decoders can of course direct byte programming. Regards, |
Is it just the write success that's failing? If you write an address and move it back to the main track does the new address work? |
FL11 and FL12 does not send reply, it need page mode programming. |
I just bought two new Kato locos and installed ESU Lok DCC 5v sound decoders. I had the exact same issue and searched for hours for a solution. My lights worked, but no movement. Then out of chance, I enter loco number 3 without any zeros in front and magically everything worked. So "03" and "003" are treated different than "3" in NCE Power Cab. Not sure this will fix your issue, but give it a try. |
Version
DCC-EX
Issue description
I can program address for Kato motor DCC decoder, but I can not setup the address for Kato FL12 DCC light decoder, is it compatible problem, what can I do? thanks!
The Kato FL12 DCC light decoder is working, default address is 03, and I can turn on/off the light, just can not change the address ID, it is very confusing, I tried lots of times to program the address ID, nothing happened!
Hardware
Mega 2560 wifi UNO R3 mega328p ESP8266
L298 motor shield
The text was updated successfully, but these errors were encountered: