tams-railcom-en
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | tams-railcom-en [2018/11/12 08:56] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ======Tams RailCom RC-Link====== | ||
+ | [[: | ||
+ | [[english|Content]] -> **[[english# | ||
+ | * [[: | ||
+ | \\ | ||
+ | |||
+ | \\ | ||
+ | |{{http:// | ||
+ | | [[http:// | ||
+ | \\ | ||
+ | \\ | ||
+ | ===== Links ===== | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | |||
+ | |||
+ | \\ | ||
+ | |||
+ | ===== Versions ===== | ||
+ | ^ Component ^ Version ^ Remark ^ | ||
+ | | RC-Link | Firmware 1.5 | | | ||
+ | | Rocrail | 5699+ | Older revisions do not support the RCD-8. | | ||
+ | | **[[: | ||
+ | |||
+ | \\ | ||
+ | |||
+ | ===== Communication Setup ===== | ||
+ | Select **[[: | ||
+ | * baudrate: 19200 | ||
+ | * handshake: CTS | ||
+ | The __**[[# | ||
+ | |||
+ | \\ | ||
+ | |||
+ | ===== Test results ===== | ||
+ | ^ Function ^ RCD-1 ^ RCD-8 ^ | ||
+ | | RailCom detection | Yes | Yes, but too slow. ((Not usable for auto mode.)) | | ||
+ | | Current detection | No | Yes ((Multiple repeated reports: One for the RailCom address and one for the occupancy; Rocrail filters it out.)) | | ||
+ | | Multiple RailCom decoders in one section | Address zero is reported. | No report. | | ||
+ | | POM CV read | Yes | Yes | | ||
+ | |||
+ | \\ | ||
+ | |||
+ | ===== POM CV Read Reporting ===== | ||
+ | If the used command station supports read CV on the main, like **[[: | ||
+ | < | ||
+ | 20100220.140925.442 r9999c rclinkre ORcLink | ||
+ | </ | ||
+ | Those values will be shown in the Rocview programming dialog.\\ | ||
+ | |||
+ | \\ | ||
+ | ===== Considerations ===== | ||
+ | * Limitation of 24 detectors per RC-Link. (3 x RCD-8...) | ||
+ | * Extra bus wiring; Max. length is not known. (RS485) | ||
+ | * If no RailCom addresses are detected, or only seldom, the booster wires should be swapped on the RCD-x unit. | ||
+ | * The CV POM read does not report the CV number but only the value so the host program must save the number and hopes the read match to it. | ||
+ | |||
+ | |||
+ | \\ | ||
+ | |||
+ | ===== Device ===== | ||
+ | ==== Mac OS X ==== | ||
+ | The **[[: | ||
+ | On the MacBook, running OS X 10.6, the device name is: | ||
+ | < | ||
+ | / | ||
+ | </ | ||
+ | |||
+ | |||
+ | \\ | ||
+ | ==== Linux ==== | ||
+ | The RC-Link is bind in the system without special device drivers and is most likely named as: | ||
+ | < | ||
+ | / | ||
+ | </ | ||
+ | |||
+ | Check the kernel messages for the right device name. | ||
+ | === / | ||
+ | < | ||
+ | usb 2-2: New USB device found, idVendor=0403, | ||
+ | usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 | ||
+ | usb 2-2: Product: FT232R USB UART | ||
+ | usb 2-2: Manufacturer: | ||
+ | usb 2-2: SerialNumber: | ||
+ | usb 2-2: FTDI USB Serial Device converter now attached to ttyUSB0 | ||
+ | usbcore: registered new interface driver ftdi_sio | ||
+ | </ | ||
+ | |||
+ | \\ | ||
+ | |||
+ | ==== Windows ==== | ||
+ | The device driver can be downloaded here if the used Windows version do not provide direct support: | ||
+ | * http:// | ||
+ | |||
+ | |||
+ | \\ | ||
+ | ===== Ident Sensor Setup ===== | ||
+ | :!: Before Rocrail can handle loco identification it is a prerequisite that this is set on the [[http:// | ||
+ | |||
+ | ==== Recommended Wiki Pages ==== | ||
+ | * [[sensors_and_blocks-en# | ||
+ | * **[[loc-gen-en# | ||
+ | * [[sensor-bi-directional-en|Bi-Directional Communication]] | ||
+ | |||
+ | |||
+ | \\ | ||
+ | |||
+ | ===== Startup ===== | ||
+ | After setting up the connection to RC-Link the following messages will confirm a valid configuration: | ||
+ | < | ||
+ | 20130809.082156.222 r9999I rclinkre ORcLink | ||
+ | 20130809.082156.882 r9999c rclinkre ORcLink | ||
+ | 20130809.082157.659 r9999c rclinkre ORcLink | ||
+ | 20130809.082157.659 r9999c rclinkre ORcLink | ||
+ | ... | ||
+ | </ | ||
+ | |||
+ | |||
+ | \\ | ||
+ | |||
+ | ===== Address and Placing Reporting ===== | ||
+ | If all components are connected according the manufacturer manuals the reporting of decoder addresses will take place as soon a loco runs in a detected track section: | ||
+ | < | ||
+ | 20100219.090833.065 r9999c rclinkre ORcLink | ||
+ | 20100219.090845.826 r9999c rclinkre ORcLink | ||
+ | </ | ||
+ | RCD-1 reported the Lenz Köf with address 4958 in block b1:\\ | ||
+ | {{: | ||
+ | The direction represents the real placing of the loco on the tracks. Running through a reversing loop will swap this flag.\\ | ||
+ | This direction flag is only displayed but not processed to determine the placing to avoid conflicts with the software placing flag in Rocrail.\\ | ||
+ | |||
+ | ==== Example ==== | ||
+ | <code xml> | ||
+ | <plan rocrailversion=" | ||
+ | <zlevel title=" | ||
+ | < | ||
+ | <fb id=" | ||
+ | </ | ||
+ | < | ||
+ | <bk id=" | ||
+ | <fbevent id=" | ||
+ | </bk> | ||
+ | </ | ||
+ | < | ||
+ | <lc id=" | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | \\ | ||
+ | If the block is free, or the occupying loco is idle, the matching loco with the reported Identifier is set in this block: | ||
+ | < | ||
+ | 20100220.162810.365 r9999c rclinkre ORcLink | ||
+ | 20100220.162810.366 r9999W rclinkre OBlock | ||
+ | 20100220.162810.366 r9999I rclinkre OLoc 1695 cmd " | ||
+ | 20100220.162810.366 r9999I rclinkre OBlock | ||
+ | 20100220.162810.366 r9999I rclinkre OBlock | ||
+ | 20100220.162810.366 r9999I rclinkre OBlock | ||
+ | </ | ||
+ | {{: | ||
+ | In this example the Talent with Identifier " | ||
+ | |||
+ | |||
+ | |||
+ | \\ | ||
+ | |||
+ | ===== Gallery ===== | ||
+ | ==== Test environment ==== | ||
+ | {{: | ||
+ | |||
tams-railcom-en.txt · Last modified: 2018/11/12 08:56 by 127.0.0.1