FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We have started the migration process.
This community is now in READ ONLY mode.
Read more: Important
information on the platform change.
05-14-2024 04:40 PM - last edited on 06-13-2024 02:33 PM by CodeShepherd
All devices which have been manufactured and shipped with release 1.20.7 or higher, are equipped with a device certificate which represents the "ctrlX Device ID". For Bosch Rexroth devices (e.g. ctrlX CORE X3), the serial number (S/N) is still used for licensing; however, for partner devices the "ctrlX Device ID" will be used. To make this possible, starting with release 1.20.7 or higher a fallback mechanism was introduced that allows Bosch Rexroth devices to further rely on the S/N for licensing and in parallel to use the "ctrlX Device ID" on other devices. Error "Bad request (400) - Host ID error - response does not match system hostid - 080E0200 - 0C7A0202" will be shown.
When downgrading a device that was shipped with Release 1.20.7 or higher to a previous version that does contain Device Admin XCR-V-0120.6 or lower (e.g. by using a Setup file) the licenses that were issued for the device's serial number are not recognized anymore. Instead the device will expect the license to be issued for the "ctrlX Device ID" and previously working license files issued for the device's S/N will not be accepted anymore, leading to the error "Host id mismatch detected. Please compare the host id inside the capability response file with the target host id."
⚠️Please note that licensing dongles are not affected by this issue!
The easiest method is to simply update the Device Admin to version XCR-V-0120.7 or higher.
As an alternative to creating a new backup, you may manually update an existing Setup.
The following screenshot shows an example.
Solved! Go to Solution.
09-06-2024 07:38 AM - edited 09-06-2024 07:41 AM
The easiest method is to simply update the Device Admin to version XCR-V-0120.7 or higher.
As an alternative to creating a new backup, you may manually update an existing Setup.
The following screenshot shows an example: