Using the ReduxLib Configurator#

The ReduxLib configurator is a basic interface for setting device CAN IDs and performing firmware updates.

Accessing the configurator#

ReduxLib must be installed and deployed in your robot project with at least one device instantiated in your robot code for the configurator to be accessible.

Alternatively, adding CanandEventLoop.getInstance() to your robot initialization code and then deploying it will also initialize the code.

// Put this in your robot initialization code.
CanandEventLoop.getInstance();

Upon code deploy, while connected to your robot’s network, navigate to http://roborio-XXXX-frc.local:7244 with XXXX replaced by your team number in order to access the Configurator.

Troubleshooting connectivity issues#

  • Make sure you’re connected to the robot network. If you’re connected via USB, try http://172.22.11.2:7244 instead.

  • Make sure your code is not immediately crashing on startup by viewing the robot controller logs through the driver station.

  • Make sure that ReduxLib is installed properly.

Managing a CAN bus and selecting a device#

Every opened CAN bus will be available on the first drop-down after Select a bus to manage:.

Select a bus to see which devices are currently visible on the bus on the top table. You can click anywhere in a device’s row to select it for configuration.

Don’t see the device?#

  • Make sure the device is powered.

  • Make sure the device can see the robot controller’s CAN bus and is wired properly * Canandgyros and Canandcolors will blink green if they can see the robot controller over CAN and are not in an ID conflict.

    They will blink red otherwise. This is intended to help users identify breaks in CAN buses.

Setting IDs and resolving a CAN ID conflict#

Setting IDs normally#

To set an ID of a device not currently in an ID conflict, select a device, enter a new ID in the CAN device ID box, and click Change ID. The device will be deselected and should momentarily re-appear in the list of detected devices under its new ID.

If the new ID would conflict with another detected device on the bus, an error will be shown when attempting to click Change ID.

You can use the Start blinking LED and Stop blinking LED buttons to trigger the device to flash its status LED in an identifying pattern to help locate it on a robot.

Resolving a CAN ID conflict#

All Redux devices ship new with a CAN ID of 0. Thus, if there are multiple on the same CAN bus, ID conflicts are expected.

Devices in an ID conflict will be grouped into a single device entry in the detection table.

Select it and a Devices in ID conflict box will be shown with the serial numbers of all devices sharing both the same CAN ID and device class.

To deconflict devices:

  1. Select a serial number in the Device in ID conflict box, and then click Activate selection

  2. Set a new device ID in CAN device ID and click Change ID.

  3. Re-select the entry for conflicting devices in the Devices detected on this bus table

  4. Repeat until only one device is left in the list of conflicting devices.

If the Devices in ID conflict box only shows one device, clicking Activate selection with Attempt to activate all devices selected will attempt to kick the device out of ID conflict mode without needing to change its ID.

Tip

The LED blink controls can be used to identify which device is currently activated after pressing Activate selection.

Firmware updates#

  1. Select a device in the Devices detected on this bus table.

  2. Select a firmware update file by clicking on Select firmware update file:

  3. Press Start update and wait for the process to complete.

If the device’s LED is stuck as a solid teal after the update, try pressing Reboot device to attempt to boot the firmware, or retrying Start update.

Tip

If a selected device is of the same device class as the previously selected device (e.g. Canandcolor ID 2 to Canandcolor ID 5) the current firmware file selection will stay selected, allowing one to flash the same firmware to multiple of the same device.