Good day. I need help from those on the forum that use an ECOS to control their layout. I have an ECOS 50200, I also have a ECOSBoost. The layout it is split into two sections with the ECOS and the ECOSBoost having their own area to power. I have 50 engines on the layout but only run 4 at a time on the main lines. So while I know every engine is drawing some power even while sitting the vast majority of the engines are not being give any power, the lights are off and no sound is activated.

I use the shuttle feature on the ECOS to provide some animation. Primarily, I use it to have engines shuttle between coaling tower and turn table, railbuses making runs between village stations and the main station, and some switching in my port or industrial area.

I have created a total of 8 shuttle programs (that is the max that ECOS allows). These are very simple, feedback provided by two contact tracks and the engine running between each. Once occupied the feedback is provided and train stops and then waits before returning to the other contact track. Very basic stuff.

After adding the 8th shuttle scenario on the ECOS, the ECOS now shuts down when some of the occupancy tracks associated with the shuttle programs get occupied.

I did trouble shoot and I am sure that there is no short anywhere, I have switched the power source for the ECOS Detector providing the feedback, so I know it isn't a power source issue, and I even replaced the contact track to rule out any kind of short that I couldn't see or detect.

I had the problem with one track but after turning off the ECOS and changing the order in which I started running engines the problem switched to another contact track. So it wasn't even specific to a particular contact track or shuttle sequence.

I was able to remove the problem when I deleted all of the shuttles in the ECOS. I can now run the engine or wagon over the contact track and the feedback will show on the ECOS with no issue. The ECOS remains on and everything is running fine.

This leads me to believe it is a software glitch, the ECOS can't handle the computing in the shuttle program now (I am running the latest software 4.3.1 and see the shuttle inputs are much different than before), or I am doing something wrong when it comes to creating a shuttle.

Can anyone offer any suggestions?

Thanks,

Chris