NVRAM Safety Information

Note
Since V6.4.6, ASCET‑RP supports only the ES900 hardware system. Projects with an ES1000 hardware configuration cannot be used. To work with RTPRO-PC hardware configurations, you have to use an external INTECRIO V4.7.2 or older as hardware configurator (see Selecting an External Hardware Configurator)(see Selecting an External Hardware Configurator).

Note

Since V6.4.6, ASCET‑RP supports only the ES900 hardware system.

Projects with an ES1000 hardware configuration cannot be used.

To work with RTPRO-PC hardware configurations, you have to use an external INTECRIO V4.7.2 or older as hardware configurator (see Selecting an External Hardware Configurator)(see Selecting an External Hardware Configurator).

For details on the NVRAM possibilities of the ASCET‑SE targets, see the ASCET‑SE documentation and the documentation of the production targets.

WARNING
Harm or property damage due to unpredictable behavior of vehicle or test bench Wrongly initialized NVRAM variables (NV variables) can lead to unpredictable behavior of a vehicle or a test bench. This behavior can cause harm or property damage. Projects that use the NVRAM possibilities of the experimental targets or the ASCET‑SE targets expect a user-defined initialization that checks whether all NV variables are valid for the current project, both individually and in combination with other NV variables. If this is not the case, all NV variables have to be initialized with their (reasonable) default values. Due to the NVRAM saving concept, this is absolutely necessary when projects are used in environments where any harm to people and equipment can happen when unsuitable initialization values are used (e.g. in-vehicle-use or at test benches).

WARNING

Harm or property damage due to unpredictable behavior of vehicle or test bench

Wrongly initialized NVRAM variables (NV variables) can lead to unpredictable behavior of a vehicle or a test bench. This behavior can cause harm or property damage.

Projects that use the NVRAM possibilities of the experimental targets or the ASCET‑SE targets expect a user-defined initialization that checks whether all NV variables are valid for the current project, both individually and in combination with other NV variables. If this is not the case, all NV variables have to be initialized with their (reasonable) default values.

Due to the NVRAM saving concept, this is absolutely necessary when projects are used in environments where any harm to people and equipment can happen when unsuitable initialization values are used (e.g. in-vehicle-use or at test benches).