/
index.shtml
1175 lines (924 loc) · 47.7 KB
/
index.shtml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html lang="en">
<head>
<meta name="generator" content=
"HTML Tidy for Mac OS X (vers 31 October 2006 - Apple Inc. build 15.17), see www.w3.org">
<title>JMRI Hardware Support - XpressNet</title>
<meta name="author" content="Paul Bender, Egbert Broerse">
<meta name="keywords" content=
"XpressNet java model railroad JMRI install"><!-- Style -->
<meta http-equiv="Content-Type" content=
"text/html; charset=us-ascii">
<link rel="stylesheet" type="text/css" href="/css/default.css"
media="screen">
<link rel="stylesheet" type="text/css" href="/css/print.css"
media="print">
<link rel="icon" href="/images/jmri.ico" type="image/png">
<link rel="home" title="Home" href="/"><!-- /Style -->
</head>
<body>
<!--#include virtual="/Header" -->
<div class="nomenu" id="mBody">
<div id="mainContent">
<h1>Hardware Support: XpressNet</h1>
<p>XpressNet is a Command Bus developed by Lenz and used by:
<a href="http://www.atlasrr.com">Atlas</a>, <a href=
"http://www.hornby.com/uk-en/">Hornby</a>, <a href=
"http://www.lenz.com">Lenz</a>, <a href=
"http://www.opendcc.de/index_e.html">OpenDCC (DIY)</a>,
<a href="http://usuaris.tinet.cat/fmco/home_en.htm">Paco
Canada (DIY)</a>, <a href="http://www.roco.co.at">Roco</a>
<a href="http://www.viessmann-modell.com/">Viessmann</a> and
<a href="http://www.ztccontrols.com">ZTC Controls</a>.</p>
<p>The XpressNet specification (available from the <a href=
"http://www.lenzusa.com/techinfo/index.htm">Lenz website</a>)
specifies the electrical communications standards and command
set needed for devices to communicate with the command
station.</p>
<ul>
<!-- TOC -->
<li><a href="#hardware">Hardware</a></li>
<li><a href="#limitations">Limitations</a></li>
<li>
<a href="#connecting">Connecting with:</a>
<ul>
<li><a href="#connectLi100">LI100, LI100, LI101 or
LI101F</a></li>
<li><a href="#connectLiusb">LI-USB</a></li>
<li><a href="#connectLzv200">LZV200</a></li>
<li><a href="#connectLiusbServer">LI-USB Server</a></li>
<li><a href="#connectLiusbEthernet">LI-USB
Ethernet</a></li>
<li><a href="#connectSim">XpressNet Simulator</a></li>
<li><a href="#connectZtc">ZTC 640</a></li>
<li><a href="#connectElite">Hornby Elite USB</a></li>
<li><a href="#connectXtncp">XnTcp adapter</a></li>
<li><a href="#connectXpa">XPA and a modem</a></li>
</ul>
</li>
<li><a href="#tools">JMRI XpressNet Tools</a></li>
<li><a href="#documentation">Documentation</a></li>
</ul><a name="hardware" id="hardware"></a>
<h2>Supported Hardware</h2>
<h3>Command Station</h3>
<p>The XpressNet protocol allows the DCC manufacturers that
use it to select what functionality they wish to provide in
their command stations. This functionality ranges from
"supports all features" to "bare bones minimal".
Unfortunately, this restricts the features you can access via
JMRI - if the hardware doesn't support it, it isn't there to
be used by JMRI.</p>
<p>In general, the features that JMRI cares about can be
grouped into three areas:</p>
<ul>
<li><strong>Operating</strong> Locomotives and Turnouts on
the layout</li>
<li><strong>Programming</strong> decoders on a programming
track or in ops mode</li>
<li>Getting <strong>Feedback</strong> from the layout (the
state of turnouts, ops-mode feedback, etc.)</li>
</ul>The following table tries to show which systems support
these three feature groups. System specific limitations are
also expressed in the <a href="#Limitations">Limitations</a>
section of each system below.
<div class="list">
<dl>
<dt class="left">Full</dt>
<dd class="first">
<h4>Operating Programming Feedback</h4>
<ul>
<li>Lenz LZ100 based systems (software version
3.x)</li>
<li>Lenz LZV100 based systems (software version
3.x)</li>
<li>Lenz LZV200 based systems (software version
3.x)</li>
<li>OpenDCC's Command Center</li>
<li>Paco Canada's NanoX-S88</li>
</ul>
</dd>
<dt class="left">Partial</dt>
<dd>
<h4>Operating Programming <font color=
"#FF0000"><strike>Feedback</strike></font></h4>
<ul>
<li>Roco LocoMaus 2 (Roco Part number 10760)</li>
<li>Roco MultiMouse (Roco Part number 10810)</li>
<li>Hornby Elite</li>
<li>Paco Canada's NanoX</li>
</ul>
</dd>
<dt class="left">Minimal</dt>
<dd>
<h4>Operating <font color=
"#FF0000"><strike>Programming</strike></font>
<font color=
"#FF0000"><strike>Feedback</strike></font></h4>
<ul>
<li>Atlas Commander</li>
<li>Lenz Compact</li>
<li>Lenz LH200</li>
<li>ZTC Controls ZTC511 (with Command Station
Software version 4.0)</li>
</ul>
<h4><font color=
"#FF0000"><strike>Operating</strike></font>
Programming <font color=
"#FF0000"><strike>Feedback</strike></font></h4>
<ul>
<li>Lenz BlackBox</li>
</ul>
<h4><font color=
"#FF0000"><strike>Operating</strike></font>
<font color=
"#FF0000"><strike>Programming</strike></font>
Feedback</h4>
<ul>
<li>Paco Canada's GenLI-S88 (adds Feedback to
existing XpressNet System)</li>
<li>Paco Canada's RS2PC (adds RS-Bus based Feedback
without XpressNet)</li>
</ul>
</dd>
<dt class="left">Unknown</dt>
<dd>
<h4>The following systems are untested, but should be
at least partially supported:</h4>
<ul>
<li>ZTC Controls ZTC521 (with XpressNet (aka X-Bus
V3.0) software)</li>
<li>Hornby Select</li>
<li>Viessmann Commander</li>
<li>Roco 10830 multiZENTRAl-PRO</li>
</ul>
</dd>
</dl>
</div>
<h3>Computer Interfaces</h3>
<p>Currently 15 XpressNet computer interfaces are supported
by JMRI:</p>
<ul>
<li>The Lenz LI100 is Lenz's original computer interface.
It is limited to a serial port speed of 9,600 baud.</li>
<li>The Lenz LI100F is an improved version of the LI100. It
supports serial port speeds of 9,600 and 19,200 baud. The
Factory default is 9,600 baud.</li>
<li>The Lenz LI101F is Lenz's last serial port based
computer interface. It is significantly different than the
LI100 and LI100F in physical appearance, and in the method
by which the device is configured. The device is configured
via a software tool provided by Lenz which runs on Windows
only. We have included a configuration tool with JMRI that
will allow users of other operating systems to configure
their LI101F as well. The LI101F supports serial port
speeds of 19,200, 38,400, 57,600, and 115,200 baud. The
factory default is 19,200 baud.</li>
<li>The Lenz LI-USB (Lenz part number 23150 ) is Lenz's
first USB based computer interface. Internally, the device
contains a USB to RS232 serial adapter, and an XpressNet
interface circuit similar to that of the LI101F. Note: If
you are using the XpressNet version 3.6 update in your
command station, you should also update your LI-USB to
version 3.6. There are instructions <a href=
"https://groups.yahoo.com/neo/groups/DigitalPlusbyLenz/conversations/topics/13501">
in this user group message</a> or on <a href=
"http://www.lenzusa.com/manuals/xpressnet/liusbupdatev36.pdf">
the Lenz website</a>. The device is configured via a
software tool provided by Lenz which runs on Windows only.
JMRI provides a tool that will allow users of other
operating systems to configure their LI-USB as well. On
Windows, starting with version 2.7.2, JMRI supports
interfacing with the LI-USB through the Lenz LI-USB
Server.</li>
<li>The Lenz LI-USB-Ethernet (Lenz part number 23151) is a
revised version of the LI-USB which includes a built-in
Ethernet adapter. The USB connection on the device is
provided by a Microchip chipset and registers itself as a
USB CDC-ACM (Abstract Control Model) device. For Windows
users, connection via the USB port will be identical to the
previous version of the LI-USB. For Linux users, the device
will appear as a /dev/ttyACMx device (where x is replaced
with a number). For Mac OS X users, the device name will be
/dev/tty.usbmodemXXX (where XXX is replaced with a 3 digit
number)<br>
The protocol used to connect to the device via USB is
identical to the prior LI-USB device, so the USB connection
is supported by any JMRI version with support for the
LI-USB. When configuring to communicate with the device via
USB, be sure that <b>Flow Control is turned off.</b><br>
Connection via an Ethernet connection is available through
the LI-USB Ethernet connection type, which was first made
available in JMRI version 2.13.7.</li>
<li>The Lenz LZV200 is Lenz's command station with a built
in computer interface. The computer interface is very similar
to the LI-USB and can ve configured using the JMRI tool for
configuring the LI-USB. The LZV200 connection option was added
in version 4.15.7, though thr LZV200 can also be configured
using the LI-USB or LI-USB Server options.</li>
<li>In addition to the Lenz purpose built computer
interfaces, we have also included support for using an
XpressNet Phone Adapter (XPA) as an interface to the an
XpressNet based DCC system. This interface is relatively
slow, and it only allows controlling mobile and stationary
decoders, but it may be perfect for someone who is
interested in trying out the control functions of a
computer before deciding to go with a full fledged
interface. Note that <b>an XPA cannot be used to program
decoders</b>.</li>
<li>The ZTC Controls ZTC640 is ZTC's USB interface. We have
had limited experience with this device, though the current
JMRI drivers are believed to be stable. Operationally, the
device appears to be similar to the Lenz LI-USB.</li>
<li>The Hornby Elite's built-in USB interface can also be
used. Hornby has provided limited information about how the
device works, and currently only provides a USB driver for
Windows, so we are unsure of it's usability with other
operating systems. As with the ZTC640, we have had limited
experience with this device, though the current JMRI
drivers are believed to be stable. <b>Note: The first JMRI
release supporting the Hornby Elite USB connection is
version 2.1.2</b></li>
<li>The <a href="http://www.terdina.net/rails/">XnTcp</a>
interface allows you to connect to your XpressNet layout
via Ethernet-based networking from the JMRI programs.
<b>Note: The first JMRI release supporting the XnTcp
adapter is version 2.1.5</b></li>
<li>Paco Canada's <a href=
"http://usuaris.tinet.cat/fmco/lokmaus_en.html#genli">GenLi</a>
is a do-it-yourself XpressNet interfaces that emulate an
LI100. There is also a USB version of this device. To
configure these devices in JMRI, please see the
instructions for configuring the Lenz LI100.</li>
<li>Paco Canada's <a href=
"http://usuaris.tinet.cat/fmco/lokmaus_en.html#genlis88">Gen-LI-S88</a>
has the same functionality as a GenLI, plus adds an S88
feedback module. It can be used to add feedback to an
existing XpressNet equipped layout. To configure this
devices in JMRI, please see the instructions for
configuring the Lenz LI100.</li>
<li>Paco Canada's <a href=
"http://usuaris.tinet.cat/fmco/rs_en.html#RS2PC">RS2PC</a>
Interface allows adding Lenz (and compatible) RS Feedback
Bus modules to a system that does not support the RS
Feedback Bus. To configure this devices in JMRI, please see
the instructions for configuring the Lenz LI100.</li>
<li>Like Paco Canada's GenLi project, there is an interface
called <a href=
"http://www.sleutelspoor.nl/technieken/S88XPressNetLI-V0.2.pdf">
S88XpressNetLi</a>, which is designed and built by Karst
Drenth and <a href=
"http://people.zeelandnet.nl/rosoft/">Wim Ros</a>, and
consists of a small print (available as kit or built
module) with 2 XpressNet connectors, a serial interface
(9600baud at the moment), and a S88 connection (both
traditional and S88-N connectors).</li>
<li>The OpenDCC project has two interfaces for use with
JMRI. The OpenDCC <a href=
"http://www.opendcc.de/elektronik/opendcc/opendcc_e.html">Command
Station</a> and the <a href=
"http://www.opendcc.de/elektronik/gateway/gateway.html">OpenDCC
Gateway</a>. These devices should be configured as LI100F
devices with the port speed set to 19,200bps. The OpenDCC
Command Station provides feedback via an S88
connection.</li>
</ul><a name="Limitations" id="Limitations"></a>
<h2>Limitations</h2>
<div class="list">
<dl>
<dt class="left">JMRI</dt>
<dd class="first">
<p>JMRI supports the current version (XBus/XpressNet
Version 3.0). We may add XBus Version 1.0 and 2.0
support in the future, which will allow all XBus based
systems to work with JMRI.</p>
</dd>
<dt class="left">Atlas</dt>
<dd>
<p>The Atlas Commander provides support only for
operation of equipment on a layout (running trains and
throwing switches) from JMRI. You cannot program
decoders from a computer with the Commander.</p>
<p>If you have an Atlas Commander, and would like to
use it to control your layout from the computer, an XPA
and Hayes Compatible Modem may be a more cost effective
solution than the LI100, LI100F, LI101F or LI-USB</p>
</dd>
<dt class="left">Hornby</dt>
<dd>
<p>We provide support for the Hornby Elite using it's
built in USB connection. The Elite can be used for
operating equipment on a layout (running trains and
throwing switches) and for programming from JMRI.</p>
<p>It is unknown at this point in time if we can
control either an Elite or a Select using one of the
other interfaces. Hornby's manuals warn against using
their equipment with that of other manufacturers, so we
expect some incompatibilities in this area.</p>
</dd>
<dt class="left">Lenz</dt>
<dd>
<p>We have a pretty good handle on what instructions
each Lenz Command station should support. If you find
that you cannot perform a function you think you should
be able to using a Lenz system and the LI100, LI101F or
LI-USB, please let us know.</p>
<p>LZ100, LZV100, and LZV200 based systems support the full
range of JMRI functionality. The LZ100 is the command
station used in the Set-01. The LZV100 is the command
station used in the Set-90, Set-100, and Set-LI.</p>
<p>The LH200 provides support only for operating
equipment on a layout (running trains and throwing
switches) from JMRI. The LH200 is the command station
used in the Set-02. You can't program decoders from a
computer with Set-02.</p>
<p>The Compact is the same device as the Atlas
Commander, and has the same restrictions as the
commander. The Compact is not available in North
America.</p>
<p>If you have either an LH200 or a Compact, and wish
to add computer control to your layout, an XPA and
Hayes Compatible Modem may be a more cost effective
solution than the LI100, LI100F, LI101F, or LI-USB.</p>
<p>The BlackBox is a standalone decoder programmer. It
can be connected through an XpressNet interface (such
as the LI101F, etc) with a suitable cable. There are
some instructions for creating that cable in the LZV100
manual. The BlackBox only does programming, and cannot
operate either locomotives or accessory decoders
(turnouts) on the layout.</p>
</dd>
<dt class="left">Roco</dt>
<dd>
<p>Note: Roco calls their XpressNet implementation
"RocoNet".</p>
<p>The Roco LocoMaus 2 (Roco Part number 10760) has
been shown to support operating equipment on a layout
(running trains and throwing switches) as well as
programming locomotives on the programming track.</p>
<p>For programming in service mode, the LocoMaus 2
appears to only be able to write to CV's.</p>
<p>It is not known at this point in time if the
LocoMaus 2 supports Operations Mode Programming.</p>
<p>The LocoMaus 2 does not support feedback.</p>
<p>The Roco MultiMaus (Roco Part number 10810) has been
shown to support operating equipment on a layout
(running trains and throwing switches) and programming
locomotives in both service and operations mode.</p>
<p>The Roco multiZENTRAL-PRO (Roco Part number 10830)
is the new command station for use with Roco's
MultiMaus-PRO wireless throttles. The unit features a
built in USB port, but it is unknown at this time how
we can utilize it.</p>
<p>The multiZENTRAL-PRO also provides ports for
connecting a RocoNet device (MultiMaus, LocoMaus 2,
etc). These ports can be used to connect one of the
supported XpressNet computer interfaces, but it is
unknown at this point what, if any, limitations exist
when using this connection.</p>
</dd>
<dt class="left">OpenDCC</dt>
<dd>
<p>The <a href=
"http://www.opendcc.de/elektronik/opendcc/opendcc_e.html">
OpenDCC Command Station</a> should be supported by JMRI
through either the RS232 port or the built in USB
port.</p>
<p>This device should be configured as an LI100F device
with the port speed set to 19,200 bps.</p>
</dd>
<dt class="left">Paco Canada</dt>
<dd>
<p>Paco Canada has two versions of his do-it-yourself
Nanox DCC system available, both are compatible with
JMRI.</p>
<p>The original NanoX DCC system supports operating
equipment on a layout (running trains and throwing
switches) and programming locomotives.</p>
<p>The NanoX-S88 adds feedback capabilities to the
NanoX system. This feedback comes through the use of
S88 compatible feedback modules.</p>
<p>Paco Canada also provides two methods for adding
feedback to non-feedback equipped systems.</p>
<p>The Gen-LI-S88is an XpressNet interface that
includes an S88 feedback module, so it can be used to
add feedback to an existing XpressNet equipped
layout.</p>
<p>The RS2PC interface allows adding Lenz (and
compatible) RS Feedback Bus modules to a system that
does not support the RS Feedback Bus. This device does
not require an XpressNet connection.</p>
</dd>
<dt class="left">Viessmann</dt>
<dd>
<p>The Viessmann Commander's Low Speed Bus port
supports the XpressNet protocol. We should be able to
use this to connect using one of the supported
XpressNet computer interfaces, but the limitations of
this port have not been determined.</p>
<p>Viessmann has indicated the Commander's built in USB
port can only be used for updating the firmware and
sending data to the commander, not for operating the
device.</p>
</dd>
<dt class="left">ZTC</dt>
<dd>
<p>The ZTC Controls ZTC511 (with Command Station
software version 4.0) has been shown to support
operating equipment on a layout (running trains and
throwing switches). The ZTC511 does not support any
programming operations from XpressNet devices.</p>
<p>The onboard serial interface of the ZTC511 is not
supported at this point in time.</p>
<p>The ZTC521 (with XBus V3.0 software) has yet to be
tested, so the full extent of what is supported is not
known at this time.</p>
<p>You can use any of the Lenz or ZTC interfaces listed
above to connect to a ZTC system that supports the
XpressNet (aka X-Bus V3.0) protocol.</p>
<p>If you have either ZTC system and wish to add
computer control to your layout, an XPA and Hayes
Compatible Modem may be a more cost effective solution
than one of the purpose built interfaces.</p>
</dd>
<dt class="left">XPA and Hayes Compatible Modem</dt>
<dd>
<p>If you choose to use an XPA and a Hayes Compatible
Modem to control your XpressNet based system, you will
be limited to control of locomotives and accessory
decoders. You cannot program decoders from a computer
using the XPA, regardless of which system you have.</p>
</dd>
</dl>
</div><a name="connecting" id="connecting"></a>
<h2>Connecting</h2>
<h3>Wiring</h3>
<p>While the Command Stations mentioned on this page support
the same commands over the XpressNet connection, they do not
all use the same hardware connectors. It may be necessary to
build an adapter to plug an XpressNet accessory into a
Command Station from another manufacturer.</p><a name=
"connectLi100" id="connectLi100"></a>
<h3>Connecting using a Lenz LI100, LI101F, or LI101F</h3>
<ol>
<li>Connect your Lenz LI100, LI100F, or LI101F to your DCC
Command station via their XpressNet connections. Then
connect the LI100/LI100F/LI101F to the computer's serial
port using a 9-pin serial cable.</li>
<li>Then go to the preferences panel of a JMRI-based
program. This opens automatically the first time a program
is run, or you can select it from the "Edit" menu.</li>
<li>Select your Lenz interface (LI100,LI100F, or LI101F)
from the top selection box. You can then select the proper
serial port in the second selection box.</li>
<li>The baud rate selection box should be set to match your
LI100, or LI100F, or LI101F. From the factory, the LI100
and LI100F are set to 9600 baud. The LI101F is set to
19,200 baud.</li>
<li>The fourth box should be left on "hardware flow
control" unless you later consistently get a message about
the LI100 control leads being improperly set up, in which
case you might want to try to bypass that by selecting "no
flow control".</li>
<li><b>This option has been removed starting in version
2.9.5</b> Check Buffer Status When Sending? Defaults to
"yes" on Windows and Linux, and "no" on MacOS 8/9 and Mac
OS X. Except when debugging problems, you should leave this
at the default.</li>
<li>Click "Save". You'll be asked if it's OK for the
program to quit, click "Yes".</li>
<li>Restart the program. You should be up and running.</li>
</ol><a name="connectLiusb" id="connectLiusb"></a>
<h3>Connecting using a Lenz LI-USB</h3>
<ol>
<li>To connect your computer to one of these XpressNet
based DCC systems, you can use a Lenz LI-USB interface unit.
Connect the LI-USB to your DCC command station via their
XpressNet connections. Then connect the LI-USB to your
computer's USB port using the supplied cable.</li>
<li>Install the appropriate drivers.
<ul>
<li>For the LI-USB (Lenz part Number 23150) with JMRI,
you must first install a software driver on your
computer. Internally, the device contains a FTDI
FT232BM USB to Serial converter. There are two drivers
available for this device, make sure you obtain the
Virtual Comm Port (VCP) driver.<br>
The device drivers for Windows are included on the CD
that comes with the device.<br>
The device drivers for Linux are included with recent
versions of the Linux kernel.<br>
Device drivers for Linux, and MacOS (8,9 and X ) and
Windows are available from the <a href=
"http://www.ftdichip.com/">FTDI website</a> (direct
link to the drivers current as of this writing:
<a href="http://www.ftdichip.com/Drivers/VCP.htm">http://www.ftdichip.com/Drivers/VCP.htm</a>).</li>
<li>For the LI-USB-Ethernet (Lenz part Number 23151) in
USB mode with JMRI, you must first install a software
driver on your computer. Internally, the device
contains a The USB connection on the device is provided
by a Microchip chipset that registers itself as a USB
CDC-ACM (Abstract Control Model) device. Functionally,
the device acts like a serial port. The Lenz
documentation indicates the drivers for Windows 7 and
MacOS are installed automatically if the computer is
connected to the internet. For Linux, the drivers are
part of the standard kernel distribution.</li>
</ul>
<p>When the device drivers are installed, and the LI-USB
is connected to both your PC and your DCC system, the
LI-USB should have a Red LED turned on, indicating the
XpressNet connection is OK, and a green LED turned on,
indicating the USB connection is OK.</p>
<p><b>NOTE: If you have installed the Lenz software, make
sure none of it is running. This includes the LI-Server,
which may be running in the background.</b></p>
</li>
<li>Once the drivers are installed, you are ready to
configure JMRI. Start one of the JMRI-based programs, Then
go to the preferences panel. This opens automatically the
first time a program is run, or you can select it from the
"Edit" menu.</li>
<li>Select "Lenz LI-USB" from the top selection box. You can
then select the proper serial port in the second selection
box.</li>
<li>The baud rate selection box should be set to 57,600
baud.</li>
<li>The fourth box should be
<ol>
<li>(<b>for the Lenz LI-USB, Lenz Part 23150</b>) left
on "hardware flow control" unless you later
consistently get a message about the LI-USB control
leads being improperly set up, in which case you might
want to try to bypass that by selecting "no flow
control".</li>
<li>(<b>for the Lenz LI-USB-Ethernet, Lenz Part
23151</b>) set to "no flow control" (the LI-USB-Ethernet
does not support flow control).</li>
</ol>
</li>
<li><b>This option has been removed starting in JMRI
version 2.9.5</b> Check Buffer Status When Sending?
Defaults to "Yes" on Windows and Linux, and "No" on MacOS
8/9 and Mac OS X. Except when debugging problems, you
should leave this at the default.</li>
<li>Click "Save". You'll be asked if it's OK for the
program to quit, click "Yes".</li>
<li>Restart the program. You should be up and running.</li>
</ol><a name="connectLiusbServer" id=
"connectLiusbServer"></a>
<h3>Connecting using a Lenz LI-USB and the Lenz LI-USB Server
(Windows Only)</h3><b>Note: The first JMRI release supporting
the Lenz LI-USB Server connection is 2.7.2</b>
<ol>
<li>To connect your computer to one of these XpressNet
based DCC systems, you can use a Lenz LI-USB interface unit
and the Lenz LI-USB Server software. Connect the LI-USB to
your DCC command station via their XpressNet connections.
Then connect the LI-USB to your computer's USB port using
the supplied cable.</li>
<li>In order to use the LI-USB server with JMRI, you must
first install the Lenz drivers and software. These are
provided on the CD that comes with the LI-USB.
<p>When the device drivers are installed, and the LI-USB
is connected to both your PC and your DCC system, the
LI-USB should have a Red LED turned on, indicating the
XpressNet connection is OK, and a green LED turned on,
indicating the USB connection is OK.</p>
<p><b>NOTE: to use the LI-USB server, you MUST install the
Lenz software and the LI-Server must be running.</b></p>
</li>
<li>Once the drivers are installed, you are ready to
configure JMRI. Start one of the JMRI-based programs, Then
go to the preferences panel. This opens automatically the
first time a program is run, or you can select it from the
"Edit" menu.</li>
<li>Select "Lenz LI-USB Server" from the top selection box.
There are no additional configuration steps required to use
the LI-Server.</li>
<li>Click "Save". You'll be asked if it's OK for the
program to quit, click "Yes".</li>
<li>Restart the program. You should be up and running.</li>
</ol><a name="connectLiusbEthernet" id=
"connectLiusbEthernet"></a>
<h3>Connecting using a Lenz LI-USB Ethernet (Lenz Part Number
23151) via the Ethernet connection</h3><b>Note: The first
JMRI release supporting the Lenz LI-USB Ethernet connection
was v 2.13.7.</b>
<ol>
<li>To connect your computer to one of these XpressNet
based DCC systems, you can use a Lenz LI-USB Ethernet
interface unit in Ethernet mode.<br>
Connect the LI-USB to your DCC Command Station via their
XpressNet connection, then connect the LI-USB Ethernet to
your computer Network using the supplied Ethernet
cable.<br>
When the device is properly connected to the XpressNet, the
Red XpressNet LED will turn on.<br>
When the Ethernet is properly connected, a Green status LED
will turn on. This LED is located on the ethernet port
itself. This signals the drivers are installed, and the
LI-USB is connected.</li>
<li>Once the device is connected, refer to the device
documentation for information on setting the IP address.
The default IP address is 192.168.0.200. Make note of the
IP address for use when configuring the device. If the IP
address is unknown, and your system supports
auto-configuration via the MDNS protocol (also known as
Bonjour), you can open a web browser to <a href=
"http://XPressNet.local./">http://XPressNet.local./</a>.<br>
In the LI-USB-Ethernet Configuration interface, the IP
address appears in the field circled in the image
below:<br>
<a href="images/LIUSBEthernetIPAddressField.PNG"><img src=
"images/LIUSBEthernetIPAddressField.PNG" width="400"
height="427" alt=
"LI-USB-Ethernet Configuration web interface with IP Address circled.">
</a></li>
<li>Start one of the JMRI-based programs, Then go to the
preferences panel. This opens automatically the first time
a program is run, or you can select it from the "Edit"
menu.</li>
<li>Select "Lenz LI-USB Ethernet" from the top selection
box. There are two configuration options available for the
LI-USB-Ethernet. You may choose to use Manual configuration
(the default) or Automatic configuration:
<ul>
<li>To use <strong>Manual configuration</strong>, enter
the IP address you saved earlier into the box labeled
"IP Address", as shown in the image below:<br>
<a href="images/ConfigurationIPFields.PNG"><img src=
"images/ConfigurationIPFields.PNG" width="606" height=
"210" alt=
"JMRI Configuration screen and LI-USB-Ethernet Configuration screen demonstrating the IP address to be copied.">
</a></li>
<li><strong>Automatic configuration</strong> is
optional if you set the IP Address of your
LI-USB-Ethernet device to a fixed value. If you use DHCP
to configure the LI-USB-Ethernet's IP address, it is
highly recommended that you use Automatic
Configuration.<br>
To use Automatic Configuration, check the Automatic
Configuration checkbox. as shown in the image
below:<br>
<a href=
"images/LIUSBEthernetAutoConfigureCheckboxes.PNG"><img src="images/LIUSBEthernetAutoConfigureCheckboxes.PNG"
width="595" height="216" alt=
"JMRI Configuration screen and LI-USB-Ethernet Configuration screen demonstrating automatic configuration.">
</a></li>
</ul>
</li>
<li>Click "Save". You'll be asked if it's OK for the
program to quit, click "Yes".</li>
<li>Restart the program. You should be up and running.</li>
</ol>
<a name="connectLzv200" id="connectLzv200"></a>
<h3>Connecting using a Lenz LZV200</h3>
<ol>
<li>To connect your computer to Lenz LZV200using the
built in USb port, connect the LZV200 to your
computer's USB port using a standard USB A to USB B
cable.</li>
<li>Install the appropriate drivers.
<p>For the LZV200 USB connection with JMRI, you
must first install a software driver on your
computer. Internally, the device contains a FTDI
FT232BM USB to Serial converter. There are two drivers
available for this device, make sure you obtain the
Virtual Comm Port (VCP) driver.<br>
The device drivers for Windows are included on the CD
that comes with the device.<br>
The device drivers for Linux are included with recent
versions of the Linux kernel.<br>
Device drivers for Linux, and MacOS (8,9 and X ) and
Windows are available from the <a href=
"http://www.ftdichip.com/">FTDI website</a> (direct
link to the drivers current as of this writing:
<a href="http://www.ftdichip.com/Drivers/VCP.htm">http://www.ftdichip.com/Drivers/VCP.htm</a>).</p>
<p>When the device drivers are installed, and the LZV200
is connected to your PC, the LZV200 should have a Red LED
turned on, indicating the USB connection is OK.</p>
<p><b>NOTE: If you have installed the Lenz software, make
sure none of it is running. This includes the LI-Server,
which may be running in the background.</b></p>
</li>
<li>Once the drivers are installed, you are ready to
configure JMRI. Start one of the JMRI-based programs, Then
go to the preferences panel. This opens automatically the
first time a program is run, or you can select it from the
"Edit" menu.</li>
<li>Select "Lenz LZV200" from the top selection box. You can
then select the proper serial port in the second selection
box.</li>
<li>The baud rate selection box should be set to 57,600
baud.</li>
<li>The fourth box should be set to "no flow control" (the
LZV200 does not support flow control).</li>
<li>Click "Save". You'll be asked if it's OK for the
program to quit, click "Yes".</li>
<li>Restart the program. You should be up and running.</li>
</ol>
<a name="connectsim" id="connectsim"></a>
<h3>Connecting to the XpressNet Simulator</h3>
<ol>
<li>Start one of the JMRI-based programs, Then go to the
preferences panel. This opens automatically the first time
a program is run, or you can select it from the "Edit"
menu.</li>
<li>Select "XpressNet Simulator" from the top selection
box. There are no additional configuration steps required
to use the XpressNet Simulator.</li>
<li>Click "Save". You'll be asked if it's OK for the
program to quit, click "Yes".</li>
<li>Restart the program. You should be up and running.</li>
</ol><a name="connectZtc" id="connectZtc"></a>
<h3>Connecting using a ZTC ZTC640</h3>
<ol>
<li>To connect your computer to one of these XpressNet
based DCC systems, you can use a ZTC ZTC640 interface unit.
Connect the ZTC640 to your DCC command station via their
XpressNet connections. Then connect the ZTC640 to your
computer's USB port using the supplied cable.</li>
<li>In order to use the ZTC640 with JMRI, you must first
install a software driver on your computer. Internally, the
device contains a FTDI FT232BM USB to Serial converter.
There are two drivers available for this device, make sure
you obtain the Virtual Comm Port (VCP) driver.
<p>The device drivers for Windows are included on the CD
that comes with the device.</p>
<p>The device drivers for Linux are included with recent
versions of the Linux kernel</p>
<p>Device drivers for Linux, and MacOS (8,9 and X ) and
Windows are available from the <a href=
"http://www.ftdichip.com/">FTDI website</a>. (direct link
to the drivers current as of this writing: <a href=
"http://www.ftdichip.com/Drivers/VCP.htm">http://www.ftdichip.com/Drivers/VCP.htm</a>)</p>
<p>When the device drivers are installed, and the ZTC640
is connected to both your PC and your DCC system, the
ZTC640 should have a Red LED turned on, indicating the
XpressNet connection is okay, and a green LED turned on,
indicating the USB connection is okay.</p>
</li>
<li>Once the drivers are installed, you are ready to
configure JMRI. Start one of the JMRI-based programs, Then
go to the preferences panel. This opens automatically the
first time a program is run, or you can select it from the
"Edit" menu.</li>
<li>Select "ZTC Controls ZTC640" from the top selection
box. You can then select the proper serial port in the
second selection box.</li>
<li>The baud rate selection box should be set to 19,200
baud.</li>
<li>The fourth box should be left on "no flow
control".</li>
<li><b>This option has been removed starting in version
2.9.5</b> Check Buffer Status When Sending? Defaults to
"yes" on Windows and Linux, and "no" on MacOS 8/9 and Mac
OS X. Except when debugging problems, you should leave this
at the default.</li>
<li>Click "Save". You'll be asked if it's okay for the
program to quit; click "Yes".</li>
<li>Restart the program. You should be up and running.</li>
</ol><a name="connectElite" id="connectElite"></a>
<h3>Connecting using the Hornby Elite's built in USB
connection</h3><b>Note: The first JMRI release supporting the
Hornby Elite's built-in USB connection is 2.1.2</b>
<ol>
<li>To connect your computer to the Hornby Elite using it's
built in USB connection, connect your Hornby Elite's USB
port and the computer's USB port using the supplied
cable.</li>
<li>In order to use the Hornby Elite's built in USB port,
you must first install a software driver on your computer.
<p>The device drivers for Windows are included on the CD
that comes with the device and from the <a href=