I have got my very first Tsunami2 PNP EMD. Installation went fine. Programming is done with Decoder Pro (JMRI 4.4-R1ccf 76b current version, doenloaded 7/22). Decoder Pro identified the Tsunami2 Sound Decoder fine.
Prime mover select should be done via CV123.
Two problems
1. I can not find any input field to select the prime mover
2. CV 123 is not listed in the CV tab. It can not read or written.
I am quite new JMRI and Tsunami user. What did I miss?
ps. CV123 was set with my DCC controller at the layout to get 645 none turbo for the GP38-2.
Reinhard
Sounds like the definition file for the Tsunami2 is incomplete in that version of JMRI. Check the JMRI site if there is an updated definition file, otherwise you will just have to adjust it manually for now.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
Thank you. That was the problem.
Here is a nice explanation how to do it
http://www.dccguy.com/?p=1302
The sound selection issue was corrected in July. The updated definition is in the latest test release (4.5.5) if you wish to try it.
Other options are to wait until next month for the next production release or join the JMRI users group and download the updated definition from the files area.
Peter
Thanks for the help. I got an updates decoder file and that solved the problem. Great to know the next product release it up next month.
There's no good reason to not run the latest test version of JMRI, as long as you check the release notes for specific issues which may affect you. That's how they find and fix bugs, by having users try the test releases (which by the way are tested by the developers before being released.)
I've been using JMRI for about 13 years now and have always installed the latest test version as soon as it's released, and on a couple of occasions, even unreleased "nightly builds" to test a new/updated feature.
I can't remember that I ever had to back off a test release because of a problem. It might have happened, but not often enough or serious enough that I have any recollection of it.
That is very true. In fact I regularly check the latest developer commits and use the development build installers to test them and report any issues I encounter so they can be corrected prior to the test release. They are no longer "nightly builds" as such but automatically generated as the developers add changes.
I'm currently using 4.5.6ish downloaded this morning. This will culminate into the 4.5.6 test release in the next week or 2.