-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mid0076 (Alarm status) always creates revision 3 #79
Comments
// Example:
// this creates an illegal command (should be rev1, but is rev3 with missing ToolHealth data):
mid = new Mid0076(alarmStatus, errorString, controllerReady, toolReady, alarmTime); // this works
mid = new Mid0076(1)
{
AlarmStatus = alarmStatus,
ErrorCode = errorString,
ControllerReadyStatus = controllerReady,
ToolReadyStatus = toolReady,
Time = alarmTime
}; |
And if you add revision 3 to Mid0070, Mid0071 has to be updated with revision 3 as well. |
Hello @IngeRuppio, thanks again for providing another issue. Since there is a way to make it work, I will be fixing this issue in the next project which is to implement new updates from Otherwise, if it's causing a big impact into applications, I might fix it before the project. Is it a huge problem for you to wait until the next project update is done? |
It is a big issue here, because two large companies are affected and the workflow is blocked. |
Hello Inge, Had to fix another issues that had no workaround and already implemented the necessary fix to Mid0076. Version |
If a
Mid0076
is created using a revision 1/2/3 constructor, it always is revision 3, because there are no revision arguments in the constructors. Therefore always LAST_REVISION, which is 3, is used.By the way, revision 3 cannot be used, because
Mid0070
(Alarm subscribe) only supports revision 2.The text was updated successfully, but these errors were encountered: