Releases: mtconnect/cppagent
Releases · mtconnect/cppagent
Version v2.3.0.6
Bugs fixed in this release
- Fixed issues with respect to changing UUIDs
Version 2.3.0.4
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
inDevices.xml
file by @mnoomnoo in #424
Full Changelog: v2.3.0.3...v2.3.0.4
Version 2.3.0.3
What's Changed
- README.md update by @dwickelhaus in #416
- Added
deviceModel
anduuid
documentation for SHDR protocol.
- Added
- 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
Changes
Minor release that changes .
to _
in the agent device topic to support ignition.
Version 2.3.0.1
New Features
- Version 2.3 new condition Id for Condition observations and associated activations
- Added Sender configuration setting
Sender = ...
to override header - README updates for MQTT, SHDR, and other fixes
- Added 2.3 schema files
Contributors:
Version 2.2.0.17
Summary
2.2.0.17 is mainly a bug fix release, along with updating urns in stylesheets to match the schema version.
What's Changed
- JSON Parser error handling and randomizing MQTT client id as a solution before connections pooling by @wsobel in #372
- MQTT last will topic and payload by @wsobel in #374
- chore: add
styles/old
to.dockerignore
by @ottobolyos in #376 - Resolve undefined boost::log symbol using ExtractTimestamp transform by @simonyg in #391
- Empty
CDATA
xml generation fix by @wsobel in #401 - stylesheet schema version updated to 2.2 by @robot-ranger in #403
- Should set device UUID when specified in adapter config by @wsobel in #405
- Update schema version in stylesheets by @wsobel in #407
Version v2.2.0.16
What's Changed
- MQTT adapter docs and example by @robot-ranger
- MQTT random client so each broker connection has a unique identifier
MqttClientId
can still be specified.
- MQTT Last Will and Testament added with configuration topic:
MqttLastWillTopic
- Default topic is: MTConnect/Probe/Agent.{UUID}/Availability
- Value will change from
AVAILABLE
toUNAVAILABLE
when agent disconnects from broker.
Version v2.2.0.15
Added support for MQTT JSON payloads.
Full documentation will be provided, this is just a brief overview.
The following formats are supported:
Simple observations
{
"timestamp": "2023-11-09T11:20:00Z",
"a": "ACTIVE",
"b": 123.456
}
Conditions and messages
{
"timestamp": "2023-11-09T11:20:00Z",
"a": {
"level": "fault",
"nativeCode": "BAD!!!!",
"nativeSeverity": 1000,
"qualifier": "HIGH",
"value": "high temperature fault"
},
"b": {
"nativeCode": "ABC",
"value": "some text"
}
}
Arrays of observations with different timestamps
[{
"timestamp": "2023-11-09T11:20:00Z",
"a": "ACTIVE",
"b": 100.0
},
{
"timestamp": "2023-11-09T11:21:00Z",
"a": "READY",
"b": 101.0
}]
Specifying device names or uuid:
{
"device1": {
"timestamp": "2023-11-09T11:20:00Z",
"e": "ACTIVE",
"p": 100.0
},
"device2": {
"timestamp": "2023-11-09T11:21:00Z",
"e": "READY",
"p": 101.0
}
}
Timeseries
{
"timestamp": "2023-11-09T11:20:00Z",
"a": {
"sampleRate": 8000,
"value": [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]
}
}
Data sets and tables
[{
"timestamp": "2023-11-09T11:20:00Z",
"a": {
"r1": {
"k1": 123.45
},
"r2": {
"k2": "ABCDEF",
"k3": 6789
}
}
},
{
"timestamp": "2023-11-09T11:20:00Z",
"a": {
"resetTriggered": "NEW",
"value": {
"r1": {
"k1": 123.45,
"k3": 6789
},
"r2": null
}
}
}]
Version v2.2.0.14
Patch Release
- Fixed connection status: Changed from from LISTENING to LISTEN
- Added support for NaN and Infinity in JSON
- NaN is represented as the string "NaN"
- Infinity and -Infinity are represented as the strings "Infinity" and "-Infinity" respectively.
Version v2.2.0.13
Patch Release
- Fixed dll copy on windows for shared on some build system
- Optimized streaming performance
- Added better logging and script feedback for embedded mruby