Jump to content

kronauerl

Mitglieder
  • Gesamte Inhalte

    6
  • Benutzer seit

  • Letzter Besuch

Letzte Besucher des Profils

Der "Letzte Profil-Besucher"-Block ist deaktiviert und wird anderen Benutzern nicht angezeigt.

  1. Hi EASY I hope he is watching the forum too. He can decide on the practicability of the idea. kronauerl
  2. Hallo MarkoP This feature isn't built-in now. It can be a goal to develop. "The hope dies last." kroanuerl
  3. Hi EASY I have a few decades of experience in programming and process controlling. It would make me happy if you would see the idea useful. kronauerl
  4. Hi Everybody I mentioned the value substitution in my previous posts. I explain what I mean in response MarkoP's posts about the cars in the train. The "$Variable_name" means the value of the "Variable_name" now. This should continue to think about. My idea: For example the "{variable_name}" similarly behaves like "$Variable_name" but it can be anywhere in the expression. The "{variable_name}" replaced with the current value in expression text. Loco.Car_count = 3 Loco.Car1 = Blau_3te_KL Loco.Car2 = Blau_2te_KL Loco.Car3 = Bayern "$Loco.Car{Loco.Car_count}" means "Bayern" because "{Loco.Car_count}" replaced by its value "3" and "Loco.Car3" is "Bayern". In this way it would be possible to handle simple arrays. Other example for usage nested substitution: Loco.Max_speed = 320 To set train speed to reverse max. speed when "Loco" reaches the exit of the station (Actions only): Set track vehicle speed Locomotive: [Trigger 1: Locomotive] Track: [All track] Speed: -{{_Trigger1._Name}.Max_speed} 1st substitution: "{_Trigger1._Name}" replaced "Loco" 2nd substitution: "{Loco.Max_speed}" replaced "320" The resulting expression is "-320" as used now. I think this idea is useable - to collect cars of the train if it will be "Car enters/leaves track" event. - to point the car to detach it (if the cars are enumerated in an array) - to select any device (track switch, signal etc.) by an alphanumeric index Viele Grüße kronauerl
  5. Hello Bahnland What I have written the demand for a solution to a problem encountered. _Triggerx isn't yet it would be further trigger variable. This should contain the name of the neighbor track in a future development. In the new aspect it is not so important already. Altought I have idea about the nested value subtitution in an expression. So. I also got similar result but in reverse logic. The task to detect the train coming from the 6140 to the 6110. When this event triggered and proper the train is on 6110, 6140 and so on but it is not on 6120 (other end of the 6110) surely Therefore the event configuration is: 1. Event - Train enters to a track - [All locomotives] - 61101. Conditions - Locomotive/Wagon is located on a track - [All] - 6120 - Negate1. Actions - ... Fine. There are two alternatives. I can choose between them at the right distance or any other aspects. Many thanks for your thoughts kronauerl
  6. Hello Neo and BahnLand I play MBS since a few days only. I like it. I built a simple railroad table and try to control trains on it. The one of the difficulties for me is the recognizing the direction of the train what entered or left a track. I lack the information about the other relevant track in the event. These are the previous track in "Train enters to a track" event and the next track in "Train leaves a track" event. The query "Locomotive/Wagon is located on a track" is uncertain when the concerned tracks are short. Solving this problem may be one of the next developing goals. For example the 6120 and 6230 are an railway crossing with barriers ...|-6140-|----------------6110-------------|===6120===|=6230=|----------6210-----------|-6240-|---... Events 1. Any train enters to 6110 from LEFT - close barriers 2. Any train enters to 6210 from RIGHT - close barriers 3. Any train leaves the 6120 to LEFT - open barriers 4. Any train leaves the 6230 to RIGHT - open barriers If the event handler would serve the name of the other relevant track in the event to "_Triggerx" than the defining events can be easy. 1. Event - Train enters to a track - All locomotives - 6110 1. Conditions - Variable has the values - $_Triggerx._Name - 6140 1. Actions - ... 2. Event - Trains enters to a track - All locomotives - 6210 2. Conditions - Variable has the values - $_Triggerx._Name - 6240 2. Actions - ... 3. Event - Trains leaves a track - All locomotives - 6120 3. Conditions - Variable has the values - $_Triggerx._Name - 6110 3. Actions - ... 4. Event - Trains leaves a track - All locomotives - 6230 4. Conditions - Variable has the values - $_Triggerx._Name - 6210 4. Actions - ... This way helps to decide which end of the train triggered the event too. In another version I can imagine to define the required neighbor of the target track in the 3rd event parameter. If the 3rd parameter can of "All tracks" the event handling remains compatible. Other possibilities: The "All tracks" option in 2nd parameter enables the traceability with event handling. Sorry for English I can't speak German. Viele Grüß kronauerl
×
×
  • Neu erstellen...