ESU LOKPROGRAMMER WITH version 4 decoders

TONYWARD50

TONYWARD50

Tadpole sexing</br>
I have been happily using a Loksound Programmer with ESU V3.5 chips with few problems. Now that the new XLV4 chips are available I have downloaded the latest software but I cannot use the Programmer as there is an error message saying that the Programmer cannot be detected and that I should use a USB cable with an FTDI chip.
Can I get one of these easily and why doesn't the programmer work with V4 although it is still function1ng with V3.5 decoders ?

Any help would be appreciated, chaps.
 
Sorry I don't understand.

So you have downloaded AND installed the latest LocProgrammer PC software that supports the 4.0 decoders. Correct?

You can no longer talk to the LocProgrammer, sounds like some sort of COM port problem (using the wrong one).

If you can't talk to the programmer from your PC how come you can still program V3.5 decoders?

I would have thought that the interface cable you need is exactly the same one that came with the programmer, and the one you used previously with V3.5 decoders (or is it a serial cable rather than a USB one?)
 
Cliff you are quite correct !
The Programmer will "talk" if you load the old version, i.e. 3.5 and program the old decoders
The new program will not recognise the Programmer.
The cable is a serial to USB cable which was supplied with the Programmer 3 years ago
Hope this helps
 
The first thing that comes up when I run up my (admitedly older) version of the Loc Programmer software is to ask which COM port to use. If it is the same for you just try selecting each COM port in turn and see if you can connect to the programmer.
 
This doesn't sound like the com port thing as it wouldn't work with the 3.5's either. I'd send ESU a email via their website as there have been several issues with V4 chips and see if they know and have a fix. Alternatively, where did you buy it? SWD or DCC supplies? Give them a buzz as they use them for loading sounds so should know any common bugs. ;)
Sorry but I've not uploaded to v4 yet as I haven't got any new chips so can't help more at present.
 
PaulRhB said:
This doesn't sound like the com port thing as it wouldn't work with the 3.5's either.
Click to expand...

Yes it would if the newer software decided to use a different port. It does not yet sound to me that there is any evidence of a problem with the new V4 chip. As I understand it the problem seems to be takling to the programmer with the newer software. Of course talking to ESU/DCC Supplies etc might help.
 
The way I read the LokProgrammer manual, you can only use the new software version to programme the V4.0 decoders, so you have to continue using the old software version with the older decoders. The programmer is the same. Do you have a V4.0 decoder or do you just want to try out the new software?
 
bunnyrabbit03 said:
The way I read the LokProgrammer manual, you can only use the new software version to programme the V4.0 decoders, so you have to continue using the old software version with the older decoders.
Click to expand...
Dunno about the manual, but the software download section on the ESU website seems to imply the above, as it doesn't include the V3.5 decoders in the list of supported devices - instead they're listed in the download for the older version of the software.

Personally I'd consider that rather poor software design, to have to switch between two different programs to work on different decoders from the same manufacturer - let's face it, many users will end up with both types. I'd have expected the software to read the decoder version and configure itself appropriately - as does something like JMRI DecoderPro.
 
I now have the new lead and it works !
Only problem is that having programmed successfully I tweaked a few of the CVs to ensure smoother running and the chip went up in smoke !!! No short-circuit but this is the second ESU chip in 2 months to go west !!
I can get them replaced but no-one seems to have any stock.

Can anyone help with ideas ?
 
TONYWARD50 said:
I have a new V4 decoder.
I purchased it from Coastal in Ipswich.
Click to expand...
Might be worth talking to Kevin of Coastal DCC then?

I know him personally and he is a very helpful chap....
 
TONYWARD50 said:
I now have the new lead and it works !
Only problem is that having programmed successfully I tweaked a few of the CVs to ensure smoother running and the chip went up in smoke !!! No short-circuit but this is the second ESU chip in 2 months to go west !!
I can get them replaced but no-one seems to have any stock.

Can anyone help with ideas ?
Click to expand...


Oooh, that's a bit worrying - I've never managed to fry a decoder just by altering some CVs! OK, I've blown a few bulbs in the past (including the so-far-impossible-to-replace ones in my black Ts3.... :@) but never anything worse, touch wood! I always thought that, like computers, you couldn't really "break" anything permanently just by programming - at the worst you might have to reset them and start again.
If two have failed on you, that smacks of either a bad batch or a real problem somewhere.........

Jon.
 
TONYWARD50 said:
I now have the new lead and it works !
Only problem is that having programmed successfully I tweaked a few of the CVs to ensure smoother running and the chip went up in smoke !!! No short-circuit but this is the second ESU chip in 2 months to go west !!
I can get them replaced but no-one seems to have any stock.

Can anyone help with ideas ?
Click to expand...

Just out of interest, what did you alter (or try and alter) when they died? I've just ordered two v4's and their too expensive to make pretty smoke signals... What loco's have you got them fitted in?
 
USA Trains NW2 and I reduced the top speed (CV5).
I was using the Loksound Programmer and it seemed to not want to turn off.
The loco then started buzzing and the plume of smoke.
DO PLEASE BE VERY VERY CAREFUL AS THERE IS NO INSULATION AROUNF THESE V4S -they have lots of solder tags etc.
Mine was mounted on Plasticard so should be OK.

The last one was working well but suddenly decided to shoot off at top speed and then burnt out....

Regards
 
No, certainly not through adjusting CVs as you mentioned previously. I did blow a Lenz decoder once but it was my fault through mis-wiring. I managed to repair it with a replacement component.

I have 3 or 4 ESU LokPilot XL decoders installed, very pleased with them although I did have to re-program a couple which seemed to have been preloaded with settings for small scale decoders (inappropriate BEMF settings etc.)
 
andyspencer said:
Has anybody else had issues with chips dying apart from when there were obvious external faults?
Click to expand...
No.

I've got three ESU decoders and never had a problem with them.

Apart from a faulty board, or incorrectly connected decoder, it is hard to see why just changing CVs could blow a decoder. I've programmed quite a few from many manufacturers and never had any issues, nor would I expect any.
 
I just purchased a LokProgrammer 53452 to tweek ESU XL v4.0 decoders as I mentioned yesterday on the CS3 T&T thread. I used it today (actually yesterday as it's well past midnight local time) to adjust settings on a LokPilot XL v4.0 I had installed in a RhB Ge2/4, LGB 2045.

I loaded the LokProgrammer 4.5.1 software on a laptop running Windows 7. Windows recognized the LokProgrammer's USB/RS-232 cable as soon as it was plugged into a USB port, searched for, and downloaded the needed device drivers. I did not need to download the driver from the ESU site. The LokProgrammer firmware updated and everything went smoothly.

The ESU software sure makes it easy to adjust their decoders. No more CV's! I fixed the headlights to work in the Swiss fashion as described in the decoder manual. I also modified the motor response from the default exponential to linear. This made Ge2/4 speed match the range I'd chosen, 0-60 kph, for loc when I added it to the CS3. In other words, 30 on the controller is now half the max controller speed of 60. Slow speed response is still very good. The lok will just crawl along at a setting between 1 and 5. I also fiddled with the starting voltage, maximum speed, acceleration and breaking delays and limited the recognized digital modes to M4 (Mfx) and DCC. The LokProgrammer actually makes changing decoder parameters a pleasurable task.

I'm quite pleased with how the Ge2/4 now operates with the CS3. I also checked it with analog control. It works fine except the headlights are no longer constant brightness. I had changed the bulbs when I put in the decoder from 5V to 24V so they would not burn out from the constantly applied digital track voltage. I plan to put the 5V bulbs back in now that I know how easy it is to modify decoder functions using the LokProgrammer software. I'll just set voltage limits of about 4V on the decoder headlight and Aux1 outputs. Those are the outputs driving the headlights and directional cab lighting. This should restore "constant brightness" to the headlights in analog operation as I've got the starting voltage set to 5V. While I'm at it, I might separate the two cab lights to their own decoder function so I can try out some timed dimming or other effects.

The only issue I had with the LokProgrammer and software was loss of communication between the laptop and LokProgrammer when a "project" was closed. Simply unplugging and re-plugging the USB cable connection restored communication between the LokProgrammer software and hardware. The ESU device driver may solve this issue, but it is only a vary minor inconvenience.

Out of curiosity, I tired to read a LGB factory Mfx decoder equipped locomotive with the LokProgrammer. It was not recognized and an error message to that effect was displayed by the software.

Phil S.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom