Issue
A Niagara R2 / MicroSmart integration is creating IbsMs invalid condition and receive message entries in the Standard Output Window. Here is an example:
***IbsMs receive message: 454130433130464631433543 ***IbsMS invalid condition received: 28
Environment
- Niagara R2
- MicroSmart
Cause
When the points are learned into the UNC station, it is in a specific order and the station records this information for making requests. If that order is changed in the MicroSmart, then the mismatch occurs.
Resolution
The mismatch occurs specifically when a record number is reused (i.e. a point is deleted and a new point created) and the point types are different.
For example, an Analog Output point is deleted and a Start/Stop point is created – with the Start/Stop point being assigned the record number that was previously used by the Analog Output point. The UNC is expecting an analog point for that record number but is getting a response from a different point type.
There are two choices to fix this situation:
- The controller is to be re-learned. Unfortunately, this will result in lost links and the need to go back and re-link all bindings done with this controller's database.
- Re-load the MicroSmart controllers with the original database so that it matches the learned database in the station. To find the offending controller(s), turn on de-bug and see if that will provide pointers to the controller(s) creating the error message.
When done, make sure to turn off de-bug as it will create a large amount of entries in the Standard Output Window.