I'm using a Zephyr (DCS50) with a LocoBuffer USB and trying to write CV's to a Tsunami decoder in ops mode but nothing happens when I make changes. Decoder Pro read the Tsunami just fine on the Program Track. Also, my DT402D throttle writes change okay in ops mode. Any ideas as to what I might be doing wrong?
Jerry
Rio Grande vs. Santa Fe.....the battle is over but the glory remains!
I have found that the DT402D can have conflicts sometimes. Most have blamed it on me or needing a 9.6 volt battery. I can tell you that I have this problem between that throttle and Decoder Pro.
What I have done is to dispatch the loco from the DT402D and opened up a throttle using Decoder pro. I then open the Ops mode programmer and go to work using the Decoder pro throttle and Programmer.
Richard
Thanks Richard. My problem didn't seem to be between the DT402D and Decoder Pro. The problem was that Decoder Pro wouldn't write CV's on the main because when I checked the results with my DT402D nothing changed.
However, I did what you said and opened a throttle in Decoder Pro and tried programming on the main with that throttle and it worked just fine. I closed that throttle and went back to Deocoder Pro and tried programming on the main again and checking the results with the DT402D and now it works???? What you suggested seems to have triggered something.
So, maybe somehow it does have something to do with the DT402D. Next time it dosen't work I will check the results with the Zephyr and see if that works.
Might be a dumb question but did you dispatch the loco from the 402D before using decoder pro?
Springfield PA
Hamltnblue Might be a dumb question but did you dispatch the loco from the 402D before using decoder pro?
It doesn't seem to matter. If I'm running the loco with the DT402D, start up Decoder Pro, make a change with Decoder Pro, like changing the whistle, then check it with the DT402D, the change is made okay. This wouldn't work before but now it does.
davidmbedard I have delt with this issue in the past. You might find that stopping the loco will help it program in Ops mode. So if you are trying to program your chuff rate, then you need to stop it for the decoder to accept it. Keep in mind that this issue isnt there with the PR3. It seems to be a slight limitation of the Locobuffer II. David B
I have delt with this issue in the past. You might find that stopping the loco will help it program in Ops mode. So if you are trying to program your chuff rate, then you need to stop it for the decoder to accept it.
Keep in mind that this issue isnt there with the PR3. It seems to be a slight limitation of the Locobuffer II.
David B
It doesn't happen when I use my DT400R or the UT4R, only with the DT402D. I have observed the DT402D loosing and even requiring a manual re-entry of addresses--with a new battery. It generates conflicts.
So, I would have to say the problem is not the loco buffer, but the DT402D and the locobuffer working together. And since the DT402D has issues working with the other throttles, I tend to fault the DT402D.
jwils1 So, maybe somehow it does have something to do with the DT402D. Next time it dosen't work I will check the results with the Zephyr and see if that works.
You're welcome.
From my experience the Zephyr will be more reliable. But, using the Decoder Pro throttles seem to make sense on a lot of levels. For example you can control the loco and adjust effects all on your computer screen, not having to go from handling one device and then another.
jwils1 The problem was that Decoder Pro wouldn't write CV's on the main because when I checked the results with my DT402D nothing changed.
The problem was that Decoder Pro wouldn't write CV's on the main because when I checked the results with my DT402D nothing changed.
How are you "checking" the results with the DT402? OPS mode programming is strictly a "write only" mode of programming and will display the same results every time because it can't read back CV values. There is no CV read back with OPS mode.
Colorado Front Range Railroad: http://www.coloradofrontrangerr.com/
Renegade1c jwils1: The problem was that Decoder Pro wouldn't write CV's on the main because when I checked the results with my DT402D nothing changed. How are you "checking" the results with the DT402? OPS mode programming is strictly a "write only" mode of programming and will display the same results every time because it can't read back CV values. There is no CV read back with OPS mode.
jwils1: The problem was that Decoder Pro wouldn't write CV's on the main because when I checked the results with my DT402D nothing changed.
By "checking" I mean I'm pressing the 2 button to see if the whistle sound actually changed, or other function buttons to see if the changes took effect. I'm not trying to check CV's.