8209 Last boot failed

Description

The message is usually triggered due to a drop in the control voltage of the PacDrive controller, a reset of the PacDrive controller or an error is detected in the last restart procedure. Use DiagExtMsg to localize the issue. While restarting, the PacDrive controller logs the individual phases in the NvRam. If this results in an error (Error LED is ON constantly), then the next restart starts only with the basic configuration and the diagnostic message 8209 is triggered.

NOTE: If the PacDrive controller is started in minimal restart mode, the configuration and the PLC configuration parameters are set to their default values.

NOTE: The next startup proceeds in normal restart mode. If this does not happen, the default configuration is used for the next startup. The process is then repeated.

DiagExtMsg	Meaning
1	Restart procedure begins before kernel initialization
2	Kernel initialization complete; FTP server priority adjusted; Time Slicing switched on; System clock; No. Tick per second defined; Tick per second determined.
3	Init logger and NvRam complete; interrupts blocked
4	Diagnostic created, messages sent before ObjectContr new
5	After ObjectContr new
6	After axis release, before WatchDogEin
10	Begin Constructor ObjVerObjektContr; Tasklock active
11	Configuration and Parameter files read
12	Configuration file evaluated, generate before objects
13	Generate after objects
14	Set after CycleTime
15	After initialization of Moni.Max, LogGeb, VirtGeb, PhyGeb, construction of RTP before filling in indication table.
16	Set after parameter
17	After Sercos phase-up
18	After runtime system start
19	After RTP start, before program load
20	After program load
31	Before ScanDisk
1020	CoDeSys runtime starts and the boot application is loaded.
RAM < 32 Mb	Insufficient RAM in the PacDrive controller

Procedure:

Logic Builder connection with TCP/IP
Read and evaluate message logger (DiagExtMsg)
The DiagExtMsg can be used to read which phase of the restart procedure was executed correctly the last time.

Cause	Solution
The FC_SysReset() function was called, although the restart procedure of the PacDrive controller was not yet complete.	Use the FC_GetPacDriveBootState() function to ensure that the PacDrive controller has stopped the restart procedure before you use the FC_SysReset() function.
DiagExtMsg = `19`: program error, indicating that the application is incorrect.	Verify and correct if necessary your program and download it to the PacDrive controller.
DiagExtMsg is not 19.	Contact your service representative.
The PacDrive controller was booted twice in quick succession. This may have been caused by pressing the reset button twice or a drop in the control voltage.	Verify and correct if necessary the control voltage (also refer to the technical data).
Insufficient RAM in the PacDrive controller for the project (DiagExtMsg=`out of memory`). Meaning: A memory requirement could not be executed. Memory is required when booting, resetting the task, calling up system function blocks, setting/reading parameters, establishing/terminating an FTP connection, transferring data (remote device), communicating with Logic Builder, and establishing/terminating a Telnet connection and communicating with Telnet.	Optimize the configuration. Decrease the RamDiskSize. Reduce number of tasks. Apply a PacDrive controller that has more RAM.