LokProgrammer v 5.1.7 Released

ESU LokSound has released v5.1.7 software for the LokProgrammer. If you have Check for new updates selected you will be automatically notified of the update and given the option to download and install it. If you do not have this selected you can enable it by clicking on the Tools/Program Settings menu and checking Check for update on startup.

The abbreviated list of updates is as follows:

New Firmware 5.6.142 for LokSound 5 / LokPilot 5 family: new CV 122 Bit 4 in general output settings enforces the slave communication at AUX3, AUX4.

<Author's Note>

From ESU:

This is just important for ESU locomotives with an I/O expander chip on the mainboard. In all other cases, this bit does not need to be set at all.

It is just for compatibility with some older ESU locomotives (such as BR151) that have been equipped with LokSound V4.0 first, and that need to be upgraded to V5 decoder…

• SignalPilot: new SBB L Main signal Halt/FB1/FB2/FB3/FB4/FB5/FB6/Hilfssignal N/Rot/Ersatzrot Signal.

• Bugfixes: LokSound 5 / LokPilot 5 family: Physical output configuration showed mapped outputs in gray by mistake occasionally.
  
  

---

• If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it.

Even If It's Just The Lights!

The author recently installed a Soundtraxx Economi PnP decoder into an Atlas (Kato drive) GP9. No problems getting it to fit (after modifying the light tubes). The speaker fit well to the roof of the long hood and there was even room for a Train Control Systems KA1 keep-alive. Sound and movement tests all checked out.

Now for the lights, for the last year the author has used SMD micro-LEDs for the headlight and reverse light. These are so small that they can be fitted anywhere including the small ditch light holders on the front sill of the locomotive. Some types of these LEDs come pre-equipped with 1 k Ω shrink wrapped resistors which makes for less work. They are not that expensive either, usually less than $1 apiece.

Back to the lights, the LEDs were hooked up to the decoder lighting outputs via standard jumper cables (sets are available at Radio Shack) for testing. No joy! Every combination of polarity, with/without a resistor and anything else possible was tried. Still no lights. This is a first. The author has never had a problem with Soundtraxx decoders before, why now. 

So, resigned to removing the decoder and sending it back to Soundtraxx, the removal process was start...WAIT A MINUTE!!! A while back there was a new decoder being worked on that was virtually dead. Remembering you should always factory reset a new decoder, the author reset it and it came back from the dead and worked perfectly after that. Let's try that on this one, VOILA!! LIGHTS!! and everything else also.

Note to self: Even if it's just the lights, factory reset a new decoder.

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it.

Java Upgrade for JMRI

After the 4.26 production release of JMRI (which should happen very soon since it's now at 4.25.8) the developers will require you to upgrade Java to version 11. Azul Software's JRE is one of the recommended upgrade packages. This is based on the OpenJDK software and includes choices for both a JDK (software development kit) and a JRE (runtime environment). The vast majority of users will only need the JRE.

It is available on the Azul downloads page. You can select Java Version, Operating System, Architecture and Package to install . An example is shown in Fig 1. The developers also recommend that you do not install a version higher than v11 since JMRI has not been tested with those versions. Windows users should select the "JRE" and the ".msi" package. This is the auto-installer. 

Fig 1 Azul selections

The author has had this Java version installed for some time now and has encountered no problems. It also appears to be slightly faster than the Oracle version.

<CAUTION!>

It is recommended to completely remove your current Java version before performing the upgrade. Some people have had strange results if they do not. If you are using Oracle's Java they have a tool to remove it completely, It is located here.

---

If you have an idea for a blog post here, let me know. If I can comment on it, I will or I'll see if someone else can and post it.