can-gcln-en
Differences
This shows you the differences between two versions of the page.
— | can-gcln-en [2020/07/06 14:51] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== CAN-GCLN ====== | ||
+ | [[english|{{ | ||
+ | [[: | ||
+ | * [[: | ||
+ | * [[: | ||
+ | * [[: | ||
+ | \\ | ||
+ | ^By Rob Versluis | ||
+ | \\ | ||
+ | | {{ : | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
+ | \\ | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== Firmware Programming ===== | ||
+ | |||
+ | Kits will be delivered with pre-programmed chips.\\ | ||
+ | Self programming of firmware is easily done with the right equipment, | ||
+ | and is not realy difficult.\\ | ||
+ | There are many ways to achieve that :\\ | ||
+ | * Pickit 2, Pickit3 both from Microchip. | ||
+ | * EasyPic from Mikroelektronika. | ||
+ | * MiniPro from https:// | ||
+ | |||
+ | and many others.\\ | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | \\ | ||
+ | |||
+ | ===== Introduction ===== | ||
+ | The **CAN-GCLN** is a CBUS-LocoNet(r) Bridge for sharing specific hardware modules not available on the other side of the bridge or just for migrating from LocoNet(r) to CBUS without loss of investments.\\ | ||
+ | \\ | ||
+ | // | ||
+ | |||
+ | |||
+ | \\ | ||
+ | ===== The Bottle Neck ===== | ||
+ | The bottle neck is the big difference between the CBUS and the LocoNet transfer rate.\\ | ||
+ | CBUS uses **125**KBit/ | ||
+ | This implicates that a burst on the CBUS side can't be broadcasted to the LocoNet side.\\ | ||
+ | The goal is to make a buffer as large as possible to deal with this, but filtering will be the best option to prevent overflows.\\ | ||
+ | |||
+ | \\ | ||
+ | |||
+ | ===== LocoNet CS with CAN-GC3 ===== | ||
+ | Together with **[[: | ||
+ | All needed commands are translated into CBUS and visa versa.\\ | ||
+ | To keep sessions alive at the CAN-GC3 side it automatically send every 10 seconds idle time a keep alive request for all active slots.\\ | ||
+ | This is needed because the default purge time in LocoNet Command Stations is much longer then the session timeout in the CAN-GC3.\\ | ||
+ | |||
+ | \\ | ||
+ | |||
+ | ===== Features ===== | ||
+ | * Support for Digitrax **[[: | ||
+ | * Support for Uhlenbrock **Lissy**(IR) and **MARCo**(Railcom(r)) Receivers. | ||
+ | * Support for **[[: | ||
+ | * Fast clock from CBUS to LocoNet | ||
+ | * Jumper to enable power on the RJ12 connectors. | ||
+ | * Loconet throttle support; Dispatch from Loconet and CBUS. | ||
+ | * Rocrail connected on the Loconet side. | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * Loco 8 functions and lights. | ||
+ | * Start of Day LocoNet -> CBUS. | ||
+ | * Service track: R/W CVs. | ||
+ | * Programming on the main: PoM. | ||
+ | * Slot ping after 10 sec idle. | ||
+ | * Extra feature | ||
+ | |||
+ | \\ | ||
+ | ===== Dispatching a Loco ===== | ||
+ | Before the dispatch command the loco must have a valid CBUS session which can be forced by a zero speed command in Rocview.\\ | ||
+ | Without a CBUS session it is not possible to dispatch a loco for a FRED(i) or other LocoNet throttle.\\ | ||
+ | |||
+ | |||
+ | |||
+ | \\ | ||
+ | ===== Filtering ===== | ||
+ | Filtering is needed from CBUS to LocoNet because CBUS makes no distinction between input and output accessory events. | ||
+ | |||
+ | \\ | ||
+ | ===== Address mapping ===== | ||
+ | * [[: | ||
+ | |||
+ | \\ | ||
+ | |||
+ | < | ||
+ | ===== Setup ===== | ||
+ | {{: | ||
+ | |||
+ | ==== LocoNet ==== | ||
+ | === Read only === | ||
+ | Only LocoNet packets are translated to CBUS, not visa versa.\\ | ||
+ | === CBUS sensor events === | ||
+ | Enable the CBUS sensor filter.\\ | ||
+ | === Start of day === | ||
+ | Translate "CBUS Start of Day" to LocoNet to get the actual LocoNet sensor status.\\ | ||
+ | \\ | ||
+ | |||
+ | ==== CBUS ==== | ||
+ | === CANID === | ||
+ | The ID on the CAN bus.\\ | ||
+ | === SoD === | ||
+ | Start of Day event number.\\ | ||
+ | === Switch filter === | ||
+ | Filter definition for the event number range to be translated from CBUS to LocoNet as switch requests.\\ | ||
+ | === Sensor filter === | ||
+ | Filter definition for the event number range to be translated from CBUS to LocoNet as sensor reports.\\ | ||
+ | |||
+ | |||
+ | |||
+ | \\ | ||
+ | ===== Jumper settings ===== | ||
+ | ^ Jumper | ||
+ | | JP1 | jumper set | 120 Ohm terminator to Can bus connected | ||
+ | | JP2 | jumper 1-2 | +12V to RJ12 connector railsync + line | | ||
+ | | JP2 | jumper 2-3 | Railsync+ from central unit to RJ12 connector railsync+ line | | ||
+ | | JP3 | jumper set | 15 mA Current source Loco-I/O line | | ||
+ | \\ | ||
+ | ===== LocoNet current source, what is that? ===== | ||
+ | \\ | ||
+ | Click [[LNet_current_source-en| __here__ | ||
+ | |||
+ | ===== Hardware ===== | ||
+ | | {{: | ||
+ | | {{: | ||
+ | | {{: | ||
+ | | {{: | ||
+ | ^ N.B. Only complete ordered kits will be supported! ^ | ||
+ | {{: | ||
+ | |||
+ | |||
+ | |||
+ | ===== The final board ===== | ||
+ | {{: | ||
+ | |||
+ | |||
+ | |||
+ | ==== Connectors, LEDS and Jumpers==== | ||
+ | |||
+ | ^ Connector ^ Description ^ | ||
+ | | J1 | CAN-GCA | | ||
+ | | J2 | CAN-GCA | | ||
+ | | J3 | MERG | | ||
+ | | J4 | GCA LocoNet | | ||
+ | | J5 | GCA LocoNet | | ||
+ | | J6 | RJ12 LocoNet | | ||
+ | | J7 | RJ12 LocoNet | | ||
+ | | ICSP1 | PIC Programming | | ||
+ | \\ | ||
+ | |||
+ | ===== Jumpers ===== | ||
+ | |||
+ | ^ Jumper ^ Description ^ Remark | ||
+ | | JP1 | CAN Termination | ||
+ | | JP2 | LocoNet 12V on RailSync | ||
+ | | JP3 | 15 mA source to LoocNet signal line | ||
+ | \\ | ||
+ | ===== Led signalling ===== | ||
+ | |||
+ | ^ LED ^ Description ^ | ||
+ | | 1 | CBUS read activity | | ||
+ | | 2 | CBUS write activity | | ||
+ | | 3 | LocoNet read activity | | ||
+ | | 4 | LocoNet write activity | | ||
+ | | 5 | Run | | ||
+ | | 6 | FLiM Programming, | ||
+ | \\ | ||
+ | |||
+ | ===== Files ===== | ||
+ | * https:// |