The compatibility between the custo diagnostic server client and custo diagnostic client server depends on the used API. Not all clients are compatible to the all server.
Compatibility matrix custo diagnostic server client versus custo diagnostic clientserver:
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.
Compatibility The compatibility defines a best-of order of updates. Example in this case (the update. For example 5.0.7 -> 5.0.1)2:
- first First update the server -> because the "old" clients also work with the new server
- then Then update the clients