You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

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.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

  • No labels