It reports the state of all of the 'possible' 239 inputs. The one thing that still seems to be outstanding that would be good to fix is the amount of 'chatter' that the DCC4PC computer interfaces generates on the RC-Link bus. The sensor is triggered but the train must be manually assigned to the block. A non-railcom equipped deocder in the block results in RocRail functioning as it would do with more 'standard' voltage drop occupancy detection (e.g. By creating a sensor and a block and then linking the sensor to the +in and -in events of the block, I am now able to place a Railcom decoder equipped train on the block and have it automatically assigned to the block by the software. I can now report that I have a functioning set-up! It would appear that the sensors are simply addressed from 1-16 for the first board. The discussions with the Rocrail guys have proved fruitful insomuch as Rob has helped to remove a lot of the 'noisiness' of the diagnostic traces that was slowing down Rocview (and effectively making it unusable) as well as correcting a couple of issues in the way that the RC-Link traffic was being turned into trace messages (so it is now easier to debug!). However, when placing the loco on the track I never see this change to report the address (it stays at 0000).Ĥ) How do I set up and address the 16 sensors? Again I couldn't find anything on the wiki to talk about addressing the sensors from the DCC4PC board via RC-Link.Īny help with the above very gratefully received! Is it telling me anything useful? Can I switch it off as it seems to make the interface unresponsive?ģ) In the controller trace I see something more encouraging: '00:13:11 detector reported address state direction ' where YY loops from 1 to 24. I have the following questions:ġ) I'm not sure what to put in the sensors configuration part of the controller screen (see attached screenshot) - the wiki doesn't seem to give help with this?Ģ) Once I power on, I see continuous scrolling in the server trace of: 'detector XX out of range'. I have added the controller as per specified on the wiki. Lenz LZV100 - v3.6 (I checked to ensure that the Railcom cutout was set propoerly).ĭCC4PC Railcom Reader - Set to address 1 (rather than the default of 0, as per the manual).ĭCC4PC Railcom Computer interface - Firmware updated to 1.4 (TAMS RC-Link compatibility mode).ġ single track section wired in to J1 of the Railcom Reader. I'm trying to use the DCC4PC Railcom Reader with Rocrail via the TAMS RC-Link compatibility mode and failing miserably!

Rocrail sensor set