4.3 START-UP

4.3.1 Start-up of LCU

The LCU is booted from a boot script which loads ESO standard software (LCC, drivers, communication software and motor control module) and starts LCC. The boot script shall be created and modified with the tool vccConfigLcu, see [8].

The boot script calls a set of module startup scripts, xxx.boot where xxx is the module name. There is one such script for each LCU module.

Application software modules shall supply such a script containing the loading of the module and the required initialization, see the[8] for the format. The module startup script shall be inserted into the boot script with vccConfigLcu.

It is recommended to start the application from an initialization process, which spawns the processes required by the application.

For restarting of a system after a crash or when the application processes have been terminated (killed) there are two possibilities:

1. reboot the LCU for a complete restart (lccColdStart)

2. terminate (kill) all application processes and restart them:

a. terminate the processes by sending a KILL or EXIT command

b. optionally reload the application processes. This can be done with the LCC service lccReload (command LCCRLD) or just execute the module startup script

c. start the application processes. This can be done with the LCC service msgScheduleProcess (command MSGSCHP)

If the process is complex it is preferably done by a VxWorks script or more flexible with a sequencer script

To save memory unload modules which are not needed after the start-up phase.

4.3.1.1 Errors during booting

In case an error occurs during the execution of the boot script, the execution is interrupted and the error can be viewed on the system console connected to port 1 of the CPU board. If you do not have any system console, reboot your system with the tool vccConfigLcu. Now the output to the system console will be sent to the WS window where you started vccConfigLcu.

It is also possible to inspect the bot log after a boot failure with the tool lcustatCheck. This tool also gives you the possibility to supervise the state of your LCU(s).

During loading of the database or a CDT file a message like the following will be printed if the database or the CDT is big:

0xe723cc (tlccInitAll): memPartAlloc: block too big - 35 in partition 0xe8716c.

When loading the database LCC allocates a certain amount of memory and starts filling it with the database. When this first memory partition is full, VxWorks gives an error, and LCC allocates more memory for the database.This error is normal for a big database or a big CDT, because we do not want to allocate the maximum amount of memory which we possibly would need.

The error message printed on the console comes from VxWorks and cannot be suppressed. But as explained it is not an error, just an indication that LCC allocated more memory. Therefore we have to live with it and ignore it

Quadralay Corporation http://www.webworks.com Voice: (512) 719-3399 Fax: (512) 719-3606 sales@webworks.com