portal

[netting2010]

hi

I am running TS12 and have set up a route that utilizes portals at various ends of the route. Each RECEIVING portal is set up to return consists to an alternative portal. however I get error messages "unable to plot route to destination" each time a consist is consumed but note that the consist does appear as instructed by the portal and then continue with the schedule. Happens with all types of portals. I have checked all junctions signals etc to no avail.

 

[dnevans8]

I too have seen this error and as you say it also does not affect the production of the consist at the named portal. I believe what is happening is that as the consist leaves the route via the portal the program still tries to set a route from the portal that it is exiting from. If it cannot see a route because for example there is a track direction marker preventing it using the track from the exit portal then you get the error message. It is only when the consist is produced at the second portal that a valid route is set. You can check this by putting a crossover between the tracks attached to the two portals if that is possible or just make sure there is a valid route out of the consuming portal to the route from the producing portal (remove any track direction markers).

 

[netting2010]

The only alternative I have found is to have one receiving portal only at the receiving position set up to return consists through "none" and have a junction in front of the exit, by at least a consist length, with direction markers set after the junction to ensure its on the right track. Haven't come up with an answer if one wants to send it to a portal at the opposite end of the layout. ( I am using the portals to turn a consist around and having one receiving and one producing to save any delays accessing the receiving portal etc.) Noting that the set up does work the main issue is that the program starts to fill the message box with error messages. It would be great if the system said which consist was having the issue rather than a general message! Takes some finding if you have a lot of consists in a city track!
I did not notice the problem in TRS2006. The theory is to eventually have all consists running terminal to terminal but the "other half" could have some issues with the time involved!
Thanks for your reply, appreciated.

 

[netting2010]

dnevans8

Just had a re-read of your reply and think I understand what you are saying. (I am 58 so getting a little slow!) Do I take it that as the consist enters the exiting portal the program processes as follows...
1st process - receive consist
2nd process - checks consist schedule and can't find a suitable route.
3rd process - registers error message. (your suggestion should correct this).
4th process - reads "return through" instruction.
5th process - Sends consists to return portal.
6th process - consist is produced at return portal and starts its schedule as programmed.

If this is the case is it an error in the Portal / program / consist / operator!

 

[dnevans8]

netting2010;

I have an extra seven years on you so sometimes what I write can make sense to me but is not so easy for others to follow.

Your six steps are an accurate summary of what I said but where the error is I do not know although it probably is not a true error as it only shows up as a message in the message window rather than the red dot that comes up in the bottom right hand corner when a script error occurs. Since the consist operates properly afterwards I think it can be ignored although it would be nice if it did not happen.

 

[netting2010]

dnevans8

Many thanks and don't worry about the sense issue unless, once you have written it, it does not make sense. THEN we are in trouble! The crossover, by way of providing a track that connects in front of the 2 portals, does the trick for using portals to turn a consist around.

take care.
Shane Graham