Ignition 8.x Compatible Release Notes

• Sign up for Software Release Notifications

Cirrus Link recommends our Customers always thoroughly test new module versions in a test environment before releasing to production.

• Color Code: Bug Fix, Feature/Enhancement, Optimization
  
  

Cirrus Link Modules for Ignition v4.0.1 - June 19, 2019

• AWS Injector

  • Fixed support for auto-detected Edge Nodes in tag trees
    

  • Various tag path handling fixes
    

  • Various UDT fixes
    

  • Improvements to handling of null values
    

  • Added Agent record validation in Web UI configuration
    

• Azure Injector

  • Fixed support for auto-detected Edge Nodes in tag trees
    

  • Various tag path handling fixes
    

  • Various UDT fixes
    

  • Improvements to handling of null values
    

  • Added Agent record validation in Web UI configuration
    

  • Fixed publishing of NBIRTH messages for Event Hubs
    

• Google Cloud Injector

  • Fixed support for auto-detected Edge Nodes in tag trees
    

  • Various tag path handling fixes
    

  • Various UDT fixes
    

  • Improvements to handling of null values
    

  • Added Agent record validation in Web UI configuration
    

• IBM Cloud Injector

  • Fixed support for auto-detected Edge Nodes in tag trees
    

  • Various tag path handling fixes
    

  • Various UDT fixes
    

  • Improvements to handling of null values
    

  • Added Agent record validation in Web UI configuration
    

• MQTT Distributor
  • None
• MQTT Engine
  • Fixed online status info tags to denote the proper values
    
  • Added support for Ignition7/Transmission to publish to Ignition8/Engine with quality code translations
    
  • Fixed multiple tag write issues
    
  • Various tag path handling fixes
    
  • Fixed issues with property merging in MQTT Engine
    
  • Various UDT fixes
    
  • Fixed typing of JSON tags in custom namespaces
    
• MQTT Transmission
  • Improved Transmitter field validation in the Web UI configuration
    
  • Added support for multiple tag paths in a single Transmitter configuration
    
  • Added support for additional topic tokens to be published via special char sequence in a Sparkplug Device folder
    
  • Fixed multiple tag write issues
    
  • Fixed support for auto-detected Edge Nodes in tag trees
    
  • Fixed issue that could result in Transmitter Threads running after Transmission shutdown
  • Various tag path handling fixes
    
  • Various UDT fixes
    
  • Improvements to handling of null values
    
  • Fixed connected Server URL info tag handling
    
  • Added sorting of UDT definitions to ensure proper order for creation of UDTs
    
  • Added batching and caching components to improve performance
    
  • Fixed alias support
    
  • Improvements to Disk-backed history stores
    
• Opto22 groov EPIC and SNAPPAC Driver
  • None
    
    

Cirrus Link Modules for Ignition v4.0.0 - May 13, 2019

• AWS Injector
  • Initial port to Ignition8
    
• Azure Injector
  • Initial port to Ignition8
    
• Google Cloud Injector
  • Initial port to Ignition8
• IBM Cloud Injector
  • Initial port to Ignition8
• MQTT Distributor
  • Initial port to Ignition8
• MQTT Engine
  • Initial port to Ignition8
  • Known issues
    • Throughput is not as good as it was in Ignition 7 compatible modules
• MQTT Transmission
  • Initial port to Ignition8
  • Removed default transmitter and now seed a default transmitter with the same functionality as the old default transmitter
  • Added support for multiple tag paths to a single transmitter
  • Added custom property to 'exclude tags' from payloads
  • Added custom property to specify which tags changes events will be stored in store and forward cache
  • Known issues
    • Throughput is not as good as it was in Ignition 7 compatible modules
• Opto22 groov EPIC and SNAPPAC Driver
  • Initial port to Ignition8

  • Improved tag writing throughput working with massive tag lists and during episodes of congested writes

  • An initially scanned floating point value of Not-A-Number (NaN) is better handled

  • Scanner waits for acceptance of tags before publishing data

  • Duplicate tag definitions are prevented

  • In extreme cases, 32- and 64-bit integer values may have erratically updated