Serge NOEL
141 lines
5.6 KiB
Plaintext
141 lines
5.6 KiB
Plaintext
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta name="generator" content="HTML Tidy for HTML5 for Apple macOS version 5.8.0">
|
|
<title>JMRI Hardware Support - Power Line - System Names</title>
|
|
<!--#include virtual="/help/en/parts/Style.shtml" -->
|
|
</head>
|
|
<body>
|
|
<!--#include virtual="/help/en/parts/Header.shtml" -->
|
|
|
|
<div id="mBody">
|
|
<!--#include virtual="Sidebar.shtml" -->
|
|
|
|
<div id="mainContent">
|
|
<h1>Hardware Support: Powerline - System Names</h1>
|
|
Individual inputs (Sensors) and outputs (Turnouts and Lights) in JMRI are accessed via System
|
|
Names.<br>
|
|
For information on the general scheme, please see <a href=
|
|
"../../doc/Technical/Names.shtml">JMRI Naming</a> in the <a href=
|
|
"../../doc/Technical/index.shtml">Technical documentation</a>.
|
|
<h2 id="hardware">Supported Hardware</h2>
|
|
|
|
<h3>X10</h3>
|
|
X10 devices are addressed via a "House Code" of A through P, and a "Device Code" of 1 through
|
|
16.
|
|
<p>Outputs (Lights or Turnouts) in each House Code are numbered with their Device Code,
|
|
e.g.</p>
|
|
|
|
<ul>
|
|
<li>PTA1 is a JMRI Turnout that talks to device 1 on housecode A</li>
|
|
|
|
<li>PTB3 is a JMRA Turnout for device 3 on housecode B</li>
|
|
|
|
<li>PLP16 is a JMRI Light for device 16 on housecode P</li>
|
|
</ul>
|
|
|
|
<p>If an output is called as a Turnout (name starts with PT-), you only get On and Off as
|
|
output options.</p>
|
|
|
|
<p>An output that is used as a Light (name starts with PL-) will take variable intensities.
|
|
However, some physical X10 devices may not support dimming.</p>
|
|
|
|
<p>Inputs (Sensors) are identified by the house code and device number that was reported by
|
|
some other X10 device like a motion sensor or light control pad.<br>
|
|
NOTE: Due to a large number of false codes experienced by X10 users, Sensors are not
|
|
automatically generated. They must be manually entered in the Sensor Table by the user.</p>
|
|
|
|
<p>JMRI configures the adapter to use House Code "A" now. We'll eventually make that
|
|
configurable, but for now that means that input messages will only be received from devices
|
|
set to House Code A, so only sensors "PSA1" through "PSA16" will work.<br>
|
|
(Early versions of JMRI X10 support used an all-numeric address like PT12, with no House Code
|
|
letters; this is no longer available, because it caused way too much confusion)</p>
|
|
|
|
<h3>Insteon</h3>
|
|
<p>
|
|
Insteon Adapters are labeled with a three-part number that looks like "01.2A.B4". These are
|
|
just random strings as far as the user and the program is concerned, and we don't make any
|
|
effort to subdivide them. You should enter these exactly as they appear on the device you
|
|
want to address. Do not delete or add leading zeros, etc.
|
|
<p>For example, if the device is labeled "01.2A.B4", the corresponding JMRI Light System
|
|
Name is "PL01.2A.B4".</p>
|
|
|
|
<h3 id="documentation">Adding an item to the table</h3>
|
|
|
|
<p>When you add an item to one of the tables, many times you only have to fill in the numbers
|
|
to have JMRI construct the complete system name.<br>
|
|
Here's a summary, split up for outputs (eg. Turnouts) and inputs (eg. Sensors):</p>
|
|
|
|
<table>
|
|
<tbody>
|
|
<tr>
|
|
<th>In/Out</th>
|
|
<th>Entry</th>
|
|
<th>Meaning</th>
|
|
<th>makes System Name</th>
|
|
<th>Mask</th>
|
|
<th>Minimum</th>
|
|
<th>Maximum</th>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td>i/o</td>
|
|
<td>A3</td>
|
|
<td>House code A + num device code</td>
|
|
<td>PTA3</td>
|
|
<td>caps letter + num</td>
|
|
<td>house code: A; device: 1</td>
|
|
<td>house code: P; device: 16</td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td>i/o</td>
|
|
<td>01.2A.B4</td>
|
|
<td>Light (module) PL01.2A.B4</td>
|
|
<td>PL01.2A.B4</td>
|
|
<td>3 x 2 chars</td>
|
|
<td>not documented</td>
|
|
<td>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<!-- this table is an excerpt from the table in the help/en/html/doc/Technical/Names.shtml
|
|
based on information from the Hardware help pages
|
|
by Egbert Broerse @silverailscolo July 2017 -->
|
|
|
|
<h3>DMX512</h3>
|
|
<p>
|
|
The DMX universe uses a array of 512 bytes for all the devices on that connection.
|
|
Each device has an intensity of 0 to 255. In JMRI, this is expressed as a value of 0.0 to 1.0.
|
|
</p>
|
|
<p>
|
|
Only lights are supported from JMRI. Each lamp may have a ramp rate to control the rate of change.
|
|
This works from the fast clock. If the clock is not running, the effects are immediate.
|
|
</p>
|
|
<p>
|
|
The USB interface device must support a serial port for connecting to the USB device.
|
|
Most of these are FTDI driver devices. The Anyma DMX device uses a USB device driver that
|
|
is not currently supported on Windows. That device will work for Linux and Mac systems.
|
|
|
|
<h2>Documentation</h2>
|
|
|
|
<h3>Third Party info</h3>
|
|
|
|
<p>More information on the X10 hardware can be found on the (admittedly obnoxious) <a href=
|
|
"https://www.x10.com/">X10.com website</a>.</p>
|
|
|
|
<p>More information on Insteon hardware can be found on the <a href=
|
|
"https://www.insteon.com/">insteon.com website</a>.</p>
|
|
|
|
<h3>JMRI Help</h3>
|
|
|
|
<p>Back to the <a href="index.shtml">Powerline Help page</a>.</p>
|
|
<!--#include virtual="/help/en/parts/Footer.shtml" -->
|
|
</div>
|
|
</div>
|
|
<!-- close #mBody -->
|
|
<script src="/js/help.js"></script>
|
|
</body>
|
|
</html>
|