Change Logs

Updates to our Terms of Use

• Our Terms of Use has been updated to include links to our privacy policy and data privacy addendum (DPA). We’re making these updates to clarify our terms and ensure that how we use your data remain transparent for you, as well as to cover all Dickson products, services, and features. You can read the entire Dickson Terms of Use here.

Bug Fixes and Improvements

• Resolved an issue where Reference Lines were incorrectly displayed when converting to a temperature display unit different from the company default setting
• Resolved an issue where data readings on the Channel and Logger/Equipment widgets for Custom Dashboards were not automatically updating
• Resolved an issue where Universal Sensor alarms were not displayed in the Audit Trail
• Resolved an issue where Universal Sensor alarms were not triggering SMS or Email notifications for custom alarms
• Resolved an issue where users were unable to specify a custom unit for custom alarms on Universal Sensors
• Resolved an issue where an alarm banner for Universal Sensor alarms was displayed multiple times
• Resolved an issue where an alarm banner would persist even after the alarm condition was modified
• Resolved an issue where End dates on the calendar only showed NaN for one-time reports if users selected the Start year before selecting the month

Features

• Bulk Acknowledgement and Bulk Commenting
  • Added the ability to acknowledge and comment on alerts in bulk, enabling users to acknowledge and/or comment on multiple active or resolved alerts simultaneously
• Bulk Alarm Pause and Automatic Resuming
  • Introduced the ability to automatically resume paused alarms/alarm templates so that applied alarms are temporarily paused for a user-specified duration
  • Added the ability to pause alarms in bulk, enabling users to pause multiple alarms applied to a data logger or equipment at once
• Cobalt X Enhancements
  • Added the ability for users to acknowledge alarms on CBX data loggers using their PIN
  • Added the signal strength and battery level of CBX data loggers to the UI
• Language Support
  • Updated Spanish and French language support to include recent features

Design Updates

• The following Audit Trail updates were made to Alarm-related event types to support DicksonOne’s enhancements to pausing alarms:
  • Changed Event Type “Alarm” to “Alarm Triggered” for alarms that triggered
  • Changed Event Type “Alarm” to “Alarm Resolved” for alarms that returned to normal
  • Changed Event Type “Alarm Activated” to “Alarm Resumed” for paused alarms that resumed
  • Changed Event Type “Alarm” to “Alarm Updated” for alarms that were updated with Reason Code, Corrective Actions, and/or Preventive Actions
• The following design updates were made to the Monitoring Points > Equipment / Data Loggers > Alarms pages to support DicksonOne’s enhancements to pausing alarms:
  • Added checkboxes to each alarm applied to the equipment or data logger
  • Added a yellow “Paused” label with the scheduled period to each alarm that is currently paused
  • Added a “Paused” label to each channel that is paused
  • Added an Alarm Pause modal that opens when users click on the “Pause” button for individual alerts and bulk pausing alerts so that the pause duration of the alarm(s) can be specified
  • Changed “Applied to (#)” label to “Channels (#)”
  • Changed the “Unapply” button label to “Remove”
  • Removed the toggles for each channel associated with the alarm
  • Updated button components to adhere with DicksonOne’s updated design styles

Bugs

• Resolved a bug where the logger used an old token to communicate and therefore failed to post data to DicksonOne
• Resolved a bug where calibration dates had discrepancies
• Resolved a bug where old unsent readings were associated with a new sensor serial number after sensors were swapped
• Resolved a bug where configuration packets were being sent from DWE logger while on battery power (NO AC power connected)
• Resolved a bug with RTC Synchronization related to Non-Sequential Reading Timestamps
• Resolved a bug where SSL_MAX_CONTENT_LEN is too small for Amazon Certs issue resolved

Enhancements

• DWE now sends sensor configuration packets before sending readings
• Communications are now only allowed over HTTPS (no more option to turn SSL off)
• A flag has been added to the API packets to identify the current sensor plugged into a data logger
• x509 TLS certs have been refreshed
• Rollback settings protection was added
• Added a “pod_port” field to the readings packet in the API
• Added SSID field in the main configuration file when DWE logger is communicating on Ethernet
• Added exponential retries to DWE when DicksonOne is unavailable
• Updated RTC Fallback Logic with every firmware release
• Removed channel & BSSID-based scanning
• Removed code from the firmware related to an old external battery pack no longer offered

Sensor Support

• Introduced compatibility with Oceasoft PT100 Smart-Sensor
• Introduced compatibility with Oceasoft Temperature and Humidity Smart-Sensor
• Introduced compatibility with Oceasoft Co2 Triple Smart-Sensor
• Introduced compatibility with Oceasoft Universal Smart-Sensor
• Introduced compatibility with Open/Close Sensors (ROC & RTHMOC)

Bugs

• A bug that caused Dicksonware export mode latest to not display the table after pod swap was fixed
• A bug that caused RFL loggers to lose network communication was fixed
• A bug that causes Sensor Calibration Date discrepancies was fixed
• A bug that caused RFL to display temperature readings even though sensors were unplugged was fixed
• A bug that caused RFL to send incorrect Serial Numbers to DicksonOne was fixed
• A bug that caused CH2 “RH” label to be missing from RFL display when using the RS010 sensor was fixed
• A bug that caused RFL with Universal Sensor to not switch to Voltage channel was fixed

Enhancements

• RFL now sends packets to DicksonOne informing when a sensor was unplugged from the data logger
• A firmware build number screen was introduced for RFL bootup sequence

Sensor Support

• Introduced compatibility with Oceasoft PT100 Smart-Sensor
• Introduced compatibility with Oceasoft Temperature and Humidity Smart-Sensor
• Introduced compatibility with Oceasoft Co2 Triple Smart-Sensor
• Introduced compatibility with Oceasoft Universal Smart-Sensor
• Introduced compatibility with Open/Close Sensors (ROC & RTHMOC)

Bug Fixes and Enhancements

• Resolved an issue where users were unable to create new Reference Lines
• Resolved an issue where Reference Line values remained the same after users changed the logger display unit
• Resolved an issue where timestamps for “Alarm Snoozed” events on the Audit Trail were displaying in ISO 8601 format and UTC time zone instead of the format set for the account
• Resolved an issue where the “Alert Acknowledged” event on the Alert Modal did not display the user who acknowledged it
• Resolved an issue where users were unable to search for data loggers by serial number using the Data Loggers filter under the “More Filters” pane
• Resolved an issue where Alerts (Entire Account) Widgets for Custom Dashboards did not link to the Alerts Overview page
• Resolved an issue where alarm-type events in the Audit Trail did not adhere to the account’s selected decimal separator setting
• Improved validation message in cases where a user attempts to create a PIN that is already in use
• Resolved an issue where a Reason Code is required to add a corrective or preventive action for an alert
• Resolved an issue where Calibration Reports displayed code instead of icons when calibration is up-to-date or overdue
• Optimized loading performance of custom dashboards on the DicksonOne Overview page

Design Updates

• On the Alerts pages, updated the “Only acknowledged alerts?” checkbox under the “More Filters” pane to an “Alert Acknowledgement Status” dropdown, enabling users to filter on unacknowledged alerts
• On the Alerts pages, the Alert “Triggered” timestamp has been moved from the “View More” accordion to the primary Alerts table as the rightmost column for improved visibility of the time an alert occurred

Bug Fixes and Improvements

• Updated the database storage unit for Differential Pressure allowing for greater granularity.
• Resolved a bug where deleted alert notification policies still showed as active. 
• Resolved a bug where TWE/TWP Loggers using Relay Sensors cannot associate the Relay Sensor with alert rules.
• Resolved a bug where Temperature and Humidity Channels were switched. 
• Resolved a bug with creating two “Primary Account” labels when creating new users. 
• Resolved a bug where sensor connections were retired after the DWE logger firmware was updated. 
• Resolved a bug with replacing sensors with different units (Either Fahrenheit or Celsius) on DWE or RFL devices, the units are not converted in the API to match the change. 
• Resolved transmission interval buffer for alerts with Cobalt X and Cobalt XS loggers.

Update to Terms of Use

• Added additional context to the Fee and Payment section of the Terms of Use identifying the liability of fees falls on the subscribing entity rather than the individual accepting the Terms of Use.

Design Updates

• Alerts pages (Overview, Excursions, and Warnings)
  • Combined “Current Alerts” and “Alert History” tables into a single Alerts table that is filtered on only the active alerts by default (removing the filter will display both current and historic alerts)
  • Moved Alert Filter options to a “More Filters” side panel
  • Moved the Acknowledge / Comment function into the new Alert Management Modal
  • Added a “View More/Less” button for each alert item to display/hide additional details of the alert
  • Changed the Alert Severity from a colored indicator to explicitly display the type as an Excursion or Warning
  • Updated the order of columns in the Alerts table
    • From: Alarm Triggered date and time, Promoted to Excursion, Data Logger, Equipment Location, Condition, and Recent Reading
    • To: the Alarm Type, Status, Condition, Duration, Equipment, Data Logger, and Recent Reading
  • Moved the Comment Count, Alarm Triggered date and time, Promoted to Excursion, and Location columns into the “View More” additional details
  • Added a Resolved date and time field for the timestamp that an alert was resolved to the “View More” expanded details

Features

• Alarm and Alert Enhancements
  • Added Snoozing Capability of individual alerts for a user-specified duration, allowing for temporary suspension of SMS, Phone, and Email notifications and escalations
  • Added automatic acknowledgment when snoozing alerts that were previously unacknowledged
  • Added Bulk Snoozing of multiple alerts simultaneously
  • Added Alert Reasons and Corrective/Preventive Actions as optional fields allowing for more detailed tracking of alerts
  • Added a new Alert Management Modal which displays Snooze Functionality, Alert Reason Codes, Corrective/Preventive Action, Acknowledge/Comment alert, and Event Log
  • Added the ability to expand/collapse alert details
• Cobalt X Enhancements (Software Support Only)
  • Battery Level Indicator displays on Location Overview and Data Logger Overview Pages
  • Signal Strength Indicator displays on Location Overview and Data Logger Overview Pages
  • Pin & Reason Codes for authorized users to use when acknowledging alarms on devices

Bugs (Resolved in v2.8.2)

• Resolved an issue where loggers would get stuck in a NTP synchronization loop if they were unable to get a response from an NTP server.

Sensor Support Originally released in v2.8.1, no impact if you already tested and upgraded to that version.

• Adds support for Open/Close sensors.
• Adds support for Oceasoft Triple-CO2 and Universal 4-20mA sensors.
• Fixed an issue where certain replaceable sensors briefly displayed invalid readings when first plugged into Touchscreen loggers.
• Calibration dates read from sensors are understood to be in local time for Chicago, IL (CST or CDT depending on the date), and are converted to UTC when stored internally.
• Calibration dates are transmitted to DicksonOne in UTC.
• Calibration dates are converted from UTC to the logger’s local time when displayed onscreen.

Networking Originally released in v2.8.1, no impact if you already tested and upgraded to that version.

• Adds support for alternate DNS addresses when using Ethernet connections.
• Adds support for Telit wifi modules.
• Fixed an issue where Touchscreen loggers would not request new registration codes from DicksonOne after an initial code had expired.
• Fixed an issue where Touchscreen loggers would become stuck sending DNS queries for up to 20 minutes during data catch-up periods.
• Include blank SSID when communicating on Ethernet

DicksonOne Communication Originally released in v2.8.1, no impact if you already tested and upgraded to that version.

• Adds support for updated DicksonOne API interface. Removes TLS certificates from the old DicksonOne API interface.
• Eliminates insecure HTTP-only communication with DicksonOne. All communication is now encrypted using TLS 1.2.

Bug Fixes and Improvements

• Resolved an issue where DicksonOne accounts could not be created due to reCAPTCHA failing.
• Resolved an issue where scheduled reports were not being generated and sent. 
• Resolved an issue with text displaying within Decimal Separator preference selector.

Bug Fixes and Improvements

• Resolved an issue where Mean Kinetic Temperature was not being calculated for any channels and instead was showing “-“.
• Resolved an issue where Users and Contacts could not be deleted.
• Resolved an issue where Alerts page Date Filter for “Triggered Before” and “Triggered After” could not select correct dates.
• Resolved an issue where no error message appeared to indicate a User or Contact was entered with an email address that is already in use.
• Resolved an issue where TWE relays are not triggering due to API response.
• Resolved an issue where channels were not able to be deleted from existing templates.

Design Updates

• Update to newest versions of core interface dependencies
• Update loading mechanisms for interface behavior scripts

Bug Fixes

• Resolved a bug where screen times out and user is given a 504 error.
• Resolved a bug where differential pressure sensors used with Cobalt X loggers were losing granularity of the data due to the unit that was stored in the database.
• Resolved a bug where error messages were not appearing to the user.
• Resolved a bug where exporting data from Monitoring Points caused an error message regarding creating alarms.
• Resolved a bug where users receive a 500 Error when logging into DicksonOne.
• Resolved a bug where sensor shows on DicksonOne as last reported today, but sensor is not connected to the logger.
• Resolved a bug where Differential Pressure is displayed to the thousandths in Channel and Location view but only to the tenth in equipment view.
• Resolved a bug where unable to delete “primary” label when it is duplicated during the user creation/invite process.

Features

• Added support for broadcasting system-wide messages to users within the DicksonOne interface (e.g. upcoming scheduled maintenance or releases)
• Added additional support for EU rollout
  • Adding support for commas as a decimal separator throughout the DicksonOne interface and generated reports
  • Updated flows for new user registration to support regional compliance requirements

This release marks the initial product release for the RFG-US-003 LoRa Gateway. Functionally, the behavior is identical to the RFG-US-002 but changes to the hardware required a new model number and therefore firmware.