Anyone have any experience controlling Bachmann DCC turnouts in DCC++ or JMRI? Bachmann programs a default address of 3 into each DCC turnout but the DCC++ controller can't find it.
This may help. On my (non Bachmann turnout decoders, you need to enter a programming mode. They can't be "read" as they have no load. http://www.bachmanntrains.com/home-usa/ez_content/EZ_Command_DCC_Turnout_Instructions.pdf This manual describes getting to program mode, on a Bachmann turnout. Sent from my iPhone using Tapatalk
Programming and controlling the turnouts on EZ Command is not the issue. The issue is controlling and programming the turnouts with JMRI over the DCC++ Base Station is. I'm trying to get JMRI to talk to my Bachmann DCC Turnouts on the layout through my DCC++ Base Station. Tried configuring the turnouts using the 'Indexed DCC Accessory Control' method outlined in the article link below: http://jmri.sourceforge.net/help/en/html/hardware/dccpp/Turnouts.shtml The first turnout (RH Crossover) I tried with an ID of 1, address of 1 and sub address of zero actually threw the switch, and I got excited but then the turnout would not close or operate again. Frustrating! But JMRI did communicate with the Crossover which is encouraging. However, no other combination of ID, address or sub-address worked again. I feel I'm getting close but still not there. Anyone else have any experience with Bachmann DCC turnouts on their DCC++ layouts? Any advice here? I've asked this same question on the JMRI forum and the DCC++ Facebook group.
Seems I have hit this issue as well and have googled for days to no avail. Does anyone have ez-track DCC turnouts working with either DCC++ or DCC++EX? If so could you explain how they are configured? I'd also be interested in any info on the actual commands a Bachmann E-Z Command base station puts out or any other technical info on these turnouts outside of the standard marketing material.
Got it sorted. It seems DCC++EX might not be there yet as it relates to turnout control. Moving to DCC++ seems to have helped as I can now throw the turnouts however it seem that after a short period of time this functionality is lost and I don't see the messages in the DCC++ traffic monitor. This could be power related so I bought a Tam Valley booster to see if that helps. For those Googling for an answer the Bachmann DCC turnouts use standard locomotive DCC address 9 and whatever address you programmed them for as the function number. In my case I used the Bachmann command center to program. I do not believe they respond to (a) accessory or (T) turnout DCC commands. Now to figure out how to tell JMRI to use then in routes.
