Rajant recommends to its customers that any upgrades to their networks take place only after testing for their individual application and networking needs.

Note

When upgrading firmware, be sure to read all release notes from the version you are currently running through the version you plan to install.

Jump to a specific version:


Firmware v11.23.3, BC|Commander v11.23.3, and BC|Connector v11.23.3

July 6, 2021

Important

Rajant recommends updating BC|Commander and BC|Connector installations to version 11.23.3 or higher for use with this firmware.

New Models

New Channel Plans and Certifications

Enhancements

BC|Commander and BC|Connector v11.23.3

Enhancements


Firmware Version 11.23.2

April 14, 2021

Enhancements

BC|Connector v11.23.2

Enhancements


Firmware Version 11.23.1 and BC|Commander 11.23.1

March 8, 2021

Rajant recommends to its customers that they upgrade their networks to this release only after testing it for their individual application and networking needs.

New Models

New Channel Plans and Certifications

New Features

Enhancements

BC|Commander v11.23.1

New Features

Enhancements


Firmware Version 11.23.0 and BC|Commander 11.23.0

January 27, 2021

Rajant recommends to its customers that they upgrade their networks to this release only after testing it for their individual application and networking needs.

New Models

New Channel Plans and Certifications

New Features

Enhancements

BC|Commander v11.23.0

New Features

Enhancements

BC|Connector v11.23.0

New Features

Enhancements


Firmware Version 11.22.10

December 16, 2020

Important

JR3 models running version 11.22.8 or later no longer support downgrading to versions older than 11.22.8. See 11.22.8 release notes.

Enhancements


Firmware Version 11.22.9

December 9, 2020

Important

JR3 models running version 11.22.8 or later no longer support downgrading to versions older than 11.22.8. See 11.22.8 release notes.

Enhancements


Firmware Version 11.22.8 (JR3 only)

December 7, 2020


Firmware, BC|Commander, and BC|Connector Version 11.22.7

October 5, 2020

Rajant recommends to its customers that they upgrade their networks to this release only after testing it for their individual application and networking needs.

New Channel Plans and Certifications

Enhancements


Firmware, BC|Commander, and BC|Connector Version 11.22.6

August 3, 2020

Rajant recommends to its customers that they upgrade their networks to this release only after testing it for their individual application and networking needs.

New Features

Enhancements

BC|Commander v11.22.6

New Features

Enhancements

BC|Connector v11.22.6

New Features

Enhancements


Firmware and BC|Commander Version 11.22.5

June 24, 2020

Rajant recommends to its customers that they upgrade their networks to this release only after testing it for their individual application and networking needs.

New Models

New Channel Plans and Certifications

Enhancements

BC|Commander v11.22.5

New Features

Enhancements


Firmware Version 11.22.3 and BC|Commander 11.22.1

December 19, 2019

Rajant recommends to its customers that they upgrade their networks to this release only after testing it for their individual application and networking needs.

This release brings all of the JR3 and DX2 functionality of v11.22.0 to the rest of our product line, in addition to those additional changes listed below. Be sure to also review the v11.22.0 Release Notes for the full list of changes for models other than JR3 and DX2.

New Models

New Channel Plans and Certifications

New Features

Enhancements

BC|Commander v11.22.1

New Features

Enhancements


Firmware Version 11.22.2

December 17, 2019

Note: This firmware version is being released for the JR3 and DX2 only.

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 or later while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

New Models

New Channel Plans and Certifications

New Features

Enhancements

BC|Commander

BC|Connector


Firmware Version 11.22.0

November 1, 2019

Note: This firmware version is being released for the JR3 and DX2 only.

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 or later while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

New Models

New Channel Plans and Certifications

New Features

Enhancements

BC|Commander


Firmware Version 11.21.1

Aug 7, 2019

Note: This firmware version is being released for the BreadCrumb ES1 only.

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 or later while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.


Version 11.21.0

July 30, 2019 (firnware for ES1) August 27, 2019 (application software)

Note: This firmware version is being released for the BreadCrumb ES1 only.

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 or later while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

BC|Commander

BC|Connector

BC|Enterprise

(see 11.15.3 release notes)

Documentation


Firmware Version 11.19.4

June 28, 2019

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 or later while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.


Firmware Version 11.19.3

May 22, 2019

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 or later while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.


Firmware Version 11.19.2

April 11, 2019

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 or later while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.


Firmware Version 11.19.1

November 30, 2018 (firmware) / January 2, 2019 (BC|Commander and BC|Connector)

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 or later while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

BC|Commander

BC|Connector


Firmware Version 11.19.0

September 12, 2018

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 or later while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

BC|Commander

BC|Connector

Documentation


Firmware Version 11.17.10

August 14, 2018

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 or later while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.


Firmware Version 11.17.9

June 3, 2018

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 or later while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

Documentation


Firmware Version 11.17.7

March 26, 2018

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 or later while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

BC|Commander

Documentation


Firmware Version 11.15.13

March 12, 2018

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 or later while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.


Firmware Version 11.15.4

November 28, 2017

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 or later while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.


Version 11.15.3

August 19, 2019

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

BC|Enterprise


BC|Enterprise Version 11.15.2

November 28, 2017

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

BC|Enterprise

New Features and Changes

New Functionality:

Issues Corrected

Note

After upgrading to v11.15.2, on Windows BC|Enterprise installations, you may reclaim disk space by deleting files from the C:\Windows\system32\config\systemprofile\AppData\Roaming\bcenterprise\var\journal directory. On Linux, you may reclaim disk space by deleting files from /opt/rajant-bcenterprise/data/var/journal. These files will not be automatically deleted by BC|Enterprise.


Firmware Version 11.15.1

September 10, 2017

Important

This version corrects an issue from 11.15.0 that could cause ME4-4950R models and ME4-2449R models to fail to boot and require repair by Rajant.

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.


Firmware Version 11.15.0

July 10, 2017

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

BC|Commander

Documentation


Firmware Version 11.13.1

February 16, 2017 (firmware)
March 10, 2018 (BC|Commander)

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

BC|Commander


Firmware Version 11.13.0

October 31, 2016

Important

As of version 11.13.0, if your BreadCrumb model is set to US or Canada and has any channel/bandwidth combinations approved by your local regulatory authority, unapproved channels and bandwidths will be unavailable to you in manual regulatory compliance mode. In this case, professional installers may still increase conducted power to accommodate situations such as RF line loss or changes in antenna. In all cases, it is the installer’s responsibility to ensure that the radio configuration does not permit operation outside of the range(s) permitted by your local applicable regulatory authorities.


If you are upgrading a BreadCrumb with RF approvals to v11.13.0 while using a channel or bandwidth that is not approved for operation (via Manual regulatory compliance mode), the BreadCrumb will maintain this setting during the upgrade so that you can migrate away from the unapproved setting(s) in a controlled manner. This will be brought to the user’s attention with warning code #335, “Non-compliant radio configuration in use”. Once configured to use an approved setting, the warning will be cleared and the preceding paragraph will apply.


To check available channels/bandwidths/etc. for a given model before upgrading, see Rajant’s online channel plans (login required).


Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Note

Three BreadCrumb ME4 models include a radio which is not correctly supported in v11.13.0. This version should not be installed on ME4-1450, ME4-1450E, ME4-2450, or ME4-2450E models. An updated version will be released to restore support for these radios.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.


Firmware Version 11.9.0

March 31, 2016

Important

Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Note

BC|Commander now requires Java 8. Installers are available that include the updated version.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

BC|Commander


Firmware Version 11.8.2

October 22, 2015

Important

Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

Important

11.8.0 introduces a new warning #21, “Recovery log detected. To clear this message, please take a diagnostic snapshot and upload to https://secure.rajant.com.” You may see this warning immediately upon upgrading your firmware; in this case, it means that the recovery log was already present prior to the upgrade. The new warning simply draws attention to its presence.


Firmware Version 11.8.1

October 8, 2015

Important

Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

Important

11.8.0 introduces a new warning #21, “Recovery log detected. To clear this message, please take a diagnostic snapshot and upload to https://secure.rajant.com.” You may see this warning immediately upon upgrading your firmware; in this case, it means that the recovery log was already present prior to the upgrade. The new warning simply draws attention to its presence.


Firmware Version 11.8.0

October 5, 2015

Important

Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

Important

11.8.0 introduces a new warning #21, “Recovery log detected. To clear this message, please take a diagnostic snapshot and upload to https://secure.rajant.com.” You may see this warning immediately upon upgrading your firmware; in this case, it means that the recovery log was already present prior to the upgrade. The new warning simply draws attention to its presence.

BC|Commander

BC|CommanDroid - Coming Soon!


Firmware Version 11.7.3

September 4, 2015

Important

Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.


Firmware Version 11.7.2

August 20, 2015

Important

Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.


Firmware Version 11.7.1

August 10, 2015

Important

Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

All Models

LX4 Models

LX/LX3 Models


Firmware Version 11.7.0

May 4, 2015

Note

Beginning with 11.7.0 Rajant is adopting a regular schedule of three releases per year of BreadCrumb firmware and associated software. These releases are planned for May, September, and January, although they may deviate slightly from this schedule as needed to support customer requirements. Additional patch releases may be published as needed to address any major issues in advance of a scheduled release.

Important

Be sure to read Special Instructions for Upgrading to v11.7.0 or Later in the BC|Commander User Guide before upgrading.

Rajant recommends to its customers that they upgrade their networks to this release after testing it for their individual application and networking needs.

Direct upgrades from v10 are no longer supported as of v11.7.0. This is required to ensure proper country settings post-installation. Upgrades from v10 must first install an intermediate v11 version (v11.5 recommended) before proceeding to 11.7.0.

Major New Features

InstaMesh Protocol

BC|Commander

Other Enhancements

Known Issues

The following will be addressed in a future software/firmware release:


Firmware Version 11.5.11

April 6, 2015

Note

This update only applies to JR2 models.

Enhancements:


Firmware Version 11.5.10

February 6, 2014

Note

This update only applies to LX5 models.

Enhancements:


Firmware Version 11.5.8

February 6, 2014

Enhancements:


Firmware Version 11.5.7

December 3, 2014

Enhancements:


Firmware Version 11.5.6

November 24, 2014

Enhancements:


Firmware Version 11.5.5

September 16, 2014

Note

This update only applies to JR2, ME4, and LX5 models.

Enhancements:


Firmware Version 11.5.3

July 15, 2014

Fixes:


Firmware Version 11.5.2

July 2, 2014

New Features / Enhancements:

Fixes:


Firmware Version 11.5.0

April 14, 2014

New Features / Enhancements:

Fixes:


Firmware Version 11.4.2

January 15, 2014


Firmware Version 11.4.1

December 19, 2013

Firmware 11.4.1

BC|Commander 11.4.1 (January 27, 2014)


Firmware Version 11.4.0

December 11, 2013

BC|Commander 11.4.0

Firmware 11.4.0


Firmware Version 11.3.3

October 17, 2013


Firmware Version 11.3.1

October 14, 2013


Firmware Version 11.3.0

September 16, 2013

BC|Commander Version 11.3.0


Firmware Version 11.2.2

July 8, 2013


Firmware Version 11.2.0

June 13, 2013

BC|Commander Version 11.2.0

Firmware Version 11.2.0

Known Issues:


Firmware Version 11.1.1

March 27, 2013

Improvements


Firmware Version 11.1.0

March 20, 2013

Improvements


Firmware Version 11.0.4

February 14, 2013

Improvements


BC|Commander™ Version 11.0.3

February 14, 2013

Improvements


Firmware and BC|Commander™ Version 11.0.1

February 4, 2013

Improvements


Firmware and BC|Commander™ Version 11.0.0-rc2

Warning

This is a Release Candidate meant for testing and evaluation by customers and resellers and is not intended for production use.

The following briefly describes some differences that will be seen when switching from v10 to v11. A more complete document is currently being developed.

Any systems running version 11.0.0-rc1 should be zeroized after upgrading to this version.

Please direct any feedback, suggestions, bug reports, etc. to feedback@rajant.com.

Differences between v11 and v10

Not Yet Implemented in v11

v10 settings are NOT currently retained when upgrading to v11.

Several v10 features are not yet available in version 11. These will be added in future versions:

Known Issues


Firmware and BC|Commander™ Version 11.0.0-rc1

Warning

This is a Release Candidate meant for testing and evaluation by customers and resellers and is not intended for production use.

The following briefly describes some differences that will be seen when switching from v10 to v11. A more complete document is currently being developed.

Note that there may be significant changes between this version and the next release candidate, based upon testing and customer feedback. Rajant will recommend that any systems running this release candidate are zeroized after upgrading to a subsequent version.

Please direct any feedback, suggestions, bug reports, etc. to feedback@rajant.com.

Differences between v11 and v10

Not Yet Implemented in v11

v10 settings are NOT currently retained when upgrading to v11.

Several v10 features are not yet available in version 11. These will be added in future versions:

Known Issues


Firmware and BC|Commander™ Version 11.0.0

December 10, 2012

This is the first production release of v11 firmware. Any systems running version 11.0.0-rc1 or 11.0.0-rc2 should be zeroized after upgrading to this version.

Warning

There is a known issue in v11.0.0 that causes v10 settings to be lost during an upgrade. Rajant recommends that any upgrades from v10 to v11 upgrade from v10.28 or higher directly to a later version

The following briefly describes some differences that will be seen when switching from v10 to v11. A more complete document is currently being developed and should be on the website soon.

Please direct any feedback, suggestions, bug reports, etc. to feedback@rajant.com.

Note

There is a known issue in v11.0.0-rc2 that causes over-the-air firmware transfers to take a very long time. If this affects your upgrade from v11.0.0-rc2 to 11.0.0, Rajant suggests using USB to perform this upgrade.

Differences between v11 and v10

Not Yet Implemented in v11

Some v10 features are not yet available in version 11. These may be added in future versions:

Known Issues (to be corrected in future releases)

Firmware

BC|Commander


Firmware and BC|Commander™ Version 10.33

Improvements


Firmware and BC|Commander™ Version 10.32

Improvements


Firmware and BC|Commander™ Version 10.31

Improvements


Firmware and BC|Commander™ Version 10.30

Improvements


Firmware and BC|Commander™ Version 10.28

Improvements


Firmware and BC|Commander™ Version 10.27c

Important Notes Before Upgrading

A small number of units shipped between May 2011 and October 2011 share MAC addresses assigned to their ethernet interfaces. If two or more units sharing the same MAC addresses are operational on the same network, unpredictable behavior may result.

To rectify this problem, this firmware update will perform a one-time MAC address reassignment on those units identified as having the potential of sharing one of its MAC addresses with another unit. After running this update, the fix is permanent even if the firmware on the device is downgraded to a pre-10.27 release.

What to do if you identify MAC address collisions after installing v10.27

If BreadCrumbs with duplicate MAC addresses are identified or suspected, remove one of the BreadCrumbs from service and contact your Rajant support engineer or support@rajant.com with the serial numbers and MAC addresses of the problematic units. Rajant will correct the issue as quickly as possible.

We apologize for any inconvenience this issue may cause. Rajant and its suppliers have enacted new quality control procedures to prevent this error from recurring.

Important Change to VLAN Configuration

As of version 10.27, BC|Commander Enterprise Edition is required to configure VLAN functionality on BreadCrumbs. If you do not have a BC|Commander Enterprise Edition license, please contact your Rajant sales representative.

New Features

Other Improvements

v10.27a

Version 10.27a is an update to 10.27 and corrects a cosmetic issue that caused 900MHz radio channels to be shown as operating in the 2.4GHz band in BC|Commander. This issue only existed in v10.27.

v10.27b

Version 10.27b is an update to 10.27 and corrects an issue that could cause over-the-air firmware transfers to fail several times before succeeding. This issue only existed in v10.27 and v10.27a.

v10.27c

Version 10.27c is an update to 10.27 that restores reporting of certain InstaMesh statistics via BCAPI. These statistics were unreported in v10.27-v10.27b.


Firmware and BC|Commander™ Version 10.25

Important Notes Before Upgrading

You may encounter issues launching BC|Commander if:

  1. The first time you launched it was through the “Online Launch + Install” link, AND
  2. You are now trying to launch it while not connected to the Internet.

If this is the case, Rajant recommends upgrading your Java Runtime Environment (JRE) to version 1.6.0_24 or higher. The latest version can be downloaded from http://java.com.

Since 10.24, BC|Commander does not uninstall previous versions during install. This means that it supports installing multiple versions at the same time. An “Uninstall” section has been added to the User Guide.

New Features

Other Improvements


Firmware and BC|Commander™ Version 10.24b

Important Notes Before Upgrading

You may encounter issues launching BC|Commander if:

  1. The first time you launched it was through the “Online Launch + Install” link, AND
  2. You are now trying to launch it while not connected to the Internet.

If this is the case, Rajant recommends upgrading your Java Runtime Environment (JRE) to version 1.6.0_24 or higher. The latest version can be downloaded from http://java.com.

Since 10.24, BC|Commander does not uninstall previous versions during install. This means that it supports installing multiple versions at the same time. An “Uninstall” section has been added to the User Guide.

Version 10.24 introduces a new warning code (81) when a remote reboot is issued. This warning includes the username and IP address of the administrator that rebooted the BreadCrumb, and will be shown for approximately ten minutes after the BreadCrumb is rebooted.

Radios now default to “Professional Mode.” Existing settings will be preserved after an upgrade.

BC|Commander now uses Java Web Start to update and launch. See the BC|Commander User Guide for details on the installation and launch process.

New Features

Other Improvements

v10.24a

Version 10.24a is an update to 10.24 and corrects an issue that could prevent the saving of configuration changes including the following:

v10.24b

Version 10.24b is an update to 10.24a and corrects an issue on the BreadCrumb UX2400 model that could result in erroneous low battery indications or battery errors under some circumstances. Other models do not require this update.


Firmware and BC|Commander™ Version 10.23

Important Notes Before Upgrading

The default channel for the first 4.9GHz radio in a BreadCrumb has been changed from 40 to 20.

New Features

Other Improvements


Firmware and BC|Commander™ Version 10.21

Improvements


Firmware and BC|Commander™ Version 10.20

New Features

Other Improvements


Firmware and BC|Commander™ Version 10.19

Note

Version 10.19 introduces a subtle change in the meaning of the InstaMesh flood limiting configuration fields. See below for details.

Note

Version 10.19 changes the default channel number for 900MHz radios from 6 to 5.

New Features

Other Improvements


Firmware and BC|Commander™ Version 10.18

New Features

Other Improvements


Firmware and BC|Commander™ Version 10.17

Note

If upgrading from a version earlier than 10.15, be sure to read the 10.15 installation notes before upgrading.

Improvements


Firmware and BC|Commander™ Version 10.16

Note

If upgrading from a version earlier than 10.15, be sure to read the 10.15 installation notes before upgrading.

New Features


Firmware and BC|Commander™ Version 10.15

Important Notes Before Upgrading

BC|Commander v10.14 or newer is required in order to discover BreadCrumbs running firmware v10.14 or newer. Because v10.14 was not widely released, v10.15 may be the first version you install with this requirement.

As of firmware v10.14, a status LED that is set to OFF via BC|Commander is not turned on via the status button. This is to prevent accidental illumination during nighttime operations.

As of firmware v10.15, an InstaMesh license key is required for all BreadCrumbs. All new BreadCrumbs shipped with firmware 10.15 or newer have this license preinstalled.

Most BreadCrumbs shipped prior to the release of v10.14 will automatically install a license included in their firmware when upgraded to 10.15 or newer.

Any BreadCrumbs running firmware v10.15 or newer that can NOT have install an InstaMesh license automatically indicate error code 311 and will reboot every fifteen minutes.

A license may be obtained and installed for these BreadCrumbs automatically using BC|Commander 10.15 or newer, via the “Mesh” -> “InstaMesh Licenses” menu. If the BC|Commander workstation has Internet access, the keys may be retrieved immediately from Rajant using your Rajant download credentials. If Internet access is not available on the BC|Commander workstation, a license request file may be exported and sent to instamesh_license_request@rajant.com at a later time. The license file that is emailed back may then be imported via the same menu, after which BC|Commander will automatically install the licenses onto their respective BreadCrumbs as the BreadCrumbs become available.

New Features

Other Improvements


Firmware and BC|Commander™ Version 10.12

New Features

Other Improvements


Firmware and BC|Commander™ Version 10.10

New Features

Other Improvements


Firmware and BC|Commander™ Version 10.08

Note

As of version 10.08, an Enterprise Edition of BC|Commander is being offered with additional features focused on large or complex networks.  Contact your Rajant sales representative for pricing.

New Features

Other Improvements


Firmware and BC|Commander™ Version 10.06

Improvements


Firmware and BC|Commander™ Version 10.05

Note

Rajant advises that BreadCrumbs running v10.04 be rebooted immediately prior to any over-the-air firmware upgrades to 10.05. Failure to do so may result in a failed upgrade, which would require a USB-based upgrade to resolve.

New Features

Other Improvements


Firmware and BC|Commander™ Version 10.04

This release introduces several new features. See the full documentation for details concerning their use.

New Features

Other Improvements


Firmware and BC|Ccommander™ Version 10.03

New Features

Other Improvements


Firmware Version 10.02

New Features

Other Improvements


Firmware Version 10.01

Version 10.01 is a new Major Revision of the BreadCrumb firmware and management software. It adds a number of new features and a framework in which still more functionality can be added that is not possible in version 9. While version 9 will still be supported, version 10 is Rajant’s focus for future software development.

Note

Version 10 is only compatible with version 9 when operating in a special compatibility mode with reduced functionality. This is intended to allow the upgrading of fielded units from v9 to v10 rather than enable long-term operation of mixed-version networks.

Some of the most significant changes from version 9 are: