/
LocoNetServer.shtml
127 lines (102 loc) · 4.76 KB
/
LocoNetServer.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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.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 - Multiple Computers to LocoNet®
via JMRI LocoNet Server</title>
<meta name="author" content="Bob Jacobsen">
<meta name="keywords" content=
"Digitrax Chief DCS Command Station LocoNet Server LocoBuffer java model railroad JMRI install windows">
<!-- 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: Connecting Multiple Computers to
LocoNet® via JMRI LocoNet Server</h1>This page describes
how to use the inbuilt LocoNet® Client/Server capability
of JMRI to connect multiple computers to a single
LocoNet-equipped layout.
<p>Briefly, one computer is physically connected to the
LocoNet, and acts as a "Server" for others. One or more
"Client" computers can then connect via standard TCP/IP
protocols to the Server.</p>
<h2>Setup for JMRI LocoNet Client/Server</h2>One computer
running JMRI acts as the Server, which is directly connected
to the LocoNet, the other computers running JMRI connect to
the Server computer as Clients.
<ul>
<li>Configure the LocoNet connection just like for any
other use. Select the protocol that corresponds to your
hardware (e.g. LocoBuffer-II, etc), the communication port,
and other options. It's best to make sure this is working
well before proceeding.</li>
<li>You can then manually start the server by selecting
"Start LocoNet Server" from the LocoNet menu. This will
allow other computers to connect to the layout until you
stop the program; the next time you start it, you'll have
to do this again.</li>
<li>You can also have the server start automatically every
time you start the program by
<ul>
<li>Open the Preferences from the Edit menu (on Windows
or Linux) or from the Application menu (OS X)</li>
<li>Under "Start Up", click "Add ▾"</li>
<li>Select "Perform action..."</li>
<li>Find and select "Start LocoNet Server" and click
"OK"</li>
<li>Save the preferences.</li>
</ul>
</li>
</ul>
<p>The program in the Client computer can then be configured
to connect to the layout via the LocoNet Server by:</p>
<ul>
<li>Make sure the Server computer is running the LocoNet
server</li>
<li>Open the program on the Client computer</li>
<li>Open the preferences from the Edit menu</li>
<li>For layout connection, select "LocoNet Server"</li>
<li>In the "Server hostname" box that appears, type the
Internet name or address of the computer that's running the
LocoNet Server. An internet address is something like
127.0.1.12; a name is something like jmri.org</li>
<li>Save the preferences and restart the program.</li>
</ul>
<h2>Notes:</h2>
<ul>
<li>It's strongly recommended that you connect the master
computer to the LocoNet with a LocoBuffer or LocoBuffer-II.
Although a MS-100 will basically work for this application,
correction of the resulting occasional LocoNet errors may
cause noticeable delays in updating the remote
computers.</li>
<li>If the computers are all close to the LocoNet, e.g.
acting as local control panels, you don't really need
LocoNet Server to do this. You can instead connect each of
the computers to the LocoNet via their own LocoBuffer or
LocoBuffer-II (or MS-100, though this is not recommended)
and have them individually take part in the LocoNet
communications. This doesn't cause any additional
communications load. It does cost a little more for the
extra adapters, and doesn't permit you to put a computer
remote from the layout.</li>
</ul>
<p>LocoNet® is a registered trademark of <a href=
"http://www.digitrax.com">Digitrax, Inc.</a></p>
<!--#include virtual="/Footer" -->
</div><!-- closes #mainContent-->
</div><!-- closes #mBody-->
</body>
</html>