[I
have bolded the "one only" above because, over the years, I have had
many owners send me a "broken" system only to open the parcel, set up
the system on my test module and find that everything worked just fine when I
pressed the ST key once. That is a very expensive way to learn that one has a
heavy finger on the key!!]
If the
LED continues to flash persistently, regardless of pressing the ST or target
key, the first step in trouble shooting is to disconnect the LZV100 completely
from the layout and place it on a workbench away from the layout.
Once
there, connect the input wires from your system power supply to the U and V
terminals on the back of the unit.
Then,
connect two wires from the J and K terminals on the back of the unit to a
length of flex track on the workbench.
Then,
plug in the cord from your LH100 or LH90 into the DIN socket on the back of the
unit.
Then,
turn on the power supply to the unit.
If the
LED is still flashing, press the ST (LH100) or Target (LH90) key once.
If the
LED stops flashing, you know that the problem is not with your Lenz system, but
somewhere on your layout.
There
may, for example, be a continuing short somewhere on the layout. There may be a
short in the latest bit of track work done, or wiring done. There may be a
crossed wire in the Xpressnet bus.
Whichever
it may be, you at least will have begun to isolate the problem. And without the
cost and bother of sending your system away and having it returned.
-
1.b .- General
System Failure: Steady or Flashing "LH100" on the LH100 display or
intermittent loss of display
An "LH100"
on the display of the LH100 or intermittent flashing of the display and loss of
ability to control locomotives with the LH100 can be due to several things.
The most
common is one or more broken wire(s) in the cable, either at the plug or at the
LH100 end. This is often a result of repeated flexing of the plug/cable in use
(usually hard or careless use).
The fix
for this is to send the unit to us to repair or replace the cable. (In years
2-10 after purchase, there will be a service charge and the cost of return
shipping.)
Alternatively,
if the owner is comfortable with voiding the warranty, the
fix is to cut off about 6 inches from the end of the cable where the break(s)
have occurred and resoldering the wires to the
LH100's pc board or the contacts in the DIN plug.
Lenz
does not recommend this approach.
There
have been very rare occasions where this problem has been caused by
condensation or oxidization of contacts on the socketed
eprom either inside the
LH100 or inside the LZV100.
Again,
the fix is to send the set into us to check out and repair as necessary.
Again,
there is an alternative, if the owner is comfortable with voiding the
warranty. The fix is to open the LH100 case, remove the micro and
reseat it. Or, to open the LZV100, remove the pc boards and remove and reseat
the eeprom on the command pcboard.
Lenz
does not recommend this approach.
1.c. - General
System Failure: ERR 03 on LH90
An "ERR
03" on the display of an LH90 in V.3.6 systems normally indicates that the
operator is attempting to set up an MU lashup without
having first taken control of a locomotive with the LH90 being used to create the
MU. The fix for this is to review your manual and follow closely the steps for
setting up an MU lashup.
On older
systems, i.e., those at pre-V3.6 software/firmware, the "ERR 03" normally
indicates that the owner/operator is attempting to use an LH90 with V.3.6 firmware
version. The only fix for this is to upgrade the system to V.3.6 or to degrade
the LH90 to pre-V.3.6 firmware.
On older
systems, i.e., the old Set-01 made up of the LZ100 and LV100/LV101, which have
been upgraded to V.3.6, the "ERR 03" can result from one of the
inherent hardware limitations of old production system components. When talking
through this problem with an owner, we found that doing a system reset (with
another LH unit) removed the "ERR 03" from his LH90.
1.d. - General
System Failure: LZ100/LV100 (or LV101) or LZV100/LV102 combination will not
control decoders
Often an
owner, on newly setting up his old LZ/LV two box system
will find that he is unable to operate a locomotives that worked either
previously or on other layouts or test tracks.
I have
now had two such instances where we have tried everything via telephone
troubleshooting and nothing has worked.
After
they sent in their systems to me, and after I had checked and verified full
functionality, the solution to the problem became obvious.
There
are three wires that connect the C, D & E terminals of the LZ unit to the
LV unit. These wires carry the command signals from the command unit to the
power unit.
What had
happened was that the owners had reversed the C & D wire connections (i.e.,
so that the C went to the D and vice versa). Reconnecting the C to the C and
the D to the D made all of the previous problems disappear.
Finally,
on one ocasion, this has proved to be the problem
when a second power section fed by an LV102 on a layout would not function.
Again, it transpired the the owner had not correctly
connected the C, D & E wires from their terminals on the back of the LZV100
to the back of the LV102
The Moral:
ALWAYS check to make sure that you have ALL your terminal
connections connected correctly.
1.e. - General
System Failure: Xpressnet - LA152 units set up in
series not working.
I have
had several owners, on installing the LA152 Faceplate/Adaptors on the fascia of
their respective layouts report to me that one or more of their LA152 units is
not working or connecting to the Xpressnet bus. The
LA152 units are very simple electronically and in 25 years, I have yet to have
one returned to me that has been defective.
In each
of these instances, after troubleshooting we have found the problem lay in the
connections between one or more of the LA152 units.
FIRST:
The
first connection from the LZV100 unit to the nearest LA152 unit should be done
with discrete wires from each of the green L, M, A &
B terminals of the LZV100 unit to the green L, M, A & B terminals of the
LA152 unit. (20 Ga. wire is fine for this, 18 Ga.
better.)
When
installing, use colour-coded wire and/or do each wire connection one at a time
in order to avoid a misconnection (e.g., L terminal to A
terminal). This kind of misconnection is one principal window for error and the
cause of many of the problems reported to me.
SECOND:
All
subsequent connections from the first LA152 unit can be made using the cable
supplied with the unit.
If you
are spacing LA152 units farther apart than the cable supplied and not using the
cable supplied or splicing the cable supplied with the LA152, this establishes
a second window for error which has been the cause of virtually all the other
problems reported to me.
These
break
down to the following:
If an
owner has used cabling to connect from one set of L, M, A & B screw
terminals to those on the next LA152, the problem has invariably been either a
misconnection or a bit of insulation interfering with proper mechanical contact
between the wire and the terminal thus interfering with electrical continuity;
If the
owner has tried splicing the cable supplied with the LA152 to make it longer,
the problem has often been that one or more of the wires has been misconnected;
Alternatively,
If an owner has made his/her own cable, a failure in
the crimping process has caused one or more of the wires in the cable not to
connect correctly to the RJ plug. Redoing the cut/crimp process has usually
fixed this.
Finally,
if an owner has made his/her own cabling, the positions of the wires in the
cable have inadvertenly been reversed, thereby
changing a patch connection to a crossover connection. Follow closely the
diagram/instructions at page 27 of the LZV100 manual (http://www.lenzusa.com/1newsite1/Manuals/LZV100V36Manual.pdf)
when making your own cable.
Section
2 - Decoders Not Programming or Running properly
(As a preface, let me apologize: I had understood that software
V.3.6 had addressed the problem some owners of non-NMRA-Standard-Conforming
decoders had experienced because the Lenz programming track mode does not
provide sufficient voltage for their high-current-draw decoders. I have just
learned today (July 12, 2017) that is incorrect.)
Some owners may not be aware that some Soundtraxx,
Tsunami, and most QSI, Digitrax, Broadway Limited and
other non-NMRA-standard-conforming spound decoders
require a higher programming voltage on the programming track than the NMRA
standard specifies. This is because of significant capacitance and other
elements of their decoder circuitry.
For Lenz Digital Plus system owners to be able to program these
decoders, it is necessary to raise the voltage output to the programming track.
One way to do this is to buy a programming track power booster from any of a
number of commercial sources.
The least expensive way of accomplishing the same thing,
however, is to wire in series on either the P or Q wires to the programming
track a 10 Ohm, 1 Watt Resistor. These resistors should be
available cheaply from places like Radio Shack or any electronic parts supply
house, or perhaps even a stereo/electronic repair shop.
I have had one wired into my different test modules since the
mid 1990's and have never not been able to program an other manufacturer's decoder.
2.a. - Decoder
Incompatibility with the Lenz Railcom Capability
In
V.3.6, the current Lenz system software version, the default setting has Railcom capability turned ON.
Many
currently available decoders from other manufacturers do not conform completely
to the NMRA DCC standard and will not work properly in an environment that has
the Railcom capability turned on.
In order
to operate such non-conforming decoders in the Lenz system, it is necessary to
turn off the system's Railcom capability. I have put
together a couple of step by step guides that may help owners to do this on
their own:
2.a.1 Turning off Railcom with the LH100: Step-by-Step [Click Here]
2.a.2 Turning off Railcom with the LH90 Step-by-Step [Click Here]
-
2.b. - Decoder
Programming with the LH100 - A Step by Step Guide
Some
users have found the Set 100 and LH100 manual difficult to follow (or have
never tried to follow it) where programming decoders to new addresses are
concerned.
Click here
to go to a Step-by-Step guide.
2.c. - LE103XF
Decoder & Digitrax
In
August 2013, Ron Ruyg asked why his LE103XF decoder
would not work on Digitrax (&NCE) systems.
The
answer is that the LE103XF (which has been out of production since 1999) was
not designed to work on systems set to 128 speed steps.
The
LE103XF, first produced about 1996, only supports 14-27 and 28-55 speed steps.
2.d. - ESU sound
decoders - Problems with Programming Decoders and Functions not performing
properly in the Lenz System
In
July-August 2014, Dewey Jones found he was not able to control the sound
functions, specifically the diesel horn (F2), with his newly repaired Lenz Set
100.
The horn
sound was intermittent, though other sounds seemed to work fine most of the
time.
After
several go rounds with us, with his decoder installers and with the ESU folks
(I think), someone hit on the solution of hitting the 8 key on his LH100
several times while the locomotive was in idle mode in order to reset the sound
CVs in the decoder.
That
seems to have taken care of the intermittent horn sound for him.
William Seabrooke had a problem in May 2015 programming an address
into his new Rapido GMD-1 equipped with, he told me,
an ESU sound/motion decoder. We went through the programming sequence several
times with everything seeming to work as it should, only to find that when put
on the running track, the locomotive was totally non-responsive. I suggested
that the fix above be tried. Again to no avail.
However,
I had him take the locomotive off the track and then put it back on. Lo and
behold, everything worked as it should at the newly programmed address.
So,
something else to try. (I'm not making these things up.)
2.e. - Problems with
Digitrax, Broadway Limited and Other Non-NMRA
Conforming Decoders
Broadway
Limited, MTH, Digitrax and other manufacturers
produce and sell decoders or locomotives equipped with decoders that do not
conform to the NMRA DCC Standard.
This may
cause ERR 02 messages when an owner tries to program such decoders on a Lenz
(fully NMRA-Standard conforming) DCC system. This is due to the fact that
programming such decoders commonly draws more current/voltage than the system
is designed to provide on the programming track (i.e., the P & Q terminals
of an LZV100).
There is
a work-around that often allows Lenz owners to program such
Decoders/Locomotives.
The
first step is to program, on your programming track, a Lenz or other decoder
which can be programmed without ERR readings to the Address and other CV
setting you wish to put into the problem decoder.
After
doing this, you should read and note down the CV values of the decoder for the
things you have programmed. For instance, the CVs to read for a four digit
address are CV17, CV18 and CV29.
Once you
have done this, you should put the problem locomotive on a running track or
jumper the problem decoder's red and black wires to to
a running track.
The
default address for any new decoder is supposed to be 03. Call up Address 03 on
your LH100 or LH90 and see if the locomotive/decoder responds.
If it
does not respond, then you will have to contact the manufacturer or whomever
you bought it from to determine what address is in the locomotive/decoder.
Assuming
the locomotive/decoder responds, you should go into Programming On the Main (POM) programming mode with your controller.
Once in
POM, enter the values into all of the CVs which you noted when reading them in
the step above.
Once you
are finished enter all the new CV values, escape out of POM.
Bring up
the address which you have programmed into the locomotive/decoder and see if it
responds at that new address.
If
it does, all well and good.
If it
does not, you may have to repeat the POM operations with an LH90. About 15
years ago, I had one owner for who this would work only with the LH90, not the
LH100. I have no explanation for that.)
If it
still does not, then you will have to contact the manufacturer of the
locomotive/decoder for support.
Broadway
Limited Locomotive with "Lenz Sound Decoder"
George
Campbell reported a problem he experienced with a locomotive he had bought
which had had installed what was called a "Lenz Sound Decoder". His
locomotive would run but back and forth but did not have any operable sounds on
his Digitraxx DCC system.
After
several hours and go-rounds with me, Broadway Limited and Digitrax,
he discovered that:
(a) his locomotive had a Lenz decoder installed in tandem with a
BL "Paragon One" sound decoder,
(b) this is a problem known to the BL folks,
(c) that
while the fix above will, apparently, work with "Paragon Two" and "Paragon
Three" sound decoders, that there is no known fix for the "Paragon One"
other than to have it replaced with a more recent production version, by
Broadway Limited.
So,
apparently the only way to avoid this specific problem is to avoid buying a
model with the problematic (Non-NMRA-Standard-conforming)
decoder.
["Compatible
with" does not mean the same thing as "Conform to".]
3.
Problems with the LI-USB/Ethernet (Lenz P/N 23151) Computer Interface
3.a. Windows 7 &
Windows 8 Drivers
In the software
supplied with the old LI-USB, the device driver may not always set up properly in
64 bit computers.
While I
am happy to provide a new installation disk file with bug-free software that
should (fingers crossed) fix the problem, it may be necessary to install
another driver.
The
following URL will provide you with that driver for Windows 7, as well as
comments from some not so happy Lenz system owners:
http://www.bahnfan.net/post/2010/04/25/64-bit-drivers-for-Lenz-LI-USB-on-Windows-7
The
following URL will provide you with that driver for Windows 8:
http://www.bahnfan.net/post/2013/01/25/Lenz-LI-USB-64-bit-drivers-for-Windows-8
With
thanks to Søren Jacob Lauritsen
for his work, I hope this may get you running your LI-USB.
* * *
The
following website: http://www.ftdichip.com/Drivers/VCP.htm,
appears to offer drivers for Windows 10 for the the 23150.
Please visit it if nothing else works in getting your LI-USB functioning
correctly.
3.a. Windows 10
Drivers & Problems after W10's Periodic Updates
There
has been repeated discussion of problems with W10 drivers for the LI-USB and
problems that occur after W10's periodic updates. Apparently, the later problem
arises from W10s requirements for signed drivers and from the periodic updates
wiping out of previously installed drivers. I don't pretend to understand this.
Thanks,
however, to Gus Hollbusch (I think I have that
correct) who has today (2017-12-03) put up a link that offers step by step help
on getting the 23150 running again, and also fo providing
a file with drivers.
The link
he has provided is as follows: https://1drv.ms/f/s!Ai0rg99dWaBgkcli2DzwQjvzlulszw.
(If you Click Here, you should be taken to his page.)
* * *
The
following website: http://www.ftdichip.com/Drivers/VCP.htm,
at one point appeared to offer drivers for Windows 10 for the 23150. I am not sure
if it is still functional.
4.
Problems with the LI-USB/Ethernet (Lenz P/N 23151) Computer Interface
4.a. - Touchcab/IPhone Set Up
Most
often in the past, problems getting the 23151 unit working
properly has proved to stem from one of two issues:
First, there is
sometimes a software switch or setting either in one's computer firmware or
one's application that incorrectly set. This can be devilishly hard to find
because the internals of computers differ and the setting concerned is often
well hidden and/or poorly documented.
If this is
the case, only very patient, careful trouble shooting is the answer. That, or hiring a computer engineer or a 15 year old
computer whiz-kid to find the incorrectly set switch.
I am
not, unfortunately, either, so I cannot help much other than to commiserate.
The second
issue is, however, much easier to handle because it boils down to the IP
address of the LAN/Wireless Router being set so that it is incompatible with
the hardware address of the 23151 unit.
The TouchCab developer has published a wondrously clear way to
fix this. It is (or was when this was written) located at the following URL: http://www.touchcab.com/forum/viewtopic.php?f=7&t=443.
If, there is any difficulty in connecting to that URL, I have copied the article
and it can be reached by clicking here.
4.b. - Touchcab/IPhone Operation
Steve Sansome of Belleville, Ontario got his interface set up
properly and found that the Iphone/Interface
communication seemed to work but he was not getting any response from the
locomotives on his layout.
Troubleshooting
confirmed that the 23151 was properly connected into the Xpressnet.
Every time he pressed a function key or changed speed or direction, the signal
light on the interface blinked. His LH90 connected to the Xpressnet
controlled locomotives properly. So did his LH100.
But no
command signals were getting from the 23151 to the LZV100.
There
seemed clearly to be a hardware problem: Either in the 23151/Xpressnet wiring or RJ plugs/sockets. I had him check all
the hardware and the wiring and he confirmed there was full continuity on each
line and at each end of the connection.
Then,
after telling him to pack it up and bring it into TLA so we could check it on
our test module, I asked - almost by the by - whether his LH100 was plugged
directly into the LZV100 or into one of the Xpressnet's
LA152 faceplate interfaces.
He had
it plugged into the DIN socket at the back of the LZV100.
As Gru would say: "Light Bulb!".
I asked him to disconnect the LH100 from the LZV100's DIN socket and plug it
into one of the LA152s.
!Bingo! Everything
worked properly.
Don't
ask me why, but IF you have your Xpressnet wire-connected
to the LMAB terminals at the back of the LZV100 AND you have a controller
plugged into the DIN socket at the back of the LZV100, THEN it
appears that the full Xpressnet functioning may be impaired.
Solution:
DO NOT/NOT
plug an LH90 or LH100 into the back of the LZV100 if you have
other Xpressnet devices connected to the Xpressnet.
4.c. - Android Apps
comparable to the Touchcab/IPhone
Link Up
Several
people have asked me about this. I have not tried nor checked it, but there
appears to be an Android App calle RC-Cab that claims
to work with the Lenz system.
If anyone
has tried out and has a working knowledge of this App - or, indeed, any other App,
it would be interesting to hear about his/her experience..
4.d. - Windows 7 64 bit
machines
Several
Owners of the 23151 interface have had different problems setting up their
software and getting it operating correctly.
If
,
despite repeated attempts at installing the software using the disk supplied
with the 23151, it may be necessary to contact me for the latest files which I
have from Lenz Germany.
If you
go to the Lenz File Page, you will see
several of the files that I have been able to put up for downloading.
4.e. - Faulty connection
to the Xpressnet/LA152
Bill Seabrooke encountered weeks of frustration, trying to
connect the 23151 to his LA152. Every time he connected it as well as his LH100
to the LA152, the display on the LH100 would read "LH100", i.e.,
short or no continuity.
When he
had the LH100 only connected, everything worked fine. When he had the 23151
only connected, everything appeared to be fine.
It was
only when he sent the LA152 and the 23151 and the cables he was using to me
that the source of the problem became clear.
He was
not using the cable provided with the 23151 to connect to the LA152. he was using commercially available telephone cabling with
RJ11 plugs to do his connection.
When I
cut off one of the plugs, reversed the order of the four wires in a new RJ plug
and and crimped it, everything worked properly
together.
4.e. – Changing
the IP Address of the LI-USB/LAN (p/n 23151)
The following is courtesy of Brian Williams of Belleville, Ontario,
who did all of the work and the writing:
"Lenz offers a couple of
devices to enable a personal computer (any flavour) to connect to Xpressnet. I chose the Ethernet interface (23151) for a couple
of reasons. The first was that I didn’t want my layout to be hard-wire
tethered to a specific computer, which a USB or an RS-232 connection would
require. My choice of the Ethernet interface allows any computer on my LAN,
including Wi-Fi-capable tablets and phones to connect.
"The second reason that I chose the Ethernet interface is that with one
additional non-Lenz device, I didn’t have to have my layout hard-wire
tethered at all. I effectively have my Xpressnet set
up as a Wi-Fi client connecting wirelessly to my LAN.
"A look first at the 23151 and getting it on the household LAN, or a
separate LAN as one might desire.
"The 23151 requires
power, so the first step is to connect the interface to Xpressnet.
Using the cable that came with the 23151, I simply plugged mine into one of the
RJ-25 (6 pin) sockets on the back of my LA152 Adapter (which extends both the
throttle connection and the Xpressnet connection to
the perimeter of my layout). The red LED on the 23151 will glow if layout power
is on.
"The 23151 comes with its IP address set to 192.168.0.200
"This is where we deviate from the instructions found in the manual.
"Using a standard Ethernet cable, connect the 23151 to your LAN at any
Ethernet switch in the LAN. The 23151 won’t yet be recognized by anything
(unless your LAN is using subnet 192.168.0.x.). At this point you should know
something about your LAN, such as what is the actual subnet (I use
192,168.110.x). Another aspect is whether or not you have enabled DHCP on your
router. There are many reasons not to do so, but it is a personal choice.
Without DHCP, each network device would be manually configured and assigned a
unique IP address. This is referred to as a static address.
"Now is decision time. Will you be assigning a static IP address, and if
so, what will it be? If going with
DHCP, be aware that the IP address is dynamic and may well change any time that
the layout power is turned off and on.
"Why might knowing the
IP address of the 23151 be important? Because whatever software you choose to
use may require you to specify the IP address of the 23151 to which you want to
connect. In other words, your model railroad software needs to know how to
connect to Xpressnet, and the IP address is key. This could mean that, upon powering up the layout, you
may have to seek out the new IP address and edit the parameters of your
railroad operating application accordingly. (Assigning a static IP address
saves a lot of headaches, and it is a practice that should apply to all devices
on your LAN. There are many benefits.)
"The 23151 has an on-board web server to enable reconfiguration as
desired. The manual offers couple of processes by which one can connect to the
23151 and reach that web server. Using whichever computer you want on your LAN,
create a new (temporary) network configuration for that computer. Give it
address 192.168.0.100. Set the router address to 192.168.0.1, and the subnet
mask to 255.255.255.0. If your computer requires that a DNS address also be
assigned, make it the same as the router address (192.168.0.1). Now make you
computer active on that network configuration.
"In your browser. enter http://192.168.0.200 (return) and the web
server for your 23151 should appear. In the upper right corner, a Union Jack
should appear. Clicking on that will change the language of the web page to
English.
"If you have decided to use DHCP, and your router supports that, read to
the end of this paragraph before proceeding. When one checks
the DHCP box and "Save", the web page will disappear, which can be a
problem unless you have some means of discovering the newly assigned IP
address. It will be an address (on your LAN) to which your computer is not
currently connected. Revert back to your regular network configuration and
rejoin your LAN. The manual instructions for macOS
are out of date and will not work to find the new IP address. I cannot advise on Windows or other OS. So what to do? It is far better
to know what the IP address will be, and assigning it as a static address.
"If you intend to assign a static address, enter the address, the subnet
mask, the router (Gateway) address. Click on "Save". The web page
will then disappear. It is, nonetheless, on your LAN, to which your computer is
not currently connected. Revert back to your regular network configuration and
rejoin you LAN. Try http:// (the IP address that you assigned). You should
reach the 23151’s server. If not immediately, try again in a few moments.
"…..
"Earlier I wrote "The second reason that I chose the Ethernet
interface is that with one additional non-Lenz device, I didn’t have to
have my layout hard-wire tethered at all. I effectively have my Xpressnet set up as a Wi-Fi client connecting wirelessly to
my LAN.” How did I do that?
"I took one of my spare Airport Express devices and configured it to join
an existing wireless network (that being the Wi-Fi part of my LAN, to which my
mobile devices connect). The Airport Express also has Ethernet ports, through
which the LAN can be extended. The Airport Express is on my layout, and the
23151 Ethernet connection is to the Airport Express
Ethernet port.
"That’s it. My
23151 is attached to my LAN, and I can use JMRI DecoderPro
main desktop computer to run my train, as I can also do so on my Wi-Fi
connected laptop computers. I have also succeeded in having an iPad app WiThrottle (Lite) control my train through JMRI (which is running
on my desktop machine)."
5.
Computer Program Design for the LI-101F and the LI-USB
We
received the following request from Graham Plowman in 2011:
We
received the following advice from Lenz Germany:
If
your program is designed to send successive requests to the Lenz system, those
should be set up sequentially, i.e., one after the other.
After
each command is sent to the Interface, your program should be designed to wait
until the interface has repeated 0x01 0x04 0x05 (for the LI-101F) or 0x255
0x254 0x01 0x04 0x05 (for the LI-USB) before sending the next command.
The
program needs to check for that response to the previous command before the
next new command may be sent.
6.
Programming Lenz Components with Other DCC systems
6.a. - Programming
the LS110 with Digitraxx
In April
2013, Joe Montenigro sought help with programming the
LS110 stationary decoder. After some head scratching and advice from Lenz
Germany, he reported the following:
"I
connected the LS110 to my Digitrax programming track
and selected "Page Direct" programming mode.
"I'm
happy to report success in reading and reprogramming CV values for the LS110
address and for decoder operation settings. (Note: in the Digitrax
system, you can't see that you're programming CV1; the system displays "AD2".
I happen to be a geek, and knew this tidbit. Otherwise, I might not have known how
to access "CV 1".)
"Following
the Lenz instruction manual, I rigged up pairs of LEDs with dropping resistors,
set the decoder to 32 for "constant" operation, and watched the LEDs
alternate as I hit "throw" and "close".
"Thus
enboldened, I connected a PECO twin coil motor, and
was able to throw and close it as well.
"So,
all is working fine, and I have a much better feel for tackling more complex
connections as described in the manual.
I like
the LS110 and look forward to permanently installing several on my layout.
Summary: programming the LS110 on a Digitrax system
is straightforward and easy, just like any other decoder."
7.
System Components - Mechanical, Electrical, Technical Information
7.a. LH100 - Cable
Wire Colour Coding
Some
owners have undertaken to replace their LH100 cables or the DIN plugs on the
LH100 cables.
This is
not rocket science, but some have asked about the colour coding of the wires,
just to be sure.
This is
wise: A crossed or incorrect connection could damage the LH100, the LZV100 or
both.
The
following is the wire colour coding for the two most used cables:
The
standard Lenz uncoiled cable with the straight DIN plug
and
The NCE
coiled cable with the L-shaped DIN plug.
Cable
Wire Colour Coding
|
Terminal
|
Lenz
Cable
|
NCE
Cable
|
|
L
|
Yellow
|
Yellow
|
|
M
|
Brown
|
Black
|
|
A
|
Green
|
Green
|
|
B
|
White
|
Red
|
-
7.b - Lenz Decoder Programmer
p/n 23270 (V.1) Documentation
At least
one person has asked whether he manuals for the Lenz
Decoder Programmer V.1 (p/n 23270) are available in
English. I have asked Lenz Germany and they are, apparently available only in
German.
Benjamin
Lanza, an owner of the 23270, has done a translation
of the ley parts of the manual and has very
generously agreed to let me pmake it available here
to share it with others.
To open
the .pdf file with Ben's translation, please click here.
-
7.c - Changing the
Output Voltage on the LZV100
William
Moore called for some help in clarifying how to change the output voltage on
his LZV100.
After
doing it successfully, he was kind enough to send along step by step
instructions for any others who may find the Lenz Manual somewhat unclear on
the procedure.
This
entails changing the value of CV7 in the programming software which resides in
the LZV100.
Use the
LH100 Keypad Dispatcher’s Throttle.
1. Use
Programming on the Main (POM) mode just as though you would if you were going
to program a locomotive decoder on the Main. You do not have to specify an
address.
2. Press
the "F" key then the "7" key (to get yourself into POM
mode).
3. Press
the "Enter" key and when "CV" shows is on the display,
press "Enter" again. "CV*" should show on the display.
4. Press
"7" and "Enter". "C7*" should appear on the
display.
5. Press
the "5"and then the "0" key, then press "Enter".
The red LED on the front of LZV100 should begin to flash.
6. WHILE
the LED is flashing, pres the "ESC" key ONCE. "C7*" should
be on the display.
7. WHILE
the LED is still flashing, enter the value (from the Manual's Table) of the
output voltage that you want. For example, for an output setting of 15 volts,
enter the value 30 by pressing the "3" key, then the "0" key
and then "Enter"
REMEMBER,
this must be done while the LED is flashing. The LED will
flash for approximately a 20 sec. interval once you complete step 5 above.
8. Press
"ESC" after you have entered the value for the output you want. Then,
press "ESC" again until you are completely out of POM programming
mode.
The
Table in section 7.4 of the LZV100 manual gives the values that CV7 must be set
to for various output voltages.
A
Word of Caution:
While the
LZV100 is designed to manage overload conditions, owners
shoud be aware that whenever it is set to reduce the
output voltage significantly below the input voltage, the circuitry of the unit
will be forced to try to dissipate the heat created by the voltage reduction.
This is
because the only way to reduce voltage is essentially to burn off the excess
voltage. This adds to the current draw on the LZV unit.
In
normal operation, with most model railroad input power supplies in the 15-16
volt range, this will not cause a problem.
I have,
however, had one or two owners (both running an "O"
or larger scale layout) who ran into significant overheating problems
lowering an 18-22 volt input to 16 volts or less output. For them the internal
heat sink of the LZV100 was insufficient and they had to remove the front and
back plates to increase air flow. In one case, the owner had to rig up a
computer fan to get the best perfomance from his
unit.
-
7.d – Changing the Display Language on
the LH101
There
does not appear to be any clear indication in the English documentation for the
LH101 on how to change the display language from German to English (ou au Français).
Andy
Chisholm found the way to do this after playing with his new LH101 for a bit
when he got it home and was kind enough to pass on the following steps:
1. Press the "M"
key.
2. Turn the knob
until "Setup LH101" appears on the display.
3. Press the knob
once.
4. Turn the knob
until "Sprachauswahl" appears on the
display.
5. Press the knob
once.
6. Turn the knob
until "English" (ou "Français") appears on the display.
7. Press the knob
once.
8. Press "ESC"
All indications
on the display should now be in English. (Ou Français, si vous l'avez choissi) .
-
7.e – Firmware Upgrades to the LH101
The
first releases of the LH101 were at firmware version 1.02. Lenz has released firmware version 2.0
for the controller which can be done using a W10 computer with USB ports and a
special USB/RJ cable which I am able to provide at a nominal charge to owners.
It
took me a bit of experimentation to get the process right, but it is not really
difficult. The step-by-step
procedure is as follows.
A. Preparation for Updating:
(1)
Install the V.1.5 CV Editor.
(If
you don't have it you can download it from the Lenz Files page on this site or
from the Lenz Germany Website.)
Go
with the Default installation.
If
you are lucky all the correct drivers will install on your computer.
(2)
Open the CV Editor by clicking on the Icon now installed on your Desktop.
Select
English (the Union Jack icon at the top right of the application) as the
language.
(It
may be necessary to close the program and restart it to proceed further in
English.)
(3)
In the CV Editor, go to the “Setup” page/tab.
(4)
In that Window, click on the box that says “LH101 Update”
(5)
In the Window that pops up, look for the blank box that has “Update
file” to the LEFT of it.
Click
on the little box to the RIGHT of it to see where the CV Editor program will
look for Update files.
On
my computer this directory was “/Documents/Lenz/LH Firmware”.
(6)
Exit the program. Then, using your
File Explorer, copy the current LH101 V.2 Upgrade hex file
from wherever you have it (USB stick or Download) to the
directory you noted above.
(At
time of writing “LH101_V200_B1066.hex” is the correct upgrade file.)
B. Updating an LH101:
(1)
Open the CV Editor from the icon on your Desktop and go to the
“Setup” page/tab.
(2)
Plug the update cable ONLY (i.e., WITHOUT the LH101 connected to the other end)
into a USB port on the computer.
(3)
Hold down the knob on the LH101 and, while holding it down, insert the RJ
connector into the controller.
On
the display of the LH101, it should read “neues
LH101-Prgm vom PC senden!”
(“Send
new LH101 program from computer”)
(4)
In the CV Editor, click on the LH101 Update Box.
(5)
In the Window that pops up, look for the blank box at the top, to the left of
“Port”.
From
the pull-down menu in that box, select the USB Port to which the LH101 has
connected.
(It
will look completely different from all the 254 possible other COM ports.)
(6)
In the next blank box, select the current update file
(“LH101_V200_B1066.hex” at writing).
In
the big white box below, you should get a “Read successful”
message.
(7)
Click on the “Connect” box
You
will see the narrow rectangular box beneath the big white box begin to fill up
from left to right.
(8)
Wait until that box is full and you get a message in the big white box that the
update was successful.
(9)
Click on the smaller rectangular box “Schliessen”
in the lower right hand corner of the popup in order to close the operation.
(10)
Disconnect the cable from the controller and the computer and you are all done.
Your
LH101 will display its current version.
This page updated November 29, 2019
Home | Lenz DCC page| Lenz Warranty
and Uprgade Information | Lenz File Page