Skip to content

Releases: mtconnect/cppagent

Version v2.3.0.14

19 Jun 23:04
43331b2
Compare
Choose a tag to compare

Bug fix release

  • Fixed issues with MQTT disconnect and options passing to the pipeline
  • Fixed MQTT Host and Port in the URL

Version 2.3.0.11

14 Jun 17:06
cd82ee3
Compare
Choose a tag to compare

Bug fix release

  • Fixed bug where observations were not set to unavailable when MQTT Source would disconnect from broker
  • Fixed bug with topics being incorrectly set when parsing the path

Version 2.3.0.10

05 Jun 10:05
b903f15
Compare
Choose a tag to compare

This is a bug fix release.

  • Fixes some unhandled exceptions relation to numeric conversions in the pipeline.
  • Fixes Windows Services with a configuration file other than agent.cfg

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:https://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