Page 1 of 1
| Two weird behaviours... 24/04/2011 at 10:09 #2919 | |
Quaxo76
17 posts |
I just noticed two things that puzzled me. First: I had 2K09 entering from Spalding. It entered on time, and the F2 screen showed it running at 45mph; but presently it started reporting being late. The delay increased steadily, just as if it was stuck somewhere (except it wasn't); when the delay reached 13 minutes, it suddenly was reported on time again. I saw the train descriptor color change from green, to yellow, to red, to green again. And then, when it arrived at PBRO, it was 6 minutes early. The same thing happened almost at the same time with 1L04, entering from Ketton. It entered on time, then the delay grew to 4 minutes, then suddenly dropped to 0. I have a save-file with both trains showing delay. Another thing: two LCs, mainly Holme and Holme lode, sometimes close late. I had them slow down both 1A13 and 1A14, for example. And they were 125mph trains, which when showed the yellow signal, dropped to about 80mph before seeing green again and accelerating. And as it takes some time to go back from 80 to 125, they lost time. Again, is this something to be expected or a problem in the simulation? Thanks, Cristian Save file Log in to reply |
| Two weird behaviours... 24/04/2011 at 10:09 #15319 | |
|
Quaxo76
17 posts |
I just noticed two things that puzzled me. First: I had 2K09 entering from Spalding. It entered on time, and the F2 screen showed it running at 45mph; but presently it started reporting being late. The delay increased steadily, just as if it was stuck somewhere (except it wasn't); when the delay reached 13 minutes, it suddenly was reported on time again. I saw the train descriptor color change from green, to yellow, to red, to green again. And then, when it arrived at PBRO, it was 6 minutes early. The same thing happened almost at the same time with 1L04, entering from Ketton. It entered on time, then the delay grew to 4 minutes, then suddenly dropped to 0. I have a save-file with both trains showing delay. Another thing: two LCs, mainly Holme and Holme lode, sometimes close late. I had them slow down both 1A13 and 1A14, for example. And they were 125mph trains, which when showed the yellow signal, dropped to about 80mph before seeing green again and accelerating. And as it takes some time to go back from 80 to 125, they lost time. Again, is this something to be expected or a problem in the simulation? Thanks, Cristian Save file Log in to reply |
| Two weird behaviours... 24/04/2011 at 11:59 #15321 | |
postal
5265 posts |
Cristian The Down line speed is restricted down from 125mph to 105mph from Holme Lode crossing (at 70m 02ch), and then further restricted to 100mph from 71m 00ch to 72m 00ch. It changes to 115mph as far as 75m 24ch, reverting to 105mph until 76m 31ch (Peterborough Station). It is then raised to 115mph and back to full line speed (125mph) at 76m 70ch. Some of the slow acceleration you have recorded may actually have been trains running at full permitted speed. Reference is National Baseline Declaration, 1 April 2009. Details of how to download this are at Posting #19 here. JG “In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe Log in to reply |
| Two weird behaviours... 26/04/2011 at 04:44 #15359 | |
|
Quaxo76
17 posts |
Hi Postal, Thank you for your reply. The restrictions you mention may be the cause for the slow acceleration. But I still think that the LC's act a little slow, especially if they have to lower twice in a row. Just a few minutes ago, I had a 125mph train slow down to about 40, because it was shown a yellow signal because the crossing wasn't clear yet. Is it possible that after a train passes, the LC raises the bars even if another train is approaching, and then it can't lower again for a certain amount of time? Cristian Log in to reply |
| Two weird behaviours... 26/04/2011 at 08:16 #15361 | |
|
postal
5265 posts |
Quaxo76 said:Correct - so if you have two trains running block and block or a train has just passed in the opposite direction, there will be a delay in the crossing dropping. “In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe Log in to reply |
| Two weird behaviours... 26/04/2011 at 09:52 #15363 | |
|
Quaxo76
17 posts |
OK, thank you! 
Log in to reply |
| Two weird behaviours... 26/04/2011 at 13:16 #15366 | |
|
clive
2789 posts |
The first thing is a known problem. I can't remember the cause or whether it's been fixed in newer simulations, but it only happens where you have very long block sections without signals. ARS ignores the crossings when setting routes. The "two greens" rule should give enough time for the crossing to lower, but this may need some tuning (in the simulation - nothing you can do about it). When a crossing raises, there's a minimum time (something like 30 seconds simulation time) before it can lower again. If you think this will be a problem, you need to hold the crossing down by hand, for example by setting a route across it on the opposite line. Log in to reply |
| Re: Two weird behaviours... 10/05/2012 at 15:31 #32225 | |
|
Aurora
183 posts |
Started playing Peterborough a few days ago. " said: Just a few minutes ago, I had a 125mph train slow down to about 40, because it was shown a yellow signal because the crossing wasn't clear yet. The train deccelerates because it is running at a fast speed and the driver must deccelerate until such time as the signals change to a double yellow signal (in general circumstances from my experience with the sims, before LCs it'll go straight to green once the barriers are down as long as the following few sections are clear) where the driver will then start accelerating again. The specific 40kph would be the speed that drivers use as they know that a red signal will not be too far away and they will then deccelerate when approaching a red signal to stop until such time as the signal clears. The barriers stay down until there are no more lit-up paths across it. Once there are no more lit-up paths, the LC barriers will then be raised until the next time a train is pathed across it. About the thirty seconds thing posted by another user above, I haven't noticed it in my recent play. Nil. Last edited: 10/05/2012 at 15:35 by Aurora Log in to reply |
| Re: Two weird behaviours... 15/05/2012 at 15:53 #32353 | |
|
clive
2789 posts |
" said:It's definitely in the code, though it can be set to a different value for each crossing during development. Log in to reply |
| Re: Two weird behaviours... 15/05/2012 at 15:55 #32354 | |
|
clive
2789 posts |
" said:First: I had 2K09 entering from Spalding. It entered on time, and the F2 screen showed it running at 45mph; but presently it started reporting being late. The delay increased steadily, just as if it was stuck somewhere (except it wasn't); when the delay reached 13 minutes, it suddenly was reported on time again. I saw the train descriptor color change from green, to yellow, to red, to green again.The very long track circuits on that section confuse the "is the train on time" logic. It's a low-priority bug that will get fixed one day. The Uffington line behaviour has the same cause. Log in to reply |
| Re: Two weird behaviours... 16/05/2012 at 11:05 #32365 | |
|
Aurora
183 posts |
" said:" said:First: I had 2K09 entering from Spalding. It entered on time, and the F2 screen showed it running at 45mph; but presently it started reporting being late. The delay increased steadily, just as if it was stuck somewhere (except it wasn't); when the delay reached 13 minutes, it suddenly was reported on time again. I saw the train descriptor color change from green, to yellow, to red, to green again.The very long track circuits on that section confuse the "is the train on time" logic. It's a low-priority bug that will get fixed one day. The Uffington line behaviour has the same cause. The train 'delay time' accumulates while the train doesn't progress to the next track circuit? Nil. Log in to reply |
| Re: Two weird behaviours... 16/05/2012 at 21:45 #32375 | |
GeoffM
6377 posts 
|
" said:" said:Well, it's by train describer berth rather than track section (as per real life) but the interpolation calculations can get skewed by long sections, as Clive said." said:First: I had 2K09 entering from Spalding. It entered on time, and the F2 screen showed it running at 45mph; but presently it started reporting being late. The delay increased steadily, just as if it was stuck somewhere (except it wasn't); when the delay reached 13 minutes, it suddenly was reported on time again. I saw the train descriptor color change from green, to yellow, to red, to green again.The very long track circuits on that section confuse the "is the train on time" logic. It's a low-priority bug that will get fixed one day. The Uffington line behaviour has the same cause. SimSig Boss Log in to reply |
| Re: Two weird behaviours... 16/05/2012 at 22:50 #32377 | |
|
Stephen Fulcher
2084 posts |
CCF in reality is just as bad.
Log in to reply |
| Re: Two weird behaviours... 18/05/2012 at 02:16 #32391 | |
|
mfcooper
707 posts |
" said:CCF in reality is just as bad.The is not a high enough of a value of Yes that i can use to support this statement. Especially when there is a collection of pathing time (or similar) in a schedule. Log in to reply |
| Re: Two weird behaviours... 18/05/2012 at 11:28 #32395 | |
|
Stephen Fulcher
2084 posts |
I am strugging to understand that post Matt. CCF in case anyone wonders, is the system used in control centres to track trains based upon the TD indications and TRUST inputs from various boxes. Log in to reply |
| Re: Two weird behaviours... 18/05/2012 at 14:34 #32401 | |
|
Lardybiker
771 posts |
I think what Matt is trying to say is that he agrees with your sentiment about CCF and then some! In other words, he thinks it may not be just as bad but possibly much worse..... Log in to reply |
| Re: Two weird behaviours... 18/05/2012 at 17:43 #32404 | |
|
GeoffM
6377 posts
|
" said:I am strugging to understand that post Matt.I think he's using a Russian keyboard! SimSig Boss Log in to reply The following user said thank you: guidomcc |
| Re: Two weird behaviours... 19/05/2012 at 02:54 #32409 | |
|
mfcooper
707 posts |
" said:" said:Indeed ;-) Greetings from St Petersburg! (but this time fromI am strugging to understand that post Matt.I think he's using a Russian keyboard! an iPhone keyboard) Log in to reply |
| Re: Two weird behaviours... 19/05/2012 at 12:11 #32414 | |
northroad
872 posts |
Can someone explain what an Interpolation calculation is Geoff fom an I Pad Log in to reply |
| Re: Two weird behaviours... 19/05/2012 at 12:44 #32415 | |
|
AndyG
1842 posts |
It's basically calculating intermediate values from known end values eg if a train is 1/3 the distance along a given length, it's assumed to have taken a 1/3 of the time (allowance) between the two ends.
I can only help one person a day. Today's not your day. Tomorrow doesn't look too good either. Log in to reply |
| Re: Two weird behaviours... 19/05/2012 at 12:53 #32416 | |
Peter Bennet
5402 posts |
" said:Can someone explain what an Interpolation calculation isSee here and a simple example here Peter I identify as half man half biscuit - crumbs! Log in to reply |