Page 4
Connecting the USB:
In order to fully configure your system, you need to connect USB and
open Command software. If you plan to check for firmware updates,
detect devices to build a new configuration, assign installation ID’s or want
all devices to accept the full configuration immediately after transfer, then
you need to follow the bootup and initialization process first. All devices
need to be powered and connected to Core-R via WeCanX connector
before power and ignition are applied to main Core-R. Once the boot-up
and initialization process are completed, USB can be connected from a
computer with Command software.
Note: Power must be applied to Core-R in order to update the
firmware of WeCanX devices.
If you are just transferring a new configuration, extracting a configuration,
or updating the firmware of the main Core-R controller only, all you need
to do is connect USB to Core-R via USB-C connector without external
power. This provides communication and power to the main controller
only. If there is no configuration currently on Core-R, the Status indicator
will rapidly blink
Orange
signifying no main power/ignition as well as no
configuration. If there is a valid configuration, the Status indicator will
rapidly blink
Green
to signify no main power/ignition as well as a valid
configuration. If there is no OBDII or analog connections the Activity
indicator will be steady
Blue. Note: If you send a configuration to Core-
R with only USB connected, the configuration will not be sent to all
devices until power and ignition are applied to Core-R with WeCanX
connection maintained to powered devices.
Booting up Core-R:
When you first apply power and ignition to Core-R, the Status indicator will
blink
Magenta
to indicate that it is booting up the application code. After
about 2 seconds, Core-R should access its application code and go
through the initialization process outlined in the next section.
Initializing Devices and Updating Firmware:
Initialization:
To ensure proper initialization, make sure all devices are connected via
WecanX and are powered with 10-30VDC
BEFORE
applying ignition to
Core-R. When ignition is applied, Core-R will then register all devices it
can communicate with through the WeCanX bus. The Status indicator will
flash
MAGENTA
, and the Activity indicator will flash
Blue
showing
message communication.
NOTE: If you have no configuration on Core-R, 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-R and hooked up to Command.
Updating Firmware:
To update firmware in Command, make sure you have gone through the
Core-R initialization process and that all devices are still connected via
WeCanX and powered
in
accordance with their installation instructions.
Plug in USB and open Command and select Core-R 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-R. 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-R 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-R 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-R 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-R 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.
