The sequence of operations at switch on is as follows:

Operations performed by OSE (Operating system eprom)

1.The eprom-resident OSE operating system, after performing hardware diagnostics, checks for the presence of the RTE operating system on the Compact flash

If it does not find it, it remains in "waiting for a command" mode [on CPU: Message Code 42 with L7 ON]. The user must now load, via the RDE development environment or by copying the firmware to the CF from PC, the RTE operating system.

If it finds it, it will yield the command to him.

Operations performed by RTE (Real time extended)

1.Reading and analysis of configuration file RTE.CFG with possible diagnostic in report

2.From RTE 34.24.8, verification of writing to the retentive zone. If the test fails,alarm 9 is generated.

3.Retentive zone verification: retentive register area (NVR, NVRR, NVSR)

4.Retentive zone verification: parameters area(predefined variables)

5.Retentive zone verification: alarm history area

6.Resetting of all volatile registers (R, RR, SR) and non-retentive predefined variables

7.Various initializations, including those of serial channels configured as follows (by default):

P.SER 1 : DLE-BCC3 communication

P.SER 2 : DLE-BCC3 communication

P.SER 3 : DLE-BCC3 communication

P.SER 4 : DLE-BCC3 communication

1.Checking the validity of the data saved in the retentive memory and the correct previous shutdown:

A.If user registers retention area loss is recognized and there is no "LOSTRNA.STP" file in flash, alarm "1 User Registers loss" is issued

B.If a reduction in the registers area is recognized, the alarm "9000 User Registers Reduced" is issued

C.If a change in the memory area size of user structs is recognized, alarm "9005 Retentive Memory structure modified" is issued

D.If a different number of registers is recognized between those detected in retentive memory and those defined in the configuration file, alarm "9001 Different User Registers Definition" will be output

E.If the inability to have retentive parameters is recognized, alarm "9002 Parameter Registers Area Not Available" will be output

F.If the loss of the retentive parameter area is recognized and there is no "LOSTPANA.STP" file in flash, alarm "2 Parameter Registers loss" will be output

G.If the number of parameters present in retentive area is different than those managed by RTE program alarm "9003 Different Parameter Registers Area" will be output

H.If alarm history area loss is recognized and "LOSTPANA.STP" file is not present in flash, alarm "3 Alarm History loss" will be output

I.If the alarm history area is reduced the alarm "9004 Alarm History dimension reduced" will be output.

J.If it is not possible to have retentive global variables, alarm "4 Unable to initialize Persistent Global Variables" will be output.

K.If a data error is found or a reset of the retentive memory area of global variables has been requested and the file "LOSTPGVNA.STP" is not present, alarm "5 Checksum error in Persistent Global Variables" will be output

L.If the memory area of the retentive global variables has been moved and the file "LOSTPGVNA.STP" is not present, the alarm "6 Unable to read Persistent Global Variables" will be output

M.If the internal layout (which depends on the specific version of RTE) of the memory area of the retentive global variables has been changed the alarm "9007 Pers.Glob.Var. appearance modified. PGV area to be reset"

N.If during the last shutdown the normal handling performed by RTE could not be performed, the alarm "995 Power OFF left out, SYSTEM has been reset <task>" will be output

2.In case of errors in the retentive zone, the "Lost memory mode" is selected: as long as at least one of the above alarms is present in the alarm stack, excluding alarm 995, the control does not proceed further. It merely honors the BCC commands and displays a continuously changing numeric code

3. Once any previous alarms have been reset:

A.If user logs had been lost, they are reset and the LOSTRNA. STP or LOSTREG.STP files are executed

B.If parameters had been lost, they are reinitialized with default values and the LOSTPANA.STP or LOSTPAR.STP files are executed

C.If the alarm history had been lost, we proceed to its reinitialization

4. Execution of the AUTOEXEC.STP file

5. Managing the configuration file related to data exchange via profibus(PFB.CFG)

6. Managing the configuration file related to data exchange via deviceNet(DNSn.CFG)

7. Management of the configuration file related to CanOpen communication(COCn.CFG)

8. Management of the configuration file related to DF1 communication(DF1.CFG)

9. Management of the configuration file related to EtherCAT communication(ECATn.CFGX and FB.CFG)

10. Management of the configuration file related to synchronous CNET between controls(RBXCNET.CFG)

11. Management of the resolution of external variables of any loaded tasks

12. Operating mode setting:

A.If task 1 has been loaded it is put into execution along with any ladder tasks present

B.If task 1 has not been loaded or if FEED+ and MODE pressed then control is put into loading mode (if ladder tasks were already running they are not stopped)

C.If the keyword COND_LOAD_WITH_ADV is present, it is possible by pressing the ADV button to stop loading by RTE. It will then be up to the user to load the tasks with shell commands

13. RTE starts executing the instructions contained in the file task1.elf

At this point the management of the device is totally in the hands of the application. Enabling the other tasks is the responsibility of task 1.

NOTE: It is possible to override some of the commands in RTE.CFG via the OVERRIDE.CFG file.

NOTE: It is possible to get information about the operations performed by RTE via the MREPORT command (from shell), instead use the D MO or MODE directive to know the status of the control.