search

ecgconnelly / uss8

Run8 external dispatching program based on Hawk777's iecc8, with Union Switch and Signal styled UI
GNU General Public License v3.0
0 stars 0 forks source link

Signal 28 won’t clear #32

Open Hawk777 opened 1 year ago

Hawk777 commented 1 year ago

I was unable to clear signal 28 in either direction in USS8, even though there were no conflicting occupancies or routes set, and the signal cleared fine in F3. It would make the code noise and drop out the lamps, but come back with the red signal indication lamp still lit.

ecgconnelly commented 1 year ago

Oops, I didn't think anyone would actually try to use that signal. Looking at it now, I'm not sure of the best way to handle this - the UP CTC switch just west of the crossing complicates it a bit. I don't think the BNSF desk should have control of that switch, but clearing signal 28 will route-lock it. Maybe instead of having a signal lever for 28, we should have a 29 Lock/Unlock lever that, when unlocked, allows the UP dispatcher to clear their signals at Calwa.

It might be possible at some point to model the "UP dispatcher" calling us on the phone or have a a TOL on the UP so we know there's a train needing to cross.

Hawk777 commented 1 year ago

Ah, I just thought it made life a bit more fun to have trains crossing over the territory (even if I have to adjust some switches and some additional signals in F3), rather than just running end to end. I’m not sure what the prototypical option would be.

ecgconnelly commented 1 year ago

Oh agreed, we should definitely have some way to deal with crossing traffic. Shouldn't be too awful...

2-8-4 commented 1 year ago

I've stumbled on this situation at all three crossings.

That's why I thought of annunciator lamps at Calwa Crossing. To announce the BNSF dispatcher a train wants to cross and have signal 28 cleared.

Two track circuits into the single annunciation lamp at L and one at R?