LOCONETBD7OPSWMODE
Board Address
Device Type
Device Manufacturer (NMRA number)
Serial Number
Normal Sensitivity
Higher Sensitivity
Lower Sensitivity
(unknown sensitivity)
Detection uses
Normal
Slow
Detection speed is
Forces all detection to "occupied"
has no effect on occupancy reporting
Track power "off"
CVs
<html>The "CV" column in the table above shows CV
numbers, not the Op Switch number.<p>To see those, hover
your mouse over a variable on the OpSw Settings pane.
<p>CVs 1 and 2 are the low and high (respectively) 8-bit
"Base Address" values.<p>The "Base Address" is practically
limited to 2040, max.<p>The JMRI "Roster" tool and its
Roster entries <em> cannot</em> change the
"Base Address".
Basic
<html>
<p>This roster entry will only access the specified
board if the Base Address specified above <br>was
correctly entered when the roster entry was first created.
You <em>cannot</em> change it in the Roster Entry.
</html>
OpSw Settings
<html><h2>Detection Settings
Notes
<html><h2>Notes:</h2>
<ul>
<li>The BDL716 device implements features that "use" various
types of addresses in<br>
several types of "Address Spaces". It is important that the
device <em>only</em> uses those<br>
addresses that are <em>not</em> used by any other device,
whether on LocoNet or connected<br>
to the "DCC Track" signal. </li>
<li>The BDL716 is believed to use the addresses as described below:<br>
<table border="3">
<tr><th>Address Type</th>
<th>Range of Addresses</th>
<th>Comments</th></tr>
<tr><td>Sensors</td>
<td>Base Address to<br>(Base Address + 15)</td>
<td>The BDL716 implements 16 "Detection<br>
Sensors" in the LocoNet sensor address<br>
range.</td>
</tr>
<tr><td>Switches</td>
<td>(None)</td>
<td>The BDL716 does not implement any<br>
"Turnout"s in either the LocoNet or<br>
the "NMRA Accessory" address range.</td>
</tr>
<tr><td>NMRA "Extended<br>Accessories"
<br>(Signal Aspect<br>Accessories)</td>
<td>Base Address to<br>(Base Address + 3)</td>
<td>The BDL716 uses NMRA "Extended<br>
Accessory" ("Signal Aspect") <br>
addresses for accessing Device<br>
"CV" settings, but does not otherwise<br>
implement any "Extended Accessory"<br>
addresses.</td>
</tr>
<tr><td>Transponding<br>"Zones"</td>
<td>(None)</td>
<td>The BDL716 does not implement any<br>
"Transponding" addresses in the<br>
LocoNet Transponding address range.</td>
</tr>
<tr><td>"Power/Track<br>Status"</td>
<td>(None)</td>
<td>The BDL716 does not implement any<br>
addresses in the LocoNet "Power/<br>
Track Status" address range.</td>
</tr>
</table>
<li>The BDL716's CVs can be mapped to a "Base Address" that
"overlaps" another<br;>
device on this LocoNet connection, or otherwise
conflicts with an NMRA<br;>
Extended Accessory decoder.<br;>
<em>When programming with this roster entry, such a conflict
can cause the conflicting<br;>
device to be mistakenly configured.</em></li>
<li>Because the DT602 or other mechanisms (like this roster entry!)
can access this<br;>
BDL716 device's CVs by any of a number of "device addresses"
(See 'NMRA<br>
"Extended Accessories" in the table above), this roster entry's
"Board Address"<br;>
should be configured to the actual device's Base Address. This
will reduce the<br;>
likelihood of mis-configuring this BDL716 or any other device
that may be<br;>
configured by this type of configuration method, whether a
LocoNet peripheral or</li>
some other kind of device.</li>
<li>Because of the notes above, </em>it is recommended</em>
that this BDL716 roster entry <br;>
should be set to the BDL716's "Base Address" setting, and that
care must be taken<br;>
to avoid other devices from using addresses that this BDL716
will use.</ul></html>