Menu ▾ ▴

#815 fix of broken links in html\hardware\loconet

closed
Bob Jacobsen
None
Documentation
5
2013-02-01
2013-01-15
Walter Thompson
No

attached zip file for many changes
a few were covered before I found the full file needed work.

1 Attachments
loconet.zip

Discussion

  • Bob Jacobsen

    Bob Jacobsen - 2013-01-31

    This patch only seems to change three files:

    M StandaloneLocoNet.shtml
    A images/StandaloneLocoNetSignallingNet.png
    M Fleischmann.shtml

    The Standalone LocoNet change seems to remove a lot of discussion. Is that intended? Where did it go?

    ===================================================================
    --- StandaloneLocoNet.shtml (revision 22658)
    +++ StandaloneLocoNet.shtml (working copy)
    @@ -45,7 +45,7 @@

  • LocoNet RailSync Signal "Generation"


      @@ -72,10 +71,7 @@

      General ideas

         <p><i>This page is a work in progress</i></p>

      -

      A "Standalone" LocoNet® is a LocoNet bus which does not have a LocoNet

      • command station. Since it does not have a LocoNet command station, it cannot
      • control locomotives, and cannot directly influence the DCC track signal created
      • by a DCC command station.


        +

        A "Standalone" LocoNet® is a LocoNet bus which does not have a command station.



        There are several situations where a standalone LocoNet bus is useful. Some of these situations are listed here:

        @@ -83,18 +79,7 @@
      • When using LocoNet peripherals with a non-DCC railroad.
      • To isolate LocoNet peripherals from LocoNet throttle activity.
      • To avoid LocoNet traffic issues associated with the Digitrax command station's - small buffer for forwarding LocoNet switch commands to the DCC track signal.
        • -
      • Some users even find it useful to have JMRI communicate with two or more - LocoNet connections. One LocoNet connection might be a "standard" - LocoNet, with a LocoNet-based command station, so that JMRI can program - decoders and perhaps control mobile decoders. Another LocoNet connection could be - a standalone LocoNet, with block detection, signal control, and switch - control hardware monitored and controlled by JMRI. This standalone - LocoNet is quite useful when implementing a CTC panel, as it ensures - that the block detection and signaling cannot be influenced by throttle - activity. In other words, a LocoNet throttle user might send LocoNet - switch control messages, but those messages won't have any effect on the - switches and/or signals which are on the standalone LocoNet.
        • + small buffer for forwarding switch commands to the DCC track signal.

      This page gives some general suggestions for implementing a standalone LocoNet as well as suggestions for configuring JMRI software to make use of the standalone @@ -125,13 +110,19 @@ DeviceSlot ManagementRailSync LocoNet Data signal terminationFast Clock Master - Digitrax DCS100/DB150/DCS50/DCS51 (as command station)ProvidesProvides DCC signal + Digitrax DCS100 (as command station)ProvidesProvides ProvidesProvides - Digitrax DCS100/DB150/DCS50/DCS51 (as booster)Requires DCC signal + Digitrax DCS100 (as booster)Required - Non-LocoNet command stationCan provide DCC signal * + Digitrax DB150 (as command station)ProvidesProvides + ProvidesProvides + + Digitrax DB150 (as booster)Required + + + Non-LocoNet command stationCan provide * Provides?Provides? Computer Interface Devices @@ -141,32 +132,31 @@ Digitrax PR3 (in MS100 mode)Optional Required, can provide - RR-CirKits LocoBuffer-II/LocoBuffer-USBOptionalRequired for power ** + LocoBuffer, RR-CirKits LocoBuffer-II/LocoBuffer-USBOptional Required, can provide - LocoBufferOptionalRequired, might provide *** LocoNet Throttles DeviceSlot ManagementRailSync LocoNet Data signal terminationFast Clock Master - Digitrax DT100x/DT200x/DT300x/DT400x/DT402x throttleRequiredOptional, for power + Digitrax DT100x/DT200x/DT300x/DT400x/DT402x throttleRequiredOptional (only for power) RequiredOptional Some Other LocoNet Devices DeviceSlot ManagementRailSync LocoNet Data signal terminationFast Clock Master - Digitrax LNRPRequires DCC signal + Digitrax LNRPRequired Required Digitrax DS54/DS64 - Required if connected to LocoNet + Optional - Digitrax BDL16/BDL162/BDL168Requires DCC signal + Digitrax BDL16/BDL162/BDL168Required Required, can provide - Digitrax PM4/PM42 - Required, can provide + Digitrax PM42Required + Required Digitrax SE8C Required @@ -180,58 +170,45 @@ Team Digital SIC24/SIC24AD/SRC8/SRC16 Required - RR-Cirkits TC-64Required for power ** + RR-Cirkits TC-64 Required - RR-Cirkits LNCP - Required - Logic Rail Technologies LocoNet Fast Clock RequiredRequired, can provide - -

      * Some circuitry may be required to generate the RailSync signals from - a non-LocoNet booster. See - RailSync from a non-Digitrax command station, - below.

      -

      ** LocoNet devices with optically-isolated LocoNet interfaces must - take power from the LocoNet RailSync wires to power the LocoNet side - of their optically-isolated interface hardware. These devices may - not require that the RailSync wires have a copy of the DCC track - signal, but they do require sufficient voltage and current. A DC - power supply, as shown below in - RailSync power from a DC power supply, is sufficient to meet the - power needs of the LocoBuffer-II, the LocoBuffer-USB RailSync, and - the TC-64. If the RailSync wires do not provide sufficient voltage - and current, these devices will be unable to communicate reliably - with LocoNet.

      -

      *** Some versions of the LocoBuffer design can provide LocoNet - termination if additional components are installed on the LocoBuffer - board. Other versions of the original LocoBuffer design do not have - places for the additional components to be installed. These comments - do not apply to the LocoBuffer-II or LocoBuffer-USB designs.

      - + * Some circuitry may be required to + generate the RailSync signals from a non-LocoNet booster.

      LocoNet Data Signal "Termination"

      -

      "Termination" of the LocoNet Data Signal is something that allows the - LocoNet data path to work. One device on LocoNet must provide this - "termination" so that all LocoNet devices may communicate on the - LocoNet "data" wires. Without this "termination", LocoNet devices - cannot pass LocoNet messages to each other.

      +

      Technically, the term "termination" can be somewhat misleading. For our purposes, + LocoNet data signal "termination" is a current source which provides a + positive 15 mA current source from a +12V supply, and which is + connected to the LocoNet "Data" pins (pins 3 and 4), and which is + referenced to the LocoNet "Ground" pins (pins 2 and 5). This provides + a "pull-up" for the "wired-or" signaling used on the LocoNet "data" wires.

      +

      Some Digitrax documentation describes devices which can act as the LocoNet + "master", and other Digitrax documentation describe the "LocoNet Master" as + (in part) the LocoNet device which provides the current source for the + LocoNet data lines. So, the term "LocoNet Master" may sometimes imply + a device which can provide the LocoNet Data signal termination.

      +

      In this context, "data signal termination" does not refer to "electrical + transmission line termination". According to Digitrax documentation, there + should not be any need to provide "electrical transmission line termination" on + the LocoNet data signal.

      Some commercial hardware which can provide LocoNet Data signal termination

      • BDL16, BDL162, BDL168

        The instructions in the BDL16x manual includes a section on how to use the BDL168x with a non-Digitrax layout. This section mentions setting one of the the BDL16x boards to act - as a LocoNet master. Doing this will set the BDL16x board - to provide LocoNet Data signal termination.

        -

        This is done by changing the value of OpSw 11 to "thrown" on - one of the BDL16x boards. Only one source of LocoNet - Data signal termination should be active at any time, so all - other BDL16x boards should be configured with OpSw 11 as - "closed", and all other sources of LocoNet Data signal - termination should be disabled or disconnected.

        + as a LocoNet master. This is done by changing the value of + OpSw 11 to "thrown" on one of the BDL16x boards. + Doing this will set the BDL16x board to provide LocoNet Data + signal termination. Only one source of LocoNet Data signal + termination should be active at any time, so all other BDL16x + boards should be configured with OpSw 11 as "closed", and all + other sources of LocoNet Data signal termination should be + disabled or disconnected.

                 </LI>
         <LI>PR3
             <p>Follow the instructions in the PR3 manual for enabling MS100 mode with LocoNet termination.

        @@ -242,21 +219,15 @@
        be necessary to manually force the PR3 to "MS100 mode with
        LocoNet termination" each time JMRI is started, just after JMRI
        starts up.


        -

        Because the PR3 would require manual intervention by the user
        - each time that JMRI is started when using PR3 to provide
        - LocoNet data signal termination, the PR3 is not recommended as
        - a source for LocoNet Data signal termination when used with JMRI.


        +

        Because manual intervention is required when JMRI is started, the
        + PR3 is not recommended as a source for LocoNet Data signal termination.



        • -
      • LocoBuffer-II, LocoBuffer-USB
        +
      • LocoBuffer, LocoBuffer-II, LocoBuffer-USB

        See the instructions for the appropriate hardware for the
        - required switch and/or jumper settings. These devices power
        - their LocoNet data signal termination using power provided by
        - the LocoNet RailSync wires.


        -
      • LocoBuffer
        -

        Some versions of the original LocoBuffer design allow the builder
        - to add components to provide LocoNet Data signal termination.
        - Consult your LocoBuffer documentation to determine whether your
        - hardware can provide LocoNet Data signal termination.


        + required switch and/or jumper settings. Per the documentation,
        + it will be necessary to provide a power source for the LocoBuffer
        + current source logic externally to the LocoBuffer via the RailSync
        + LocoNet wires.




      Do-it-yourself LocoNet Data Signal Termination


      @@ -281,22 +252,6 @@
      no electrical path back to any LocoNet wire, or if they connect
      the power supply negative terminal directly to the LocoNet "Ground" pins.


      Other Internet resources may show circuits for LocoNet termination.


      -

      Technical information about LocoNet Data Signal "Termination"


      -

      Technically, the term "termination" can be somewhat misleading. For our purposes,
      - LocoNet data signal "termination" is a current source which provides a
      - positive 15 mA current source from a +12V supply, and which is
      - connected to the LocoNet "Data" pins (pins 3 and 4), and which is
      - referenced to the LocoNet "Ground" pins (pins 2 and 5). This provides
      - a "pull-up" for the "wired-or" signaling used on the LocoNet "data" wires.


      -

      Some Digitrax documentation describes devices which can act as the LocoNet
      - "master", and other Digitrax documentation describe the "LocoNet Master" as
      - (in part) the LocoNet device which provides the current source for the
      - LocoNet data lines. So, the term "LocoNet Master" may sometimes imply
      - a device which can provide the LocoNet Data signal termination.


      -

      In this context, "data signal termination" does not refer to "electrical
      - transmission line termination". According to Digitrax documentation, there
      - should not be any need to provide "electrical transmission line termination" on
      - the LocoNet data signal.


      LocoNet RailSync Signal "Generation"


      As shown in the table above, some LocoNet devices require that the
      RailSync wires on the LocoNet cable are powered or are an accurate
      @@ -306,7 +261,7 @@
      at 12VDC is sufficient. In other cases, one or more LocoNet device
      requires an accurate representation of the DCC track signal on the
      standalone LocoNet cable.


      -

      RailSync power from a DC power supply


      +

      RailSync power from a power supply


      For cases where the standalone LocoNet does need to provide power to
      the RailSync lines but does not need to provide a low-power version
      of the DCC track signal, a simple power supply connected to the LocoNet
      @@ -335,9 +290,9 @@
      RailSync wires.


      If there is any concern about sneak paths between the power supply for the
      Digitrax command station and the Standalone LocoNet, then some sort of
      - isolation must be provided. Isolation of this nature is beyond
      - the scope of this documentation; opto-isolators could be used for
      - this purpose.


      + isolation must be provided.


      +

      Isolation of this nature is beyond the scope of this documentation;
      + opto-isolators could be used for this purpose.


      RailSync from a non-Digitrax command station


      The Digitrax BDL16x manual gives recommendations for providing a "RailSync+"
      signal from the "Rail A" output of a non-Digitrax DCC booster. This
      @@ -429,63 +384,10 @@
      is that a power supply should be connected to, at most, one type of
      board.



      Examples

      • Isolating the LocoNet throttle bus from LocoNet

      • Isolating the LocoNet throttle bus from LocoNet
        Turnouts, Detection & Signaling

      • The diagram below shows an example with a LocoNet-based command station and

      • throttles on a "primary" LocoNet, and a standalone LocoNet which
      • provides block detection, signal control, and control of switches.
      • In this example, devices on the "primary" LocoNet, including throttles,
      • cannot directly control switches or signals on the standalone LocoNet.

      • <img src="images/ThrottleLocoNetIsolatedFromStandaloneLocoNet.jpg"
      • alt="Example showing Throttle LocoNet isolated from Standalone LocoNet">

      • JMRI signal control logic can interpret the LocoNet block occupancy report messages

      • generated by the BDL168s, and can control signal aspects by generating
      • appropriate LocoNet messages to the SE8Cs. JMRI can also control
      • switches connected to the DS64. This type of connectivity may be useful
      • when JMRI is used to implement a CTC panel.

      • For the connectivity shown in this diagram, the DS64 should be

      • configured to take its switch control messages from LocoNet
      • instead of from its DCC track inputs. This should avoid some
      • reported instability of DS64s when connected to the DCC track signal.

      • This diagram assumes that there are no sneak current paths between any

      • device associated with the standalone LocoNet and any device associated
      • with the primary LocoNet. This allows connection of the Digitrax
      • command station's LocoNet "Ground" wire to the Standalone LocoNet "Ground"
      • wire. It also shows the use of two LocoBuffer-USB devices as computer
      • interfaces. These devices provide optical isolation of the signaling
      • between the "computer" side of the device and the "LocoNet" side of the
      • device, which eliminates "sneak current paths" between each LocoNet and
      • the computer. If one or more LocoNet interface device is used which
      • does not provide isolation, then there is a possibility that
      • "sneak current paths" could be present. See
      • "Sneak paths" and Computer Interfaces, above, for more information.

      • Switches (DS64), Detection (BDL168) and Signals (SE8C) with non-Digitrax DCC command station

      • The diagram below shows a possible implementation of a standalone LocoNet

      • for computer-controlled signaling using Digitrax BDL168 boards for
      • occupancy detection, Digitrax SE8C boards for driving signals, and
      • Digitrax DS64s for controlling switches. For this example, one of
      • the BDL168 boards should be configured to provide LocoNet data signal
      • termination.

      • <img src="images/SwitchesAndDetectionAndSignallingExample.jpg"
      • alt="Example showing DS64, SE8C, BDL168 and non-Digitrax Command Station">

      • JMRI signal control logic can interpret the LocoNet block occupancy report messages

      • generated by the BDL168s, and can control signal aspects by generating
      • appropriate LocoNet messages to the SE8Cs. JMRI can also control
      • switches connected to the DS64. This type of connectivity may be useful
      • when JMRI is used to implement a CTC panel.

      • The RailSync Generator block should be implemented as described in

      • RailSync from a non-Digitrax command station.

      • For the connectivity shown in this diagram, the DS64 should be

      • configured to take its switch control messages from LocoNet
      • instead of from its DCC track inputs. This should avoid some
      • reported instability of DS64s when connected to the DCC track signal.

      • This diagram assumes that an isolated computer interface is used to

      • prevent "sneak current paths" between the Standalone LocoNet and the
      • computer. If one or more LocoNet interface device is used which
      • does not provide isolation, then there is a possibility that
      • "sneak current paths" could be present. See
      • "Sneak paths" and Computer Interfaces, above, for more information.

      • SE8C signaling without a Digitrax command station

      • BDL16x with non-Digitrax DCC command station

      • SE8C signaling without a Digitrax command station


        The diagram below shows a possible implementation of a standalone LocoNet
        for computer-controlled signaling using Digitrax SE8C boards. The example
        assumes that detection information is not gathered from BDL168 boards
        @@ -495,21 +397,9 @@
        there is no need for a connection to the booster track outputs. But
        the LocoBuffer-USB requires RailSync power when it is in its LocoNet
        termination mode, so a RailSync power supply is shown.

      • LocoNet Data Signal Termination Diagram

      • In the diagram above, the RailSync Power Supply is implemented as

      • described in RailSync power from a DC power supply.


        -

        Acknowledgments

      • Among others, Elmer McKay and Dick Bronson have provided significant

      • input to the content of this page. Thank you!

      • LocoNet Data Signal Termination Diagram

        References

      -

      Information and support for Digitrax products may be found at the Digitrax website.


      -

      Information and support for the LocoBuffer-II, the LocoBuffer-USB, and

 
MongoDB Logo MongoDB