Sensor Profile Specific Configuration Values Outside of Monnit

Sensor Profile Specific Configuration Values

Each Sensor Profile has unique configuration values and properties. These configurations determine sensor behaviors which often affect the readings presented by the sensor. While MINE and Serial MODBUS Gateways offer the capability of modifying these configurations, Monnit does not explicitly offer the descriptions needed to configure these sensor settings. This is especially true for sensor types with complex configuration profiles such as the Advanced Vibration, CO2, and other sensors.

A note on sensor configurations in MINE

One feature of Mine, is that every sensor type has a defined “SensorEdit” method. The parameters of this method are the same parameters available on the Edit page of that sensor in iMonnit. As As, an example, you can review the Temperature SensorEdit method from MINE at this link.

Of note, these parameters are “Nullable” meaning they also present the option of only passing in the values they want to change. For example if only the Heartbeat configuration is passed through the MINE server to the sensor using the SensorEdit method, the other parameters will retain their existing values; only the heartbeat value will changed. This method also takes care of marking appropriate “dirty” flags for the user.

Guards “should” already be in place inside that method. In general if they can configure the value on the UI of iMonnit, then using the same values as iMonnit when calling the method in Mine will yield the same results.

When this doesn’t apply

As mentioned previously, some sensor profiles are more complex than the above mentioned Temperature sensor. While the raw Sensor object can be modified in MINE to edit these configurations, there are no guards that prevent passing values that can interfere with the sensor behavior. This applies to sensor configuration in both editing the raw Sensor object in MINE and configuring sensors using the Serial MODBUS Gateway. These configurations require internal information in order to be successfully applied to the sensor, and therefore details on these configurations are not made available to the public. Applying incorrect configurations may result in rendering your sensor inoperable.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.