80114 & 80116 not following orders

[jduncan]

Both of these trains start from Hengelo between 4 and 5 a.m. When starting at 5 a.m. 80116 is ready to roll to Enscheide but he arrives and won't change cabs or train numbers even though orders say to do these things on "any track". I have to change the written orders in order to get them to change direction and identity in Enscheide. Also NEITHER of these guys will respond to the radio or to platform phones in Hengelo. They apparently don't want to talk to the dispatcher until they're on the platform tracks at Enscheide. Any chance these guys can get corrected in the next Hengelo Timetable release?

Thanks!

Jim Duncan

www.gulfmobileandohiorr.com

[arc]

Had some problems with those trains too. Sometimes they don't turn into an IC at Enschede. And it also seems that those trains are staffed throughout the night. The solution that worked for me was not to let them depart from Hengelo until 3 minutes after their regular departure time, and then giving them time to execute their commands at Enschede.

[TjoeTjoe]

Both of these trains start from Hengelo between 4 and 5 a.m. When starting at 5 a.m. 80116 is ready to roll to Enscheide but he arrives and won't change cabs or train numbers even though orders say to do these things on "any track". I have to change the written orders in order to get them to change direction and identity in Enscheide. Also NEITHER of these guys will respond to the radio or to platform phones in Hengelo. They apparently don't want to talk to the dispatcher until they're on the platform tracks at Enscheide. Any chance these guys can get corrected in the next Hengelo Timetable release?

Thanks!

Jim Duncan

www.gulfmobileandohiorr.com

Jim,

not having analyzed this fully yet I am quite confinced that for the 80114 and the 80116 there too many/too few (wrong) Movement Orders in the database.

The 80114 is defined twice in the Timetable, but for different days which shouldnt be a problem.

However the 80114 should renumber into 1614, and this 1614 only runs on monday until friday.

So maybe, if you're running the sim on a sat or sun, the sim doesnt want to renumber into 1614 because it does not run that day?

Jim, could you tell on which day you were running the sim?

The 80116 renumbers to 1616 (mon -> fri), to 1762 on sat and to 1730 on sun.

Now, here the issue (I think) is caused by the MO orders for the 80116 (and actually also in Timetable table)

In short, the 80116 all have the same Train_ID_HARD what I believe is wrong.

There should be a set called ie 80116mavr, 80116za and 80116zo to make it work correct.

I can see that the correct instructions for each train number are more or less, but as it is inconsistent due to the Train_ID_HARD, the sim does not know which orders to take.

Not knowing exactly how the sim reads in its MO orders it looks like that it doesnt get any further then assigning a trainer driver and change direction in Es. ALl other MO's are ignored.

Anyway, to resolve all this, the timetable table needs the correct Train_ID_HARDs as well as the MO table for this train.

See MO orders for train 80182 on how it should have been done to get this working

Quite technical but think this is how it is now

Best regards

Erwin Lansbergen

----------------

@Richard: if all I am saying is correct then changes would be:

MO table record ID 431 - 436 and 614 - 616 need refreshing.

OrderLocation in ID 434 and 435 need to be changed to Enschede-Kap, OrderTrack to be empty

- ID 431,432,436 need Train_ID_HARD to change to 80116mavr

- ID 433,434,435 need Train_ID_HARD to change to 80116za

- ID 614,615,616 need Train_ID_HARD to change to 80116zo

In Timetable table:

- ID 817 (train 80116 > 1614 on mon-fri) change Train_HARD_ID to 80116mavr

- ID 816 (train 80116 > 1726 on sat) change Train_HARD_ID to 80116za

- ID 1470 (train 80116 > 1728 on sun) change Train_HARD_ID to 80116zo

Will try to test tonight by loading latest Hengelo_timetable.mdb and apply above suggestions.

And hopefully will not forget to send you all this by e-mail to feedback

Best regards

Erwin

[Hobbyman]

MovementOrders and Trains are correctly connected wich eachother.

The extensions mavr, za, zo are not needed for these connections.

However there might be the old problem with passing midnight while playing the simulation.

After midnight every train of the new day cannot find the MovementOrders.

Kind regards,

Leo

[Hobbyman]

Had a close look to that train.

Departure from Hengelo has been changed.

So 80116 can go directly to track 4b and change into 1726 on saturday

It will be changed in the next update.

Thank you for reporting this malfunction of train 80116.

Kind regards

Leo

[TjoeTjoe]

Had a close look to that train.

Departure from Hengelo has been changed.

So 80116 can go directly to track 4b and change into 1726 on saturday

It will be changed in the next update.

Thank you for reporting this malfunction of train 80116.

Kind regards

Leo

Leo,

you are right regarding the links between the Timetable and MO table.

I have been heavily mislead by the way the data is being shown in both tables as well as the comment for the various fields.

I thought that the Train_ID_Tech (with comment: This ID is ONLY used in this database to link MO's to the timetable) was THE link to the MO table, so that put me into the wrong direction

Did some digging in how things are linked to each other Train_ID_Hard in MO is linked to the ID field in Timetable, but showing the data entered in Train_ID_Tech from TimeTable.

Anyway, don't see what the departure from Hengelo has to do with the issue (yet).

If it initially was intented to stay in Enschede-Opstel for a while, then it should have been stabled there under a different number than 1726, right?

And finally, what about the 80114 where Jim complained about as well

The one sunday (ID=1695 in TimeTable) has no MO's, guess it just stays in Hgl.

But the monn-fri one should work, as the MO's seem to be fine

Thanks

Erwin Lansbergen

[Hobbyman]

Originaly 80116 had the same departure from Hengelo on all days.

On saturday 80116 was meant to go to track 7 and stay there for about 2 hours.

Therefore 1726 had the movement orders to go from track 7 to track 4b.

There is no need for an early arrival in Enschede and therefore departure was changed.

The movement orders and timetable were not changed accordingly.

In the next update 80116 goes directly to track 4b, changes to 1726 and is right in time for departure from Enschede.

There is no 80114 on saturday. There is an 80133 for personal to Enschede.

On sunday 80114 is stabled in Hengelo for the whole day.

Communication is checked and is fine.

It seems that 80114 and 80116 originally were staffed all night.

That has not changed. It seems not correct.

Some extra MovementOrders will be nessecary to change this issue.

Kind regards,

Leo

[graham]

Hi All,

I haven't had a problem with these two. I always set a route 30 seconds before scheduled departure and they trundle off to Enschede and pick up their new runnings no problem. I have not as yet tried it after running through midnight so this may also be something worth looking at as previously mentioned by Hobbyman.