Skip to content

Commissioning, engineering and support
Power plants and industrial processes
ALSPA P320 expert

ALSPA knowledge base

This knowledge base provides answers to various issues encountered on ALSPA P320 systems. Select a question to display the associated procedure or diagnostic information.

You can contact ICSS for assistance or to suggest new information for inclusion in this knowledge base.

Configuration and engineering tools

ALSPA P320 Series 5 — After reloading a C80-75 controller, why are tuning parameters displayed in scientific notation?

After using the Backnote Parameters function in CellLoader, some parameters may lose their original resolution. A value such as 0.000281345672 may then be stored as 2.83E-04.

Two methods can restore the parameters:

  • From a recent export. Use a project export made immediately before Backnote Parameters, then compare its tuning values with those in the current project.
  • From an older export. Find the latest adjustments made from the Watch Windows in the Controset / Edit setting operations on applicative variables log, then compare them with the values in the available export.

In both cases, ICSS can provide a tool based on SQL queries to collect parameters before and after the operation, compare the values and automatically correct affected settings.

ALSPA P320 Series 6 — How can HMI behaviour be modified in depth, for example to display more than 1,000 Historian events?

Many HMI parameters are defined in the following file:

C:\P320\exe\oc\Centralog\HMI\Pynw_Centralog.exe.config

These parameters can increase the number of events displayed or modify the behaviour and dimensions of views.

To propagate the changes to all stations, the customised file must be saved on both CIS stations at the following location:

E:\P320DATA\HMISettings\Public\Pynw_Centralog_custom.exe.config

The other stations automatically retrieve this configuration after reconnecting to the HMI.

All ALSPA P320 versions — What can be done if a Historian, HMI, Controcad or P4 library password is lost?

Most passwords used by Historian,HMI, Controcad or P4 libraries can be cleared or recovered.

For security reasons, the corresponding procedures are not published openly. Contact ICSS and specify the system, version concerned and project context.

Controllers, communications and diagnostics

ALSPA P320 Series 5 — Why is Modbus communication over IR139 lost during a C80-75 controller switchover?

Check that the Modbus arrays used by the IR139 module are assigned to redundancy areas.

During a C80-75 controller switchover, a non-redundant array may be momentarily reset. If a variable such as 11MKA10GS100_XB02 is then seen at zero for more than five seconds by the control system, the protection logic may interpret this state as a communication loss and trip the unit.

Assigning the Modbus arrays to redundancy areas retains their values during the switchover and prevents this interruption.

ALSPA P320 TGC — How can the firmware version of a CPU310 be read?

When the CPU310 is installed, its firmware version can be read over Ethernet through the ETM001 module:

  • Open Machine Edition and create an empty project
  • Add a controller of type RX3i
  • Select Target1, then Ethernet connection (physical port), and enter the IP address of the ETM001
  • Put the controller online using Online
  • Use Target → Online Commands → Show Status to display the firmware version

When the CPU is not installed in a system with Ethernet access, the procedure is similar using a suitable serial connection.

ALSPA P320 Series 5 — How can the EEM firmware version be read with Station Manager?

In Station Manager, enter the following command:

node

The information returned identifies the firmware version of the EEM module.

ALSPA P320 Series 5 — How can the list of forces present in a controller be displayed?

The list of forced variables is available in the System Watch Window.

Historian and Sun workstations

All ALSPA P320 versions — Why is Historian particularly slow to start?

At start-up, Historian clears temporary tables in the RDM database used by the HMI. This operation also applies to restored databases.

When many restored databases are present, clearing their temporary tables can significantly increase start-up time.

After backing up the data and following the applicable shutdown procedure, the contents of the hdsr_temp_tab folder can be deleted to reduce this delay.

ALSPA P320 Series 4 — What does the “Invalid format type in NVRAM” error mean after restarting a Sun workstation?

The station may display the following messages:

Ethernet address ff:ff:ff:ff:ff:ff, Host ID ffffffff

Invalid format type in NVRAM
The IDPROM contents are invalid

These messages generally indicate that the NVRAM battery has failed. The permanent solution is to replace the chip. You can contact ICSS to source a compatible spare part.

After installing the new chip, it must be programmed from the OpenBoot prompt using the mkp command. The last three bytes of the Ethernet address must match the last bytes of the Host ID. This information can be found in the station configuration file in the CCC.

Enter the following commands from the OpenBoot prompt, replacing the fields in angle brackets with the bytes corresponding to the station:

set-defaults
setenv diag-switch? false
01 0 mkp
80 1 mkp
08 2 mkp
0 3 mkp
20 4 mkp
<byte 4 of the Ethernet address> 5 mkp
<byte 5 of the Ethernet address> 6 mkp
<byte 6 of the Ethernet address> 7 mkp
0 8 mkp
0 9 mkp
0 a mkp
0 b mkp
<byte 4 of the Ethernet address> c mkp
<byte 5 of the Ethernet address> d mkp
<byte 6 of the Ethernet address> e mkp
0 f 0 do i idprom@ xor loop f mkp

The manufacturer prefix 08:00:20, used by Sun Ultra 2 and Ultra 5 workstations, must not be changed.

Temporary solution: this procedure can also be run at start-up when the NVRAM battery has failed, pending replacement of the module. It must, however, be repeated after every subsequent restart.