This article covers what Inconsistent Changes messages you may encounter when publishing your configurations in the Device Manager. We have gathered here examples of where to focus your attention when encountering this message.
Inconsistent Changes occur when there is an overlap with metrics or when the Device Manager is trying to search for a crucial piece needed to publish the setup but is unable to.
The most common Inconsistent Change message occurs when the Metric Key or Measurement Key overlap between two measurements.
Measurement Keys
When you have two different measurements, they must have separate keys. For example, what would cause an error: When you have two different measurements, they must have separate keys. For example, what would cause an error:
- Name: Motor NDE
- Key: example-vibration-key-1
- Name: Motor DE
- Key: example-vibration-key-1
Now we have two different measurements, one for Motor NDE and the other for Motor DE. However, when both of them have the same Measurement Key, we will encounter an error when publishing. If we change the key even slightly, they will not match each other anymore, and the Inconsistent Changes message will not appear:
- Name: Motor NDE
- Key: example-vibration-key-1
- Name: Motor DE
- Key: example-vibration-key-2
This would not cause Inconsistent Change message since the keys are differentiated.
Metric Keys
Metric Keys may cause similar issues. Within the measurements, you have your selection of metrics. All the metrics use a Key just like measurements do. All Keys, just as measurements, need to be separated. Here is an example of what would cause an error:
- Name: 10-1000Hz RMS
- Key: rms
- Name: 2-5000Hz RMS
- Key: rms
As you can see, the key within the 10-1000Hz RMS and 2-5000Hz RMS is exactly alike. Since the Metric Keys need to be different from each other, this would cause an error. The correct form would be, for example:
- Name: 10-1000Hz RMS
- Key: 10-1000hz-rms
- Name: 2-5000Hz RMS
- Key: 2-5000hz-rms
Keep in mind that Metric Keys and Measurement Keys are different in the sense that Metric Keys need to be different between the metrics inside the same Measurement. Even if you would have the same Metric Key in different measurements, this would not cause an Inconsistent Changes message when publishing.
Setup
When encountering Inconsistent Changes, the one leading issue could be related to the Setup on the device.
Examples of what could cause Inconsistent Changes with Setups:
- Have you deleted a Measurement linked to the Setup you are publishing? This would cause an error since the system is looking for Measurement that is not there.
- Have you made changes to the Measurement Keys after making your Setup? For example, let’s say there was a need to change the key for the measurement. You copy the measurement, delete the old one, and then paste the new one for editing. Then, you have changed the key to your new preferred one. Should you try to publish your setup, it will cause Inconsistent Change since the key is not found within your setup. Please remove the old key from the setup and add the new one.
- Have you deleted the setup itself? For example, you have previously published your setup for the device but deleted the setup from the Setup Tab after that. You can still see the name of the setup in the Device Status tab, but trying to publish it again would cause inconsistencies.
These are some of the issues that might cause you to have Inconsistent Change. It is important to be precise with your Keys and Setups when publishing.
Alarms
You might encounter Inconsistent Change when publishing your Alarms. This happens most of the time because Alarm Rule was changed or removed in the Configurations.
Please check that the Alarm Rule is not removed and is in the same Device Level as before. Inconsistent Change will happen if the Alarm tries to search for an Alarm Rule that is not to be found.
These are some of the issues that you might encounter when publishing your setup for terminal. If you run into an issue that is not presented in this article, please contact Distence at support@distence.fi for additional support in these cases.