开云体育

Programmer Busy reading CVs with Ops mode over Railcom with YD9401

Scott Walton All Messages By This Member #4817 I have a DR5000 which has been upgraded to a YD9401. When I use DecoderPro with Programming on Main to read Read All Cvs, I get many "Programmer Busy" responses. The LocoNet log shows that the Write was rejected and then DecoderPro moves on to the next CV. The result is a delay and then a retry (with the next CV) which is soon accepted. So the overall process takes longer than it should, and several CV's are left in "Error" status and I need to click on "Read Changes on page" to to resolve them (serveral times, until all have been read).? ? Does anyone know if there is a way to resolve this? ? The environment is: ? YD9401 with three boosters, 2 DR5088RC RailCom readers, LocoBufferUSB, JMRI Decoder Pro 5.11 with Java 11 on Windows 11. ? If this could be resolved, then this method of reading all CV's would be the (almost) fastest method, with only LokProgrammer being faster. ? Scott Walton.
Iain Morrison All Messages By This Member #4819 开云体育 Scott, ? There are many factors that can impact the speed of reading when using PoM, amongst them being how busy the track is i.e. how many other locos are present, with special consideration as to how many are running. The make of decoders also has an effect as some report faster than others, and I have seen the weight and quality of wiring used affect the reporting on layouts. ? I know that the first and second can impact the reliability because using iTrain to read all CVs using PoM can occasionally cause a CV or two to fail to read if there are a large number of trains running, and stopping everything will result in all CVs being read in a couple of seconds with 100% success. I also notice that the 2 x TCS decoders have more failures in reading than Zimo decoders. ? Iain Morrison ? ? ? toggle quoted message Show quoted text From: [email protected] <[email protected]> On Behalf Of Scott Walton via groups.io Sent: 20 March 2025 22:34 To: [email protected] Subject: Programmer Busy reading CVs with Ops mode over Railcom with YD9401 ? I have a DR5000 which has been upgraded to a YD9401. When I use DecoderPro with Programming on Main to read Read All Cvs, I get many "Programmer Busy" responses. The LocoNet log shows that the Write was rejected and then DecoderPro moves on to the next CV. The result is a delay and then a retry (with the next CV) which is soon accepted. So the overall process takes longer than it should, and several CV's are left in "Error" status and I need to click on "Read Changes on page" to to resolve them (serveral times, until all have been read).? ? Does anyone know if there is a way to resolve this? ? The environment is: ? YD9401 with three boosters, 2 DR5088RC RailCom readers, LocoBufferUSB, JMRI Decoder Pro 5.11 with Java 11 on Windows 11. ? If this could be resolved, then this method of reading all CV's would be the (almost) fastest method, with only LokProgrammer being faster. ? Scott Walton.
karst.drenth All Messages By This Member #4820 Lower this setting: (POM packet repeat count) ... until it completely stops reading. My experience is that 2 or 3 are a good value. Unfortunately JMRI does not handle "Busy" with a retry of the same CV. As that should be the correct response to "Busy" Greets, Karst
Scott Walton All Messages By This Member #4824 I tried 2, 3 and 4. With 4 I get some (fewer) Programmer busy messages. With 2 and 3, I don't get Programmer busy, but I do see pauses., fewer with 2 than 3. It seems that 3 is the best setting for this. I'm doing all this with a mostly idle railroad, so the only messages are occaisonal "occupied" messages -- no throttles active. Overall, looks like a definint improvement. ? Scott Walton ?

Previous Topic Next Topic