I use atlas tracks to make a 7 track parking area. Seems the dcs signal from my mth tiu cant find my engines when I power each track using those mechanical atlas connector switches. The swithches have a positive and negative wire feed in from my junction. the junction has negative and positive feeds from my mth tiu. the junction then has feeds to my layout tracks, negative and positive and also feeds to the atlas switches that turn the parking tracks on and off with fibre pins on the middle rail. my mth z4000 and mth tiu and mth wifi brick all plug in a power brick. I power the system on, the tiu and wifi unit power up and are found, turn the atlas switches on for the parking tracks on then turn the handle on my z4000 on. the mth software app on my phone then doesnt find the proto 2 or 3 engines on the parking tracks. the tiu is set super mode on, instruction indicating super mode with find my dcs on any track. if I dont do a cold boot, meaning turning everything off, I can turn my z4000 off and on, tiu still on, and the engines are found active by the mth dcs phone app. however, if I turn all power off, tiu and z4000, the engines on the parking tracks are inactive and not found. I must pick up and move the engines off the parking tracks to the tracks on my main run, and then the engines are now found on that main run track. I wanted these parking tracks so that I avoid picking up my premier, very heavy mth proto 2 and 3 engines. but it seems with a cold boot and reboot( everything on and off), I must carry the engines from the parking tracks to my main run for the app to find them active. I believe the dcs system uses the negative rails to communicate back to the mth tiu. why when I turn only the z4000 off, leaving the tiu on , the engines on the 7 parking tracks are found and active but if I turn everything off and on, the parking track engines are inactive and not found. and i noticed if I turn the z4000 handle on first, then power up the parking tracks with the atlas switch, the engines start in convention mode. if I turn the atlas power switch on first, then turn the z4000 handle on, the engines are found and are active dcs units not conventional. one option is to remove the fibre pins from 4 of the 7 parking tracks so that it has dcs 18 volts all the time for my proto 2 and proto 3 engines and then use the 3 remaining parking tracks with fibre pins and the atlas power switches for my many mth proto 1 engines which only run conventional, not dcs. But, Im missing why dcs isnt finding my engines on a cold reboot. spent hours and hours so far. can these atlas connector switches be used for both proto1 and proto2/3 on the same parking track. seems the dcs signal doesnt penetrate the atlas connector switches after a cold reboot.
Original Post
