Power Command
Power Command
PC500CL (Spec A)
PC550CL (Spec A)
PowerCommand CloudTM Web App
PowerCommand CloudTM iOS Mobile App
PowerCommand CloudTM Android Mobile App
English
Original Instructions 9-2017 A053H888 (Issue 4)
Table of Contents
1. IMPORTANT SAFETY INSTRUCTIONS ....................................................................................... 1
1.1 Warning, Caution, and Note Styles Used in This Manual ..................................................... 1
1.2 General Safety Precautions.................................................................................................... 1
2. INTRODUCTION............................................................................................................................ 3
2.1 About this Manual ................................................................................................................... 3
2.2 List of Abbreviations and Acronyms ....................................................................................... 3
2.3 How to Obtain Service ............................................................................................................ 4
2.3.1 In North America .......................................................................................................... 4
2.3.2 Outside North America................................................................................................. 4
3. DESCRIPTION............................................................................................................................... 5
3.1 Models .................................................................................................................................... 5
3.2 Cloud Based Remote Monitoring System............................................................................... 5
3.3 Controls................................................................................................................................... 6
3.4 PC500/550 Cloud Link ............................................................................................................ 7
3.4.1 LED Indicators.............................................................................................................. 8
3.4.2 TB1............................................................................................................................... 9
3.4.3 TB2............................................................................................................................. 10
3.4.4 Reset Button .............................................................................................................. 10
3.4.5 Ports........................................................................................................................... 11
5. SYSTEM REQUIREMENTS......................................................................................................... 21
5.1 Hardware Requirements ....................................................................................................... 21
5.2 Software Requirements ........................................................................................................ 21
8. OPERATION ................................................................................................................................ 53
8.1 PowerCommand Cloud Web Application.............................................................................. 53
8.1.1 Account Creation........................................................................................................ 53
8.1.2 Sign In........................................................................................................................ 53
8.1.3 Dashboard.................................................................................................................. 53
8.1.4 My Profile ................................................................................................................... 54
8.1.5 Site View .................................................................................................................... 55
8.1.6 View Asset ................................................................................................................. 56
8.1.7 Account Management ................................................................................................ 57
8.2 PowerCommand Mobile Application ..................................................................................... 57
8.3 Setup Gateway Home Page Dashboard Screen .................................................................. 58
8.4 Menu Bar .............................................................................................................................. 58
8.5 System Status Bar ................................................................................................................ 58
9. TROUBLESHOOTING ................................................................................................................. 65
9.1 Event Codes ......................................................................................................................... 65
9.1.1 Code 319 – Real-Time Clock Backup Battery – Very Low Voltage .......................... 65
9.1.2 Code 762 – Real-Time Clock Backup Battery Voltage Above Normal Operating
Range ......................................................................................................................... 65
9.1.3 Code 763 – Real-Time Clock Backup Battery Voltage Below Normal Operating
Range ......................................................................................................................... 66
9.1.4 Code 4332 – Loss of Communication with (device) on Channel 1 or 2 ................... 66
9.1.5 Code 4351 – AUX102 Not Detected ......................................................................... 68
9.1.6 Code 4353 – Software Download Failed .................................................................. 69
9.1.7 Code 4354 – Software Download has been Started ................................................ 69
9.1.8 Code 4355 – Software Update Successful ................................................................ 69
9.1.9 Code 4356 – Software Update Failed........................................................................ 69
9.1.10 Code 4357 – System Error ...................................................................................... 69
9.1.11 Code 4594 – <Sensor> has High Warning .............................................................. 70
9.1.12 Code 4595 – <Sensor> has Low Warning............................................................... 70
9.1.13 Code 5138 – Genset Control Not in Auto ................................................................ 70
9.1.14 Code 5139 – Auto Transfer Switch Not in Auto....................................................... 70
9.1.15 Code 5141 – Source 1 Connected .......................................................................... 70
9.1.16 Code 5142 – Source 2 Connected .......................................................................... 70
9.1.17 Code 5143 – Genset Running ................................................................................. 70
9.1.18 Code 5144 – Genset Stopped ................................................................................. 71
9.1.19 Code 5341 – <Sensor> is Active ............................................................................. 71
9.1.20 Code 5342 – <Sensor> is Inactive........................................................................... 71
9.1.21 Code 5657 - Source 1 Available .............................................................................. 71
9.1.22 Code 5658 - Source 2 Available .............................................................................. 71
9.1.23 Code 5659 - Source 1 Not Available ....................................................................... 71
9.1.24 Code 5661 - Source 2 Not Available ....................................................................... 71
9.1.25 Code 5662 - Source 1 Disconnected....................................................................... 71
9.1.26 Code 5663 - Source 2 Disconnected....................................................................... 72
9.1.27 Code 5664 - Genset in AUTO.................................................................................. 72
9.1.28 Code 5665 - ATS in AUTO ...................................................................................... 72
9.1.29 Code 5666 – Import Configuration Failed ............................................................... 72
9.1.30 Code 5667 – Import Configuration Successful ....................................................... 72
9.1.31 Code 5692 - ATS Test/Exercise is Active................................................................ 72
9.1.32 Code 5693 - ATS Test/Exercise is Inactive ............................................................. 72
9.1.33 Code 6736 – Restore to Factory Failed .................................................................. 72
DANGER
Indicates a hazardous situation that, if not avoided, will result in death or serious injury.
WARNING
Indicates a hazardous situation that, if not avoided, could result in death or serious injury.
CAUTION
Indicates a hazardous situation that, if not avoided, could result in minor or moderate injury.
NOTICE
Indicates information considered important, but not hazard-related (e.g., messages relating to
property damage).
Abbreviation
Definition
or Acronym
AC Alternating Current
ATS Automatic Transfer Switch
BMS Building Management System
CCM Custom Communication Module
CDMA Code Division Multiple Access
CSV Comma-Separated Values
DC Direct Current
GSM Global System for Mobile
I/O Input/Output
IMEI International Mobile Equipment Identity
LED Light Emitting Diode
MEID Mobile Equipment Identifier
NMS Network Management System
OTG On The Go
PC PowerCommand
PCC Power Command Control
PDU Protocol Data Units
RTU Remote Terminal Unit
SD Secure Digital
SMS Short Message Service
SMTP Simple Mail Transfer Protocol
SNMP Simple Network Management Protocol
SSL Secure Socket Layer
TCP/IP Transmission Control Protocol/Internet Protocol
Abbreviation
Definition
or Acronym
UI User Interface
USB Universal Serial Bus
VDC Volts Direct Current
Both the PC500 Cloud Link and PC550 Cloud Link can connect to Internet through Ethernet or 3G GSM.
3.3 Controls
The remote monitoring system supports the following generator set controls.
Control Communication
PCC 1301 Modbus RTU
PCC 1302, PC1.1 Modbus RTU
PCC 2300, PC 2.2, PC 2.3 Modbus RTU
PCC 3300, PC 3.3 Modbus RTU
PS0500 Modbus RTU
PCC 2100 Modbus RTU through Modlon Gateway
PCC 3100 Modbus RTU through Modlon Gateway
PCC 3200 Modbus RTU through Modlon Gateway
PCC 3201 Modbus RTU through Modlon Gateway
Detector and some third party Integrated discrete inputs and outputs
controls
Control Communication
OTPC Modbus RTU through Modlon Gateway
OHPC Modbus RTU through Modlon Gateway
CHPC Modbus RTU through Modlon Gateway
BTPC Modbus RTU through Modlon Gateway
CCM-T Modbus RTU through Modlon Gateway
The PC500/550 Cloud Link reads I/Os from third party generator set and ATS controls either by directly
connecting the I/Os to the PC500/550 Cloud Link or connecting to an AUX101 I/O device, which can then
be read over Modbus RTU.
3.4.2 TB1
FIGURE 4. TB1
3.4.3 TB2
FIGURE 5. TB2
NOTICE
Factory settings are not reset.
3.4.5 Ports
FIGURE 6. PORTS
4.5 Notifications
The PowerCommand Cloud web application supports Email notifications through SMTP (email). Email
notifications are setup in the My Profile section of the PowerCommand Cloud web application. In order to
receive notifications, Email notifications must be enabled, and the user must select the account or
accounts for which they would like to receive notifications. Users can also select the event severity for
which they would like to receive notifications (fault events, warning events, and informational events).
Verify the Email address in your profile is accurate. Notifications include all of the details of an event (time
stamp, source, event type, and description).
The PowerCommand Cloud mobile application supports push notifications via the mobile device. You’re
email notification settings from the web application are carried over for the push notifications on the mobile
application. For example, Email notifications must be enabled, and you have to select the account (s) and
severity level for notifications in order to receive push notifications.
4.7 Sensors
The PC500/550 Cloud Link supports the monitoring of analog and discrete sensors. Sensors are
configured in the setup gateway and displayed on the PowerCommand Cloud web application.
• Analog sensors are used to measure quantity. Examples of analog sensors are fuel, temperature,
pressure, and voltage sensors.
• Discrete sensors only have 2 values which are used to read on/off status. Examples of discrete
sensors are generator set run status, switch on/off status, and door open/close status.
Sensors that have been configured are displayed on the home page and device details under Site IOs.
The PC500/550 Cloud Link has 3 on-board inputs:
• 2 discrete inputs
• 1 analog resistive input (600–2500Ω)
When required, an AUX101/102 can be used to expand the PC500/550 Cloud Link input capabilities. No
more than 3 AUX101/102 devices can be configured.
The AUX101 provides:
• 8 analog/discrete inputs (configurable)
The AUX102 provides:
• 4 discrete inputs (not configurable)
NOTICE
Setting an exercise schedule via the PowerCommand Cloud will not overwrite or disable any
existing exercise hardware such as an automatic transfer switch.
4.11 Diagnostics
The PC500/550 Cloud Link provides diagnostic information on Modbus communication, memory
utilization, cloud connection, wireless connection, and system information.
• Modbus - Provides communications status for each configured device, including Modbus channel;
number of Modbus packets sent, received, and failed; and the date and time of the last successful
communication.
• Performance - Provides memory utilization and overall system performance.
• Cloud - Provides the current connection status and connection time, total disconnects, and total
failures to reconnect to the cloud.
• Internet - Provides the wireless signal strength, current connection status and connection time, total
disconnects, and total failures to reconnect to the internet.
• System Information - Provides the device model, gateway ID, modem type, modem software
version, modem IMEI, hardware version, OS version, software version, build number, and the date
and time of the last update.
d. Account User
• Account Users are primarily read-only users. They can view and export data, and export
events.
2. Customers have the following access permissions and roles.
a. Account Owner
• Account Owners are the owners of their account. They can add, edit, and delete sites
and assets, and invite, edit, and delete other users on the account. They can also view
and export data, and acknowledge and export events, as well as update the software for
the Cloud Link gateway remotely via the PowerCommand Cloud web application. Account
owners can also operate and disable remote operation of their assets.
b. Account Manager
• Account Managers are in charge of managing their account(s). They have the ability to
invite, edit, and delete other users on their account. They can also view and export data,
and acknowledge and export events, as well as update the software for the Cloud Link
gateway remotely via the PowerCommand Cloud web application. Account managers can
remotely operate their assets if remote operations are enabled.
c. Service Technician
• Service Technicians can update gateway software, add edit, delete, and operate assets if
remote operation is enabled, view and export data, and acknowledge and export events.
d. Account User
• Account Users are primarily read-only users. They can view and export data, and export
events.
NOTICE
TLS is always enabled so https:// must be used to access the device. Your browser may prompt
you with a security warning, this is normal and you must click to proceed.
NOTICE
Do not mount the PC500/550 Cloud Link inside a generator set or ATS enclosure. Doing so voids
certifications.
An antenna extension cable is required if, due to location, the PC500/550 Cloud Link does not detect a
wireless connection.
Hardware Description
USB-OTG Cable Allows direct connection to a PC to configure devices.
Ethernet Cable Allows connection to the network. Supports IEEE
10BASE-T and 100BASE-TX standards.
Modlon II Gateway Kit (541-1149) Required for:
and Modlon Connection Cable Kit (TBD) PCC 2100, PCC 3100, PCC 3200, PCC 3201 generator
set controls
OTPC, BTPC, OHPC, and CHPC ATS controls
CCM.
Antenna Extension (12 ft) Required for cabinet installations and if wireless strength
is weak.
NOTICE
12 feet is the maximum acceptable length for the
antenna extension cable. A longer cable will
degrade the signal.
Hardware Description
Modbus Cable Twisted shielded pair cable (24 AWG or larger) used to
connect the PC500/550 Cloud Link to the monitored
device (Belden 3106A or equivalent).
Power Supply 9 - 32 VDC, 12 VDC - 250mA, 24 VDC - 125mA, 5W
minimum (UPS is recommended).
SIM Card Required for 3G GSM wireless modem (needs to be
activated by a local provider).
NOTICE
If the cabinet is NEMA rated, make sure the perforation is properly sealed to
prevent loss of the NEMA ratings.
c. Connect the SMA straight plug end of the connector to the PC500/550 Cloud Link.
d. Attach the antenna to the bulkhead connector side of the antenna extension cable
located on the outside of the cabinet.
e. Contact a cellular service provider and activate service on a SIM card.
3. Modlon Connections: Install a Modlon II Gateway (541-1149) for converting LonWorks to Modbus
communications. When connecting to the Modlon Gateway, use the Modlon Connection cable.
a. Connect the DB9 connector of the Modlon Connection Cable to the DB9 header on the Modlon.
b. Connect the other end of the cable to the corresponding points on the PC500/550 Cloud Link
terminal block TB2. Either channel is acceptable.
4. Modbus Connections:
a. Connect a twisted pair of the Modbus cable to the RS-485 connector on the generator set
control board or AUX101 control to the corresponding points on the PC500/550 Cloud Link
terminal block TB2. Either channel is acceptable.
b. If the installation is for a separate power supply, connect a ground reference wire.
c. Connect the cable shield to either Chassis Ground on TB2 of the PC500/550 Cloud Link or the
ground pin on the generator set, ATS, or AUX101 control (not both).
5. Sensor Connections: Make the appropriate connection(s) to TB1 of the PC500/550 Cloud Link using
a standard 24 AWG or larger wire.
• Wire the appropriate sensor (fuel sensor, for example) to AIn + and AIn–.
• Wire desired devices to discrete inputs (DIn 1, DIn 2).
6. Wired Generator Set connections
• Connect TB1-7 to generator Run Status
• Connect TB1-8 to generator Common Alarm
• Connect TB1-9/10 to generator Start/Stop
• Connect TB1-12/13 to generator Fault Reset
7. Connect the PC500/550 Cloud Link to a 12/24 VDC generator set battery or an isolated DC power
supply.
8. Check the Power LED to confirm power is available.
9. Check Status LED to confirm application software is operating correctly.
10. Mount the PC500/550 Cloud Link on a DIN rail or install in a suitable location.
NOTICE
Use https because SSL security is always enabled.
2. The modem is ready for use once the SIM card is activated and installed the into the Cloud Link
device, and the Wireless data in the Gateway Setup Cellular Preferences is set to Enable.
3. Verify the wireless signal strength in the gateway setup by navigating to the diagnostics page
Internet tab, and clicking the Get Wireless Data button.
NOTICE
The first time logging into the system, enter admin for both the Username and Password.
NOTICE
SSL is always enabled so https:// must be used to access the device. Your browser may
prompt you with a security warning, this is normal and you must click to proceed.
5. If the screen below is displayed, select Continue to this website to display the login screen.
NOTICE
The address bar appears as shown below. This is expected and does not indicate a security
threat.
NOTICE
When manually entering IP address information, the network administrator needs to
map the IP address to the host name to provide access to the device using a host
name.
NOTICE
A Modlon Index is related to the generator set that was commissioned on the LonWorks
database. For example, if Gen1 is commissioned on the LonWorks database, an index of 0 is
associated with it. Gen2 is associated with index 1, and so on.
When devices are added to the system, a Modbus/TCP Unit Identifier can be assigned. The unit identifier
is used for identifying devices connected on the Modbus RTU channel when establishing a Modbus TCP
session. The PC500/550 Cloud Link metadata is accessed using device ID 100.
NOTICE
A Modlon Index is related to an ATS that was commissioned on the LonWorks database. For
example, if ATS1 is commissioned on the LonWorks database, an index of 0 is associated with it.
ATS2 is associated with index 1, and so on.
• OHPPC
• CHPC
• BTPC
• PLT
• CCM-T
3. Enter the Modbus Address of the device.
4. Select the Modbus Channel from the drop-down list:
• Channel-1
• Channel-2
5. Select the appropriate Modlon template (1, 2, 4) and enter the appropriate index number.
6. Enter the Source 1 and Source 2 name if desired.
7. Enter a device location and description if desired.
8. Select Save. The new device tile is added to the device grid and Home page.
6. Select the Select default configuration for Aux101's Inputs and Current Sources check box or
manually configure Input 1 through Input 8. To manually configure an input, select the input type
from the drop-down list.
• Analog - Continuous voltage converted to a value.
• Discrete (Active High) - Represents a binary digit of 1, or asserted state of a logical condition,
by the higher of 2 voltages. Sensor becomes active when the signal is tied to B+.
• Discrete (Active Low) - Represents a binary digit of 1, or asserted state of a logical condition,
by the lower of 2 voltages. Sensor becomes active when the signal is grounded (B–).
7. For Analog inputs, configure the associated Current Source. Use the up and down arrows, or
manually enter.
8. If the AUX101 includes an AUX102, select the Aux102 Available check box. AUX102 inputs are not
configurable.
9. Select Finish.
To quit without saving changes, select Cancel.
To go back to the previous screen, select Back.
Add sensors and output control for the new I/O device using the Sensors and Output Control setup menu.
6.8 Sensors
Sensors configuration wizards are used to enter and edit sensor information.
NOTICE
An AUX101/102 I/O device needs to be added before setting up AUX101/102 sensors.
NOTICE
The PC500/550 Cloud Link does not support Output Controls.
3. To add a new sensor, select Add New Sensor and select the sensor type from the drop-down list.
• Discrete
• Analog
To edit an existing sensor, select the sensor from the list and select Edit.
To delete an existing sensor, select the sensor from the list and select Delete.
NOTICE
The drop-down list is populated only with the available inputs. If an AUX is not
configured, only the PC500/550 Cloud Link inputs are listed. If an input is already in
use, it is not shown in the list.
NOTICE
The drop-down list is populated only with the available inputs. If an AUX is not
configured, only the PC500/550 Cloud Link inputs are listed. If an input is already in
use, it is not shown in the list.
10. You can enable a 3% Hysteresis for warning messages to cut down on nuisance warning events.
Enabling hysteresis will keep a warning active until the reading drops 3% back towards normal. For
example, if you have a warning range of 0-100, the high warning will trigger over 100, and with
hysteresis enabled, the high warning will stay active until the reading drops below 97. With
hysteresis disabled, the warning will deactivate as soon as the reading drops below 100.
11. Select Save to save the changes. The newly added sensor is displayed in the sensor grid.
To quit without saving changes, select Cancel.
To go back to the previous screen, select Back.
NOTICE
Update of software through the PowerCommand Web App is recommended.
CAUTION
Uploading a bad or inadequate zip file can cause permanent damage to the PC500/550
Cloud Link. Make sure to upload the correct zip file.
To save the current configuration as a backup, select Export Config. A browser window is displayed to
select the location to save the configured zip file.
To import a saved configuration file:
1. Select Import Config.
2. Select Browse. A browser window is displayed to select the configuration XML file.
3. Select the configuration to import.
4. Select OK.
NOTICE
If you have not received an invitation email, please check your junk/spam folder first, then
contact the distributor or dealer where you purchased your Cloud Link unit and they can
check the email address and resend another invitation.
2. Click on the link in the email invitation. The PowerCommand Cloud launches in the web browser.
• If you have already created an account for yourself on the PowerCommand Cloud, click USE
YOUR CURRENT USER ACCOUNT. This will allow you to add permissions to an existing
account.
• If you are registering for the PowerCommand Cloud for the first time, click REGISTER NEW
USER ACOUNT.
3. A new page will open with Terms of Service. You must accept the terms of service to register a new
account. Check the box next to "I have read and accept the terms of service" and click ACCEPT.
4. A new page will open to create your PowerCommand user account. Enter your email address and
click the SEND VERIFICATION CODE button once. This sends a verification code to your email
address.
NOTICE
Make sure to click the SEND VERFICATION CODE button only once. A new verification code
is sent each time the button is clicked. The registration process accepts only the most
recent code.
5. From your email client, open the email from PowerCommand Cloud.
6. Enter the code shown from the email into the Verification Code field in the web browser.
7. Choose and enter a password. The password must be 8-16 characters and must contain 3 of 4 of
the following:
• Lowercase Characters
• Uppercase characters
• Digits (0-9)
• One or more of the following symbols: @#$%^&*-_+=[]{}|\:',?/`~"()
8. Click CREATE and you should not have access to the PowerCommand Cloud site at
https://portal.powercommandcloud.com.
NOTICE
You cannot right click in the gateway setup so you must use Ctrl+V to paste the copied
access key.
4. Click SAVE on the Cloud Connectivity setup screen and a provisioning process will start. If
provisioning is successful, the cloud icon on the top right of the gateway setup screen will change
from grey to blue.
NOTICE
If you continue to experience issues getting the cloud to turn blue, first verify that you have
an internet connection, then refer to the troubleshooting in Chapter 9 on page 65.
NOTICE
In addition to adding the devices in the gateway setup, you also need to have a valid Cloud
connection with your PC500/550 Cloud Link.
6. Click SAVE. The site and assets can now be viewed on the PowerCommand Cloud.
8.1.2 Sign In
In your web browser, navigate to https://portal.PowerCommandClound.com.
1. Registered customers and end-users, click on SIGN IN and enter the Email address and password
associated with your user account. If you have forgotten your password and are unable to sign in,
click on the Forgot your password? link to reset your password.
2. Registered Cummins employees and Dealers, click on the “Cummins Employees and Dealers Click
Here” link to sign in. This will direct you to the Cummins Online Login page where you will use your
standard Cummins login information. If you have forgotten your password and are unable to sign in,
please contact your normal IT support.
8.1.3 Dashboard
The home screen or dashboard displays all of your customer sites on an interactive map. On the toolbar
across the top of the screen you can get back to the dashboard, access Account Management, and
access My Profile or log out by clicking on your name on the top right of the screen.
• Accounts are shown on the left.
• Status of all sites (Fault, Warning) are shown accross the top and on a map.
8.1.4 My Profile
In My Profile, you can edit your name and contact telephone number. You can also select your Preferred
Account if you have access to multiple accounts. This will determine which account you can see and
manage from the dashboard. You can also select your Language, and set Metric or Imperial units.
Customer users can change the password in My Profile via the link in the Login Info section.
NOTICE
Cummins Employees and Dealers will not have the option to change their password in My
Profile.
My Profile is also where you can setup your email notifications. You must click the Enable option, and
select which account(s) you would like to receive notifications for. If you enable notifications, you will
receive all fault events, warning events, and informational events by default, but you can select by severity
to only receive certain notifications. You can also select an alternative email to receive notifications.
NOTICE
Setting an exercise schedule via the PowerCommand Cloud will not overwrite or disable any
existing exercise hardware such as an automatic transfer switch.
Clicking on the System Status Bar causes the Event Log to be displayed.
When there are no fault messages, the following message is displayed.
The system Event Log Page displays a list of active or acknowledged events.
8.8.1 Modbus
The Modbus tab displays the Modbus communication status of all monitored devices.
8.8.2 Performance
The performance tab displays a list of performance data and allows the user to perform a soft
reboot/restart of the PC500/550 Cloud Link System.
8.8.3 Cloud
The Cloud tab displays the current cloud connection status, the length of time you have been connected,
and the total number of disconnects, and failures to reconnect. You can reset the counters by clicking on
Clear Counters. You must have an internet connection to connect to the cloud.
8.8.4 Internet
The internet tab displays the current internet connection status, the length of time you have been
connected, and the total number of disconnects, and failures or reconnect. You can reset the counters by
clicking on Clear Counters.
Also, click on Get Wireless Data to see your wireless signal strength.
NOTICE
Internal battery replacement should be done by a certified distributor; otherwise the warranty will
be voided.
NOTICE
Internal battery replacement should be done by a certified distributor; otherwise the warranty will
be voided.
NOTICE
Internal battery replacement should be done by a certified distributor; otherwise the warranty will
be voided.
Corrective Action
Possible Cause PCC 2100, PCC 3100, PCC 3200, PCC 1301, PCC 1302, PCC 2300,
PCC 3201 and ATS Controls PCC 3300, PS0500 Controls
There has been a power interruption 1. Verify if there has been a power If the battery of any of the generator
to the device that the PC500/550 interruption to the Modlon that is sets being monitored is disconnected,
Cloud Link is monitoring. sending Modbus information make sure that the generator set that
from the device to which has lost communication to the
communication was lost. PC500/550 Cloud Link is properly
energized.
2. If Modlon has not lost power,
check if any of the devices
(Generator Sets or ATSs)
connected to the Modlon have
lost power to their controls.
• For generator sets, this
fault can be caused if a
generator set battery is
disconnected.
• For ATSs, this fault can be
caused if there is not a B+
on J27-21 of the ATS
digital board and there is
an interruption to the utility
power.
The Modbus RTU protocol of the Verify that Modbus protocol is
device (Generator set or ATS) that is enabled on the device (Generator Set
being monitored is not detected. or ATS) that is being monitored. This
can be verified by navigating through
the control's display or by connecting
to the control with the InPower service
tool.
The Modbus settings on the device do Browse to the Modlon that is sending Connect the control to the InPower
not match the settings on the the data for the device that has service tool or navigate through the
PC500/550 Cloud Link channel. communication issues and verify that display and verify that the control
the settings on the nciModLonCfg Modbus settings match the settings
network match the settings on the on the Modbus Settings menu in the
Modbus Settings menu in the PC500/550 Cloud Link user interface.
PC500/550 Cloud Link user interface.
Modbus data cable connected with an On TB2, verify that the Modlon to Verify that all devices are daisy
inverted polarity to the channel PC500/550 Cloud Link cable is chained properly (no inverted cable)
Terminal Block (TB2) of the properly connected on the channel and that the + and – of the cable
PC500/550 Cloud Link. being used to monitor the equipment. matches the labeling on PC500/550
(Modbus RTU protocol is polarity Make sure that the wires are not Cloud Link TB2. One inverted cable
sensitive.) inverted. can cause communication failures
with all devices.
Bad Modbus device. Use LonMaker to verify that all Lon Use ModScan, or any other Modbus
devices are properly commissioned monitoring software, to verify that all
and communicating with each other. If Modbus information is being received
so, connect ModScan, or other from the control or AUX101.
modules monitoring software, to verify
that all Modbus information is being
received from ModLon II.
Corrective Action
Possible Cause PCC 2100, PCC 3100, PCC 3200, PCC 1301, PCC 1302, PCC 2300,
PCC 3201 and ATS Controls PCC 3300, PS0500 Controls
Connected to an incorrect Modbus On the Device Configuration page in On the Device Configuration page in
channel on the PC500/550 Cloud the Setup menu of the PC500/550 the Setup menu of the PC500/550
Link. Cloud Link UI, verify that the device is Cloud Link UI, verify that the device is
configured to use the channel it is configured to use the channel it is
connected to. connected to.
Wrong Modbus address on device. Each Modbus device should have a Each Modbus device should have a
unique Modbus address on the unique Modbus address on the
network. Use LonMaker to verify the network. Verify that the Modbus
ModLon address. Verify that the address for the ModLon matches the
Modbus address for the ModLon Modbus address entered on the
matches the Modbus address entered Device Configuration page in the
on the Device Configuration page in Setup menu of the PC500/550 Cloud
the Setup menu of the PC500/550 Link UI.
Cloud Link UI.
Wrong index or template. The index is the third number on the
Modbus register that the ModLon
sends for each control. For example,
Gen1 has registers 40000-400, Gen2
has 40100-401, and so on. The index
for Gen 1 is 0 and the index for Gen2
is 1. Make sure the correct index is
selected for each of the devices being
monitored.
CAUTION
Uploading the wrong software file can cause
permanent damage to the PC500/550 Cloud Link.
Make sure to upload the correct file.
A power interruption occurred during the software update. Upload the correct software file again and ensure that
there is no interruption to the system during this process.
Possible Cause PCC 1301, PCC 1302, PCC PCC 2100, PCC 3100, PCC Remote I/Os
2300, and PCC 3300 3200, PCC 3201, and ATS
Controls Controls
The device that is being On the Device Configuration On the Device Configuration On the Device Configuration
monitored is not configured page in the Setup menu of page in the Setup menu of page in the Setup menu of
properly. the UI, identify the the UI, identify the the UI, identify the AUX with
generator set with incorrect generator set or ATS with incorrect readings in the
readings in the Device incorrect readings in the Device Name column.
Name column. Verify that Device Name column. Select the AUX device and
the Device Model column is Verify that the Device Model select Edit to verify that the
the correct model for the column is the correct model inputs of the AUX module
control of the device. If the for the control of the device. are configured according to
model is not correct, select If the model is not correct, the type of sensor that is
the generator set that is select the generator set or being used on each of the
displaying incorrect ATS that is displaying different inputs.
information and select Edit incorrect information and
to make the proper select Edit to make the
changes. proper changes.
Calibration of a control Connect the control that is
needs to be updated. displaying incorrect
information to Modbus
master software, such as
ModScan. Use the Modbus
Register Mapping
(A029X159) manual to
understand the meaning of
each Modbus register. If the
registers do not match what
is displayed for the
generator set in the UI, use
the latest available
calibration from the INCAL
website and perform an
calibration update on the
generator set control.
Corrective Action
Possible Cause PCC 1301, PCC 1302, PCC PCC 2100, PCC 3100, PCC Remote I/Os
2300, and PCC 3300 3200, PCC 3201, and ATS
Controls Controls
Control has incorrect Open the LonWorks
Modlon index. database that was used to
commission the generator
sets and ATSs with
LonWorks cards. Verify
what equipment is
commissioned as Gen1,
Gen2, etc.; and ATS1,
ATS2, etc., on the Modlon
template. Make sure that
the UI index numbers are
assigned correctly (Gen1
has an index number, Gen2
has index of 1, and so on;
and the same for ATSs.
Sensor is not configured On the Sensors and Output
properly. Controls page in the Setup
menu of the UI, select the
sensor that is displaying
wrong information. Verify
that the sensor type (analog
or discrete) is correct.
Select Edit to verify the
configuration of the sensor.
Make sure the sensor has
the correct units for what is
being measured and that
the sensor voltage limits are
set properly for what the
sensor is sending to the
AUX101/102.
Telemetry information from This is the correct functionality of a PC500/550 Cloud Link. You will not see device
devices are not visible on information in the gateway user interface like you may be used to seeing on the
the gateway user interface. PC500/550 Classic. Telemetry information is all sent to the Cloud and visible at
portal.powercommandcloud.com.
CAUTION
Electrostatic discharge can damage circuit boards. Always wear a grounding wrist strap
when handling circuit boards.
4. Remove the circuit board from the enclosure by disconnecting the 2 clamps that secure the circuit
board to the enclosure, one at a time, and pulling the circuit board up as the retaining clamps are
being disconnected.
5. On the removed circuit board, carefully push the TRC battery out of the retainer with a small
screwdriver.
CAUTION
Pushing on the battery too hard can damage the soldering of the battery retainer. Take extra
precaution when removing the battery.
6. Insert the new battery and reassemble the PC500/550 Cloud Link.
Table of Contents
Figure 55. Common Power Supply - with Sensors ................................................................................... 86
Figure 56. Separate Power Supply - With Sensors ................................................................................... 87
Figure 57. Common Power Supply - with Wired Generator Set .............................................................. 88
Figure 58. Separate Power Supply - With Wired Generator Set .............................................................. 89