Whelen Engineering Company CenCom Core C399 Installation Manual page 4

about 2 seconds or less, Core should access its application code and go
through the initialization process outlined in the next section.
Troubleshooting Boot up:
If the Status indicator remains Magenta, then Core is stuck in boot up and
there is an issue with the SD card. To check the SD card, make sure
power is disconnected, and the black cover is removed via 4 T10 screws.
Located at the top right side of the unit, push the SD card into the
connector and then reapply power and ignition. If the SD card is seated
properly and the Status indicator is still Magenta, the SD card or its data
may be corrupt. Erasing the SD cards contents or installing a new SD card
will allow Core to boot up properly.
Note: If the Status indicator is steady Red (not flashing) and the
Activity indicator is off, then there is a firmware corruption. After
power and ignition is applied to the unit, connect USB to the unit and
open Command software. Follow the update firmware instructions
below to see if this fixes the corruption. If this does not work, then
the device must be sent in for repair.
Initializing Devices and Updating Firmware:
Initialization:
To ensure proper initialization, make sure all devices are connected via
WecanX and are powered with 12VDC BEFORE applying ignition to Core.
When ignition is applied, Core will then register all devices it can
communicate with through the WecanX bus. The Status indicator will flash
WHITE, and the Activity indicator will flash Blue showing message
communication.
NOTE: If you have no configuration on Core, the Status indicator will
also flash Red. If a configuration is present, the Status indicator will
also be a steady Green. When the status indicator is no longer flashing
white, the initialization process is complete. USB can now be plugged into
Core and hooked up to Command.
Updating Firmware:
To update firmware in Command, make sure you have gone through the Core
initialization process and that all devices are still connected via WecanX and
powered with 12vdc. Plug in USB and open Command and select
"Cencom Core" from the product menu. Click the "W" icon in the top left
corner, and then select "Update Firmware" from the list. Click the refresh
button to see a list of all available devices that are connected to Core.
Verify that every device you have connected is displaying its firmware
version; if there are any missing devices, restart the initialization process
and try again. Update the firmware of any device that needs it and do not
remove WecanX connection or power until this process has been
completed. Command will inform you when the process is completed.
When a firmware update is initialized for a device, the diagnostic indicator
will slowly flash Blue to indicate that it is in the boot-loader and that it
recognizes its application code. The firmware update is done one device
at a time and when the actual transfer of data is taking place, the
diagnostic indicator on the specific device being updated will start blinking
Blue faster to indicate that its current application data is being modified.
While firmware is updating, the Activity indicator on Core will be blinking
Blue to show activity. Note: When the peripheral devices have finished
updating, the diagnostic indicator on each respective device will turn
off unless the diagnostic indicators are configured to be on, in which
case they will turn Green when finished.
Troubleshooting Firmware Updates:
If command informs you that the transfer failed, unplug USB and cycle
power to all units and reinitialize the system. Then plug USB back into
Core and hit the refresh button on the Command "Update Firmware" page.
Verify that all devices are up to date and repeat the firmware update
process if firmware is not up to date. If a device fails to update and all
connections are intact, its diagnostic indicator will remain blinking blue to
indicate that it is in the boot loader. After re-initializing the system, the
device will show up in the "Update Firmware" page with firmware version
"Unknown". From there you can then update the firmware to the newest
version. Note: If at any point your device stops working and you have
verified that all the proper connections are intact, re-initialize and
check for firmware updates.
Configuring Devices:
The fastest and easiest way to configure your system is immediately after
the initialization and firmware update processes are complete. Having
your entire system up to date and still communicating with Core allows
you to import connected devices into a brand-new configuration using the
"Detect via USB" in the "My Hardware" page. All devices presently
communicating with Core will populate the hardware list. There are certain
types of devices that are not automatically populated due to the need of
further configuration such as lightbars, Inner edges and Traffic Advisors.
Command will prompt the user of the devices that these types of devices
are connected but are not automatically populated on the list. Note: Any
device that you have multiples of need to have their installation ID
configured.
Installation IDs
Command will prompt you that the installation IDs are not set if you "detect
via USB" multiples of the same device type but, as a rule, if you have more
than one of the same device type, you need to set the installation ID
manually. For Example, two Remote 16s would need their IDs set but one
Remote 16 and one Remote 8 would not, or two Arges Remote Spotlights
would need their IDs set but one Arges Remote Spotlight and one Arges
Profocus would not. Click on the "W" icon in the top left of the "My
Hardware" page and select "Assign Installation IDs". The easiest way to
set them is one at a time so that you know which one you are setting. All
devices you are setting will have a default ID of unassigned. Unplug all the
devices you plan to set except for one. Refresh the list and select the
number you want from the drop-down menu, check the box next to the
device and then click assign. After you have assigned the device you can
add each subsequent device one at a time and iterate the installation ID.
If you have already set installation IDs before you "Detect via USB",
Command will automatically populate the hardware list with the correct
configuration ID to match the Installation ID. Note: The installation ID
numbers only differentiate between devices of the same device type,
meaning that you can have multiple devices with the same
installation ID if they are different devices types.
Troubleshooting Installation IDs:
Anytime you have more than one of the same device types in your
configuration and only one of them is working, the installation ID may not
have been set. After you have checked to make sure you have proper
connections, and the initialization and firmware process has been
completed, check to make sure all identical device types have installation
IDs set.
Page 4