Loksound - 73100 strange issue

[tchrisk]

Hello all, I'm somewhat new to the forum, and very new to sound installs, but have been an N-scale modeler for some time with several decoder installs under my belt. I am currently installing a Loksound 73100 into a Intermountain SD45-2 and using a sugarcube speaker. I attached the speaker, and installed the decoder without issue. I used JMRI to read the program and set the unit number by modifying that page only. First of all, the unit runs fantastic, but only if F5 is set to "off" (maybe "on", I can verify). I found this by accident just testing function buttons. Secondly, while the horn, bell and spitters sound great, I have no diesel engine sound at all. F8 seems to have no affect on anything. I am going to build a new configuration tonight and write it to the decoder and see if that makes a difference, but I'm wondering at what point I just do a factory reset.

Currently running Digitrax DSC100, upgraded from JMRI 4.08 to 4.10 last night, connected to a Raspberry Pi with a PR3, and a UT4R throttle.

Any tips before I do a reset?

-Chris

[jdcolombo]

Did you order the 73100 with a particular file installed?  If so, which one?

John C.

[tchrisk]

75410FT , but probably should have gotten the 20 cylinder version.

Also should mention that I do not have a Loksound programmer.

-Chris

[RBrodzinsky]

Well, per that project, F5 is simply controlling Aux3 output, so shouldn't have anything to do with the motor.  Are you sure it wasn't F10, which would be Independent Brake (if ON, then you have the brake on, and it won't start moving), or F7 (in which case, you have it in "switching mode", where all voltages are decreased by 50%(IIRC))?

Did you load your JMRI profile with the current settings from the decoder by doing a READ ALL SHEETS?  That should have taken quite a while.  An alternative, even if you don't have the LokProgrammer hardware, is to use the LP software (on a Windows machine); load the project file from the ESU website; and then do an Export CV List.  The created text file can then be imported into DecoderPro (File | Import | LokProgrammer CV List File), and you now have all the default values for every CV. 

[jdcolombo]

Rick is correct.  If you didn't do a "read all sheets" before writing new values in the decoder via JMRI, then you almost certainly messed up the decoder file.  JMRI does NOT have the correct default values for ESU sound files; you have to "read all sheets" or use the trick Rick outlines with the LokProgrammer software to get those defaults.

If you didn't do a "read all sheets" first, then I'd go ahead and do a factory reset to get yourself back to starting position.  Then either use the Read All Sheets command, or Rick's LokProgrammer Software trick to get the correct default values into JMRI.  THEN you can program to your heart's content.

John C.

[tchrisk]

Yes, I did a read all sheets before I did anything, and it took around 45 Min to do. I built a new config from scratch and loaded it last night and during the process, I could hear the diesel engine, start, run and shutdown. This is the first time I have heard this, so I know the sound files are still on there. I am only writing changes to the sheets, one sheet at a time, so hopefully I haven't lost my sound file. I'll get it on the railroad tonight and see if the problem is fixed. If not, I will download the LP software and write my CV's as Rick suggests.

The tips are appreciated. As I mentioned, this is my first sound install, and while it hasn't gone totally to plan, I'm not frustrated yet! 

-Chris

[RBrodzinsky]

The one nice thing is you cannot lose the sounds. They are there, even if you do a CV8=8 reset, until you download a new sound project to the decoder with a LokProgrammer.

Is it possible that whoever loaded your project possibly put the F8 sound on/off instead to the multi-step Volume / mute?

[tchrisk]

Well then... You ever have one of those days where the more you learn the dumber you feel?

I built a config file from scratch - no joy

I used Loksound to build a CV list and compared the CV's - no joy

I tried manually tweaking CV48 to several configurations to see if I could make one work - no joy

On a whim, I plugged sound slot 1 into F1 instead of F8 and HOORAY! I have diesel sounds! But now, F8 doesn't turn on my bell. I'm not sure what would cause this. When monitoring loconet, I can see F8 turning on and off when I toggle the switch, but the decoder just doesn't see it. Sound like another forum search is called for as I have narrowed down the issue here. 

-Chris

[RBrodzinsky]

Hmm, something is screwy in the decoder settings, just not sure what.

Try this -- using the created CV list from the project on the ESU website (as I describe above), import those settings into your JMRI loco definition.  Then, individually, write each sheet to the decoder (you can do a "write all sheets", but this way you can see the progress better).  The Function Map tab will take a while, as will the sounds tab.  This will put known good values everywhere.

[tchrisk]

I may have just found my problem... I will verify tonight.

https://www.therailwire.net/forum/index.php?topic=40225.msg533460#msg533460

-Chris

[tchrisk]

Just to wrap this up, when I opened up my DCS100 to check the 2 digit code on the chip, I found it marked BG. I then reprogrammed my decoder flipping the F5-F8 with F9-F12 and everything is perfect. I will flip it back when I get my DCS upgraded. Thanks for all the help, and sorry for the wild goose chase.

-Chris

[reinhardtjh]

I'm glad my post helped.  You must have a fairly old DCS100 for a "BF" firmware code.  As far as I know, the function problem was resolved around 2004-ish.  I got my DCS100 when I got one of the first Duplex systems in 2009.