|
Warning |
When it happens |
What to do |
|
Product not yet registered |
When the product is installed but the activation code was not requested and entered. |
Obtain the activation code from CAREL. Enter it in System pages, Information. Log out and open the product again. |
|
guardianPRO setup |
At first PlantVisorPRO Locale or RemotePRO launch. |
Set up and start guardianPRO to monitor unmanaged alarms, check variable changes and hardware and software performance (see chapter PVPRO loc: procedures) |
|
Restart the engine |
Field configuration changed (devices or sites added or deleted). Monitoring still considers the previous configuration, ignoring new devices or sites. |
Reboot from message. |
|
Trial period expired |
The product was first started more than 30 days ago and the product has not been activated yet. |
Launch the product (see page System: information) |
|
Behavior |
When it happens |
What to do |
|
The computer rebooted |
guardianPRO found a fault condition that required machine reboot. See chapter guardianPRO: basic concepts |
Check for potential fault conditions in the events page. |
|
The system does not seem to have recognized setup changes |
|
Restart the engine to permit the new configuration to be read. |
|
Behavior |
When it happens |
What to do |
|
As soon as the user calls a function, PlantVisorPRO Locale exits the active session and displays the logon page |
When maximum system stand-by time expires. The time set by Installers in the System page (see chapter System: system status) When another user with the same account logs onto the system. |
Re-access the system. |
|
A sound tied to an alarm is heard but the alarm window does not appear |
For some reason the alarm window is behind the PlantVisorPRO window. |
Close the browser window |
PlantVisorPRO Locale 2.2.0 -