Quick Portal Rule Problem

[Yorkshire]

I have been using Quick portal Manager V2 for a few days now with success. I still had Portal Timetable installed and discovered that they could conflict! So deleting the old Portal Timetable rule answered that problem. However, I have discovered a new problem. I have added some new consists with locos in surveyor. Unfortunately, the new consists do not show up in the surveyor list within Quick Portal Manager. They did show up in Portal Timetable rule. I have tried restarting the computer to see if it will trigger a recognition but to no avail. It only seems to be reading the original consist list that existed when I first installed the Quick P rule. Anyone had a similar experience. I want to get it working since it combines the original timetable rule with instant despatches from the portal into my terminus and it is very impressive.

Regards

Yorkshire

 

[fran1]

I've got the same problem, will try deleting the rule and re applying.

 

[Yorkshire]

Thanks - at least I am not alone!! Wonder if the author might be able to shed some light on this.

 

[pguy]

Quick Portal Manager has been designed to use consist definition from the global consist library which is a new component introduced with QuickDrive from TS2009 SP1 and later.

If you define and edit directly your consist in the global consist list library editor (you can access this editor at anytime in driver or surveyor or even mainmenu mode through the option menu), the consist definition is immediately available in quick portal manager.
This new editor has been designed with QuickDrive rule design at a time where Auran planned a TS2009EE edition with quickdrive and no surveyor mode. Now they have released TS2010EE edition with surveyor included, so the need for global consist list library is not so obvious, but it has some interesting features like multi list support which can be usefull in quickdrive rule and quickportal manager.

if you define your consist using the traditional way under surveyor, your consist definition will still be available under quickdrive and quickportal manager, but delayed as you will need to wait for the system to copy the surveyor definitions to the global consist list named surveyorlist. This just now happens in TS2009 and TS2010 when QuickDrive rule is loaded in a route either directly from the menu (quickdrive mode) or in driver or surveyor mode.

So just now to retrieve new surveyor consist definition in the quickdrive portal manager you need to include quickdrive rule also in your session (which needs also the consistdatahandler rule to be included) and if you save and reload your session the new surveyor consist definitions should be available under the global consist list surveyorlist. I understand it is not very practical but the quickdrive and quickportal manager rules have not been designed initialy to use anymore the surveyor consist definitions but to use directly consist defined under the global consist list library editor. Adding the global consist list surveyorlist has been done later to offer an upward compatibility to retrieve previous surveyor definitions in the GCL component.

What I can improve in a next QuickPortal manager version is to include a link in the interface to enforce a GCL refresh of the surveyorlist from QuickPortal manager. You will still have to ask for a GCL refresh, but you will no longer need to include QuickDrive and to save and reload your session.

I will try to add this functionality in a few weeks. And if you have some other wishes for QuickPortal manager, let me know. And I already know a documentation is needed ...

Pierre.

 

[Yorkshire]

Thank you very much for that very full reply Pierre. Much appreciated, I have much to learn about using this excellent rule!

Kind regards

Yorkshire

 

[Yorkshire]

Just to confirm that I have understood your instructions and guidelines and got it working! I must admit I haven't used global consist library until 5 minutes ago! And I didn't realise that the consist datahandler and quick drive were required in the session. Once I had included those everything fell into place. Many thanks once again for your support.

Yorkshire

 

[celje]

Hello pguy

The best thing with Portal Timetable rule is possibility to include any time you wish. It seems that Quick Portal Manager has only recurrency and I think that's step back.

regards

 

[EdrickV]

It seems SP2 may fix some of the problems with Quick Portal mentioned here, once it's released:

Made the SurveyorList the default list in GclLib
Fixed the SurveyorList not being generated until QuickDrive was loaded in Driver

http://online.ts2009.com/mediaWiki/index.php5/TS2010_SP2

 

[Lots_Trains]

Hi Celje

You can edit the time in Qportal just click on the time it is fully editable.

Cheers

Lots

 

[celje]

Hi Celje

You can edit the time in Qportal just click on the time it is fully editable.

Cheers

Lots

hello Lots, if i was doing correct then only one time can be set for one day(e.g. 10:02) and then of course repeat in equals hours( after 1 h, 2h..). In Portal timetable you can use many times for one train in one day(10:15, 11:02, 11:15, 11:59 14:04......etc). Am I missing something?

regards

 

[pguy]

Hello pguy

The best thing with Portal Timetable rule is possibility to include any time you wish. It seems that Quick Portal Manager has only recurrency and I think that's step back.

regards

Quick Portal Manager and Portal Timetable have not been designed with the same goals. So they have not organized their data the same way and QPM is not just now an update for PT even if they offer similar functionalities.

Portal Timetable is a rule made as a set of entries with no relations between each entry. Each entry is based on a portal reference and a consist definition and has a list of time associated with it to schedule the consist out of the portal.

Quick Portal Manager was made to enable cross map transfer by stacking all the consists outgoing from a portal in a first route and rescheduling these consists at the same time ingoing out a portal in a second route. So it was organized by having a list of dynamic entries based on time associated to a portal with each entry containing a reference to the consist soup. The interface has been designed so that it would be easy to consult under driver mode the list of ordered scheduled entries for a portal. Entries can either be initial schedule with consist definition from the global consist list library or transfer schedule with consist definition internal reference saved in some soup databundle.

This explains the difference in the approach. The question now is can we merge the two approach in one convenient rule for both purposes. You are quite right that the main difference is portal timetable multi time support in one entry instead of only recurence support in QPM. May be I can introduce multi time support also in QPM entry with auto reschedule to the next timeframe after a schedule done. Some people have also asked me to introduce a day of the week variable concept so that schedules can be planned for a full week. The day of week variable concept is under progress but I need to see how to include all this improvements without making the interface too complex.

There should be some new versions both for QPM and for PT in the next months.

Have a nice day.
Pierre.

 

[celje]

Thank you pguy for explanation.

I admitt that i don't use iportal and for me is not interesting.
Portal timetable rule is very important because you can make a good working schedules for all trains. QPM has a different goals and it's very good. There is no need for any changes because he include two day pass and i think it's enough.

Pguy thank you again

regards

 

[Yorkshire]

I think there may be an issue in running both portal timetable rule and quick portal rule in the same session. I discovered that quick portal emitted a consist and then a copy of the loco followed it and just stayed on the track leading away from the portal. As soon as I deleted timetable portal rule from the session, the problem did not re-occur. Has anyone else noticed a behaviour like this - or is it just a conflict on my system!!

Yorkshire