Subscriber & Member Login

Login, or register today to interact in our online community, comment on articles, receive our newsletter, manage your account online and more!

Multi-Decoders - Decoder Lock not working?

1200 views
17 replies
1 rating 2 rating 3 rating 4 rating 5 rating
  • Member since
    June, 2009
  • From: QLD, Australia
  • 991 posts
Multi-Decoders - Decoder Lock not working?
Posted by tbdanny on Wednesday, May 10, 2017 3:26 PM

Hi all,

I have a steam engine in which I'm using a Digitrax DZ123 decoder for motor/lighting control and a Digitrax SFX006 soundbug decoder for sound.  I'm now trying to program them using the decoder lock feature and I'm running into a couple of problems.

On the DZ123, I have the lock CV (CV16) programmed to a value of 1.  For the SFX006, this same CV is programmed to a value of 2.  Currently, they're not wired together, but are connected to the programming track at the same time.  (I wanted to get my head around using decoder locks before installing them together).  However, when I have CV15 set to 0, both decoders will accept programming, even though they're only supposed to do so when CV15 and CV16 match.

Futhermore, when I do a 'Search' using the multi-decoder control function of JMRI, it doesn't detect decoders with 'ID Number 1' and 'ID Number 2'.  Instead, it'll detect 'ID Number 3' - the total of the two CV16 values.

Am I missing something?

I'm using JMRI DecoderPro via a SPROG2v3 programming interface.

The Location: Forests of the Pacific Northwest, Oregon
The Year: 1948
The Scale: On30
The Blog: http://bvlcorr.tumblr.com

  • Member since
    September, 2004
  • From: Dearborn Station
  • 16,423 posts
Posted by richhotrain on Sunday, May 14, 2017 6:08 AM

I am surprised that no one has replied to this thread by now.

I am not sure that I can offer much help, but let me make a few comments.

It seems to me that you are handling CV15 and CV16 correctly, so I wonder if JMRI Decoder Pro via SPROG is the problem.

The other possibility could be the fact that both decoders are "connected to the programming track at the same time". Digitrax recommends connecting the target decoder to the programming track all by itself.  Have you tried that without using JMRI Decoder Pro?

http://www.digitrax.com/tsd/KB519/decoder-lock-cv15-cv16/

Rich

Alton Junction

  • Member since
    July, 2006
  • 8 posts
Posted by fcwilt on Sunday, May 14, 2017 8:20 AM

Based on my readings locking should work on the programming track.

But, just as a test, have you tried programming on the main to see if locking works there?

Frederick

  • Member since
    September, 2004
  • From: Dearborn Station
  • 16,423 posts
Posted by richhotrain on Sunday, May 14, 2017 9:19 AM

fcwilt

Based on my readings locking should work on the programming track.

I was referring to the following instructions on the Digitrax web site:

Implementation Specifics: 

To configure unlocked decoders at installation: Each decoder is shipped from the factory unlocked with both CV15 & CV16 programmed to a value of 0. 

Before installing each unlocked decoder in the locomotive:
 

a) Connect the target decoder to the programming track all by itself 

b) Write a value of 08 to CV08 to ensure CV15 and CV16 are both zero 

c) Optional: Read CV15 to confirm that the CV Value is 0 meaning that the decoder is unlocked.

d) Program CV values desired into any CVs in the target decoder.  Program the address to the one you will use for all of the decoders that will be locked together. 

e) When you are finished programming the CVs, lock the decoder by writing CV16 to the desired ID number, for example 02 for a sound decoder. This step locks the target decoder to ID 02. 

f) Disconnect the target decoder from the programming track and install it in the locomotive 

g) Repeat in turn for each decoder to be installed in the locomotive. Note that this decoder lock method can be performed even when only a write-only programming method is available. Also, it is possible to use a "legacy" non-lock version decoder along with new lock capable decoder(s). In this case, program the decoders with the lock feature first, locking each one when programming is complete, and leave the non-lockable decoder to be programmed last. 

To access a decoder after installation:
 

a) When you want to program CVs in the target decoder with ID XX again, unlock it by programming CV15 to match the ID XX programmed in CV16. In the case of the example decoder, program CV15 to 02. 

b) Once the decoder is unlocked, program CVs as desired. 

c) When programming is finished, lock the decoder by programming CV15 to 0. 

To identify the decoder(s) present in a locomotive


a) Write a 0 to CV15 

b) Attempt to read a 0 from CV16. 

c) If no acknowledge is received, there is no decoder with ID 0. If an acknowledge is received, a decoder with ID 0 exists. 

Repeat this process for ID 1 through 7 to check for those IDs. 

 

Alton Junction

  • Member since
    March, 2010
  • From: Sherwood Park, Alberta, Canada
  • 144 posts
Posted by CNR378 on Sunday, May 14, 2017 11:40 AM

It was noted on another forum that the SFX006 does NOT support decoder locking (CV 15/16).

  • Member since
    February, 2008
  • 5,751 posts
Posted by maxman on Sunday, May 14, 2017 1:32 PM

tbdanny
I have a steam engine in which I'm using a Digitrax DZ123 decoder for motor/lighting control and a Digitrax SFX006 soundbug decoder for sound.

Since these are both Digitraxx decoders, is it possible that there are no conflicting CVs that would require you to lock the decoders in the first place?

  • Member since
    July, 2006
  • 8 posts
Posted by fcwilt on Sunday, May 14, 2017 4:57 PM

Not supported? Well that might have something to do with it.

 

  • Member since
    September, 2004
  • From: Dearborn Station
  • 16,423 posts
Posted by richhotrain on Monday, May 15, 2017 4:59 AM

CNR378

It was noted on another forum that the SFX006 does NOT support decoder locking (CV 15/16).

 

Can you be more specific? Which forum? Can you provide a link?

Rich

Alton Junction

  • Member since
    July, 2006
  • 8 posts
Posted by fcwilt on Tuesday, May 16, 2017 11:11 AM

richhotrain

 

 
CNR378

It was noted on another forum that the SFX006 does NOT support decoder locking (CV 15/16).

 

 

 

Can you be more specific? Which forum? Can you provide a link?

 

Rich

 

The data sheet:

http://www.digitrax.com/static/apps/products/sound-decoders/sfx006/documents/SFX006_2.pdf

 

IF page 10 is a complete list it does not show CV 15/16.

Frederick

  • Member since
    September, 2004
  • From: Dearborn Station
  • 16,423 posts
Posted by richhotrain on Tuesday, May 16, 2017 1:55 PM

fcwilt
 
richhotrain

 

 
CNR378

It was noted on another forum that the SFX006 does NOT support decoder locking (CV 15/16). 

 

Can you be more specific? Which forum? Can you provide a link? 

Rich 

 

The data sheet:

http://www.digitrax.com/static/apps/products/sound-decoders/sfx006/documents/SFX006_2.pdf

 

IF page 10 is a complete list it does not show CV 15/16.

Frederick 

The fact that CV15 and CV16 are not mentioned in that Instruction Sheet doesn't necessarily mean that the Soundbug does not support the decoder lock feature. Those CVs are omitted on most of the Digitrax Instruction Sheets. Digitrax decoders generally support the lock feature, and I will be surprised if the SFX006 does not since it is intended to be used along with a motive decoder.

Rich

Alton Junction

  • Member since
    February, 2008
  • 5,751 posts
Posted by maxman on Tuesday, May 16, 2017 2:15 PM

Okay, I'll ask my question again.  I thought that the purpose of the decoder lock thing was when one had two decoders with conflicting CVs (i.e. two identical CVs that had different fuctions), one decoder was locked while the CVs were programmed on the second decoder, and then the reverse was done to program the other decoder.

Since both decoders are Digitraxx, are there any CVs that actually conflict with each other, or was Digitraxx kind enough to avoid this situation?

  • Member since
    September, 2004
  • From: Dearborn Station
  • 16,423 posts
Posted by richhotrain on Tuesday, May 16, 2017 2:40 PM

maxman

Okay, I'll ask my question again.  I thought that the purpose of the decoder lock thing was when one had two decoders with conflicting CVs (i.e. two identical CVs that had different fuctions), one decoder was locked while the CVs were programmed on the second decoder, and then the reverse was done to program the other decoder.

Since both decoders are Digitraxx, are there any CVs that actually conflict with each other, or was Digitraxx kind enough to avoid this situation?

 

Unfortunately, the OP has not returned to this thread since he started it 7 days ago.

maxman, my understanding of the decoder lock feature is the same as yours.

Regarding the OP's problem, my initial reply was to wonder if JMRI Decoder Pro via SPROG is the problem. If it were me, I would follow the Digitrax instructions and connect the Soundbug to the programming track all by itself.  Forget about the decoder lock.

Rich

 

Alton Junction

  • Member since
    June, 2009
  • From: QLD, Australia
  • 991 posts
Posted by tbdanny on Tuesday, May 16, 2017 2:55 PM

Hi all,

Thank-you for the replies.  I should clarify - I programmed CV15 on both decoders separately, with the motor decoder having a value of 1 and the SFX006 a value of 2.  Following this, I connected both decoders to the programming track to test the decoder lock feature.  While the lock worked on the motor decoder, the SFX006 (with identical programming) did not work.

I just ended up installing a jumper on one of the track power leads to the SFX006, which allows me to disconnect it if the motor decoder needs to be programmed.  For programming the SFX006, I'll just lock out the motor decoder.

The Location: Forests of the Pacific Northwest, Oregon
The Year: 1948
The Scale: On30
The Blog: http://bvlcorr.tumblr.com

  • Member since
    September, 2004
  • From: Dearborn Station
  • 16,423 posts
Posted by richhotrain on Tuesday, May 16, 2017 3:05 PM

tbdanny

Hi all,

Thank-you for the replies.  I should clarify - I programmed CV15 on both decoders separately, with the motor decoder having a value of 1 and the SFX006 a value of 2.  Following this, I connected both decoders to the programming track to test the decoder lock feature.  While the lock worked on the motor decoder, the SFX006 (with identical programming) did not work.

I just ended up installing a jumper on one of the track power leads to the SFX006, which allows me to disconnect it if the motor decoder needs to be programmed.  For programming the SFX006, I'll just lock out the motor decoder.

 

Thanks for that reply, tbdanny. 

Good to hear back from you and glad you solved your problem.

Rich

Alton Junction

  • Member since
    July, 2006
  • 8 posts
Posted by fcwilt on Tuesday, May 16, 2017 4:50 PM

richhotrain

 

The fact that CV15 and CV16 are not mentioned in that Instruction Sheet doesn't necessarily mean that the Soundbug does not support the decoder lock feature. Rich

 
Understood - which is why I said "IF".
 
Frederick
  • Member since
    September, 2004
  • From: Dearborn Station
  • 16,423 posts
Posted by richhotrain on Tuesday, May 16, 2017 4:56 PM

fcwilt
 
 
richhotrain

 

The fact that CV15 and CV16 are not mentioned in that Instruction Sheet doesn't necessarily mean that the Soundbug does not support the decoder lock feature. Rich 

Understood - which is why I said "IF".
 
Frederick
 

Frederick, sorry about that. I failed to read your comment the way that it was intended to be read. My bad.

Rich

Alton Junction

  • Member since
    July, 2006
  • 8 posts
Posted by fcwilt on Tuesday, May 16, 2017 7:56 PM

richhotrain

 

 
fcwilt
 
 
richhotrain

 

The fact that CV15 and CV16 are not mentioned in that Instruction Sheet doesn't necessarily mean that the Soundbug does not support the decoder lock feature. Rich 

Understood - which is why I said "IF".
 
Frederick
 

 

 

Frederick, sorry about that. I failed to read your comment the way that it was intended to be read. My bad.

 

Rich

 

 

No biggie - just didn't want you to think I was an idiot.

Frederick

  • Member since
    September, 2004
  • From: Dearborn Station
  • 16,423 posts
Posted by richhotrain on Tuesday, May 16, 2017 8:05 PM

fcwilt

No biggie - just didn't want you to think I was an idiot.

Not at all, your speculation made total sense.

Rich

Alton Junction

Subscriber & Member Login

Login, or register today to interact in our online community, comment on articles, receive our newsletter, manage your account online and more!
Popular on ModelRailroader.com
Model Railroader Newsletter See all
Sign up for our FREE e-newsletter and get model railroad news in your inbox!
ADVERTISEMENT
ADVERTISEMENT

Search the Community

ADVERTISEMENT
Find us on Facebook