RFEYE FIRMWARE
RELEASE NOTES

About

CRFS RFeye Node firmware runs on our RFeye Node range of hardware products.

V2.24 is a major update over the previous v1.x firmware versions, moving the operating system over to CRFS Core. This provides significant security upgrades and the addition of new features such as Tasker and HTTPS certificates, as well as an updated OpenVPN client.

Core v2.24.1 is a minor update to Core v2.24, adding the ability to upgrade 40-8 nodes over a network connection.

Please take note of the special instructions included in this document as they are more involved than previous software releases due to how significant of an upgrade this is.

Please note that while all the nodes listed under ‘Supported Nodes’ are compatible with running the v2.24 software release, not all of them are upgradable using the provided upgrade files. Please read the relevant sections for specific details. 

Supported Node Models

This firmware release is intended to be compatible with the following products:

RFeye Node models, including all arrays running these models:

  • 40-8
  • 50-8
  • 100-8
  • 100-18
  • 100-18 LW
  • 100-40

Over-the-Air (OTA) Upgrade Pack Compatibility

A node can only be over-the-air upgraded to v2.24.1 using the provided installers if ALL of the following conditions are met:

  1. The RFeye serial number is greater than 100129 if starting with a 1
  2. The RFeye serial number is greater than 200101 if starting with a 2.
  3. The SSUS status is ‘active’ in the license manager.

If your node is not one of these models and is under active SSUS please contact support@crfs.com as there are other options available to assist you to upgrade to v2.24.1 

New Features

In version 2.24.1:

  • Added support for 40-8 nodes to be compatible with the CRFS Core v2.24.1 upgrade process and files.

In version 2.24:

  • Tasker
  • HTTPS Certificates

Please refer to the separate Tasker User Guide and Core Firmware User Guide for details on how to use these features.

Fixes and Improvements

In version 2.24.1:

  • Fixed an issue where a node could present a ‘META data with valid "fqdn", not null’ warning in the log in Mission Manager.

In version 2.24:

  1. The EMP API has been updated with new features that support Tasker. An updated EMP user guide is also available which includes this.
  2. OpenVPN has been updated to version v2.5.8 from the previous v2.3.4, adding significantly greater compatibility for modern configuration files. Please note that client configuration files are often not compatible between these releases, so creating a v2.5-compatible config might be required.

Mixed Node Network Compatibility

A node software compatibility matrix is available below showing which node firmware versions can be run together in a deployed mission in a network together:

 

Firmware Version

Mission

v1.22-9958

v1.23-21873

v1.24.3

Core v2.24.1

TDOA (GPS)

Yes

Yes

Yes

Yes

POA (GPS)

Yes

Yes

Yes

Yes

POA (Synclinc)

Yes

Yes

Yes

Yes

Sync Sweep

Yes

Yes

Yes

Yes

Sync Sweep (Synclinc)

Yes

Yes

Yes

Yes

AOA Geolocation

Yes

Yes

Yes

Yes

 

Please note that v1.24.0 is not able to run in a mission with the rest of these nodes. Please upgrade to v1.24.3 if this is a requirement for your deployment.

Software compatibility

Please only use this release with the following version numbers of CRFS software:

  • RFeye Site v1.53.6 or newer,
  • Mission Manager v2.11 or newer,
  • GMP v1.10 or newer.

Upgrade Process

Important Notes

  • Do not use Mission Manager to upgrade from v1.x to v2.24.1. This is an extra-ordinary upgrade involving multiple steps. Future upgrades will be possible using Mission Manager again.
  • If upgrading from Core v2.24 to v2.24.1 Mission Manager can be used.
  • Do not attempt to upgrade over an OpenVPN connection if upgrading from v1.x. If upgrading over an active OpenVPN connection is important to you please contact support@crfs.com for assistance on how to do so as there is a mechanism available.
  • It is not possible to downgrade to v1.x after installing this upgrade to v2.x

    There is a specific upgrade path that must be followed, only run the section below which corresponds to the version of firmware you are running, depending on if you are upgrading a node from v1.x of the Debian-based firmware, or you were using a Beta release of Core firmware.

1.1 v1.24.x to v2.24 Upgrade Process

  1. Create a backup of your configuration files.

    Using the Node->Backup web page with the "Target OS" set to Docker.
  1. Confirm the node is running v1.24.3 or higher.

    If not, upgrade to this release first.
  1. Confirm your node meets all the requirements to run RFeye Core.

    As set out earlier in this document, specifically the node model and over-the-air upgrade compatibility.
  1. Check your SSUS is active on the node (Licenses -> Licenses).
  2. In the Upgrade section of the node webpage select ‘upload new file’ and submit the ‘crfs-debian-to-core_1.0_amd64’ upgrade file.

    The node will reboot several times during the upgrade process, and you will see ‘Pending’ and ‘Node Offline’ cycling on the top-right of the node webpage. This averages about 7 minutes to complete but could take up to 20 minutes. When complete you will be prompted to login to the node webpage again. The default username and password is ‘admin’ and ‘rf3y3’.
  1. Submit the ‘docker_2.24.1’ installation file when prompted to ‘Select Installer’

    Log in and select ‘Software Manager’ on the top right. Click ‘Select Installer’ and select the. This will install the docker container. After installation it will show as ‘running’ in green text on the webpage.
  1. Click ‘RFeye Node’ on the top right to go to the main node Webpage.

    Change your node webpage username and password to a secure combination and generate your rescue scripts (Security -> Generate Rescue Scripts).

1.2 BETA Users to final v2.24 Upgrade Process

  1. Create a backup of your configuration files.

Using the Node->Backup web page with the "Target OS" set to Docker.

  1. Confirm the node is running any Beta version of v2.23 or v2.24 software.
  2. Confirm your node meets all the requirements to run RFeye Core.

    As set out earlier in this document, specifically the node model and over-the-air upgrade compatibility.
  1. Check your SSUS is active on the node (Licenses -> Licenses).
  2. IF you are running a Core Beta release lower than v2.23-23079 navigate to the Software Manager section of the node webpage and apply the ‘crfs_core_2.23-23079’ update by choosing to ‘Select Installer.’ If you are running a version of v2.23 higher than this or a Beta version of v2.24 ignore this step.
  3. Navigate to the Software Manager section of the node webpage and apply the ‘crfs_core_2.24.1’ update by choosing to ‘Select Installer.’

    The node will reboot several times during the upgrade process, and you will see ‘Pending’ and ‘Node Offline’ cycling on the top-right of the node webpage. This averages about 7 minutes to complete but could take up to 20 minutes. When complete you will be prompted to login to the node webpage again. The default username and password is ‘admin’ and ‘rf3y3’.
  1. Submit the ‘docker_2.24.1’ installation file when prompted to ‘Select Installer’

    Log in and select ‘Software Manager’ on the top right. Click ‘Select Installer’ and select the. This will install the docker container. After installation it will show as ‘running’ in green text on the webpage.
  1. Click ‘RFeye Node’ on the top right to go to the main node Webpage.

    Change your node webpage username and password to a secure combination and generate your rescue scripts (Security -> Generate Rescue Scripts).

Additional Notes

  1. It is not possible to downgrade to v1.x after installing this upgrade to v2.x
  2. SSH access is disabled by default in this release. It can be re-enabled in the firewall of the node’s web interface, though this is not recommended.
  3. The default credentials for the web interface are:
    Username: admin
    Password:   rf3y3
    Please ensure you change this and set a secure username/password combination.
  1. Please make sure to pro-actively generate your rescue scripts per node in order to be able to use them if needed (available under Security -> Generate Rescue Scripts in the Node webpage).
  2. Only IPv4 addresses are supported in this release, IPv6 support will be added in a future release.

Disclaimer

The information contained in this document is not intended to amount to advice on which reliance should be placed. Although we take reasonable steps to ensure the accuracy of the information provided, we provide it without any guarantees, conditions, or warranties as to its accuracy or reliability. To the extent permitted by law, we expressly exclude all conditions, warranties and other terms which might otherwise be implied by law. We have the right to revise and amend this information from time to time.

Overview

RFeye Core is designed as a robust foundation for future updates and features, enhancing security and ensuring powerful new functionalities and compatibility across CRFS’ range of hardware products.

How to update or upgrade to RFeye® Core

  • Customers with Version v1.24.x and SSUS will automatically be eligible to upgrade their compatible RFeye Nodes.

  • Customers without SSUS can upgrade by talking to Customer Support about SSUS renewal and upgrade.

  • Customers running on v1.24 or older without SSUS should contact their Account Manager or Customer Support about an upgrade.

Upgrading to Core 2.24 will move you from v1.x to v2.x. Starting in July 2024, all new software features and system updates will be exclusively available to customers using RFeye Core (v2.24) firmware or newer.


New features

  • Tasker: Tasker Application is an RFeye Node-based application that allows customers to send solutions from RFeye Site to an RFeye Node or run an EMP API mission locally, saving the resultant data locally on the RFeye Node. This benefits users who want to execute a task on an RFeye Node without requiring an active API stream over a network connection or manual configuration during the mission. Users can generate configurations through the Node webpage or program the Node using RFeye Site. Tasker is designed for simplicity, with a user guide that provides detailed descriptions of its functionality and instructions. 
  • HTTPS encryption support: Allows secure communication and over a network connection.

Please see the full release notes for additional details on all changes and improvements.

Further reading: "RFeye Core: the firmware foundation for CRFS technology".

Overview

CRFS RFeye Node platform software runs on our RFeye Node range of hardware products.

V1.24.2 is a minor update to the major v1.24 release, which added new features and
functionality, as well as including fixes and a significant number of quality-of-life
improvements, the details of which are included in this document.

It is recommended all customers with compatible Node models upgrade to this release.

Supported Nodes

This platform software release is intended to be installed on the following RFeye Node models:

  • 40-8
  • 50-8
  • 100-8
  • 100-18
  • 100-18 LW
  • 100-40

Please ensure that the Nodes are running at least v1.23 before upgrading to this release.

New features

The following new features have been added:

  •  EMP optionally returns applied attenuation values with returned sweep results
    when using AGC.

Fixes & improvements

In version 1.24.2:

  • Fixed FM Audio Demodulation bug (along with RFeye Site v1.53.6 or newer),
  • EMP: removed running mission limit of eight,
  • Refined array calibration lookup mechanism. 

Software compatibility

Please only use this release with the following version numbers of CRFS software:

  • RFeye Site v1.53 or newer (v1.53.6 or newer recommended),
  • Mission Manager v2.10 or newer,
  • GMP v1.10 or newer.

Please see the full release notes for additional details on all changes and improvements.

Overview

CRFS RFeye Node platform software runs on our RFeye Node range of hardware products.

V1.24.1 is a minor update to the major v1.24 release, which added new features and functionality, as well as including  fixes and a significant number of quality-of-life improvements, the details of which are included in this document.

It is recommended all customers with compatible Node models upgrade to this release.

Supported Nodes

This platform software release is intended to be installed on the following RFeye Node models:

  • 40-8
  • 50-8
  • 100-8
  • 100-18
  • 100-18 LW
  • 100-40

Please ensure that the Nodes are running at least v1.23 before upgrading to this release.

New features

The following new features have been added:

  • IQ Streaming – Stream IQ data over TCP or UDP in the VITA-49 format, using RFeye Site or the EMP API.
  • EMP Status Information – Node GPS location and status information are available through the EMP API.
  • EMP API Restart Functionality – The EMP service can be restarted individually using the a new ‘Restart EMP’ button available under Admin -> Troubleshooting on the Node webpage.
  • Support for VectorNav 100 has been added.
  • Support for the RF Switch Daughter box
  • Future Node upgrade compatibilityAdded software features needed to support future Node firmware releases for all models of Node.

Software compatibility

Please only use this release with the following version numbers of CRFS software:

  • RFeye Site v1.53 or newer,
  • Mission Manager v2.10 or newer,
  • GMP v1.10 or newer.

Please see the full release notes for additional details on all changes and improvements.

Overview

CRFS RFeye Node platform software runs on our RFeye Node range of hardware products.

This release is a major update, adding new features and functionality, as well as including fixes and a significant number of quality-of-life improvements, the details of which are included in this document.

Supported Nodes

This platform software release is intended to be installed on the following range of products:

  • RFeye Node models:
    • 40-8
    • 50-8
    • 100-8
    • 100-18
    • 100-18 LW
    • 100-40
  • Please ensure that the Nodes are running at least v1.23 before upgrading to this release.

New features

The following new features have been added:

  • IQ Streaming
    • Stream IQ data over TCP or UDP in the VITA-49 format, using RFeye Site or the EMP API.
  • EMP Status Information
    • Node GPS location and status information are available through the EMP API.
  • EMP API Restart Functionality
    • The EMP service can be restarted individually using the a new ‘Restart EMP’ button available under Admin -> Troubleshooting on the Node webpage.
  • Support for VectorNav 100 has been added.

Software compatibility

Please only use this release with the following version numbers of CRFS software:

  • RFeye Site v1.53 or newer,
  • Mission Manager v2.10 or newer,
  • GMP v1.10 or newer.

 

Fixes

  • AOA antenna ports now show correct numbers on initialisation.
  • Minor bug fixes

Improvements

  • The version of AVR has been included in the Versions tab in Node 40-8 Web pages for completeness.

Known Issues

  • IMPORTANT: RFeye Nodes 40-8 with Radio Hardware E08 cannot be downgraded to older versions after 1.23-20632 is installed

New Features

  • Signed Rescue Scripts can be created and downloaded from the RFeye Node webpage. Note that each Node now has a set of unique rescue scripts which can be used only on that Node and no other. Going forward, a USB rescue stick will no longer be shipped with each Node since the rescue scripts must now be generated by the user from the Node webpage.
  • The RFeye Node webpage has new submenus to allow the user to format an external USB drive and also to manage external storage devices.

Improvements

  • BIST Test SyncLinc Wording improvements for clarity
  • Improvements for Automatic Gain Control (AGC) in the RFeye Node 100-40

Fixes

  • GNSS satellites which do not have a sufficiently strong signal are no longer reported on the Diagnostic page (previously shown as being present with an SNR value of 0).
  • In some cases a SenS Remote unit would not always load the radio driver when the eth0 network port was not connected, this has now be fixed
  • Check box for EMP fixed on the RFeye Node webpage
  • OpenVPN state is preserved after an upgrade and correctly reported on the webpage
  • Increased robustness of the radio FPGA recovery when using the Troubleshooting feature
  • FIFOD long term stability improvements
  • App status is reinstated after a restore from a backup configuration file
  • In some circumstances the node would reboot when RBW set to 50kHz or lower, now fixed in 4.64 onwards of radio firmware
  • Cause of "Reference synthesizer lock failed" message has been fixed
  • Stable operation of SenS Remote with DeepView
  • Improved stability of Node 40-8 upgrade process
  • Minor bug fixes

New Features

  • Support for automated antenna sequencing when used with RFeye Site version 1.52, to allow antenna sweeping missions. This is useful when using multiple antenna ports with directional antennas and can enable a sector-based geolocation approach.
  • Mixed Node network support for TDOA on RFeye Nodes 40-8, 50-8 and 100-x.To benefit from this feature, please upgrade other firmware and software to the following minimum version numbers (where applicable):
    • GMP version 1.8.3.71 or later
    • RFeye Site version 1.51.2.27 or laterMission Manager version 2.8.3 or later

Improvements

  • RFeye Site reports the power (dBm) of a detection in the Data Table tab. It is possible to view and record the signal power in each case.
  • You can now upgrade Node 100-40 and Node 40-8 to Node firmware 1.22 using the same image installer file. Prior to this, Node 100-40 required its own separate release. Now all Node Firmware installs can be completed with one installer package.

Fixes

  • Improvement to the RFeye Stormcase LED sequences: the Error light no longer flashes during Logger activity.

New Features

  • Internal GPS module’s fix and number of satellites are displayed on the Status web page and sent to Mission Manager when using fixed position.
  • Display information about UTC validity on Status and GPS Diagnostics web pages.
  • Improved detection and handling of GNSS spoofing.
  • Perform SyncLinc scan as part of BIST.
  • Improved behavior of Stormcase LEDs.
  • Node 40-8 sweep speed improvements.
  • Nodes no longer use the GPS until they get the UTC correction, which can take up to 12 minutes from power-up.
  • The “No Omni antenna covers range” error is now a warning.

Fixes

  • Fixes an issue where the padding in the first sweep of the logger set was different to all subsequent sweeps.
  • Fixes an issue where Logger was not functioning with padding which was added to a sweep set.
  • Fixes an issue where running BIST on a Node configured to use a GPS reference without a GPS fix, made the NCPd freeze.
  • Fixes an issue where POA and synchronous sweeps were not working on 40-8 Nodes.
  • Fixes an issue where  repeating mount errors/warning in dmesg occured during upgrade.
  • Fixes an issue where NCPd returned significantly higher number of IQ samples than requested for short time captures.

New Features

  • Improvements to pulse detectors to reduce false alarms against the noise floor.
  • Support for POA on Node 40-8.
  • Upgrading of webserver and Node webpage UI.

Fixes

  • Fixes an issue where EMP abruptly halts when running.
  • Fixes an issue where recorder was failing to initiate when LED switch was not selected from the UI.
  • Fixes an issue where Nodes were freezing when asked to capture 3 seconds of data at a decimation of 256.
  • Fixes an issue where the fourth antenna port was not working on Node 40-8.
  • Fixes an issue where OS corruption caused by incorrectly using FIFOd and Syncd.
  • Fixes an issue where BIST was showing failures after reboot where no failures are present.
  • Fixes an issue where incorrect firmware versions were being displayed on the node webpage.
  • Fixes an issue where NCPd occasionally locked when issued with synchronous commands.
  • Fixes an issue where Reset MCU button on node webpage did not always work.

New Features

  • Adds pulse power and SNR to debug JSON.
  • Displays SNR of GPS satellites on the Node web page.
  • Pulse bandwidth measurements are now more stable when measured against uneven spectra.
  • Power consumption limit is now 70W.
  • LFDF antennas (North, South, East, West, Sense) are expected to pull between 45 and 85 mA.

Fixes

  • Fixes an issue where there was a bug with timestamp and sequence number of IQ packets when streaming.
  • Fixes an issue where NCPd panics when loading AOA and WW calibration files directly from Node Firmware version 1.18-6951.
  • Fixes an issue where the Linux time could not be set properly from NCP.
  • Fixes an issue with Nodes reporting Logger’s state as “Possible crash or in a bad state”.