UPS Configurators

Configuration Options in the Deployment Window
By the Editor Release of the StandOS Configurator you can create operating states as for example Power-On, Run, GotoSleep, Sleep, Wakeup and Flash. By the Resource Deployment you then can configure events to the operating states, as for example interrupts, resets, timer-cycle-events and occured error events, which are set by the self diagnosis of the StandOS operating system. When such an event needs an activity, like an emergency power off, this can be deployed into an operating state in realtime.

Configuration Options in the Organisations Window
In the Organisation window for every deployment input- and output drivers and applications can be created. It it also is possible to force all input and output data. For the applications a multitasking  can be configured. When multitasking is configured and another Universal Programming Studio tool is debugging in cycle step, all multi tasking steps are executed to complete the cycle. When ARCON or RACKSYS controllers are applied, automatically the proper input and output drivers will be entered in the respective columns as configured by the System Configurator.

The Editor Release of the Diagnose Configurator offers you all aspects of the development of UDS diagnostic software:

• The tracking history
• The creation all UDS diagnostic messages
• The creation the complete AutoSAR compatible DTC error memory
• The organisation of the non-volatile memory

 

The Editor Release of the System Configurator offers the following:

• The configuration of networks
• The hard and software configuration of the frontend controllers

The configuration of networks
The Editor Release of the System Configurator offers the configuration networks of distributed controllers, where the net structure relates to the directory tree of the hierachical ordered projekts.

The hard and software configuration of the frontend controllers
At each double click on a controller hard and software configurators are called, by which all digital and analog inputs and outputs can be configured. In case of ARCON and RACKSYS controllers respektive input and output drivers for the StandOS operating system configured.

The Code Generation Release of the System Configurator offers the generation of configuration files (html and header files) for the StandOS operating system and for all Universal Programming Studio tools.
All features of the Editor Release are included in the Code Generation Release.

The Code Generation Release offers the generation of C, C++ or C# code by the StandOS Configurator. After clicking the menu "File - Save and generate code" the complete code for the selected deployment is generated. The created C, C++ or C# code will finally be copied into the StandOS directory of the seletcted project and be displayed in the output window.

Quite a few of functional safety software is generated automatically, as for example the self diagnose software for the supervision of exceeded cycle times. StandOS is applying the slim and safe Round-Robin-Multitasking, thereby avoiding critical timing incidents.

By the Generate Code Release C, C++, C# and header code can be generated as an input for the StandOS Configurator. StandOS is then responsible for the respective activities in the ECU.
In the Generate Code Release all features of the Edit Release included.

The StandOS operating system can up- and download all configuration data of the hard- and software of the distributed controllers. In this way modifications of the communication as well as the hard- and software of the distributed controllers can be done at runtime.
All features of the Editor Release and the  Code Generation Release are included in the Online and Debug Release.

The window "Testing StandOS" offers the test of all newly configured deployments. While for example load tests are run by the PMS- AutoSAR Tester, the StandOS Configurator can in the "Testing StandOS"  window show all cycle timings, as for example the minimum-, maximum- and mean- timings of all deployments. When cycle timings are exceeded, also the date and time is displayed in milliseconds.

In the DTC window all error data are shown, as fixed in the AutoSAR standards. All timing data are captured by StandOS in realtime and polled by StandOS via diagnose messages.