MTConnect.NET 6.9.0

This is the v6.9.0 Release of MTConnect.NET

What's Changed

• SHDR: ensure UTC-safe timestamps via ToUnixUTCTime to fix #113 by @ojusms in #115
• Improve MQTT Relay Module Buffer Path Handling by @virajdere in #114

New Contributors

• @ojusms made their first contribution in #115

Full Changelog: v6.8.0...v6.9.0

MTConnect.NET 6.8.0

• Includes PR #105
• Includes feature request from #106
• Updates MQTTnet to v4.3.7

MTConnect.NET 6.7.0

• Updated for MTConnect v2.5
• Updated to be compatible with .NET 9
• Added ability to output timestamps for a specific Time Zone
• Added better logging for XML format errors
• Updated IronPython to address issue #100
• Merged Pull Request #102
• Merged Pull Request #84

MTConnect.NET 6.6.0

This is the v6.6.0 Release of MTConnect.NET

• Added Error/Exception Handling to Mqtt Entity Server to address Issue #93
• Fixed Issue #91
• Merged Pull Request #90
• Fixed Issue with XML Entity formatter output

Thank you to all the contributors who have created Issues and Pull Requests!

MTConnect.NET 6.5.1

• Fixed issue with adding a Device that already exists in an Agent

MTConnect.NET 6.5.0

• Updated to support the latest MTConnect v2.4
• #73 Added configuration option to omit MQTT CA Validation
• #77 Fixed issue with MQTT Quality of Service configuration
• #78 Fixed issue with SHDR Adapter start/stop
• #79 Fixed issue with closing HTTP requests and streams

Thanks to those that submitted Pull Requests and Issues! Please feel free to submit questions and bring attention to issues as that helps this project grow and makes MTConnect easier to implement.
 
The MTConnect.NET project now has over 500,000 downloads on Nuget! Thank you for all of the support and I hope this project continues to be helpful.

-Patrick

MTConnect.NET 6.4.7

• Fixed issue with Http Client streaming buffer

MTConnect.NET 6.4.6

• Fixed issue with SHDR Ping/Pong Heartbeat referenced in Issue #70
• Added IgnoreHeartbeatOnChange configuration parameter for SHDR Adapters to toggle whether PING data is sent even if data has been received.

MTConnect.NET 6.4.5

Fixed issue with MTConnectHttpClientStream that caused an exception to be thrown when using multiple MTConnectClient connections. Moved the _httpClient variable from being static to be a class member and now requires the MTConnectHttpClientStream class to be disposed.

MTConnect.NET 6.4.4

Fixed issue with HTTP client where some agents don't support a "?from=0" in a sample stream request.