开云体育

Thank you both for your replies.

Bob: I do not have any hand held throttles to use for testing, as the layout is intended to be computer controlled entirely. As to incompatible commands, I have e-mailed Mr. Deloof to ask which command station setting should be used in JMRI. I have not yet had a reply, although I only e-mailed him earlier to-day.

BillyBob - I tried both programming on the main and programming on the programming track, both with the same error message, as reproduced above. I am not too concerned about not being able to read values on the main if this is an inherent limitation: I only tried to do this because I could not get it to work on the programming track. Reading values (other than the address) on the main does work with my Digikeijs DR5000 command station (but not with JMRI - I cannot get any reading to work with JMRI, as described above).

As to the programming on the programming track issues, I will address these in turn.

1. Insufficient electrical connectivity with the decoder: I do not think that this is an issue as turning the lights on and off works without problem, as does moving the locomotive.
2. Insufficient voltage to program a decoder: I am not sure why this would be the case. There is sufficient voltage to run the locomotive at a moderate speed, so this seems unlikely.
3. Using a programming mode not compatible with the decoder or programming device: I have tried both Direct Byte and paged. What other modes would you suggest? I understand that the others are rare and that Direct Byte is generally recommended
4. Decoder is malfunctioning: I do not think that this is the case, as I am able to read and write values without difficulty using the DR5000 and its native software.
5. Programming device is malfunctioning: this is possible, I suppose, but I am not sure how to test for this, and it is suspicious that I am getting the same fault with JMRI with two separate command stations. Nonetheless, I have written to Mr. Deloof to query the problems that I am having.
6. Programming tool is configured to program a decoder type which is not matched to the actual decoder: I have set the correct decoder type in DecoderPro (a Zimo MX617N), so I do not think that it is this. In any event, I am trying to read an individual CV value, so this seems doubtful.
7. Programming tool is configured to use the wrong programming interface: there is only one programming interface, unless I have misunderstood what you mean here by "programming interface", being the LocoBuffer USB.
8. Programming tool is configured in a way which does not communicate with the programming hardware: I am not sure what this would entail or how to deal with this. However, if I understand what you mean correctly, this seems unlikely: I able to turn on or off the lights and move the locomotive on the programming track using the very same hardware, software and interface that fails when attempting to read CVs.

Thank you again for your assistance: this is most helpful.