| Re: Panels in general [message #487 is a reply to message #482] |
Mon, 03 December 2012 16:17   |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear Susanne and Christian,
> - A <speed> signal information further contains the parameters "kind"
> (values: announcement, execution and end) and "speedChangeRef".
A list of <speedChangeRefs> please. (Several speed profiles, each
referencing the same <speedChange>.)
I suggest not to distinguish between "execution" and "end" because of this
may depend on the speed profile. Rather, an attribute
/kind/="announcement"|"execution" should be enough also for the "ends".
Additionally, we need both the "valid for head of train" (not the same as
/kind/!) and "virtual" information as well, as already discussed and
agreed.
> - A <milepost> signal information further contains the parameters
> "shownValue" and "realValue".
Is "realValue" the same as the /pos/ of this element at the track, isn't
it?
> - A <braking> signal information further contains the parameter
> "trackConditionRef", which refers to a <trackCondition> where the
> attribute "type" allows for the values 'nonStoppingSection',
> 'noRegenerativeBraking', 'noEddyCurrentBraking', 'noMagneticShoeBraking'.
I suggest to use a bake type already existing (tVehicleBrakes or such) and
an attribute declaring "not for vehicles with the following brakes...".
Please do already think at the German places for "Betriebsbremsung" or
"Zwangshalt" - should we use such a <signal> there, possibly with
/virtual/='true'? If so, we would also use a /type/ therefore.
Best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
