HIMA X-CPU 01

Description

HIMA X-CPU 01Safety-Related Processor SystemThe safety-related processor module is a 1oo2 processor system. Continuous self-testsensure safety-related operation.Characteristics:Two synchronous microprocessorsSpecific DDRAM memory for each microprocessorTestable hardware comparator for data busesWatchdog (WD)Gold capacitor for buffering date/timeLEDs for indicating the system statusesMode switch for configuring the module behavior when voltage is switched onThe processor module compares the data on both processors and triggers an interrupt if afault occurs.A watchdog monitors both processors. Self-tests of the module also check the watchdog.3.4.3System ControllerThe system controller handles the entire data transfer between the various components ofthe module:Safety-related processor systemSystem busses A and BEthernet switch with connected interfaces3.4.4MemoryThe module has a RAM and a non-volatile memory. The non-volatile memory is protectedby a CRC.The non-volatile memory contains the following programs and information:Operating SystemUser projectEnable switch, watchdog time, safety timeOnline modificationsVariable with the RETAIN attributeProduction data and, if necessary, trimming dataFault status historyEventsWhile booting, the system transfers the program code from the non-volatile memory to theredundant program and data memory.3.4.5Alarms and EventsThe processor module records alarms and other events in its non-volatile memory.Events are state changes of a variable that are performed by the plant or controllers andare provided with a timestamp.Alarms are events that signalize an increasing risk potential.The HIMax system records the state changes as events specifying the time point when theyoccurred. The X-OPC server transfers the events to other systems such as controlsystems, that display or evaluate the events.HIMax differentiate between Boolean and scalar events

Boolean Events:Changes of Boolean variables, e.g., of digital inputs.Alarm and normal state: They can be arbitrarily assigned to the variable states.Scalar Events:Exceedance of the limit values defined for a scalar variable.Scalar variables have a numeric data type e.g., INT, REAL.Two upper limits and two lower limits are possible.For the limit values, the following condition must be met:Highest limit ≥ upper limit ≥ normal area ≥ lower limit ≥ lowest limit.An hysteresis can be effective in the following cases:- If the value falls below the upper limit.- If the value exceeds the lower limit.An hysteresis is defined to avoid a needless large number of events when a global variablestrongly oscillate around a limit.The processor module can only create events if they are configured in SILworX, seeChapter 4.1.5.3.4.6Creating EventsBoth the processor module and certain types of I/O modules are able to create events. Inthe following sections, these I/O modules are referred to as SOE modules.Creating Events on the Processor ModuleThe processor module uses global variables to create the events and stores them in thebuffer, see Chapter 3.4.7. The events are created in the user program cycle.Creating Events on SOE ModulesSOE modules can create events using the input states. The events are created in the SOEmodule cycle.The SOE module stores the events in the intermediate buffer that the processor modulesuse to read them. The intermediate buffer is part of the volatile memory so that the eventsare lost if the power is switched off.Every event that has be read can be overwritten by a new event.System EventsIn addition to events, which records changes of global variables or input signals, processorand SOE modules creates the following types of system events:Overflow: Some events were not stored due to buffer overflow. The timestamp of theoverflow event corresponds to that of the event causing the overflow.Init: The event buffer was initialized.Operating mode Stop: A SOE module changed its operating mode to STOP.Operating mode ‘Run’: A SOE module changed its operating mode to Run.Establishing communication: Communication between processor module and SOEmodule has started.Losing communication: Communication between processor module and SOE modulewas terminated.System events contain the SRS identifier of the module causing the events