Overview

Mission Manager 2.11.1 provides an updated Docker file, ensuring that Mission Manager remains secure, robust and up to date.

About

Version 2.11.1 is a minor update to upgrade the version of the Docker file which Mission Manager uses.

New Features

• None

Improvements

• Docker version updated to 27.1.2 for security and longevity of the product.

Fixes

• N/A

Overview

Mission Manager 2.11 takes the powerful capabilities introduced in 2.10 to the next level, delivering enhanced security, improved data visualization, and critical usability fixes that optimize operational efficiency.

The zipped exports and imports of data sets, introduced in 2.10, can now be optionally password-controlled, allowing offline storage of encrypted files. In addition to bolstering security, Mission Manager 2.11 enhances data management with the ability to include Transmitters of Interest in your downloadable CSV for occupancy data. Visual clarity and precision have also been improved, with bearing data sweep graphs updated to the latest style, offering a more modern and intuitive user experience. Moreover, Mission Manager 2.11 addresses numerous critical fixes, including accurate dates on GPS status report chart axes and low scale rendering of low-scale Signal Power Scan data points.

New Features

• Transmitter of Interests (TOI) already show on the Occupancy report’s graph, now you can choose to include their TOI name, group and frequency in the CSV download for offline analysis
• Missions, Schedules and Schedule Groups have a ‘Created’ data column so you can sort them based on when they are created in addition to the date they were first scheduled to run
• You can optionally encrypt JSON and CSV exports with a password, then unencrypted on import, ensuring that data sets are encrypted in transit between Mission Manager and your PC
• You can print Report pages by clicking a new print button on the pages for offline analysis

Improvements

• When upgrading a Node, Mission Manager checks the installer file and confirms the Node Firmware version before proceeding to install
• Incidents can be updated and closed in a single command, resulting in greater user efficiency
• The VITA 49 standard has been added as a recording format for Remote recording schedules drop-down, to align with Node Firmware feature
• When importing a list of detectors you can add a unique name and postfix to the detector to distinguish them from any existing detectors in the list
• Additional Tooltips have been added to the Schedule page to guide the set up and editing of schedules
• The Bearing data’s sweep graphs now use the latest graphical styling to match the other graphs across Mission Manager
  

Fixes

• Dates have been added to the GPS status chart axis so that you can see the dates when looking at data older than the last 24 hours
• The Signal Power Scan’s data points now display correctly on the graphs axis when using a lower scale
• Filtering the Schedule page by owner displays the list alphabetically
• The Node dropdown has been removed from Signal power section of Reports
• The maximum number of rows which can be selected in pages across Mission Manager has been limited to 999 rows for better memory management
• Multiple fixes have been added for performance and security

Known Issues

• Selecting a large data set for export may result in high memory usage, small sets are highly recommended; memory management improvements expected in 2.11.2
• Node Status Graph may automatically reset their scale a few minutes after being zoomed, to be addressed in 2.13
• Node’s GPS status may report as ‘offline’ when Node’s true state is ‘fixed’, to be addressed in 2.13

New Features

• Datasets can be exported and imported as zipped files. Any dependent datatypes are automatically included in the zipped file
• File uploads and downloads are listed in a new File page, under the Manage menu
• The top bar in the user interface can be colour coded, so multiple Mission Manager instances can be identified in the same web browser
• Notification emails attach the CSV data for the waterfall chart from Signal Power reports for offline viewing

Improvements

• Schedules:
  • Fields have been renamed in the scheduling of Sweep scans
  • A TDOA geolocation schedule will prompt for a minimum of 3 or 4 Nodes to guide users during the creation of a schedule
  • The local GMP server is automatically added to schedules for quicker scheduling
• Chart improvements across Mission Manager:
  • Charts have a new style and menu bar, including options to download data and PNG for offline analysis
  • Targets Of Interest can be assigned a different color to distinguish them in charts
• The Node page has been improved for clarity and security:
  • Option to Encrypt Connections over HTTPS in preparation for CRFS CORE Node firmware
  • Node passwords are required when first connecting to Nodes
• User Interface improvements:
  • When selecting all items in a Report or Data page all items in the database are selected rather than items in the page view

Fixes

• The “Resolved Incidents” field shows the correct count of incidents
• A typographical error in the password reset email has been corrected
• Multiple fixes for performance and security

Known Issues

• Following an upgrade POA sweep scans in schedules need to be recreated in order to display the correct noise floor
• It is not currently possible to export and import POA geolocation reports
• Dates are not included in the GPS status report charts

New features

• N/A

Fixes

• Fixes issue where Mapbox tiles were incompletely displayed in the map view.
• Fix for Mission Manager Error "Error: Unknown hydrate: Set"

Note: Following 2.9.0, the next customer release is 2.9.2. Version 2.9.1 was an internal release.

New features

• Database capacity threshold incident reporting. A proportion of the disk is reserved for essential database maintenance and cleanup. An incident will be raised when the data capacity matches a preconfigured percentage threshold. This allows a system administrator to take action, such as deleting old data and running “mm.sh freedisk”.
• Reports ordered based on their creation date. A new column has been added called “created”. The default ordering has been set to show the most recent reports first at the top of the “Created” column list. Existing reports in the database will have their “created” field set to the “data start” field. It is still possible to sort the ordering based on other columns.
• Hide Node password field from users. If a user doesn’t have the ‘add and edit’ permissions for nodes, the HTTP password field is hidden in the web UI for that user login.

Improvements

• In some circumstances the Calendar view opened at a date in the past. Now the calendar will open and default to the current day’s date.
• Signal Power Reports have been improved, so they have greater precision.
• Power reports correctly default to max on the aggregation function for display, and min for low.

Fixes

• It was previously possible to create a Schedule with a start and stop time with the same time. This has been fixed so it is no longer possible.
• The message “Could not run schedule entry” has been changed from an Error to a Warning.

New features

• The server logs can be deleted using the clearlogs function from the command line.
• Support for PKI certificates (including card readers) to allow users to log on to the Mission Manager web page.

Improvements

• Time stamps have been added to the Mission Manager logs

Fixes

• It is now possible to import and use some solution files from RFeye Site version 1.51.2 and onwards.
• Fixes a segmentation report when data is not returned correctly in some circumstances.
• A non-functional option called “Encode Noise Floor” has been removed from Mission Manager’s UI.

Known issues

• It is not possible to import POA Geolocation from RFeye Site to Mission Manager.

Overview

The key feature of this release is the ability to create a complex mission within RFeye Site and then export that configuration into Mission Manager so it can be run on an automated, scheduled basis. These are called Mission Automation Configuration (MAC) files.

Features

• Allow a user to import a Mission Automation Configuration (MAC) from RFeye Site and run as an automated schedule entry against GMP.
• Allow a user to connect to the Site Mission Processor (SMP) HTTP / JSON interface and receive trigger and geolocation data.
• An auto-delete function can be set in the settings.py file to auto-delete data from the database.
• Improved keyword search in the list views to give fuzzy results.
• Histogram for spectral data hit count.
• Filter and export geolocations within a given area.
• Disabled nodes are now visible when creating a schedule.
• Users can now be seen from the User Group Detail View.
• Add TOI icon option to bulk TOI import.

Fixes

• Stabilizes the database at larger volumes and when running intensive queries for reports.
• Known user interface issues with some parts of the calendar and maps.
• Non-super users are allowed to create super users.
• Fixes known crashing errors caused by certain interactions on the UI.
• Cloning issues when attempting to cloning certain objects.
• A graphical issue in the calendar which does not accurately reflect repeating schedules.
• Database memory leak.

Known issues

• Spectrum coverage chart will display inaccurate information when rendering logarithmic values based on a subset of data from a previous report.

New features

• Added the uncertainty fields Above and Below to the “View geolocation data” page.

• The sweep scan mask filter in the schedule entry page now includes separate options for the import and export of the masks based on the file formats (JSON or CSV). The new options are export mask to JSON, export mask to CSV, import mask from JSON and import mask from CSV.

• The raised incidents are classified into either of the 2 types, i.e., system or mission wherein:
  • System incidents: Incidents related to the system configuration, e.g., those related to the configured Nodes or servers.
  • Mission incidents: Incidents raised by the missions or scans configured in the system.

• The incidents are filtered as System, Mission, Geolocated or In-building in the main map view.

• Mission Manager represents the system and mission incidents using different icons in the map display.

• User interface to the “Select incident to view” page:
  • Added the Type field to classify the incident type as system or mission.
  • Added the new filter types – Type, Nodes and Node groups.

• User interface updates to the “Select node group to view” page:
  • Added the Nodes column to display the Nodes associated with each Node group.
  • Added the Node dropdown filter to filter the Node groups by the associated Nodes.

• The “Schedule entry to view” page displays a warning status in the STATUS column for any schedule that has a warning or error associated with it. Hover the mouse pointer over the warning status to view the warning message details. Click the warning icon to view the log entry details.

• The main map view shows overlay icons for the displayed Nodes that have either triggered an incident or encountered a system issue.

• The main map view is updated such that if an incident is raised within a building and the building icon is selected, the map displays the icon flashing in red and orange.

• On the Mission Manager homepage, the incident alarm button is set to off by default.

• User interface updates to the sweep scan input for schedules:
  • Added the Antenna

• The POA geolocation report has been changed to either cover a center frequency or a range.
  • A mask of relative power can be applied to be the geolocation report
  • POA geolocations and POA geolocation reports can be asked to include Guard Node sweep data as part of the geolocation solution

• Frequency aggregation function has been merged with the signal power report and signal occupancy report
  • Single-value and range markers can be created and saved to the charts
  • Charts can be exported as .png
  • Reports loading in the background can be deleted mid-process if no longer required

Improvements

• Updates to Format field in the TOIs >> Import page:
  • Added support for the SFAF (Standard Frequency Action Format) file format import.
  • Removed support for the PUB7 file format.

• Improvements to the TOIs (Transmitter of interest) feature include:
  • Verification of TOI minimum and maximum power.
  • Efficient TOI matching.
  • Specifying the exclusion bands for the TOIs.
  • Verification of the authorized radius for the TOI.

• User interface updates to the “Add TOI” page:
  • Added the power (dBm), Max. power (dBm), Exclusion bands, Authorized radius fields.

• User interface updates to occupancy scans in Schedules and IFDS ranges:
  • Removed the occupancy (%) and Max. occupancy (%) fields in the Incidents subsection displayed when the TOI filter type field was not specified.

Fixes

• Fix to display a detailed error message when importing an invalid file in the sweep scan mask editor. The system now exports masks using Data instead of Body.

• Fix to display the TOI details in the “Select TOI to view” page by clicking the Associated TOIs link from the other pages.

• Fix to match the number of incidents shown on the main map to those visible inside a building.

• Fix to display all the incidents in the building view by default without explicitly selecting the Incidents.

• Fix to resolve incorrect formatting of the text in the email notifications.

• Fix for incorrect mapping of the bandwidth specified in line 114 of PUB7 to the TOI’s bandwidth on importing the PUB7 file. The fix replaces the PUB7 format with the SFAF (Standard Frequency Action Format) file format.

• Fix to remove the filter pre-sets on the map aggregation for consistency.

• Fix to resolve incorrect occupancy for TOIs.

• Fixes some issues with the spectrum browser not displaying data.

Features

• Mission Manager is distributed as a .deb installer and a Docker image. Users wishing to perform the advanced Docker installation will be provided with the Docker image instead of the .deb installer.

• The installation includes an upgrade procedure that allows the user to upgrade from the previous release.

• The Mission Manager management script includes a new sh status command that allows the user to view the status of the upgrade process such as stopped, starting, upgrading database, upgrading data, running, stopping, crashed.

• Mission Manager raises incidents based on the Node status. The system raises an incident if any of the monitored Node status metrics (input voltage, input current, baseband temperature, radio temperature and disk usage) exceeds the recommended level. Mission Manager raises one incident per metric per Node per day.

• User interface updates to the “View status data” page include:
  • Any of the monitored Node status metrics (input voltage, input current, baseband temperature, radio temperature and disk usage) exceeding the recommended level is displayed in red. Hovering the mouse pointer over the metric displays the detailed error message.

• User interface updates to the “Select incident to view” page include:
  • The system raises an incident if any of the monitored Node status metrics (input voltage, input current, baseband temperature, radio temperature and disk usage) exceeds the recommended level.

• The “Select node to view” page displays the Node hardware status. The flag is red if the input voltage, input current, baseband temperature or disk usage exceed the recommended level. Hovering the mouse pointer over the icon displays the detailed error message. Clicking the icon displays the “View status data” page for the corresponding Node.

• User interface updates to the “View node” page include:
  • The Latest status field in the Resources subsection displays error messages in red, if any of the monitored Node status metrics (input voltage, input current, baseband temperature, radio temperature and disk usage) exceeds the recommended level. Details of the metrics are displayed in the “View status data” page for the corresponding Node.

• In the “Select incidents to view” page, the system displays the incidents raised if any of the monitored Node status metrics, i.e., input voltage, input current, baseband temperature, radio temperature and disk usage exceeds the recommended level.

• The Node pop-up window visible on clicking the Node on the map is updated to display the Node hardware status. Hovering the mouse pointer over the icon displays the detailed error message. Clicking the icon displays the “View status data” page for the corresponding Node.

• User interface updates to the main map display:
  • The Node icon is displayed in red to indicate a Node status error.

• User interface updates to the Manage >> Buildings view:
  • The Node icon is displayed in red to indicate a Node status error.

• On multi-select boxes or selection widgets, hovering the mouse pointer over a list item displays the full item name. For example, hovering the mouse pointer over the selectable user permissions in the User permissions field of the “Add user” page displays the full permission name. This update applies to the following fields on the user interface:
  • “Add user” page: User permissions and Groups
  • “Add zone” page: Layers
  • “Add user group” page: Permissions
  • “Add overlay” page: Layers
  • “Add marker” page: Layers
  • “Add node access entry” page: Nodes and Users
  • “Add signal power report” page: Nodes
  • “Add signal occupancy report” page: Nodes
  • “Add POA geolocation report” page: Nodes, GMP servers, Guard Nodes
  • “Add GPS status report” page: Nodes
  • “Add Node status report” page: Nodes
  • “Add schedule entry” page: Nodes, GMP servers, Guard Nodes, Detectors
  • “Add IFDS range” page: Nodes, GMP servers, Guard Nodes, Detectors
  • “Add TOI” page: TOI groups, Operation zones, Exclusion zones fields.

• The sweep data frequency aggregation displays the TOI count and chart areas.

• The maximum value for the Aggregate measurements field is set to 128 for sweep scans, synchronous sweep scans, bearing scans and occupancy scans.

• User interface updates to the frequency aggregation charts for sweep, synchronous sweep and occupancy data include:
  • Clicking the Associated TOIs hyperlink displays the “Select TOI to view” page.
  • Hovering the mouse pointer over the TOI in the frequency aggregation chart displays the TOI name, center frequency and bandwidth.
  • Clicking the TOI in the frequency aggregation chart displays the “View TOI” page for the particular TOI.
  • Selecting either 2 or all 3 of the max, avg and min parameters, displays the chosen parameters as a shaded region in the frequency aggregation chart. Selecting only 1 of the max, avg and min parameters, displays the chosen parameter as a solid line in the frequency aggregation chart.

• User interface updates to the “View sweep data” page:
  • Selecting Actions >> Show TOIs and hovering the mouse pointer over the TOI in the chart displays the TOI name, center frequency and bandwidth.

• User interface updates to the “View occupancy data” page:
  • Selecting Actions >> Show TOIs and hovering the mouse pointer over the TOI in the chart displays the TOI name, center frequency and bandwidth.

• User interface updates to the “Select time data to view” page:
  • Added the Modulation dropdown to filter the time data entries by modulation type.

• User interface updates to the “Select signal data to view” page:
  • Added the Modulation dropdown to filter the signal data entries by modulation type.

• User interface updates to the “Select incident to view” page:
  • Added the LAST UPDATED column to display the username of the user who last modified the incident.

• The user can export the displayed charts to a PNG file. The PNG retains the zoom level defined in the chart. The PNG file can be exported from the following:
  • Data >> Sweep data.
  • Data >> Occupancy data.
  • Data >> Time data.
  • Data >> Bearing data.
  • Reports >> GPS status report.
  • Reports >> Node status report.
  • Diagnostics >> Mission Manager status.
  • Diagnostics >> Node status.

In case the chart export includes several traces that cannot be well-formatted using the defined legend, the system displays a warning message similar to “For a chart of this size, it is suggested that you select no more than [x] traces for export. You have [y] selected. This may result in formatting issues for the legend in the PNG.”

• The system can now be configured to send email notifications to selected users on completion of both the historical reports (added via the Reports menu) and parallel reports (added via the Schedules and IFDS ranges menus). The users to be notified via email on completion of the report are to be selected from the Users field in both the historical reports and parallel reports.

• Added the Notifications subsection that includes the Users field to the following:
  • Reports >> Add signal power report.
  • Reports >> View signal power report.
  • Reports >> Add signal occupancy report.
  • Reports >> View signal occupancy report.
  • Reports >> Add POA geolocation report.
  • Reports >> View POA geolocation report.
  • Reports >> Add Node status report.
  • Reports >> View Node status report.
  • Reports >> Add GPS status report.
  • Reports >> View GPS status report.
  • Schedules >> Add schedule entry >> Signal power report.
  • Schedules >> Add schedule entry >> Signal occupancy report.
  • Schedules >> Add schedule entry >> POA geolocation report.
  • Schedules >> Add schedule entry >> GPS status report.
  • Schedules >> Add schedule entry >> Node status report.
  • IFDS ranges >> Signal power report.
  • IFDS ranges >> Signal occupancy report.
  • IFDS ranges >> POA geolocation report.
  • IFDS ranges >> Node status report.
  • IFDS ranges >> GPS status report.

• The authentication details HTTP username and HTTP password are mandatory fields when adding the Node details in the “Add Node” page.

• The authentication details HTTP username and HTTP password are mandatory fields when adding the GMP server details in the “Add GMP server” page.

• In the “Add Node” page, it is mandatory to specify the authentication HTTP username and HTTP password fields.

• Updated the Mapbox tiles to display borders in the map view.

• Markers can be placed within the configured buildings.

• On encountering an unexpected frontend error, Mission Manager now displays an “unexpected error” page. The user can click the Download report icon to download the error report in a plain text file to send to support@crfs.com for further investigation.

• All reports generated from the Reports menu accept only past or historical dates in the start and end fields.

• Removed the retrieve average noise floor feature from the database, API and user interface. Set the retrieve noise floor functionality to true by default. In the user interface, the Retrieve noise floor checkbox is removed from the following:
  • Schedules >> Sweep scans.
  • Schedules >> Synchronous sweep scans.
  • IFDS ranges >> Sweep scans.
  • IFDS ranges >> Synchronous sweep scans.

• Added support for triggered remote recordings in schedule entries and IFDS range entries. The I/Q data files stored on the Nodes 50-8/100-8/100-18 can be recorded in NCP, Xdat, Hdf5 or WAV-E formats.

• Users can clone and edit entries configured in the system by clicking the Clone button in the following pages:
  • TOIs >> View TOI.
  • TOI groups >> View TOI group.
  • Schedules >> View schedule entry.
  • Schedule groups >> View schedule group.
  • Missions >> View mission.
  • Areas >> View area.
  • IFDS ranges >> View IFDS range.
  • Signal power reports >> View signal power report.
  • Signal occupancy reports >> View signal occupancy report.
  • POA geolocation reports >> View POA geolocation report.
  • GPS status reports >> View GPS status report.
  • Node status reports >> View Node status report.
  • GMP servers >> View GMP server.
  • IMG servers >> View IMG server.
  • PBD servers >> View PBD server.
  • Nodes >> View node.
  • Zones >> View zone.
  • Icons >> View icon.
  • Tile sets >> View tile set.
  • Overlays >> View overlay.
  • Markers >> View marker.
  • Layers >> View layer.
  • Buildings >> View building.
  • Schematics >> View schematic type.
  • Users >> View user.
  • User group >> View user group.

• Mission Manager allows third party systems to create incidents using the API.

• Users can customize the color schemes used in the chart display. In case of ranges, users can define separate colors for the area between the lines and the lines themselves. The color schemes can be customized in the following:
  • Data >> Sweep data.
  • Data >> Occupancy data.
  • Data >> Time data.
  • Data >> Bearing data.
  • Reports >> GPS status report.
  • Reports >> Node status report.
  • Diagnostics >> Mission Manager status.
  • Diagnostics >> Node status.

• Users can create a TOI from signal data, mask data and geolocation data by clicking the +TOI button in the following:
  • Data >> Signal data.
  • Data >> Mask event data.
  • Data >> Geolocation data.

• Removed the DNS dependency from the proxy service to unblock MapBox.

Fixes

• Fix for the Rate field under synchronous sweep scans to be specified only in seconds.

• Fix to resolve the mismatch between the number of incidents shown on the main map and those visible in the building view.

• Fix for the incorrect chart name label in the “View signal occupancy report” page.

• Fix for incorrect display of the green tick icons in MS Edge.

• Fix to indicate a connection failure to the IMG server by displaying the “Connecting” status indicator in the map view of the “View IMG server” page.

• Fix for the error “Cannot combine frequencies of different ranges” encountered when combining the sweep data of Field Strength and Power units to create a frequency aggregation.

• Fix for IMG servers unable to resolve local DNS names.

• Fix to resolve the progress bar’s inaccurate status during the file submission process, particularly in case of slow connections.

• Fix to add debounce handler to drawing zones.

• Fix for incorrect mask output in the data charts that can be higher than the available frequency data.

• Fix to display tooltips in all the “Import” pages.

• Fix for the dropdown options in the chart display to work as expected.