Skip to content

Versions & Seeq Compatibility

The connector's version number looks like 100.35.137. This page explains what each part means, because the first number is not what most people assume, and knowing what it does mean makes release notes and support conversations much easier to follow.

Reading the version number

100.35.137
└─┬─┘ └┬┘
  │    └── EEI build number — this connector's own release counter
  └─────── the Seeq Connector SDK line this build was made on

100.35 identifies the Seeq Connector SDK the build was compiled against. Endeavor Engineering builds this connector on Seeq's official Connector SDK, and the connector version carries that SDK's line so anyone holding a bundle can tell what it was built from without looking anything up.

137 is EEI's build number. It increases with every release and is the part that identifies this release on the EEI side. Two builds on the same SDK line differ only in this number.

What the version does not mean

It is not a Seeq Server version. Seeq maintains two separate version lines — one for the Seeq Server platform and one for the Seeq Connector SDK — and this connector's version follows the SDK line, not the platform line. Both lines are Seeq's to manage; they simply count different things. So if you are running Seeq R66-something, that number and the connector's 100.35 are not comparable, and neither one can be derived from the other.

It is not a supported-version range. A connector version tells you what the build was made from, not which Seeq releases it is certified against. For that, see the next section.

The Seeq version a release is validated against

Each release names the Seeq platform API version it was tested against — a number like 66.188.1. That is the one to compare against your Seeq environment, and it appears in the release notes for every release.

EEI states a validated version rather than implying a supported range. Seeq ships continuously, and where Seeq has not defined a supported window, naming the exact version tested is more honest than suggesting compatibility that has not been verified.

Which Seeq agents can run a given release

Building on a newer Connector SDK does not require you to be running that SDK. Every bundle declares, separately from its version number, the oldest Seeq Link agent it supports. Releases on the 100.35 line still support agents from the 100.14 line, because nothing the connector calls changed between them.

These are two different statements, and only the second one constrains your environment:

What it says
100.35 in the version the SDK line the build was compiled on
the supported-agent floor the oldest agent the build is supported on

The floor moves only when the connector genuinely starts depending on something newer, which is a deliberate decision EEI makes and calls out in the release notes — never a side effect of routine SDK currency. If your agent is older than a release's floor, Seeq's agent will decline to load that bundle rather than run it in a degraded state, so EEI confirms your agent version before delivering an update that would move it.

Why the first number changes between releases

Seeq publishes new Connector SDK releases continuously — roughly monthly. EEI tracks them, so adopting a newer SDK moves the connector's version line: 100.14.x becomes 100.35.x. The jump can look large. It reflects how many SDK releases Seeq published in between, not the scale of change in the connector itself.

This is deliberate. Staying close to Seeq's current SDK is how the connector keeps working as Seeq evolves, rather than accumulating a year of drift that has to be paid off all at once. Every SDK release is checked automatically for anything that would affect this connector, and the connector is built and tested against it before EEI adopts it.

What this means for you

Under EEI's managed delivery model, connector updates are EEI's responsibility, not yours:

  • EEI tracks Seeq's releases, assesses each one against this connector, and validates before adopting.
  • Updates are delivered and coordinated with you, so a version-line change is never something you have to interpret or act on unprompted.
  • Item identities are preserved across upgrades, so existing Seeq worksheets, trends, and calculations keep resolving after an update.

If a version number ever looks surprising, this page is the explanation — and your support contact can confirm which Seeq API version any given release was validated against.