Page 2 of 2
Re: LZB implementation
Posted: Wed Mar 27, 2013 7:52 pm
by AndiS
Yes, I think if GetSignalState always returns 0 for green (I hope) when no train is expected and the block ahead is clear, instead of 2 (for stop), the return value of GetNextRestrictiveSignal should be all right.
I don't how how much the Augsburg signals or others use Call( "GetNextSignalState", "", 1, 1, 0 ). The traditional way of doing things is to keep track of the SIGNAL_CLEAR, SIGNAL_BLOCKED etc. messages that are sent as the aspect changes. This provides an alternative information channel - an "unprepared" signal protecting a clear block will send SIGNAL_BLOCKED but return 0 in GetSignalState.
I know that default AWS/TPWS implementations use GetNextSignalState. But that will not be a problem because when the train passes them, the signal ahead will be "prepared" so shown aspect and return value from GetSignalState will be in sync. I don't know about PZB in these routes, but it should not complicate matters more than TPWS, and that is not too bad.
Re: LZB implementation
Posted: Thu Aug 01, 2013 12:41 pm
by shanyiqua
Do anyone could make an own LZB implementation that work like RSCs? I still facing the problem, when two speed limits are close to each other for example a permanent speed limit, then 100m after this there is a signal speed limit, then only the closest limit is visible for the script, but if the train pass the first speed limit, that 100m isn't enough to slow down for the second limit.
GetNextRestrictiveSignal on LZB routes that use Munich-Augsburg KS signals gets only the red signals, and not the yellows with restricted speed(the funny is, with the old ruhr-sieg HP signals it gets the yellow signals too, however still without aspect and speed limit, but that's still more than the nothing with the KS signals). While GetNextSpeedLimit gets only the closest speed limit(including permanent and signal speed limits), and i could not find out how to set it to look ahead for two limits.
But somehow the RSC rolling stock still see the the signals that show restricted speed, before the train passed the preceding speed limit.
Is there some secret parameter for these methods?
Re: LZB implementation
Posted: Thu Aug 01, 2013 9:38 pm
by nschichan
shanyiqua wrote:Do anyone could make an own LZB implementation that work like RSCs? I still facing the problem, when two speed limits are close to each other for example a permanent speed limit, then 100m after this there is a signal speed limit, then only the closest limit is visible for the script, but if the train pass the first speed limit, that 100m isn't enough to slow down for the second limit.
GetNextRestrictiveSignal on LZB routes that use Munich-Augsburg KS signals gets only the red signals, and not the yellows with restricted speed(the funny is, with the old ruhr-sieg HP signals it gets the yellow signals too, however still without aspect and speed limit, but that's still more than the nothing with the KS signals). While GetNextSpeedLimit gets only the closest speed limit(including permanent and signal speed limits), and i could not find out how to set it to look ahead for two limits.
But somehow the RSC rolling stock still see the the signals that show restricted speed, before the train passed the preceding speed limit.
Is there some secret parameter for these methods?
Hi,
I had the same problem with the TVM 430 while rescripting the class 395. It turns out that I missed a parameter in my original explanations about GetNextRestrictiveSignal and GetNextSpeedLimit.
Both function take a third parameter which is the distance (in meters) to look from to get the next speed limit / restrictive signal. Omitting this parameter is equivalent of setting it to 0.
The usage is therefore:
Code: Select all
type, speed, distance = Call("GetNextSpeedLimit", direction, distance)
and
Code: Select all
type, state, distance, aspect = Call("GetNextRestrictiveSignal", direction, distance)
Regards,
Re: LZB implementation
Posted: Sat Aug 03, 2013 10:49 pm
by shanyiqua
Wow, thanks now this parameter solves every problems

Re: LZB implementation
Posted: Sun Aug 04, 2013 7:39 am
by MichielsJorik
Hi there,
I just got the Berling - Wittenberg streche and its amazingly detailed.
The only thing missing is the working LZB, I noticed in the manual that this is a licensing problem between RSC and "Aerosoft".
I thought it could not be a problem placing the LZB myself and maybe sharing it with other people.
I encounter a big problem trying to do so :p
The LZB start works perfectly but when I place a LZB End balise it does not work, my LZB keeps working.
Can somebody explain how to end LZB operations at a certain point?
I noticed that you have a LZB_end, LZB_endnow and a LZB_endfixed.
What is the difference between these 3?
Does somebody now from with point up to witch point the Berlin - Wittenberg route is equipped with LZB?
Thanks for the help in advance.
Re: LZB implementation
Posted: Sun Aug 04, 2013 5:56 pm
by jstange
MichielsJorik wrote:Hi there,
I just got the Berling - Wittenberg streche and its amazingly detailed.
The only thing missing is the working LZB, I noticed in the manual that this is a licensing problem between RSC and "Aerosoft".
I thought it could not be a problem placing the LZB myself and maybe sharing it with other people.
I encounter a big problem trying to do so :p
The LZB start works perfectly but when I place a LZB End balise it does not work, my LZB keeps working.
Can somebody explain how to end LZB operations at a certain point?
I noticed that you have a LZB_end, LZB_endnow and a LZB_endfixed.
What is the difference between these 3?
Does somebody now from with point up to witch point the Berlin - Wittenberg route is equipped with LZB?
Thanks for the help in advance.
Hello,
if you manage to implement LZB for this route that would br fantastic. This is the only thing that I miss on this route.
LZB start and end signs should all be there from the developer, so you could probably use them to see where you should implement it?
Re: LZB implementation
Posted: Mon Aug 05, 2013 6:04 pm
by MichielsJorik
I found the solution to my LZB END problem.
When you approach the END of the LZB zone, about 1 to 2 kilometers before, you need to place a LZB_END_fixed balise with the arrow pointing in the driving direction.
Then at the END itself you need to place a LZB_END balise with the arrow pointing against the driving direction.
This way you'll get LZB End light in the cab and a terminations of the LZB operations when you pass LZB_END.
I've added LZB to the Berlin - Wittenberg strecke on all the parts where BahnJan put visual LZB.
I was wondering if these visual LZB placement is fully correct because all these parts are pretty short and close to each other.
Could it be that the full route has LZB and not in parts?
When you leave Berlin Südkreuz you meet a 200 speed sign, does this exist in real life to?
This is the placing following the visual LZB direction Berlin - Wittenberg:
Start 11.5 up to 18.9
25.5 up to 48.6
51.3 up to 60.2
65.0 up to 92.2
Is there an LZB start sign after every junction or siding?
Or does LZB come to life when you meet the LZB wire?
Re: LZB implementation
Posted: Tue Aug 06, 2013 4:39 am
by jstange
Hi,
I think the best solution would be to post this question on rail-sim.de in the commercial add-ons/Berlin Wittenberg topic. The route developer (Jan Bleiss - bahnjan) is reading this topic from time to time and I believe he is the best to answer all your questions. You can also send him a private message there perhaps (bahnjan)...
Re: LZB implementation
Posted: Tue Aug 06, 2013 11:19 am
by 749006
MichielsJorik wrote: When you leave Berlin Südkreuz you meet a 200 speed sign, does this exist in real life to?
Might be worth a search on youtube for the real route.
I did see a cabride when I was looking for info about the line but I cannot remember where.
Peter
Re: LZB implementation
Posted: Sat Aug 10, 2013 11:14 pm
by zaphr89
MichielsJorik wrote:I found the solution to my LZB END problem.
When you approach the END of the LZB zone, about 1 to 2 kilometers before, you need to place a LZB_END_fixed balise with the arrow pointing in the driving direction.
Then at the END itself you need to place a LZB_END balise with the arrow pointing against the driving direction.
This way you'll get LZB End light in the cab and a terminations of the LZB operations when you pass LZB_END.
I've added LZB to the Berlin - Wittenberg strecke on all the parts where BahnJan put visual LZB.
I was wondering if these visual LZB placement is fully correct because all these parts are pretty short and close to each other.
Could it be that the full route has LZB and not in parts?
When you leave Berlin Südkreuz you meet a 200 speed sign, does this exist in real life to?
This is the placing following the visual LZB direction Berlin - Wittenberg:
Start 11.5 up to 18.9
25.5 up to 48.6
51.3 up to 60.2
65.0 up to 92.2
Is there an LZB start sign after every junction or siding?
Or does LZB come to life when you meet the LZB wire?
I think that LZB is active the whole from south of Berlin Südkreuz to past Lutherstad Wittenberg and that the LZB signs on the track are meant as 200km/h speed signs (for the simulator). I am only speculating this after reading Jahn's blog and the manual, but it doesn't make sense to have LZB start and end everytime the speed limit drops below 200km/h (but still is at/above 160km/h), thats what LZB is for after all.
Re: LZB implementation
Posted: Sun Aug 11, 2013 9:21 am
by MichielsJorik
zaphr89 wrote:
I think that LZB is active the whole from south of Berlin Südkreuz to past Lutherstad Wittenberg and that the LZB signs on the track are meant as 200km/h speed signs (for the simulator). I am only speculating this after reading Jahn's blog and the manual, but it doesn't make sense to have LZB start and end everytime the speed limit drops below 200km/h (but still is at/above 160km/h), thats what LZB is for after all.
I made a new LZB placement.
I found out that LZB starts from Berlin Südkreuz kp10.6 up to Leipzig.
https://www.dropbox.com/s/djxunuinh2nhhgy/KBS250LZB.rwp
Here is the download link.
This replaces your Tracks.bin so please make a backup of this first.