Page 1 of 1
| Wrong route call for Bangor incorrect on ECS 17/01/2021 at 14:01 #136499 | |
Dionysusnu
577 posts 
|
A train with the attached timetable, running from Llandudno Junction to Bangor ECS, will give an incorrect wrong route call at BR6, if routed non-stop. It seems to check if it stops at Bangor, but does not notice that it passes twice, with the first one being non-stop. The snapshot save is from before the call, the manual save is from after I answered the call with "wait 5 minutes for correct route" 
Post has attachments. Log in to view them. Last edited: 17/01/2021 at 14:03 by Dionysusnu Reason: None given Log in to reply |
| Wrong route call for Bangor incorrect on ECS 17/01/2021 at 14:59 #136501 | |
headshot119
4869 posts |
It's not an easily solvable one in simulation data unfortunately. You could change the timetable to be a through line stop at Bangor, but you'd then have a risk of 2E56 starting from the through line. The other option is to split the schedule at BR32. "Passengers for New Lane, should be seated in the rear coach of the train " - Opinions are my own and not those of my employer Log in to reply |
| Wrong route call for Bangor incorrect on ECS 17/01/2021 at 15:38 #136502 | |
|
Dionysusnu
577 posts
|
And another incorrect wrong route call, 0L54 is at reverse HJ12 and calls in about not being routed to a location it has passed earlier, HJ48. Full journey is Saltney Junction rev HJ48 rev HJ12 Holywell Junction Up Siding, join 9S00 Post has attachments. Log in to view them. Log in to reply |
| Wrong route call for Bangor incorrect on ECS 17/01/2021 at 15:47 #136503 | |
jc92
3683 posts
|
Dionysusnu in post 136502 said:And another incorrect wrong route call, 0L54 is at reverse HJ12 and calls in about not being routed to a location it has passed earlier, HJ48.This looks like my 1991 timetable. I've just checked using your download and 0L54 has a valid timetable. I was concerned it may have somehow become invalid in an update. I have no explanation for either anomaly. This timetable was tested end to end prior to release twice and I'd never encountered either issue. "We don't stop camborne wednesdays" Log in to reply |
| Wrong route call for Bangor incorrect on ECS 17/01/2021 at 15:51 #136504 | |
|
Dionysusnu
577 posts
|
jc92 in post 136503 said:Dionysusnu in post 136502 said:And another incorrect wrong route call, 0L54 is at reverse HJ12 and calls in about not being routed to a location it has passed earlier, HJ48.This looks like my 1991 timetable. I've just checked using your download and 0L54 has a valid timetable. I was concerned it may have somehow become invalid in an update. It is indeed. But modified, because some trains had invalid timetables at first. 0L54's timetable is valid in the analyser, and also seems normal to common sense. I believe it is just the wrong route code being incorrect. Something to note is that the very similar scenario to Bangor, at Holywell Junction with 0L54, did not cause the same issue. It has a stop at Holywell Junction, but it is not the first time it passes the location. Same as 5E56 at Bangor. 0L54 accepted the route HJ2-HJ3-HJ4 just fine. Log in to reply |
| Wrong route call for Bangor incorrect on ECS 17/01/2021 at 15:58 #136505 | |
|
jc92
3683 posts
|
Version 1.0.2 uploaded pending approval. I've fixed the handful of affected trains at Bangor. I've also fixed those invalid timetables which required platform numbers at Llan junction only. something that also slipped through the release copy was 9S00 needs a N: 8L54 activity at Holywell which I've now reentered.
"We don't stop camborne wednesdays" Log in to reply The following user said thank you: Dionysusnu |
| Wrong route call for Bangor incorrect on ECS 17/01/2021 at 17:53 #136514 | |
|
Dionysusnu
577 posts
|
One more thing - 9S00's initial length seems to be wrong.
Log in to reply |
| Wrong route call for Bangor incorrect on ECS 17/01/2021 at 18:00 #136515 | |
|
jc92
3683 posts
|
Dionysusnu in post 136514 said:One more thing - 9S00's initial length seems to be wrong.sorted that too - it was still custom not 20 dogfishes. "We don't stop camborne wednesdays" Log in to reply The following user said thank you: Dionysusnu |
| Wrong route call for Bangor incorrect on ECS 19/01/2021 at 14:14 #136594 | |
|
Dionysusnu
577 posts
|
And another invalid wrong route call, reverse HJ48 to Holywell Junction Up Siding thinks it should go back to Rockcliffe Hall, because it came from Saltney Junction.
Post has attachments. Log in to view them. Log in to reply |
| Wrong route call for Bangor incorrect on ECS 19/01/2021 at 15:54 #136595 | |
|
Stephen Fulcher
2076 posts |
Which train from which timetable?
Log in to reply |
| Wrong route call for Bangor incorrect on ECS 19/01/2021 at 17:10 #136602 | |
|
Dionysusnu
577 posts
|
It's not a TT issue, but 8L54 from Summer 1991 by jc92.
Log in to reply |
| Wrong route call for Bangor incorrect on ECS 19/01/2021 at 17:47 #136610 | |
|
Stephen Fulcher
2076 posts |
It can be a timetable issue. There are many schedules that have had to be split in the 2015 set - for instance the RHTT on Valleys - to cover the circumstances of wrong route coding. The other reason for knowing which timetable is it makes it easier to track down and test what happens. Log in to reply |