|
|
Post by fr8kar on Jun 20, 2020 10:30:19 GMT -8
I'm in HO scale and I've been adding sound equipped models to my roster over the past couple years. So far the majority are ScaleTrains models with LokSound, but I also have a couple Genesis models with Tsunami and Tsunami2 decoders.
When I operate it's on a Free-mo layout running Digitrax or on my own modules at home using a Digitrax Zephyr. Over the past several years I've been using the Zephyr to edit CV values on my non-sound decoders, most of which are NCE DA-SR or D13J. That process is pretty simple and I don't get too deep into modifying values beyond Acceleration, Deceleration, Address and lighting functions.
I have dabbled in the past week with modifying some CV values on the Tsunami decoders but it's pretty tedious and not very practical for editing sounds. The LokSound decoders as well as the LokPilot decoders are really beyond my abilities to edit other than the address.
So from what I've learned I need a LokProgrammer and a PC to modify the values of the Loksound decoders. The interface looks like it's easy to use and it opens up a lot of options. But it seems this won't help me when it comes to editing values in the Tsunami or other decoders I'm using.
For anything other than Loksound decoders it looks like I'll need JMRI, a PC and an interface of some kind. This is where I need help.
I have a PC, the Digitrax Zephyr and I have a programming track. Besides the LokProgrammer, what hardware is required to get JMRI to communicate with decoders from any brand other than ESU? Does the the LokProgrammer work with JMRI? Do I have to unplug one to use the other or can both be connected to the programming track at the same time?
|
|
|
|
Post by Christian on Jun 20, 2020 14:20:50 GMT -8
I use JMRI connected to my computer through the USB connection on my Zephyr. It works on my loc decoder (single) just fine all the way through the CV's in two hundreds. BUT - I can't upload sound files to the decoder. As for the computer connection - Digitrax sells a standalone USB computer connection if your Zephyr is too old. I'd suggest getting a new Zephyr because there are lots of other improvements and you already know the interface. eBay is your friend.
|
|
|
|
Post by ncrc5315 on Jun 20, 2020 16:18:16 GMT -8
I have the Lok programmer, and it does make programming the ESu decoders easy. Having said that, the Zephyr connected to a PC, with JMRI will do the same thing, and I don't think you would need the Lok programmer.
|
|
|
|
Post by fr8kar on Jun 20, 2020 16:29:38 GMT -8
My Zephyr must be pretty old! No USB connection on it. I see what you mean about the updated interface and it including the USB port compared to my old one and adding the USB connection. It's really not a bad price to just get a new Zephyr.
I think I'm going to need the LokProgrammer just because of some of the things I want to do with the Loksound decoders in my ScaleTrains models (first thing is separating the number lights from the sound on/off switch!).
|
|
|
|
Post by Colin 't Hart on Jun 21, 2020 0:20:07 GMT -8
To answer a few of your explicit questions: 2. The LokProgrammer cannot be used with JMRI. 3. Only 1 programming device can be connected to your track at a time, so you should have a way to easily switch between them if you have more than one. This is recommended anyway if using Digitrax because you will want to be able to connect the normal DCC track output to your programming/test track so you can quickly test locomotives. And your first question: You need an interface between your computer and your DCC system. The newest Digitrax Zephyr (the Zephyr Express, model number DCS52) has a USB interface built in, as does their top-of-the-range command station the DCS240, but you can also buy a USB interface separately from Digitrax or RR-Cirkits. A LokProgrammer can be used to program CVs on other manufacturers' decoders, however there's no hand-holding like there is in JMRI or like there is in the LokProgrammer software when programming ESU decoders. You need to know exactly which CV and value to change. So it can be used in a pinch but it's only marginally better than using the Zephyr (less tedious in data entry) so in the long-run you will almost certainly want to have an interface that works with JMRI. I'd recommend getting the LokProgrammer first. It will allow you to program all of your ESU-equipped locomotives -- from minor tweaking to complete replacement of sound files -- while also allowing you to change CVs in other manufacturers' decoders. The LokProgrammer has a built-in software throttle which allows you to test your locomotives without having to move them to a different track or change output to your programming/test track (like the Digitrax Zephyr does).
Something else I highly recommend if you don't already have one is a rolling road. I have and recommend the following set which you can place on your existing programming/test track: |
|
|
|
Post by nsc39d8 on Jun 21, 2020 4:13:40 GMT -8
Ryan,
I agree with all the above comments and will add a few. When you purchase the Lokprogrammer go ahead and get the decoder tester as well. While the tester means the decoder must be out of the model it does help in that all the functions you want can be tested first right after programming, really helpful on new installs. The Lokprogrammer will also help in doing firmware updates on decoders and I have found it can, on occasions, revive a brain dead decoder. Plus you can go in and design you own sound files.
I have just recently started using JMRI Decoder Pro. I use a Sprog II v4 it even comes with a USB drive with DecoderPro on it. Nice thing is the Sprog can also be used as a stand alone DCC command station, might be nice for one of those modules you have.
|
|
|
|
Post by nebrzephyr on Jun 21, 2020 7:54:32 GMT -8
I have used various decoders (NCE, TCS, etc) for many years before I ever heard of ESU. And for those I used a Digitrax system and a LocoBuffer. Years ago it was a serial interface but now USB. And for software I used JMRI. When I started using ESU products I purchased the ESU Tester and programmer. Since I have a need to continue using JMRI and ESU I set up two stub end yard tracks that I can switch between mainline power OR programming track. I use DPDT, center off toggle. Bob [  |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 21, 2020 14:17:02 GMT -8
You can download the esu look programmer software for free. It has a feature where you can list changed CVs, so you make your changes with a GUI but then can program them with JMRI or a zypher. It's a little tedious, but will save you $100 if you only rarely need to edit your ESU decoders.
|
|
|
|
Post by Colin 't Hart on Jun 21, 2020 23:09:39 GMT -8
|
|
|
|
Post by kentuckysouthernrwy on Jun 22, 2020 3:09:52 GMT -8
I have NCE. I have a stand alone 3' programming track mounted on a board with the Lokprogrammer and a NCE Powercab just for dcc programming totally separate from my layout. It attaches by USB to my computer, laptop or desktop, and works well for me.
|
|
|
|
Post by fr8kar on Jun 22, 2020 13:54:01 GMT -8
I have NCE. I have a stand alone 3' programming track mounted on a board with the Lokprogrammer and a NCE Powercab just for dcc programming totally separate from my layout. It attaches by USB to my computer, laptop or desktop, and works well for me. Because of Free-mo I'm stuck with Digitrax. All I have are Free-mo modules and no chance for a layout otherwise. Free-mo uses Digitrax exclusively so I don't want to buy a duplicate system. |
|
|
|
Post by sp8234tim on Jun 28, 2020 6:53:23 GMT -8
I use JMRI/Sprog ( www.sprog.us.com/ ) & would not be in the hobby without these. I can change any CV I would like to do with Soundtraks, ESU/Lolsound (not upload files), TCS, Broadway, Etc. I also have an Lokprogramer that I am learning to use. I would like a list of CV #, just haven't spent that much time to look for it. I find it easier to change Loksound with JMRI at this point but friend say its easier with a Lokprogramer. I have more expernce messing with Soundtraks them Loksound & I like Loksound better then Soundtraks because of the EMD Dynamic Brake noise that comes from (buzz) Soundtrak, Loksound nailed it Both clubs I belong to use Digitrax. I model 1990s to about 2005 western stuff, SP, UP & BNSF. Tim Hanesworth |
|
|
|
Post by Colin 't Hart on Jun 29, 2020 1:27:23 GMT -8
I also have an Lokprogramer that I am learning to use. I would like a list of CV #, just haven't spent that much time to look for it. Tools -> Program settings... -> General settings (default page) -> Show CV numbers (3rd down from the top) |
|
|
|
Post by Colin 't Hart on Jul 1, 2020 0:35:16 GMT -8
I also have an Lokprogramer that I am learning to use. I would like a list of CV #, just haven't spent that much time to look for it. Tools -> Program settings... -> General settings (default page) -> Show CV numbers (3rd down from the top) This is actually most interesting for those folks that don't have a physical LokProgrammer device but want to adjust the CVs in their ESU-equipped locomotives using another system (JMRI or even via direct entry using their DCC system's keypad). Simply install the LokProgrammer software. If modding a locomotive and decoder combination for which the exact project is available on the ESU site, download that project and open it in the software. If it's a LokPilot or the project isn't available, create a new project in the software for the correct decoder type. From there you can start adjusting values and it will display which CVs to change, and what to change them to. NB You won't be able to change sounds with this, though you can choose eg a different horn. |
|
|
|
Post by petergoff on Apr 24, 2022 12:51:42 GMT -8
The malfunction of the hard disk is a common reason for the incorrect works of such software. Moreover, this is one of the most difficult problems. Firstly you need to check the correct connection to SATA. I faced such a problem one week ago. The main software has not been running on my computer for a long time. Therefore, I decided to make raid configurations. Btw, you should also check the BIOS settings. You may need to select additional functions as the disk type in older versions. The sections of it should be also correct. |
|
