Some little problem

[intallonabile]

1 i can not disable fleeting mode on signal 476 (Sinzig) from number entry panel. I have no result

2 i have a train coming from branch line at 21.38 (train 7193). This train become 7194 and departs at 22.19 for branch line

In timetable window of departing train (7194) i have as start time from Remagen (Track 005) the arriving time of train 7193. Train change direction with prepared orders and i only put the new number (7194) with ZNP801 . Is my procedure correct ?

Thanks for the reply

Diego

[TjoeTjoe]

1 i can not disable fleeting mode on signal 476 (Sinzig) from number entry panel. I have no result

Have to get back on this. Can not test it right now.

Might be related to the discussion in this topic : Fahrstrasse 476-454 und 454-413 (Sinzig)

You could try to disble SB (fleeting mode) with 480 from the Number Entry Panel, and see if that works.

If I understand Richard's replies correct, this is something that will be fixed. (read: in future you can disable fleeting by 476 + SBRT + ATK)

2 i have a train coming from branch line at 21.38 (train 7193). This train become 7194 and departs at 22.19 for branch line

In timetable window of departing train (7194) i have as start time from Remagen (Track 005) the arriving time of train 7193. Train change direction with prepared orders and i only put the new number (7194) with ZNP801 . Is my procedure correct ?

You should have had two movement orders:

1. Change direction

2. Renumber into 7194

If the last is ommitted, the train should still exist as 7193 withing the simulation, and thus it will maintain the timetable of 7193, which will also been as such shown in timetable window + train overview.

BTW: In ZNP801 should officially have actually entered 17194 (1=steering number). However, ZNP801 is just an aid to you as dispatcher to remember which is train is where on the panel. But like in reality, if the wrong number is there for a train, you could really mess things up

Erwin

[intallonabile]

Thanks Erwin. As you say if i change number from 476 and i write 480 in number entry panel i can enable/disable signal named 476 on panel. As you say i hope Richard will put this in next update

Regarding train 7193 now a re-try to simulate arrive of this train. In Movements order there are two orders (changing direction and changing number), System change immediately train number because on Train overview 7193 become suddenly 7194 but after train has changed direction on panel number remain 7193 and in Time Table Viewer window also Departing hours is arriving hour for 7193

After all this i tried hovewer to change with another manual order the train number but on panel still remain 7193, This is normal ? to have correct number on panel i must use ZNP801 with 17194 as you exactly has correct me

Good evening

Diego

[TjoeTjoe]

Regarding train 7193 now a re-try to simulate arrive of this train. In Movements order there are two orders (changing direction and changing number), System change immediately train number because on Train overview 7193 become suddenly 7194 but after train has changed direction on panel number remain 7193 and in Time Table Viewer window also Departing hours is arriving hour for 7193

After all this i tried hovewer to change with another manual order the train number but on panel still remain 7193, This is normal ? to have correct number on panel i must use ZNP801 with 17194 as you exactly has correct me

Hi Diego,

well I think I really have to reproduce the situation myself with the panel in front of me (did not time to do so yesterday).

What I do understand so far is that the train executes its movements orders correctly. Read it does what is defined for it: change direction and renumber into 7194.

To me that means that the simulation know that the train now has the ID 7194 and the correct timetable *should* be linked to it.

Now what confuses me is what you mean with "in Time Table Viewer window also Departing hours is arriving hour for 7193".

1. Do you mean that the correct timetable for the 7194 is shown, nut only the system registrates the train having departed at the same time it has arrived in Remagen?

2. Or do you really see the timetable of the *old* 7193?

Again, I think I will have to reproduce it myself, but if it is answer no. 1 then this is just as it has always worked in the simulation. It is a little oddity, has always been there.

After all this i tried hovewer to change with another manual order the train number but on panel still remain 7193, This is normal ? to have correct number on panel i must use ZNP801 with 17194 as you exactly has correct me

How I understand your comment is that for all trains renumbering in the Train Number windows on the panel takes place, except for this one. Right?

Well, if that is true then (for now) I can not really explain why this behavior is shown. For what I can see, the timetable data (mdb) does not have any strange entries which may cause this.

I would have expected that renumbering on the panel would not occur for all trains ending and renumbering in Remagen, and not just for this single train.

If that would have been the case, it could be explained when you would have the following expert setting activated:

TNV Train descriptor overview operates as in real life

the system can renumber regular situations automatically via a scripting system. In all other cases, the dispatcher needs to change number manually. To ease of this amount of extra work, you can turn off the expert option and let the system do the most work for you. Still some work is needed if you see an alarm number appearing!

ANyway, for proper reproduction, I would like to know at what time and also day ( mon-fri or sat-sun) you are running the simulation.

One thing that I do not understand is why there are two entries for the 7193 and 7194 in the timetable mdb, one for mon-fri and one for sat-sun, eventhough the schedules are completely identical. Not that, from logical point of view, would be the cause as the definitions seem to be correct.

I will get back on this as soon as I have had the ability to test it myself

Erwin

[intallonabile]

Hi Diego,

well I think I really have to reproduce the situation myself with the panel in front of me (did not time to do so yesterday).

What I do understand so far is that the train executes its movements orders correctly. Read it does what is defined for it: change direction and renumber into 7194.

To me that means that the simulation know that the train now has the ID 7194 and the correct timetable *should* be linked to it.

Now what confuses me is what you mean with "in Time Table Viewer window also Departing hours is arriving hour for 7193".

1. Do you mean that the correct timetable for the 7194 is shown, nut only the system registrates the train having departed at the same time it has arrived in Remagen?

2. Or do you really see the timetable of the *old* 7193?

Again, I think I will have to reproduce it myself, but if it is answer no. 1 then this is just as it has always worked in the simulation. It is a little oddity, has always been there.

How I understand your comment is that for all trains renumbering in the Train Number windows on the panel takes place, except for this one. Right?

Well, if that is true then (for now) I can not really explain why this behavior is shown. For what I can see, the timetable data (mdb) does not have any strange entries which may cause this.

I would have expected that renumbering on the panel would not occur for all trains ending and renumbering in Remagen, and not just for this single train.

If that would have been the case, it could be explained when you would have the following expert setting activated:

TNV Train descriptor overview operates as in real life

the system can renumber regular situations automatically via a scripting system. In all other cases, the dispatcher needs to change number manually. To ease of this amount of extra work, you can turn off the expert option and let the system do the most work for you. Still some work is needed if you see an alarm number appearing!

ANyway, for proper reproduction, I would like to know at what time and also day ( mon-fri or sat-sun) you are running the simulation.

One thing that I do not understand is why there are two entries for the 7193 and 7194 in the timetable mdb, one for mon-fri and one for sat-sun, eventhough the schedules are completely identical. Not that, from logical point of view, would be the cause as the definitions seem to be correct.

I will get back on this as soon as I have had the ability to test it myself

Erwin

Thanks for your reply. As i have a bad english is difficult to explain situation , If you try to simulate arriving of train 7193 and after departure train for 7194 in Time Table Viewer window for 7194 real departing hour will not be real departing hour but an ancient hour referred at 7193 when this train is arrived at Remagen.

[intallonabile]

Hi Diego,

well I think I really have to reproduce the situation myself with the panel in front of me (did not time to do so yesterday).

What I do understand so far is that the train executes its movements orders correctly. Read it does what is defined for it: change direction and renumber into 7194.

To me that means that the simulation know that the train now has the ID 7194 and the correct timetable *should* be linked to it.

Now what confuses me is what you mean with "in Time Table Viewer window also Departing hours is arriving hour for 7193".

1. Do you mean that the correct timetable for the 7194 is shown, nut only the system registrates the train having departed at the same time it has arrived in Remagen?

2. Or do you really see the timetable of the *old* 7193?

Again, I think I will have to reproduce it myself, but if it is answer no. 1 then this is just as it has always worked in the simulation. It is a little oddity, has always been there.

How I understand your comment is that for all trains renumbering in the Train Number windows on the panel takes place, except for this one. Right?

Well, if that is true then (for now) I can not really explain why this behavior is shown. For what I can see, the timetable data (mdb) does not have any strange entries which may cause this.

I would have expected that renumbering on the panel would not occur for all trains ending and renumbering in Remagen, and not just for this single train.

If that would have been the case, it could be explained when you would have the following expert setting activated:

TNV Train descriptor overview operates as in real life

the system can renumber regular situations automatically via a scripting system. In all other cases, the dispatcher needs to change number manually. To ease of this amount of extra work, you can turn off the expert option and let the system do the most work for you. Still some work is needed if you see an alarm number appearing!

ANyway, for proper reproduction, I would like to know at what time and also day ( mon-fri or sat-sun) you are running the simulation.

One thing that I do not understand is why there are two entries for the 7193 and 7194 in the timetable mdb, one for mon-fri and one for sat-sun, eventhough the schedules are completely identical. Not that, from logical point of view, would be the cause as the definitions seem to be correct.

I will get back on this as soon as I have had the ability to test it myself

Erwin

i have tried simulation with departing hour 21:00 in saturday

[TjoeTjoe]

Hi Diego,

just tested your situation.

1. Please confirm that you are talking about the departure time reported in column Dep (A) for the 7194.

If yes, this is common simulation behavior. (read: I do not really consider this a bug)

2. Could you tell me if you have enabled the Expert Option "TNV Train descriptor overview operates as in real life"?

Only with this option enabled, I see that the train number is not renumbered from (1)7193 to (1)7194.

(With this option disabled, train number is automatically renumbered on panel as well)

The next question is, and that is for Richard or Nopileos, is if this is how it really works on the Sp Dr S 60 panels.

Does the system provide functionallity to automatically renumber (on the actual panel) or not?

Reason why I ask this to them is that the Timetable does allow auto-renumbering when "TNV Train descriptor overview operates as in real life" is enabled

So, Diego a couple of confirmations requested from your end

And hoping that Richard or Nopileos could answer my last question

Erwin

[signalsoftRC]

German ZNP801 systems do NOT provide automatic renumbering... it's nicely manually done... (oh poor dispatcher in cologne!)

if the expert option is turned off, the automatic renumbering ONLY takes place if the tick is set in the database.

If the expert option is turned on, the system attempts to update the train descriptors in most cases. There are some odd cases where a train is positioned "off limits" and the renumbering goes odd...

That's the task of the dispatcher.

we are planning to build in "wrong steering numbers" and simply a wrong train number from your neighbour... can to wrong their too...

but this is not implemented yet.

[TjoeTjoe]

German ZNP801 systems do NOT provide automatic renumbering

if the expert option is turned off, the automatic renumbering ONLY takes place if the tick is set in the database.

@Diego,

so the answer must be that you have Expert Option "TNV Train descriptor overview operates as in real life" turned on.

The timetable database is configured as such, that no train auto-renumbers, just like in real life.

So here is your explanation.

And with respect to the time value Dep(A) field (actual departure time)

I just remember your old topic for Hürth.

If a train only has a departure time defined, the actual departure time is triggered/filled in when a train 'hits' a station track.

This is (technically) exactly what happens at the moment the train renumbers on the station track. The new train 'passes' at that moment, even though it is standing still.

Erwin

[intallonabile]

@Diego,

so the answer must be that you have Expert Option "TNV Train descriptor overview operates as in real life" turned on.

The timetable database is configured as such, that no train auto-renumbers, just like in real life.

So here is your explanation.

And with respect to the time value Dep(A) field (actual departure time)

I just remember your old topic for Hürth.

If a train only has a departure time defined, the actual departure time is triggered/filled in when a train 'hits' a station track.

This is (technically) exactly what happens at the moment the train renumbers on the station track. The new train 'passes' at that moment, even though it is standing still.

Erwin

OK Now i understand. Thanks to Erwin and also Richard for reply. Now i go to work We have very big problems with train circulation on Ligure See (Genua and whole liguria) with some lines blocked, water on tracks and no electricity on line

[TjoeTjoe]

OK Now i understand. Thanks to Erwin and also Richard for reply. Now i go to work We have very big problems with train circulation on Ligure See (Genua and whole liguria) with some lines blocked, water on tracks and no electricity on line

You're welcome.

Good luck today. I read on the news that there have been some big floods in the area of Genova. Looks very bad.

A number of casualties as well. Take care

Erwin

[Wueht]

mir fällt schon längerer zeit auf, dass züge aus gleis 2 die richtung zügen fahren ihre nummer nicht mitnehmen bzw. sie verschwindet.