Collecting Signaling Related Issues For Boston Sprinter Route

Discussion in 'TSW General Discussion' started by NB642, Aug 27, 2021.

  1. NB642

    NB642 Active Member

    Joined:
    Mar 19, 2018
    Messages:
    59
    Likes Received:
    149
    After watching the last DTG stream, I understand that the next logical improvement for the route from Boston to Providence will be to address the somewhat problematic signaling (both wayside and in the cab). Here is a list of possible issues that I have noticed from my time trying out the services:
    1. This is an issue that almost everyone else has already mentioned, but the alert curve for ACSES will frequently activate much too early in advance of the actual location for a reduction in track speed. The worst offender is probably the approach into Providence.
    2. The dispatcher will set signals to stop just ahead of a scheduled station stop even though there are no trains ahead or blocked junctions. When running with cab signaling on, it makes it nearly impossible to maintain a tight schedule if you are running only 20-30 mph far in advance of a station.
    3. The positive train stop (PTS) function should only be active for "home" signals (including interlockings and control points). Distant signals, automatic block signals, and code change points should not enforce an automatic stop - theoretically you should be able to freely cruise by them at 20 mph when at their most restrictive aspect (which is Restricting) with ACSES and ATC on.
    4. In most cases, when inside a yard, there should be no cab signal higher than restricting and ACSES should not be enforcing any speed. There are exceptions of course, but the only places where you should be getting cab signals above restricting, civil speed enforcement, and positive stop enforcement is at the signalized exit of the yard to and from the mainline tracks. For example, I may be wrong, but I doubt that Pawtucket Yard has ACSES enforcing the 5 mph limit on all tracks in reality. This is similar to how the tracks are protected at 20 mph (restricting cab signal) at Boston South Station even though the posted speed is 10 mph.
    5. The use of the Approach Medium 30 cab signal indication seems improper for this route. It should really only be used for enforcing diverging speeds at switches that are specifically limited to 30 mph. It should not be used in the signal progression for a Stop/Stop and Proceed signal since the Approach Medium 45 cab signal in combination with the Approach cab signal would fulfil the role of bringing the train down to 45 and 30 mph respectively for non-diverging routes. (to be honest the only real usage for the Approach Medium 30 cab signal in my opinion, would be in territory without intermediate block signals where a distinctive warning is needed in advance of and passing through medium speed switches that would normally be protected by a visible distant signal, i.e. NORAC Rule 562 territory)
    6. The signals at Cove Interlocking may be incorrect. Approaching from the north, the pot/dwarf signal near the end of the platforms at Back Bay shows medium approach indication (low signal with yellow over flashing red), but the cab signals immediately drop to restricting - the proper cab signal would be approach. Approaching from the south, I seem to get a restricting indication (high signal with red over steady yellow) with cab signals almost immediately upgrading to clear (or approach medium? - I can't remember which). This is out of place since restricting is mostly used when diverging into unsignaled track (yard, siding, etc.). If this was meant to be medium approach, then it should show red over flashing yellow (this is a high signal) and should have a cab signal of approach.
    7. The signals on the Stoughton branch seem to prevent you from ever reaching the max speed of the line. You are limited to 30 mph by an approach signal and brought down to restricting by a pot/dwarf signal on one of the sidings. Is this really supposed to be the case? It certainly makes it hard to be on time with the current timetable.
    8. I already mentioned this on another thread, but the MBTA aspect display unit is not working correctly. Both the F40 and CTC-3 cab ADU's have the "90" and "MAS" balloons lit up at the same time for most of the route when signals are clear. This is not accurate. The ADU can only display one aspect at a time, so it should either have the "90" or the "MAS" balloons lit but not both at the same time. For reference here are the codes associated with each cab signal:
      • 180 ppm / 180 ppm: should have "MAS" lit (this corresponds to "CLEAR 150" for Amtrak trains)
      • 180 ppm / 0 ppm: should have "MAS" lit (this corresponds to "CLEAR 125" for Amtrak trains)
      • 270 ppm / 270 ppm: should have "90" lit (this corresponds to "CLEAR 100" for Amtrak trains)
      • 120 ppm / 120 ppm: should have "80" lit (this corresponds to "CAB SPEED 80" for Amtrak trains)
      • 270 ppm / 0 ppm: should have "60" lit (this corresponds to "CAB SPEED 60" for Amtrak trains)
      • 120 ppm / 0 ppm: should have "45" lit (this corresponds to "APPROACH MEDIUM" for Amtrak trains - used for both Approach Medium and Approach Limited wayside signal aspects)
      • 75 ppm / 75 ppm: should have "30" lit (this corresponds to "APPROACH MEDIUM" for Amtrak trains - relatively new cab signal to differentiate between Approach Medium from Approach Limited)
      • 75 ppm / 0 ppm: should have "APP" lit (this corresponds to "APPROACH" for Amtrak trains)
      • 0 ppm / 0 ppm: should have "RES" lit (this corresponds to "RESTRICTING" for Amtrak trains)
      • 0 ppm / 0 ppm at interlocking or other signal where positive stop is enforced by ACSES: should have "STOP" lit (this corresponds to "STOP" for Amtrak trains)
    These are the points I could gather for now, but I will definitely add to the list if I find more specific cases for signal errors/inaccuracies.
     
    • Like Like x 29
    • Helpful Helpful x 1
  2. NB642

    NB642 Active Member

    Joined:
    Mar 19, 2018
    Messages:
    59
    Likes Received:
    149
    Update: For Item (7) above, I now realize that the Stoughton Branch is NORAC rule 562 territory (no fixed ABS signals) - so we should have more code change points between Canton Junction and Stoughton Station. I think this reinforces the point that we should be getting better signals and cab signals than approach and restricting (at least before the end of the tracks).
     
    • Like Like x 6
  3. Mattty May

    Mattty May Guest

    That’s a detailed list. Very interesting too.
     
    • Like Like x 3
  4. chieflongshin

    chieflongshin Well-Known Member

    Joined:
    Jan 4, 2019
    Messages:
    4,369
    Likes Received:
    7,214
    I’ve noticed this morning on two of the depot to station moves with the cab car In boston (early 3 and 4 am ) services you’ll get to the last signal before the station and It will be red . The go via marker is about 20 yards from red signal. I sat at this go via marker for about 20 mins earlier. I noticed that you have to almost roll up onto the signal for it to change.

    I think it’s changing perhaps a tad too late or the go via needs moving . If you hit that go via about 10mph you can just about have it amber as you meet it, anymore and you spad
     
    • Like Like x 1
  5. NB642

    NB642 Active Member

    Joined:
    Mar 19, 2018
    Messages:
    59
    Likes Received:
    149
    I have noticed similar behavior with the regular services too approaching Boston (Amtrak trains from Back Bay). It seems that the dispatcher signaling priority is directly linked to the placement of these go via markers (as well as possibly the station stops themselves).
     
    • Like Like x 1
  6. jeff.engle

    jeff.engle Active Member

    Joined:
    May 27, 2021
    Messages:
    115
    Likes Received:
    36
    Thank you for the detailed list. Nice to know that I’m not the only one seeing some of these issues.
     
    • Like Like x 2
  7. Jinoss17

    Jinoss17 Well-Known Member

    Joined:
    Aug 21, 2020
    Messages:
    495
    Likes Received:
    1,109
    Just hats off for your dedication. I would never do that myself.
     
    • Like Like x 2
  8. cActUsjUiCe

    cActUsjUiCe Developer

    Joined:
    Sep 21, 2017
    Messages:
    681
    Likes Received:
    2,179
    This is pretty much the same list we're tracking internally. Keep it going and great job!
     
    • Like Like x 12
    • Helpful Helpful x 1
  9. NB642

    NB642 Active Member

    Joined:
    Mar 19, 2018
    Messages:
    59
    Likes Received:
    149
    Great to hear and thanks to you and the rest of the team for keeping track of these points! These were the items that caught my attention, but I will certainly try to add on if I spot anything else.
     
    • Like Like x 2
  10. Ravi

    Ravi Well-Known Member

    Joined:
    Feb 2, 2021
    Messages:
    432
    Likes Received:
    423
    This is a great list. Thank you. I have also had the issue with the stop times when keeping up with ATC. hopefully DTG fixes it soon.
     
    • Like Like x 2
  11. redrev1917

    redrev1917 Well-Known Member

    Joined:
    Jul 22, 2021
    Messages:
    3,502
    Likes Received:
    7,692
    It appears that most of the issues with in cab signalling is caused by no dispatch beyond stations which causes red for every station stop and the resulting speed restrictions running up to it.

    What I can't understand is how Rivet could change the no dispatch beyond stations within days of Luzern release yet BS is still broken months later.
     
    • Like Like x 1
  12. cActUsjUiCe

    cActUsjUiCe Developer

    Joined:
    Sep 21, 2017
    Messages:
    681
    Likes Received:
    2,179
    This is only a portion of the issue. While the signal programming is clever, it has a lot of gaping holes.
     
  13. Mattty May

    Mattty May Guest

    Are you working on the signalling system with DTG?
     
  14. cActUsjUiCe

    cActUsjUiCe Developer

    Joined:
    Sep 21, 2017
    Messages:
    681
    Likes Received:
    2,179
    Not working with them on that. I'm just working on fixing it in my spare time (which I have none of right now). We'll see what happens someday. No promises.
     
    • Helpful Helpful x 1
  15. NateDogg7a

    NateDogg7a Well-Known Member

    Joined:
    Sep 8, 2021
    Messages:
    524
    Likes Received:
    756
    The "dispatch beyond station" bug was mentioned very soon after the release of NEC-BP. When I have time I will try to find that thread. This was especially prevalent at Canton Jct. northbound, resulting in very slow ATC approaches until you made the station stop. It was noted that DTG was aware of the issue, but that each instance had to be reported and fixed individually. Although, once the issue became apparent, it was supposedly fixed so as not to affect future DLCs. My recent runs have featured ATC restrictions from Sharon to Hyde Park with clear aspects, so...
     
  16. NateDogg7a

    NateDogg7a Well-Known Member

    Joined:
    Sep 8, 2021
    Messages:
    524
    Likes Received:
    756
  17. cActUsjUiCe

    cActUsjUiCe Developer

    Joined:
    Sep 21, 2017
    Messages:
    681
    Likes Received:
    2,179
    Not a bug, just an unfortunate design decision. It's much easier to get a timetable to successfully compile when you do not use Dispatch Beyond Instruction, simply because trains aren't reserving more signals at any given time. I know there were issues getting this timetable to compile toward the end.
     
    • Helpful Helpful x 2
    • Like Like x 1
  18. erg73

    erg73 Well-Known Member

    Joined:
    Apr 5, 2020
    Messages:
    872
    Likes Received:
    3,030
    Hopefully we will have the opportunity to enjoy your work in the future with different projects. What you did in Boston Sprinter seems to me spectacular, also taking into account that it is your first job in TSW. This game needs third developers with your talent and professionalism.
     
    Last edited: May 16, 2022
    • Like Like x 2

Share This Page