This implies the detection cycle in Aimsun Next must be one second.
Time Synchronization ¶Īimsun Next and most adaptive controllers interchange information every second, this is a requirement of the controller. Refer to the Lisa+ section section for more details. Server Data Dir The directory where the configuration files are stored.Server Java Command: The Java command required to start the Java VM that runs the Lisa+ Emulator.Detection Time: Interval (in seconds) when Aimsun Next will send detection data.Synchronization Time: Interval (in seconds) when Aimsun Next and ETRA will synchronize data.Refer to the SCATS section section for more details. The SCATS Central Manager IP address and ITS communications port number.It is only recommended to activate this option in very special cases for example, when debugging the application. If the message does not arrive Aimsun Next will hang forever. This can be activated to disable timeout so that Aimsun Next will wait for the message to arrive without timing out. Completion message sent to SCATS: This can either be Message 127 or Message 254 depending on the SCATS configuration.Preferences ¶Īdaptive Control Interfaces Preferences are accessible from the Preferences command in the Edit menu, which opens the System Preferences editor (when no model is open) or the Model Preferences editor (when a model is open).Įxternal Controller Client: The path to the EXE file for the client executable. Note that the Sitraffic Office controller also includes two more tabs, one to specify the dynamic information to be displayed and the other to show a time line of activity and protocol use. The option to create these files is selected in the Controllers of the Scenario Editor. Log files are output by some control interfaces. The detail for each interface is described in the relevant section as the use of signals and detectors varies between the different interfaces and this is reflected in the customization of the tabs in the Adaptive Controller properties editor.
The type of controller is defined depending on the Adaptive Control Interface used to link to Aimsun Next: The details of the link for each controller type is described in the appropriate controller section. For example if Detector 2540 is linked to the controller, it can be given ID 101 in the communication and linked to transit lines as shown below. Each object is given an external ID used in the communication with the controller and other information according to controller type. In the Signal Groups, Detectors, Transit and Pedestrian Walks tabs appear according to the capability of the type of external controller selected. Nodes can also be added by selecting "New" then clicking the node in the 2D window.
Controller editor software#
Controller Editing ¶Ī Controller is created and position in the network, then linked to adjacent junctions and detectors and finally configured to link to the external software interface, as documented in the Adaptive Control Interfaces Section. This section describes the Controllers required to link to the Adaptive Control Module and the associated software interfaces developed in the Aimsun Next environment.Ī controller is the Aimsun object which represents real traffic signal controllers and their relation with detectors, signal groups, and pedestrian crossings to monitor the control plan information in junctions.
0 kommentar(er)
