The compatibility between the custo diagnostic client and custo diagnostic server depends on the used API. Not all clients are compatible to all server.
Compatibility matrix custo diagnostic client versus custo diagnostic server:
diag server 5.0 | diag server 5.0.1 | diag server 5.0.2 | diag server 5.0.4 | diag server 5.0.5 | diag server 5.0.6 | diag server 5.1.0 | diag server 5.1.1 | diag server 5.2.0 | |
|---|---|---|---|---|---|---|---|---|---|
diag client 5.0.0 |  | | | | | | | | |
diag client 5.0.1 |  | | | | | | | | |
diag client 5.0.2 | | | | | | | | | |
| diag client 5.0.4 | | | | | | | | | |
| diag client 5.0.5 | | | | | | | | | |
| diag client 5.0.6 | | | | | | | | | |
| diag client 5.0.7 | | | | | | | | | |
| diag client 5.1.0 | | | | | | | | | |
| diag client 5.1.1 | | | | | | | | | |
| diag client 5.2.0 | | | | | | | | | |
Please Note:
custo diagnostic client and custo diagnostic server can also be updated independent from each other. You can find above an overview which client is compatible with which server.
The compatibility defines a best-of order of the update. For example 5.0.7 -> 5.2:
- First update the server -> because the "old" clients also work with the new server
- Then update the clients