Help! LOKProgrammer

[nebrzephyr]

OK...so new to the ESU line of decoders. As an entry into using the LOKProgrammer I tried to read the diesel motor volume (CV259). It sates that you need to set cv32 to 1 to WRITE a value, but doesn't say anything about READ. From the screen shot below I assume by setting the check box to use CV31/32 that the programmer would do the sequence. Notice when I read it returns 0, but it should be 128. When I read a regular CV, say 63 (master volume) it returns the proper default value. I know I'm missing something.

Plus, where can you find what sounds are assigned to which "sound slots"? Thanks. Bob

[nebrzephyr]

OK....after some more research I exported the CV values. In looking thru those I found the "set" that matches the default values for the Fox Valley GP60M/B. So I was able to change the prime mover volume lower ,(default is way loud).

I'm still struggling with the overall concept of LOKProgrammer as to how to determine what CV's correspond to what sounds. For example, the "random" sounds.

Bob

[Mark R.]

Your best bet is to go to the ESU site and download the OEM file for the Fox Valley GP60. Open that file in the LokProgrammer. Now you will have the full file listings in the function pane to work from.

When you just "read" your engine, it won't list the actual names of the given sound slots.

I've never used the "read and write CVs" section on the LokProgrammer. I've always downloaded the needed file and used it aa a base point and modified from there. Once done, save your changes for future reference points.

Mark.

[bnsf971]

And when you save the file, it will ask what you want to name it, and where you want it saved. Naming the file "ATSF100", or whatever the road number is, and creating a dedicated folder for you ESU files, makes things very convenient for repeat programming. I have several I have saved like that, with correct horns, volume and momentum settings, and whether the motor starts with F8 or not. I simply open and load that file into a new engine, and am usually done in less than 5 minutes.

[nebrzephyr]

Thanks Mark and Terry. Needless to say I need more time exploring the options with LOKProgrammer. I was a little leery using DecorderPro as it sounded like it was still a "work in progress" as far as the LOK Sound chips were concerned.

Mark, let me make sure I understand your comment. So I load the GP60 file from ESU into LOKProgrammer, that will give me the various sounds and values. What I'm not sure about is do I then load the chip that's actually on the engine and make the changes based on what I found in the first load? Then save that "project" for the specific engine?

I've read thru both the LOKProgrammer and LOKSound manuals and I still not clear on most of this, probably just me. Without exporting the sounds I would never have known what values to place in CV31/32 to change 259, as I didn't see that in the manual. Again, I probably am overlooking it.

Figuring out the programming aside, I will say I'm very impressed with the LOK chips. I have 2 LOK Sounds chipped engines (1 factory, 1 my install) and 1 LOK Pilot. I put the 3 on the track as a consist and they run perfectly together.....straight out of the box!!!! Didn't need to change a single setting. Never had that happen before with other brands of sound/mobile decoders. Of course I might see different results if I was mixing different brands/releases of engines. I've read numerous times on the forum what great motor control LOK has, and I know see that for myself.

Bob

[bnsf971]

Bob, you can load the entire file onto the decoder you just installed.

[Mark R.]

Bob, if you open the Fox Valley GP60 in your programmer, and then use the "write data" option, all the CVs will be reset back to the original factory settings. At least you will then have a base starting point for your file. Make your changes using the various pages the programmer provides. When you've made your changes, use the "write data" option to make those changes to the decoder. Then save the file to your computer.

The next time you want to make any changes to that engine, just re-open your saved file and continue on from there. If you use the "read decoder" option, it WILL give you all the correct CV settings, but it won't fill in the fields by name what each sound slot is.

Mark.

[bnsf971]

Bob, when you get to the point where you are tweaking operation, I've found a setting of around 125 for cv 3 and 4 gives pretty good results.

[nebrzephyr]

Mark and Terry, thanks for the add'l info. Bob

[nebrzephyr]

OK.....think I have the basics down. Now trying to figure out the "random" sounds. It appears you can assign an individual sound to an open "sound slot", And configure the frequency/duration of each slot. It also appears there is only a single volume control for ALL random sounds. The various individual sounds can be found in the template files. Am I seeing this correctly so far?

Now what I haven't been able to figure out is how to select and load a sound from a template folder. The individual sound files have a .esut suffix but I can't see in LOKProgrammer how/where you select it. The place I found doesn't recognize the .esut sufficx. Again, I know I'm missing something, probably staring me right in the face.

Thanks again. Bob

[Mark R.]

I'm assuming you are using 4.0 decoders ?

Mark.

[nebrzephyr]

May 28, 2015 12:27:52 GMT -8 Mark R. said:

I'm assuming you are using 4.0 decoders ?

Mark.

Mark, it's "LOKSound Select DCC" #73900. The other one is the FOX VALLEY OEM version.

I did some more digging and found some doc that indicated that a "SOUND" icon should show. I don't see that. Can the "LOKSound Select DCC" have individual sounds added/modified. Bob

[Mark R.]

Only the V4.0 decoders allow you to add / remove / modify individual sounds. With the Selects, you are limited to the selection of sounds that come pre-loaded in each file. The "Sound" icon will show IF you are working with a V4.0 sound file.

Mark.

[nebrzephyr]

Mark.....bummer on the Select. But with this knowledge I will get 4.0 sound decoders after I move on beyond the Fox Valley GP 50M/B. Bob

[nebrzephyr]

Hope you guys don't mind a couple more questions. This concerns LOKSound Select. If I want to load a different sound file,replacing an existing file On the decoder, would i take these steps.

- reset the decoder to default values (8 in CV8)
- download the new sound file from ESU website
- load the new sound file into LOKProgrammer
- make any changes to values (lights, function mapping, etc)
- do a "write decoder data" from LOKProgrammer

When would you use the "write sound values" ? Or is this only for 4.0 decoders?

Also, unless stated otherwise in the "bulletin" for the specific sound file are the horn values always as listed in the decoder programming manual on the ESU web site?

Thanks. Bob

[Mark R.]

You don't have to reset, or do anything with the file that is currently in it, it gets over-written anyway.

- download the new sound file from ESU website
- load the new sound file into LOKProgrammer
- make any changes to values (lights, function mapping, etc)
- press "write sound data" (the icon with the musical note)

It takes about twenty minutes to half an hour to write the new file.

The horns listed in the manual are out-dated, do not rely on it for accuracy. The bulletin or additional information on the download page will be more accurate. Not every file has the same horn selections. ESU has well over thirty different horns, and since the Select can only have 16 to choose from, each file has a unique selection that would be appropriate for that engine (no five chime KLA in that Caterpilar file ! )

Mark.

[nebrzephyr]

Mark...thanks. So, the "write decoder data" would be used when simply modifying and EXISTING decoder configuration, say changing a horn selection. Correct?

I tend to think I'm a quick study on things but have to admit this LOK stuff is a little intimidating. I do think the LOK manuals sometimes leave out key steps.

Thanks again. Bob

[bnsf971]

When you open the decoder program, you should see a popup window. One of the options is to perform a complete update.

[Mark R.]

Bob - the "write decoder data" is what you use after you've made all your adjustments in the different panes. All it does is write all the proper CV changes. The "write sound data" is for writing / overwriting the entire sound file.

Mark.