Faulty decoder ?

Hi , I recently posted about a decoder problem with an EFE N gauge J94 loco and that problem in now resolved but I have another problem with another decoder who's I/D is unknown .I should explain the background to this to save any confusion , firstly I have very recently built a "speed profiling " track to be used for speed profiling locos in traincontroller 10 gold and decided to make it dual purpose , it is just a 1 metre straight length of track divided into 3 blocks with occupancy handled by a Lenz LRB 08 occupancy detector and this is working just fine the other intended function was to use an ESU decoder tester connected to a sprog and the tracks for use with decoder pro and this I have done .I have hit a problem though in that I tested and read the CV's on 2 decoders  a Lenz and a Zimo and all went well but on the 3rd decoder I tested (an unknown one ) decoder pro gave a 309 error which it described as a short on the tracks which puzzled me as there are definately no shorts and i'd just tested 2 decoders with no problems I am wondering if anyone has experienced a 309 error and does anyone know if it can be caused by a faulty decoder ?.

Absolutely no idea why you've encountered this problem Gary but, if 2 other decoders work perfectly, my suspicions would point to the errant decoder.

If decoder Pro won't/can't even read the manufacture code, then my guess would be there's a fault in there somewhere.  Does it work when installed in a loco ?

Having said all that, I have a Zimo tester and it will only work on Zimo decoders (thus far), although it can read the manufacturer codes on other makes I have................

Hi Peter thank you for your response , I get the same problem with the chip installed in a known to be good Loco ie just a sprog the test track and decoder pro ,I feel that I should also mention that the Lenz occupancy detector is only used and connected to the test track  for traincontroller speed profiling purposes it has 8 inputs but I only use 3 the Lenz LZV 200 CS is only connected to this system when I want to speed profile a loco within traincontroller ie the 2 systems are never used or connected both at the same time , i've joined a yahoo group for Sprog users and posted the same question there but at present i've received no replies .

I can now put this post to bed as I can now report that having joined the JMRI and Sprog user groups any of the error  codes from 301 to 309 can be produced by a bad decoder .

Mystery solved 👍


Ed

Good news that you found the problem Gary - is there any way you can find the make of the decoder or can't it be read at all on anything ?

No Peter ,decoder pro just gives the 309 error whether the chip is in a loco or the ESU decoder tester so I guess it's one for thhe bin .