Menu
▾
▴
[Jmri-commits] site/XPressNet XNetAddressing.html,NONE,1.1 index.html,1.3,1.4
|
From: <pb...@us...> - 2004-02-22 22:29:45
|
Update of /cvsroot/jmri/site/XPressNet In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv11132 Modified Files: index.html Added Files: XNetAddressing.html Log Message: Added Documentation about addressing, updated what the Roco LocoMouse can do now that it has been tested with JMRI --- NEW FILE: XNetAddressing.html --- <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> <head> <title>Lenz Feedback Bus Addressing</title> </head> <body> <IMG SRC="../images/logo.gif" ALIGN=RIGHT WIDTH="160" HEIGHT="135" HSPACE="0" VSPACE="0"> <h1>Lenz Feedback Bus Addressing</h1> On Lenz systems, feedback from input devices is handled by the Feedback Bus. The input available from the feedback bus is provided by the Lenz LR100 and LR101 Feedback Encoders, or Lenz accessory decoders which provide feedback capabilities (the LS100 for example). <h2>Addressing Accessory Decoders with XPressNet in JMRI</h2> <p> Each accessory decoder is addressed by giving it an address in the address space allocated by the NMRA for accessory decoders. This allows accessory decoder addresses from 1 to 1024. </p> <p> In JMRI's tools, you can prefix the address with XT to tell system the decoder is accessed via an XPressNet based system. If you only have an XPressNet based system configured, you can just use the address, and the programs will automatically assign an XT prefix for you. </p> <p> On the Feedback bus, accessory decoders are allowed to occupy addresses from 1 to 64. Since the feedback equiped decoders Lenz provides actually include 4 accessory decoders, this limtied address space actually corresponds to accessory decoder address 1 to 256. </p> <p> To calculate what feedback device Addresses one of your accessory decoders resides at, round up to the next multiple of 4, and divide that number by 4. </p> <p> For example, if you have an accessory decoder with address 121, the next multiple of 4 is 124. 124 divided by 4 is 31, so this decoder is included with feedback address 31. </p> <p> Feedback from accessory decoders is handled automatically by the turnout tools included with JMRI. If the turnout is equiped with feedback, the Turnout Tool, Turnout Table, or a control panel will not update the turnout's status until a response from the feedback bus indicates the turnout has been thrown. </p> <p> Status for decoders that do not report feedback is handled by waiting for a response message before changing the decoder's status. </p> <h2>Addressing Lenz Feedback Bus Sensors in JMRI</h2> <p> the Lenz LR100 and LR101 Feedback Encoders are allowed to have feedback addresses from 1 to 128. Lenz Recommends starting at address 65 and going up to avoid conflicts with turnouts providing feedback. </p> <p> NOTE: the LR100 actually has 16 inputs, and does take up two addresses. </p> <p> Each feedback encoder includes 8 inputs. These inputs are either either on or off. Each input is numbered from 1 to 8 on the Feedback Encoder. </p> <p> To determine what feedback address is being reported by the device, you need to know the address of the feedback encoder, and which input you are using. See Lenz's documentation for determining how to program the Feedback Encoder's Address. This can be done with the encoder in place on the layout. </p> <p> To calculate the address of a sensor, subtract 1 from the Feedback Encoder's address, multiply that result by 8, and then add the input number you are using. </p> <p> For Example, if you are using contact 3 on a Feedback Encoder with address 99, 99 - 1 = 98. 98*8=784. 784+3=787. The feedback address you will use is 787. </p> <p> In JMRI's tools, you can prefix the address with XS to tell system the Sensor is accessed via an XPressNet based system. If you only have an XPressNet based system configured, you can just use the address, and the programs will automatically assign an XS prefix for you. </p> <hr> Paul Bender<BR> pau...@ac... </body> </html> Index: index.html =================================================================== RCS file: /cvsroot/jmri/site/XPressNet/index.html,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -d -r1.3 -r1.4 *** index.html 11 Feb 2004 18:51:17 -0000 1.3 --- index.html 22 Feb 2004 22:16:41 -0000 1.4 *************** *** 14,17 **** --- 14,18 ---- <a href=#ComputerInterfaces>Computer Interface Information</a> <a href=#CommandStations>Command Station Information</a> + <a href=#TechnicalInformation>XPressNet Specific Technical Info</a> <a href=#XPressNetTools>XPressNet Specific Tools</a> <a name=Overview> *************** *** 38,41 **** --- 39,43 ---- <a href=#ComputerInterfaces>Computer Interface Information</a> <a href=#CommandStations>Command Station Information</a> + <a href=#TechnicalInformation>XPressNet Specific Technical Info</a> <a href=#XPressNetTools>XPressNet Specific Tools</a> <a href=#top>Go back to the top</a> *************** *** 65,71 **** --- 67,83 ---- The factory default is 19,200 baud</p> <p> + 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. + </p> + <a href=#Overview>Overview</a> <a href=#ComputerInterfaces>Computer Interface Information</a> <a href=#CommandStations>Command Station Information</a> + <a href=#TechnicalInformation>XPressNet Specific Technical Info</a> <a href=#XPressNetTools>XPressNet Specific Tools</a> <a href=#top>Go back to the top</a> *************** *** 76,79 **** --- 88,94 ---- provided by JMRI: Lenz LZV100 and Lenz LZ100 </p> + The following command stations support programming and operating + equipment on a layout, but do not support feedback: Roco LocoMaus 2 (Roco + Part number 10760) <p> The following command stations provide support only for operating *************** *** 83,90 **** <p> The following command stations have not been tested for compatability, ! but should be at least partially supported:Lenz LH200,Roco LocoMaus 2 ! (Roco Part number 10760), ZTC ! Controls ZTC511 (with XPressNet V3.0 software),ZTC Controls ZTC521 (with XPressNet ! V3.0 software), </p> --- 98,104 ---- <p> The following command stations have not been tested for compatability, ! but should be at least partially supported:Lenz LH200, ZTC Controls ZTC511 ! (with XPressNet V3.0 software), ZTC Controls ZTC521 (with XPressNet V3.0 ! software). </p> *************** *** 92,95 **** --- 106,129 ---- <a href=#ComputerInterfaces>Computer Interface Information</a> <a href=#CommandStations>Command Station Information</a> + <a href=#TechnicalInformation>XPressNet Specific Technical Info</a> + <a href=#XPressNetTools>XPressNet Specific Tools</a> + <a href=#top>Go back to the top</a> + <a name=TechnicalInformation> + <h2>XPressNet Specific Technical Info</h2> + <p> + We have some technical information about the XPressNet implementation + avaliable. Topics currently available are: + </p> + <p> + <a href=XNetAddressing.html>Lenz Feedback bus Addresses</a> + </p> + <p> + <a href=CreateXNetLogFile.html>How To Create an XPressNet Log file</a> + </p> + + <a href=#Overview>Overview</a> + <a href=#ComputerInterfaces>Computer Interface Information</a> + <a href=#CommandStations>Command Station Information</a> + <a href=#TechnicalInformation>XPressNet Specific Technical Info</a> <a href=#XPressNetTools>XPressNet Specific Tools</a> <a href=#top>Go back to the top</a> *************** *** 117,120 **** --- 151,155 ---- <a href=#Overview>Overview</a> <a href=#ComputerInterfaces>Computer Interface Information</a> + <a href=#TechnicalInformation>XPressNet Specific Technical Info</a> <a href=#CommandStations>Command Station Information</a> <a href=#XPressNetTools>XPressNet Specific Tools</a> |