55045 Problem

C

craigwrdouglas

Registered
Hi, I have just bought a 55045 module, but cant seem to get it to operate.

I have tried both the massoth cv programmer software that came in the box and the mts-pc version 6 that i have been using.

With the Massoth software, When I try to read out the values from the loco, every value comes back as 128.

With the MTS-PC software, I get a current over maximum value - I have changed the transformer to one from a stainz starter set, but still get this message with the software.

I am using a usb converter, but it is the same one on the same com port as the 55060 was using.

I have tried a few different locos, one with a factory fitted lgb chip (the yellow rhb tractor), a 2005 ish stainz with a 55021 chip and a 4/4 II with a Massoth XL chip.

Any Ideas would be appreciated.

Thanks,

Craig
 
I have never had issues with my 55045 programmer, but I use it directly on a serial port on an old laptop running Win 2000 I keep just for the railway.

So it could be the either the OS or it might be something to do with your USB convertor. I reckon that USB is a later comms protocol not supported by PC MTS 6.0....
 
I've had few problems with the 55045 on serial ports or using USB adaptors. I've used MTS v4 & v6 & Massoth. The only problem I have is it sometimes needs several tries to open the interface
 
I did believe that the expensive USB adaptor from LGB was specific to the programmer and that other generic USB adaptors would not work reliably. I also have only used the programmer on a serial port connection with success on both LGB and Massoth software.
 
The issue i get is reading any chip,i always get "Maximum Input Current Exceeded", I have updated to 55045 V6 software, but still get the same problem. the laptop is running XP
 
I use the transformer indicated in the #55045 programmer instructions, the 20 volt AC 5 amp supply. I have never seen any overcurrent alerts.
 
I am having the same problem with my 55045. I get the 'Maximum input current exceeded' followed by the 'EPROM not readable' message. I am trying to programme a twin motor LGB engine equipped with 2 x 55021s and a 55026 cable. I've used the exactly same set up to read and programme two other twin motored engines, with success.

Did you resolve your problem? If you did please let me know what you did. Thanks.
 
Power up the engine, and then switch off the lights, smoke (if applicable), sound (again, if applicable) and try again..
I often find with multiple older decoders, I need to isolate each in turn, to make sure each change of CV 'takes' to both decoders.

Quite often there are differences in programming between the two decoders as well.. I often share the load, by having lights controlled from one, and smoke from the other.
 
Phil, as you may have guessed I'm new to this, it's my first go at using my 55045 and fitting 55021s. Incidentally I have a Saxon Mayer with factory fitted decoders. I have to put the switch in position 2 for the decoders to be detected; nothing happens in positions 0 and 1.

How do Isolate each decoder? Thanks.
 
It would mean opening up the loco, and disconnecting one decoder.. Depending on the decoder, you may have white and brown wires either pushed onto pins, or soldered to the board, and going to pins on the original board.. If you remove the brown and white wires, you isolate that decoder from the track voltage.
A final option is the decoder just plugs into the main board (only one decoder does this) to isolate that decoder, you would just pull it from the main board.
 
In most cases, a load needs to be attached to the decoder in order for the responses to be detected by the programming module. Hence why you needed the switch in position 2 (motor on) for them to be "detected".

One reason to use a single larger capacity decoder in the old locos that were originally designed for 2x55021 decoders is that it will remove the need to disassemble and access each decoder individually during programming,

However, If you try to program a loco that has two decoders in it, it is possible that you can actually change CVs successfully in both decoders but there will be a conflict between them both generating the response back to the programmer which is what probably causes the software to raise the errors seen.

Newer decoders now have what is known as a "Programing Lock" which allows you to disable a decoder from responding to programming requests allowing other connected decoders to respond. Normally this works by each decoder having a CV set with a unlock value and in order to allow the decoder to be programmed, another CV needs to be set with that value causing it to be unlocked. The decoder will only respond to CV read and writes when those two CV values match. Of course different manufacturers may use different CVs to achieve this.
 
You must log in or register to reply here.
Back
Top Bottom