Skip to content

Releases: mtconnect/cppagent

Version 2.5.0.0 Release Candidate 4

13 May 23:29
2b5a5e8
Compare
Choose a tag to compare
Pre-release

Merges change from 2.3.0.9

Version 2.3.0.9

13 May 22:05
7e59720
Compare
Choose a tag to compare

Tjisi is a bug fix release and addresses the following issues:

  • The MQTT2 Sink now includes the MTConnectAssets and Header when publishing assets
  • The MTCpmmect REST API correctly honors pretty parameter when publishing assets.
  • MQTT2 Sink now publishes an empty Sample topic before data has come in to have the topic present for subscription.

Version 2.5.0.0 Release Candidate 2

03 May 17:31
eb94b8f
Compare
Choose a tag to compare
Pre-release
  • Added websockets interface
  • Removed legacy mqtt sink

For websockets you need to connect to the server and then send requests:

{
  "id": "ABC",
  "request": "probe"
}

The id and request are required.

I have added a few other properties to support the response document,format and pretty. format can have a value of xml or json. The default format is xml.

{
  "id": "ABC",
  "request": "probe",
  "format": "json"
}

All the properties except request and id are the same as the properties you get from the swagger interface. Make a request to /swagger from the agent to find all the possible properties.

   http://localhost:5000/swagger

When an interval is given for sample or current, they will publish. A request of cancel will stop a request.

Some examples:

{"id": 1,"request": "probe", "format": "json"}
{"id": 2,"request": "current"}
{"id": 3, "request": "sample", "interval": 1000, "format": "json"}
{"id": 4, "request": "current", "interval": 5000 }
{"id": 3, "request": "cancel"}

There is no additional protocol level header. The results are chunked per the websockets spec as individual messages.

Version 2.3.0.8

29 Apr 02:20
00e0d1c
Compare
Choose a tag to compare

Added support for initial value that sets the data item's observation whenever the device becomes available.

Version 2.3.0.7

15 Apr 14:48
fb69dca
Compare
Choose a tag to compare

What's Changed

  • Fixed port in url for MQTT service.

Version 2.5.0.0 Release Candidate 1

15 Apr 14:51
053cf42
Compare
Choose a tag to compare
Pre-release

What's Changed

  • Preview of 2.5 validation of observation controlled vocabulary.
  • Use the Validation = true configuration
  • Check quality attribute in the observations

See issue: MTConnect Projects Issue 3159

Version v2.3.0.6

11 Apr 21:50
e6f9692
Compare
Choose a tag to compare

Bugs fixed in this release

  • Fixed issues with respect to changing UUIDs

Version 2.3.0.4

20 Mar 23:08
Compare
Choose a tag to compare

Overview

This release is mainly a bug fix release related to some behavior associated with changing uuids, dynamic updates to the device model. One other change is reducing the log level for the file search so the logs are not so noisy on startup.

What's Changed

  • Fixed * uuid command handling in agent not as expected by @wsobel in #426
  • Reduced log level for config file search to debug. Issue #417 by @wsobel in #427
  • Issue-423: Crash when editing DataItem in Devices.xml file by @mnoomnoo in #424

Full Changelog: v2.3.0.3...v2.3.0.4

Version 2.3.0.3

10 Mar 20:46
4bf3d6d
Compare
Choose a tag to compare

What's Changed

  • README.md update by @dwickelhaus in #416
    • Added deviceModel and uuid documentation for SHDR protocol.
  • Fix for issue 420 by @mnoomnoo in #421
    • AgentConfiguration::monitorThread message reports wrong number of seconds
  • Added websockets support to MQTT Adapter by @wsobel in #422
    • Websockets support added to common MQTT client. May add to MQTT sink as well.
    • Configure using MqttWs = true in agent.cfg for the MQTT adapter.

New Contributors

Full Changelog: v2.3.0.2...v2.3.0.3

Version 2.3.0.2

20 Feb 02:02
569753a
Compare
Choose a tag to compare

Changes

Minor release that changes . to _ in the agent device topic to support ignition.