Modbus Collector

always check the compatibility matrix below before installing a new version compatibility collectors of all versions >= v1 0 0 are compatible with all factry historian versions >= v4 0 0, in both directions however, for certain functionalities, certain minimum versions of the collector and factry historian are required more information is always available in the release notes feature compatibility matrix this is the compatibility matrix for version listed on this page if you have downloaded a newer version than the one listed on this page please check the release notes of that version feature modbus collector version factry historian version collector auto update >= v1 2 0 >= v6 4 0 windows 7, 8 support <= v1 4 1 v2 3 0 released on 09/09/2026 changes measurements that sit close together in the register map are now collected in a single modbus request instead of one request per measurement a collector with hundreds of measurements can finish its poll cycle within the collection interval, where before the polls piled up and data arrived with old timestamps three advanced collector settings control this maxregistersperrequest (default 125, the modbus maximum), maxregistergap (default 8, how many unused registers may sit between two measurements before they are split into separate requests) and blockreadingenabled (default on) for coils and discrete inputs the two limits count in bits, at 16 bits per register if a device refuses a grouped request, which happens when the request covers an address it does not map, the measurements in that request are read separately instead, so only the measurements the device actually refuses are reported bad the refusal is remembered, so the collector stops paying for a request it already knows will fail, and retried every five minutes in case the device only refused it temporarily a poll no longer starts while the previous one is still running the collector skips the tick and reports it, instead of queueing requests that would report current values under an older timestamp a measurement with a collection interval or offset the collector cannot schedule is now reported as badly configured, where before it was logged and otherwise ignored measurements are no longer polled an extra time at the top of every minute regardless of their collectionoffset staggering measurements with collectionoffset now actually spreads the load, and a measurement with an offset no longer collects an extra sample each minute v2 2 2 released on 13/08/2026 bug fixes fixed the number of measurements reported in the logs on startup, it counted measurements that were deleted in the historian fixed the collector not shutting down stopping the collector waited for the poll loop, but the poll loop only stopped when the scheduler was closed, which happened after that wait the collector never exited on its own and was killed once its termination grace period ran out fixed the collector crashing on startup when the modbus client could not be initialized, for example when no default byte order is set a paused or stopping collector now stops reading the modbus server after the request that is already in progress, instead of working through every remaining measurement and discarding the results fixed points being dropped silently, and the collector hanging, when a poll finished while the collector was shutting down pausing the collector no longer discards the values the poll in progress had already read stopping or pausing the collector now waits for the poll in progress, instead of tearing the connection down underneath it a poll that takes longer than the collection interval no longer has the next poll started alongside it overlapping polls read every register twice and could report a value from the wrong poll fixed the collector leaving the previous poll loop running when it was activated again without being paused first, which also read every register twice v2 2 1 released on 16/07/2026 changes updated the base collector to v4 2 0 v2 2 0 released on 16/06/2026 changes updated to base collector v4 1 2 docid\ djs1gflkyd1m31dxqh5cu bug fixes fixed issues where the modbus connection could fall into a bad state, preventing a faulty connection from restarting v2 1 0 released on 22/01/2026 changes updated to base collector v3 5 2 docid\ djs1gflkyd1m31dxqh5cu v2 0 0 released on 23/05/2025 updated to base collector v3 1 1 docid\ djs1gflkyd1m31dxqh5cu and thus dropped support for windows 7 and 8 v1 4 1 released on 25/04/2025 changes altered a trace log to print the raw bytes received from the device v1 4 0 released on 04/04/2025 changes moved the slaveid from the collector settings to the measurement settings v1 3 4 released on 02/04/2025 bug fixes fixed reconnecting client on windows socket errors v1 3 3 released on 11/03/2025 bug fixes fixed reconnecting client on tcp disconnection v1 3 2 released on 29/01/2025 changes disabled streaming until a data loss fix is implemented updated the base collector to v2 7 3 docid\ djs1gflkyd1m31dxqh5cu v1 3 1 released on 02/01/2025 changes updated base collector to v2 7 1 docid\ djs1gflkyd1m31dxqh5cu v1 3 0 released on 03/10/2024 changes updated base collector to v2 6 0 docid\ djs1gflkyd1m31dxqh5cu v1 2 2 released on 07/06/2024 changes added support for performance monitoring with pyroscope bug fixes restored windows 7 compatibility updated base collector to v2 4 8 docid\ djs1gflkyd1m31dxqh5cu v1 2 1 changes fixed a bug where the collector would not pause a measurement updated base collector to v2 4 3 docid\ djs1gflkyd1m31dxqh5cu v1 2 0 changes added support for auto updating requires historian server >= v6 4 0 updated base collector to v2 4 0 docid\ djs1gflkyd1m31dxqh5cu v1 1 9 changes updated the base collector to v1 2 12 docid\ djs1gflkyd1m31dxqh5cu v1 1 8 changes updated the base collector to v1 2 9 docid\ djs1gflkyd1m31dxqh5cu v1 1 7 changes updated the base collector to v1 2 8 docid\ djs1gflkyd1m31dxqh5cu v1 1 6 bug fixes fixed crash if buffer path could not be opened collector no longer tries to register collector if historian api is unavailable v1 1 0 when updating to this version keep in mind that environment variables that had a different value will need to be set in the historian changes added first version of modbus documentation changed most environment variables to be configured as advanced collector settings in the historian