The Compatibility between the custo diagnostic server and custo diagnostic client depends on the users API. Not all Clients are compatible to the Server.
Compatibility matrix custo diagnostic server versus custo diagnostic client:
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 client 5.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.1.0 | | | | | | | |
Hint:
custo diagnostic client and custo diagnostic server can also be updated independent from each other. You can find an overview here as to which client is compatible with which server.
Compatibility defines a best-of order of updates. Example in this case (5.0 -> 5.0.1):
- first the server -> because the "old" clients also work with the new server
- then the clients