Seite 1 von 1

Probably another newbie question, but maybe not.

Verfasst: 23.03.2024 18:17:21
von cereal killer
I tried to do the ICE 1573 service (see attached image) but I encountered two "oddities" which could easily be due to my ignorance.
1) When opening the Ebula, it does not update to the current Km but remains stationary. This happens both on the Ebula that I start in the cabin and on the one connected to the server that I open with ZusiDisplay.
2) When I start the service, I activate the AFB and set it to maximum speed, but the LZB causes the train to travel at speeds significantly higher than those I see in the timetable. In certain sections of track, however, the speed that the LZB sets is consistent with what I read in the timetable.
Where's the mistake?
Thank you.

Bild

Re: Probably another newbie question, but maybe not.

Verfasst: 23.03.2024 18:46:19
von Christian Sch.
Hello fellow Zusi fan,

1: Did you check if Zusi is transmitting data? Konfigutation -> Netzwerk -> Button "Server starten".
There is an option in Konfiguration -> Einstellungen -> Tab Sonstiges -> Checkbox "Server autom. starten" that starts data transmition on every start of the sim.

2: When a train is guided by LZB (the german term is "LZB-geführt") the values displayed by LZB "overrule" EBuLa. LZB is a requirement for trains that go faster than 160 km/h. EBuLa is used when LZB is not active (simlplest reason: line is not equipped with it) so the speed is capped at 160 km/h.
So if line speed is 160 km/h and less, speeds match.

I hope my explanation is not too confusing.

Christian

Re: Probably another newbie question, but maybe not.

Verfasst: 23.03.2024 19:18:58
von cereal killer
Christian Sch. hat geschrieben: 23.03.2024 18:46:19 1: Did you check if Zusi is transmitting data? Konfigutation -> Netzwerk -> Button "Server starten".
Yes, the server is "up" but Ebula doesn't work as it should.
Sometimes it starts correctly by scrolling the mileage, but shortly after it freezes.
Other times (mostly) it remains stationary from the start.

Re: Probably another newbie question, but maybe not.

Verfasst: 23.03.2024 19:27:46
von timo74
Are other Zusi displays apart from Ebula started externally? The start sequence would then be interesting

Re: Probably another newbie question, but maybe not.

Verfasst: 23.03.2024 19:33:35
von cereal killer
timo74 hat geschrieben: 23.03.2024 19:27:46 Are other Zusi displays apart from Ebula started externally? The start sequence would then be interesting
Nope, I have only Ebula panel up.

Re: Probably another newbie question, but maybe not.

Verfasst: 23.03.2024 19:35:55
von cereal killer
Just wanted to add that a friend is having the same problem on the same service.
Please, could you try to replicate it too?
Thank you.

Re: Probably another newbie question, but maybe not.

Verfasst: 23.03.2024 19:39:20
von oppolo
BildThis is the situation. We are running zusi on win7

Re: Probably another newbie question, but maybe not.

Verfasst: 24.03.2024 11:06:16
von timo74
I have the same problem with this timetable. I have no idea exactly what the problem is. I have found the following as a possible solution. Set Ebula to manual before setting off and set it to KM 47. Before arriving at KM 47, set it back to localisation mode. After that, the KM seems to work again. However, I did not ride the entire route. Another option is to ride according to the printed book timetable.
Greetings
Timo

Re: Probably another newbie question, but maybe not.

Verfasst: 24.03.2024 14:38:38
von Thomas R.
Hi everyone,

probably, there is a problem with the *.timetable.xml files of "Guntershausen-Edesheim_2020_06Uhr-10Uhr" in section 1a, starting in Almstedt.
I'll try to create these files used by EBuLa newly and see if the problem is solved.
I'll get back to you when I finished doing this.

Regards,
Thomas

Re: Probably another newbie question, but maybe not.

Verfasst: 24.03.2024 18:27:57
von cereal killer
Thanks!

Re: Probably another newbie question, but maybe not.

Verfasst: 24.03.2024 20:14:39
von Thomas R.
cereal killer hat geschrieben: 23.03.2024 18:17:21 I tried to do the ICE 1573 service (see attached image) but I encountered two "oddities" which could easily be due to my ignorance.
[...]
So, this definitely is no newbie question but you found a bug. :D

Using newly created *.timetable.xml for all services in section 1a. starting in Almstedt, the problem is solved and ZD starts to count the km as usual from the beginning. Unfortunately I made a mistake in preparing the *.timetable.xml for these specific trains delivered with package 204.

As always, the amended files will be distributed within the next update package, which might take a while. For those of you that know what they’re doing, you will find the update within the file management tool soon. I will upload everything tonight.

Regards,
Thomas

Re: Probably another newbie question, but maybe not.

Verfasst: 24.03.2024 22:43:55
von oppolo
Thank you

Re: Probably another newbie question, but maybe not.

Verfasst: 25.03.2024 01:02:24
von cereal killer
Thomas R. hat geschrieben: 24.03.2024 20:14:39 As always, the amended files will be distributed within the next update package, which might take a while. For those of you that know what they’re doing, you will find the update within the file management tool soon. I will upload everything tonight.
Thank you Thomas.
I'm a new user and I own the Steam version of Zusi.
Is there anything I can do to update with fixed files or do I have to wait for an update from Steam?

Re: Probably another newbie question, but maybe not.

Verfasst: 25.03.2024 01:12:48
von Thomas R.
Since being a new user I would certainly recommend you to wait for the next update.

As a work around you can drive the same services in the "Kirchheim-Veddel_2020_06Uhr-10Uhr" timetable but all the way from Hamburg.
In this timetable the ZD problem does not occur.

Regards,
Thomas