Temperature parameters changed by software...

[DCIM_Support]

Is it possible for the software to change the lower or high temperature alarm parameters, say for example the temp (ex. 30 F Min) at which the system alerts the user? I am experiencing an issue where alarms for the temperature control systems related to the netbotz 570 are disappearing or  parameters changing. Is it possible for it to change or is that only done by user input?

TY

Juan

(CID:103586573)

[DCIM_Support]

Hi Juan,

A NetBotz with current or near current firmware should not change parameters all by itself. Are thresholds being changed or are they being deleted entirely? Have you changed the threshold and logged out and back in again to verify the configuration actually stuck?

You noted that the alarms are for a temperature control system related to a NetBotz 570. How exactly is this set up? Is the 570 monitoring this system or visa versa? How are they communicating? What firmware is the 570 running? Do the 2 systems communicate consistently or are there connection errors?

Steve

(CID:104173572)

[DCIM_Support]

We have sensor pods (150) connected to the Netbotz. the Netbotz takes the info from the sensors and displays it through DCE, which we use also to make changes to temp alarms and such. 

App version on netbotz is V4_5_0_20150518_1808, on the sensor pods 0.6.9

(CID:104173601)

[DCIM_Support]

Hi Juan, So I guess I'm missing something then. Are you creating thresholds on the NetBotz 570 and they are disappearing? Are you editing current thresholds and they're reverting back? How are you creating / editing them? I'd be more than happy to try and replicate this but I need to know exactly what you're doing and how it is being done. If you are using DCE, I would suggest testing directly to the NetBotz device. What version of DCE? Steve

(CID:104173603)

[DCIM_Support]

The temp control alarms were created on the netbotz. We had an issue of sensors reporting minimum temp alarms when the reported temperature of the sensor was not low enough to warrant such report. After changes were made, the alarms reverted to their old settings after a few days. And we started to get alarms for sensors when the minimum temp reported by the sensor was NOT below the threshold. We have since revisited the alarm thresholds and made sure that they are correct, I have not had an issue since. I was curious to know if this was an ongoing issue with sensors reporting minimum or max temp threshold alarm when the temperature did not warrant such a report.

(CID:104173604)

[DCIM_Support]

Hi Juan,

Sounds like 2 different issues.

There is an issue that should be fixed in the next NetBotz release where strange values are seen from sensors. It may be 1,000,000 degrees or it may appear to be something within range but somehow the logic simply sees it as being outside of the normal values. That release should resolve the issue with the device alerting when it appears to be in range. Some times editing the thresholds or creating new ones seems to correct this issue.

I have not seen issues with the thresholds reverting to old values unless you create a threshold using DCE then potentially re-edit that same threshold using NetBotz Advanced View. I have seen strange issues when you try to use both but not specifically what you're seeing.

Steve

(CID:104173610)

[DCIM_Support]

That is exactly what is (or was) happening with the sensor, we were getting an alarm for MIN TEMP when the temp was inside the range. As for the second issue, I will make sure to look into that so that we are not editing in two diff. applications and thus causing issues When do you expect the next release for the Netbotz? Anything that can be done in the mean time? Juan

(CID:104173611)

[DCIM_Support]

Hi Juan, I have no really good ETA. Should be by the end of the year but I can't get more specific than that. Steve

(CID:104173613)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.