Trains.com

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!

Tsunami2 programming

2335 views
6 replies
1 rating 2 rating 3 rating 4 rating 5 rating
  • Member since
    February 2002
  • From: Reading, PA
  • 30,002 posts
Posted by rrinker on Sunday, March 29, 2020 5:32 PM

 JMRI is just a throttle with a different interface. Really, that's all it does - mimics a throttle to read and write the decoder, and just presents the information as something other than just a bunch of CV numbers and values.

 If the definition is correct and the correct decoder is identified/selected, if the decoder can do it, and if a throttle can do it, then JMRI can do it.

 There is no need to fool around with index CVs with JMRI, unless you are trying to use the signel CV programmer, which is pretty much identical to doing it on an actual throttle. When you select a function setting and then write the changes, JMRI sets the index CV as required to apply the changes you've made.

                                                 --Randy

 


Modeling the Reading Railroad in the 1950's

 

Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.

  • Member since
    April 2012
  • From: Denver, CO
  • 771 posts
Posted by middleman on Sunday, March 29, 2020 4:11 PM

From the Tsunami2 Steam User Guide(page 55):

"Function mapping CVs allow you to reassign any effect to any function key, enable effects to respond automatically to direction and movement changes, map an effect to the emergency stop button, and gives you the option of using NMRA “Legacy” function mapping."

I have moved my functions all over the place with the Tsunami 2.It's easily done through my prodigy wireless throttle,but I'm not familiar with JMRI - hope someone else can chime in and help you with that.

Mike

  • Member since
    March 2018
  • 6 posts
Posted by Mac49 on Sunday, March 29, 2020 1:38 PM

Thanks for the suggestions.  On JMRI I found out there is a know problem with NCE Power Pro.  It won't write CV's >257 on the programming track.  JMRI knows this and just shuts the process down.  It should work to program on the main.  

Michael and Tom,

On 11 Jan 2020, at 1:33 PM, Tom Wilson <thomasthetrainengine@...> wrote:

The ProCab system was pre sound decoders and therefore did not anticipate the use of indexed cvs - especially the most modern decoders with many indexed cvs. It is incapable of writing indexed cvs in program track mode. What will happen if it does, is it will be writing values to the wrong cvs and you will really mess up your decoder. Decoder Pro knows this and just doesn't do the writes to keep you from messing it up.

Tom's explanation is basically correct. A clarification is that the problem is not indexed CVs per se (the DCC hardware system only works with individual CVs). The problem is with CVs>256.

A firmware problem with the NCE Power Pro truncates the CV address of Program Track Writes. So an attempt to program CV275 will instead program CV19!

SoundTraxx TSU2 and Econami are affected. LokSound decoders are unaffected because ESU provide an in-decoder workaround with high CV addresses and JMRI is programmed to automatically use that workaround.

Dave in Australia

 

  • Member since
    February 2002
  • From: Reading, PA
  • 30,002 posts
Posted by rrinker on Sunday, March 29, 2020 12:00 PM

Also check that what you are doing is even possible - not every function can be mapped to every function key, there are groups of functions that can be rearranged withing the given group, but that's the limit. It's unlikely that something that defaults to say F27 can be moved to F5 instead. Only decoders I know with 100% flexibility of functions, wires, and sounds are Loksound.

                                    --Randy


Modeling the Reading Railroad in the 1950's

 

Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.

  • Member since
    March 2010
  • From: Sherwood Park, Alberta, Canada
  • 252 posts
Posted by CNR378 on Sunday, March 29, 2020 10:57 AM

JMRI takes care of setting CV31 for you. 

If your system is locking up there is something else wrong. I suggest joining the JMRI users group on groups.io

Peter

  • Member since
    September 2003
  • 10,582 posts
Posted by mlehman on Sunday, March 29, 2020 10:23 AM

Try going to CV entry and enter as it says. Then prorgram via JMRI.

This is what the technical manual says on pg 30:

"CV 31:  Description

CV 31 and CV 32 (CV Index 2) contain the indexed address used for accessing CVs exceeding CV 256. CV 31 contains the most significant bits of the two-byte address and enablesindexed CV operation, as determined by CV 32.

Note: Modifying the default value of CV 31will disable indexed CV operation; CV 31 should never be programmed from its default value."

From: https://soundtraxx.com/manuals/tsunami2-digital-sound-decoder

Sounds like you may have something other than 16 entered in CV 31, so that needs fixed. Also check out what it says about CV 32 on the next page.

Mike Lehman

Urbana, IL

  • Member since
    March 2018
  • 6 posts
Tsunami2 programming
Posted by Mac49 on Saturday, March 28, 2020 11:27 AM

I am trying to program the function map on a Tsunami2 decoder.  I have looked at the instructions in the manual, but it says CV 31 must be set to 16.  CV 31 doesn't show up in the CV list.  When I make changes in JMRI and try to write them to the decoder, the system just locks up and nothing happens.  Any suggestions?

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!

Users Online

There are no community member online

Search the Community

ADVERTISEMENT
ADVERTISEMENT
ADVERTISEMENT
Model Railroader Newsletter See all
Sign up for our FREE e-newsletter and get model railroad news in your inbox!