Lenz ERR 02

[newbryford]

I'm trying to set the address on a Loksound v3.5 using a Lenz 100. (I've done this many times before....)

 

However, I keep getting ERR02 when I try to either read or write the address. ERR02 is usually a sign that there is a comms error between programmer and decoder.

 

Strange thing is, I get the same ERR02 on CV1/4/5/7, but it works perfectly well on CV2/3/6/8. (I've only tried up to CV8).

The loco does "chatter" when I'm trying to read/write CV1 etc.

 

I have the same issue when a lokpilot is connected instead. (Goes to find another decoder type)....

 

I've reset my Set100, but still got the same problem.

I'm going to try a couple more things, but if anyone has any other advice, it would be gratefully received.

 

Cheers,

Mick

Edited December 27, 2014 by newbryford

[Dagworth]

You'll probably find the motor is too small to draw enough current for the ack pulse to be read reliably by the Lenz set. Put a second loco on the track and program both at the same time, when you've finished then reset the other loco back to its old settings

 

A

Edited December 27, 2014 by Dagworth

[newbryford]

You'll probably find the motor is too small to draw enough current for the ack pulse to be read reliably by the Lenz set. Put a second loco on the track and program both at the same time, when you've finished then reset the other loco back to its old settings

 

A

 

Hi Andi,

Tried that - the loco is a Hornby 67 and I've had no problems in the past. If I'm ever programming an accessory decoder, I usually use my ESU decoder tester as a load with an old decoder and that works fine. So I've put that in parallel with the 67 and no joy.

Just going to power up my old laptop that runs an ESU Lokprogrammer....

 

Cheers,

Mick

[newbryford]

 

Just going to power up my old laptop that runs an ESU Lokprogrammer....

 

 

 

Download the CV's from the loco to the Lokprogrammer, change the address to the required value and upload the CV's back to the loco and Hey Presto - it works.....

 

Still mystified as to why my Lenz 100 won't read it though.....

 

cheers,

Mick

[Dagworth]

Weird....

[Sunnysa]

Out of interest, since it happened have you tried programing another loco/decoder that you know has programed in the past.

 

 Are you programing the lok 3.5 in a decoder tester.

 

 I ask that because I have a decoder tester ( home made) that will not allow programing of some CVs on Lok 3.5s. 

 

Caused by,  as Dagworth said, the motor in tester does not draw enough current for the ack pulse.

 

 Just some thoughts.

 

 Cheers

 

  Ian

[newbryford]

Out of interest, since it happened have you tried programing another loco/decoder that you know has programed in the past.

 

 Are you programing the lok 3.5 in a decoder tester.

 

 I ask that because I have a decoder tester ( home made) that will not allow programing of some CVs on Lok 3.5s. 

 

Caused by,  as Dagworth said, the motor in tester does not draw enough current for the ack pulse.

 

 Just some thoughts.

 

 Cheers

 

  Ian

 

hi Ian,

The decoder is in the loco. There has been no previous history of not programming v3.5's in locos before, especially diesels with relatively large motors.

 

I'll try another v3.5 fitted 67 when I get to the shed later and report back.

 

Cheers,

Mick

[BoD]

You shouldn't have painted the wheels yellow.

[newbryford]

hi Ian,

The decoder is in the loco. There has been no previous history of not programming v3.5's in locos before, especially diesels with relatively large motors.

 

I'll try another v3.5 fitted 67 when I get to the shed later and report back.

 

Cheers,

Mick

 

just tried my other v3.5 fitted 67 - addressed on the same kit a few weeks ago without any problems.

 

Same ERR02.

 

I wonder if the fault is within my Lenz set. I'll do some more experimenting when I get chance.

 

Cheers,

Mick

[Sunnysa]

Mick,

 

To state the obvious,reading/writing some CVs and not others is certainly weird.

 

 In 19+ yrs op Lenz I have had strange things happen but nothing like this.

 

If all connections/plugs etc, check OK unfortunately your last statement may be true.

 

 The fault may be in Lenz system.

 

 Best of luck with your investigations.

 

 Cheers

 

  Ian

[newbryford]

Mick,

 

To state the obvious,reading/writing some CVs and not others is certainly weird.

 

 In 19+ yrs op Lenz I have had strange things happen but nothing like this.

 

If all connections/plugs etc, check OK unfortunately your last statement may be true.

 

 The fault may be in Lenz system.

 

 Best of luck with your investigations.

 

 Cheers

 

  Ian

 

Hi Ian,

I've had some situations when changing some CV's was only possibly in POM mode, but nothing as important as CV1....

 

I'll try and grab a few more different decoders as well as trying the same locos on a friend's Lenz100 in a few days.

 

Cheers,

Mick

[Sunnysa]

I am not sure what  you mean by CV1.

 

Are you trying to program address via CV1 or direct mode.

 

 When programing address (long or short address) I always use direct mode.

 

 I am probably clutching at straws but, Is your lenz the LZV100 V3.6 or V3.5

 

I ask because V3.5 did sometimes have some problems programing Lok 3.5 it was sometimes intermittent.

 

 

  Cheers

 

  Ian

[newbryford]

I am not sure what  you mean by CV1.

 

Are you trying to program address via CV1 or direct mode.

 

 When programing address (long or short address) I always use direct mode.

 

 I am probably clutching at straws but, Is your lenz the LZV100 V3.6 or V3.5

 

I ask because V3.5 did sometimes have some problems programing Lok 3.5 it was sometimes intermittent.

 

 

  Cheers

 

  Ian

 

Hi Ian,

 It's a v3.6 Lenz.

I may have confused you with CV1. I normally use direct programming for address, but that wouldn't work, so I tried programming via CV.. In either case, ERR02 was the result - I couldn't even read the original default of '3' in either mode.

Can't say I had any problems before my Lenz was upgraded to v3.6 either.

 

I'll keep looking!

 

 

 

Cheers,

Mick

[Loxborough]

I've resurrected this thread because I am having a simiar issue, and am mystified.

 

I use a V3.6 LZV100, an LH90 and Lenz gold decoders. Everything is running fine, including quite a complicated block management system on the layout, but I want to change some CVs. So, I plonk a loco on the programming track and try to write a CV. Error02. So I try to read the address, as a test. Error 02. I try to read a few more CVs, Error 02 each time.

 

I  check the connections and the cleanliness of the programming track, no apparant issues. Loco drives up and down the programming track cheefully, so the decoder is clearly in touch with the rest of the world, but still any attempt to read or write gives Error 02.

 

 Change the loco and the same happens. 

 

(I should point out that this is a new issue because I have never previously used the LZV100 for programming on the layout; that has always been done using an old Dynamis on my workbench, which recently died altogather, causing me to have to try to do things 'properly'. And yes, I have organised myself with a siding on the layout which is isolated from the rest as a programming track.

 

Any suggestions VERY gratefully received!

 

Thanks, and happy Christmas all,

 

G

[RFS]

How is your programming track wired? It needs to be wired to the P and Q terminals on the LZV100. You say locos are happily driving up and down so presumably this track is also connected to the bus via J and K. Is the changeover via a switch of some kind?

[Loxborough]

Robert,

 

OK, so I am feeling realy properly stupid now...

 

I hadn't clocked that the programming track had to be wired to the P&Q; I had wired it to J&K, and had a switch which just disconnected the rest of the layout when I wanted to programme something.

 

All rewired now, and (re)coding of CVs proceeding perfectly.

 

Thank you so much for your rapid answer (and sorry for wasting your time with what was in fact a very stupid question!)

 

G