Updating Axia Routing Control Panels

Updated 11 months ago by Brett Patram

Scope

The 17 button LCD SmartSwitch and 8 button OLED SmartSwitch are designed to work with Axia Pathfinder Routing software.

When using these panels with Pathfinder Core PRO, the panel firmware needs to be on version 1.5.1d (or higher). Otherwise Pathfinder Core PRO may not be able to discover the panel. The legacy Pathfinder PC Server software doesn't require this version for compatibility.

This document will walk you through how to check if the panel is running compatible firmware, and how to update the panel if required.

17-button LCD SmartSwitch

8-button OLED SmartSwitch


Check if the current firmware is compatible with Pathfinder CorePro

If you have not set the IP address on the panel, please see this documentation for steps on how to do so

Using a telnet application like PuTTY, make a telnet connection to the IP address of the panel on port 4010.

When connected there will not be any response or greeting from the panel. Simply type in get supv state and strike enter.

The panel will respond back with a response similar to:

indi supv clients_connected=3, version="1.5.1d", device_type=RCP17SS, state=Ready

If you do not see device_type= in the response, the firmware needs to be updated. See next section "Updating firmware to 1.5.1d".

If you do see device_type= in the response, this unit should work with Pathfinder Core PRO. If the device wasn't discovered, try adding it manually from the Devices page in the Core PRO web gui, or contact support for further assistance.


Updating firmware to 1.5.1d

Download this file: axiarcp-1.5.1d.zip and extract its contents to a folder on your PC. This requires a Windows-based PC to perform the update, this will not work on macOS.

You should be left with 3 files. image.elf.S, update.bat and Uploader.exe.

Before continuing (if on Windows 7 or Windows 10), right-click on Update.bat, Select Properties. In Properties make sure to check the box next to "Unlock" and click Apply. Do this for the Update.exe file as well.

Open Windows Command Prompt. Use the CD command to change into the directory where the 3 files are located.

Type in update.bat followed by the IP address of your panel and strike enter. See example below:

C:\Users\support\Downloads\axiarcp-1.5.1d>update.bat 10.0.1.24
- -
- update.bat - Axia Remote Control Panel Net-Update Utility -
- version 0.0.1 -

C:\Users\support\Downloads\axiarcp-1.5.1d>uploader.exe -a 10.0.1.24 -i image.elf.s
Uploader - The firmware uploader version 0.2.1
Try Uploader --help for more options.

Creating image of file
Module type 0x00
Hardware revision 0x030419
Software revision 1.5.1d
Calculated CRC - D - 0x2126 B - 0x3A P - 0xBAE0
Readed CRC - D - 0x2126 B - 0xFFFF P - 0xBAE0
Image created
Connection 10.0.1.24 3000...
Device connected
Trying to Set Module into FW upload Mode
Module is successfully entered in Firmware Uploading mode
Hardware revision in module 0x000419
Readed CRC - in module P - 0xFF8B D - 0x2126
Upload new application to module? (Yes\No) YES

At this stage you will be prompted to proceed to upload the new firmware. Type YES and strike enter

                Burning success

Updated:
Hardware revision in module 0x000419
Readed CRC - in module P - 0xBAE0 D - 0x2126

Checking CRC and Run program.

C:\Users\support\Downloads\axiarcp-1.5.1d>goto end

You will see a lot of output in the console. It should complete with the last bit of output looking similar to the example above. Update is complete.


Confirming the update version

Using a telnet application like PuTTY, make a telnet connection to the IP address of the panel on port 4010.

When connected there will not be any response or greeting from the panel. Simply type in get supv state and strike enter.

The panel will respond back with a response similar to:

indi supv clients_connected=3, version="1.5.1d", device_type=RCP17SS, state=Ready

Note that the version reflects 1.5.1d and device_type is included in its response. It should be now compatible for Pathfinder Core PRO to use it.


Let us know how we can help

If you have further questions on this topic or have ideas about improving this document, please contact us.


How did we do?