Installation and Maintenance Manual

Diagnostics
RLC-SVX09H-EN 213
Starter 1A Comm Loss: MP Cprsr Immediate Latch All
Starter has had a loss of communication with the
MP for a 15 second period.
Local
Starter 2A Comm Loss: MP Cprsr Immediate Latch All
Starter has had a loss of communication with the
MP for a 15 second period.
Local
Table 135. Communication Diagnostics
Diagnostic Name
Affects
Target Severity Persistence
Active
Modes
[Inactive
Modes] Criteria
Reset
Level
Table 136. Main Processor (Boot Messages and Diagnostics)
DynaView Display Message
Description
Troubleshooting
A Valid Configuration is Present
A valid configuration is present in the MP’s nonvolatile memory. The configuration is a set of variables
and settings that define the physical makeup of this particular chiller. These include: number (airflow,
(and type of fans, number (and size of compressors, special features, characteristics, and control
options.
//Temporary display of this screen is part of the normal power up sequence.
An Invalid Configuration is Present
An invalid configuration has been detected in the Main Processor’s nonvolatile memory and the MP is
unable to proceed with the boot up. Communication via the service serial port is supported and the
TechView service tool, (Configuration View), needs to be employed to correct the configuration.
App Present. Running Selftest.…
Selftest Passed
An application has been detected in the Main Processor’s nonvolatile memory and the boot code is
proceeding to run a check on its entirety. 8 seconds later, the boot code had completed and passed
the (CRC) test.
//Temporary display of this screen is part of the normal power up sequence.
App Present. Running Selftest…
Err3: CRC Failure
An application has been detected in Main Processor’s nonvolatile memory and the boot code is
proceeding to run a check on its entirety. A few seconds later, the boot code had completed but failed
the (CRC) test.
//Connect a TechView Service Tool to the MP’s serial port, provide chiller model number (configuration
information) and download the configuration if prompted by TechView. Then proceed to download the
most recent RTWD application or specific version as recommended by Technical Service. Note that this
error display may also occur during the programming process, if the MP never had a valid application
any time prior to the download. If the problem persists, replace the MP.
Boot Software Part Numbers:
LS Flash --> 6200-0318-04
MS Flash --> 6200-0319-04
The “boot code” is the portion of the code that is resident in all MPs regardless of what application code
(if any) is loaded. Its main function is to run power up tests and provide a means for downloading
application code via the MP’s serial connection. The Part numbers for the code are displayed in the lower
left hand corner of the DynaView during the early portion of the power up sequence and during special
programming and converter modes. See below. For the EasyView, the extension of the boot code part
number is displayed for approximately 3 immediately following power up.
//This is normal, but you should provide this information when contacting Technical Service about
power up problems.
Converter Mode
A command was received from the Service Tool (Tech View) to stop the running application and run
in the “converter mode”. In this mode the MP acts as a simple gateway and allows the TechView service
computer to talk to all the LLIDS on the IPC3 bus.
Err2: RAM Addr Test #1 Failure
There were RAM errors detected in RAM Address Test #1.
//Recycle power, if error persists, replace MP.
Err2: RAM Addr Test #2 Failure
There were RAM errors detected in RAM Address Test #2.
//Recycle power, if the error persists, replace MP.
Err2: RAM Pattern 1 Failure
There were RAM errors detected in RAM Test Pattern #1.
//Recycle power, if the error persists, replace MP.
Err2: RAM Pattern 2 Failure
There were RAM errors detected in RAM Test Pattern #2.
//Recycle power, if the error persists, replace MP.
Err4: UnHandled Interrupt
Restart Timer:
[3 sec countdown timer]
An unhandled interrupt has occurred while running the application code. This event will normally cause
a safe shutdown of the entire chiller. Once the countdown timer reaches 0, the processor will reset,
clear diagnostics, and attempt to restart the application and allow a normal restart of chiller as
appropriate.
//This condition might occur due to a severe electro-magnetic transient such as can be caused by a
near lightening strike. Such events should be rare or isolated and if no damage results to the CH530
control system, the Chiller will experience a shutdown and restart. If this occurs more persistently it
may be due to an MP hardware problem. Try replacing the MP. If replacement of the MP proves
ineffective, the problem may be a result of extremely high radiated or conducted EMI. Contact Technical
Service.
If this screen occurs immediately after a software download, attempt to reload both the configuration
and the application. Failing this, contact Technical Service.