> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/deployment/upgrading-connectware/on-kubernetes/to-2-7-0-on-kubernetes.md).

# Upgrading Connectware to 2.7.0 (Kubernetes)

Prepare services with ADS endpoints for Connectware 2.7.0 on Kubernetes. Without ADS endpoints, no extra steps are needed.

Connectware 2.7.0 rebuilds the ADS connector. This guide covers the changes that services with ADS endpoints need when you upgrade. For a complete list of changes, see the [2.7.0 changelog](https://docs.cybus.io/pages/H3QzL8oZfbS5tKrECr7H#connectware-2.7.0).

{% hint style="info" %}

## Only for services with ADS endpoints

This guide applies only if your services have endpoints with `protocol: Ads`. To check, search your service commissioning files for `protocol: Ads`. If you do not use the ADS connector, upgrade as usual. See [Upgrading Connectware (Kubernetes)](https://docs.cybus.io/deployment/upgrading-connectware/on-kubernetes.md).

If you upgrade from a version before Connectware 2.6.0, also check [Connectware Upgrade Paths](https://docs.cybus.io/deployment/upgrading-connectware/upgrade-paths.md) for the steps of the versions in between.
{% endhint %}

## Upgrade to Connectware 2.7.0

Complete the following steps in order.

{% stepper %}
{% step %}

### Remove dataType and readSize from ADS Endpoints

This step applies if your ADS endpoints set `dataType` or `readSize`.

Connectware 2.7.0 takes the data type and size of every ADS value from the symbol table of the PLC, and no longer accepts the `dataType` and `readSize` endpoint properties. Earlier versions ignore both properties, so removing them before the upgrade does not change how your services work.

1. In every service commissioning file with ADS endpoints, remove `dataType` and `readSize` from the `read`, `write`, and `subscribe` sections.
2. Update each affected service with the corrected service commissioning file. See [Updating Services](https://docs.cybus.io/data-flows/services/managing/updating.md).

{% code lineNumbers="true" %}

```yaml
resources:
  counterSubscribe:
    type: Cybus::Endpoint
    properties:
      protocol: Ads
      connection: !ref adsConnection
      subscribe:
        symbolName: MAIN.counter
        interval: 1000
        # dataType: int16LE  <- remove
        # readSize: 2        <- remove
```

{% endcode %}

If you upgrade without removing them, you can no longer enable, disable, or update the affected services. Delete each affected service and install it again from the corrected service commissioning file.
{% endstep %}

{% step %}

### Check the Message Formats of ADS Endpoints

This step applies if mappings, rules, or applications process the messages of your ADS endpoints.

Check your mappings, rules, and applications for the following changes. Update them when you upgrade, because Connectware 2.6 still uses the earlier formats:

* **64-bit integers:** Connectware 2.7.0 publishes `LINT`, `ULINT`, `LWORD`, and `LTIME` values in read responses and subscribe messages as decimal strings, such as `"9007199254740993"`, and accepts a whole number or a decimal string when you write them. If your applications read or write these values as Buffer objects, switch them to decimal strings.
* **Write values:** Connectware 2.7.0 checks every write value against the data type of the symbol and refuses a value that does not fit, instead of converting it. For example, it refuses the string `"false"` for a `BOOL`, the number `1.5` for an `INT`, and a Buffer object for a `BYTE`. See [Write Values](https://docs.cybus.io/connectors/shop-floor-connectors/ads.md#write-values).
* **Read responses:** Read responses keep the structure `{ value, type, symbol }` inside `value`, but a few fields are renamed or removed. In `value.type`, `arrayData` is now `arrayInfos`, and `enumInfo` is now `enumInfos`. In `value.symbol`, `arrayData` is now `arrayInfo`, and `nameLength`, `typeLength`, and `commentLength` are removed. If your mappings read these fields, update them.
  {% endstep %}

{% step %}

### Upgrade Connectware

Follow the instructions in [Upgrading Connectware (Kubernetes)](https://docs.cybus.io/deployment/upgrading-connectware/on-kubernetes.md) to upgrade to Connectware 2.7.0.
{% endstep %}
{% endstepper %}

## Verification

In the Admin UI, check that every service with ADS endpoints is enabled and does not show **Deviated**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cybus.io/deployment/upgrading-connectware/on-kubernetes/to-2-7-0-on-kubernetes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
