/build/android/

only if condition applies IE; Execute code1 only if condition applies, else execute code2 Conditions: + / - Tests the train's movement direction against the arrow on the ATC rail: M+ is true when train drives in direction of arrow. [/<=/>=][speed] Test if train's speed is greater or smaller than the given value Examples: I- B0 W R ; S8 If the train drives in the 'wrong' direction, stop and reverse; independently accelerate to speed 8 afterwards. I<8 S8 ; If the train is slower than 8, accelerate to 8. # ATC controller operation modes static: Only give 1 static command. mesecon: Give 2 different commands depending on if the controller is mesecon-powered or not digiline: Don't give any commands by itself. When a train passes, a digiline message in the form of "[+/-][speed]" is sent on the set channel (where +/- means the same as with conditions). Any digiline message sent to the controller will be interpreted as ATC command and sent to the train. ** the latter two are not yet implemented. # Persistence ATC controllers that are configured as 'static' or 'mesecon' are persistent over mapblock unloads and will even command the train when the mapblock is unloaded. This is not possible with digilines since these do not work in unloaded mapchunks. # LUA ATC controller (in development) The LUA ATC Controller will operate by using LUA code. All operations shown above will have a function equivalent. Additionally all LUA ATC controllers share an environment and setting signal and switch status will be possible to allow for complicated railway systems/fully automated subways a.s.o. Also planned: - digicompute add-on to allow computer access to the ATC environment (railway maps... ... ... ... ...)