Unless the dispatcher found a special button, this can't be what is actually going on out there.

_________________
- Back Online!

I've noticed a few things that are not right also, I just assumed it was an error somewhere between capturing the signal and converting it to data, then sending it back to us. it must get scrambled somehow.

Or you just clicked on one of the lights when the CP was cleared.

_________________
A BNSF fan by default.

Mike, since Union Jct. is showing up in blue there, the indication packets from the field were missed. It's not your fault, it's just they weren't heard, like a faint scanner transmission. You're right, that DS display image would not be possible in the field.

Since Mississippi St. is showing up in red, you can trust that indication packet from the field.

It is possible the DS hit the wrong "button" at Union Jct., but obviously the field wouldn't allow conflicting movement.

Should Interstate be working or is it not ATCS anymore? It hasn't worked for a while now.

_________________
- Back Online!

900 Hrz. its been like that for a few weeks now. I got sick of looking at all the red blocks and removed it from the MCP packet. now it just says "No data recieved"

_________________
A BNSF fan by default.

CP Interstate is an enigma right now. It is NOT on ATCS as far as we can tell, and its evidently clear the ARES has been turned off. More than likely, BNSF communications sets this us for "triple redundancy" meaning 3 different protocols will exist simultaneously should one fail. With all the work going on around CP 163 and the Fridley Northstar station (rumored to be 5 tracks wide through this stretch??) I'm guessing there is still much more to come.

I can't imagine Interstate would be permanently off the air from ATCS with the recent upgrades of every other surrounding control point to ATCS.

Staying tuned....