NetBotz 250 Temperature sensor resolution

[DCIM_Support]

The Netbotz 250 system measures just whole degrees. Other NetBotz system can measure with higher resolution.

For example:

Netbotz 570 temperature reading is 21,6 degree.

NetBotz 250 temperature reading is just 21 degree.

We have installed a new Netbotz system to an old system, where the measured temperature data has more detail. And when the customer creates a new report, where the old and new system data are available, it is a bit confusing that the scale are different.

Can I set the NetBotz 250 system to measure with more detail?

(CID:124523569)

[DCIM_Support · Accepted solution]

Hi Gabor,

The next firmware release for the NB250 will address this issue and will display temperature precision to the tenths place. This firmware release is due out in the next few months.

-Scott

(CID:124523693)

[DCIM_Support]

I have tested the new firmware (6.5.0), and now the temperature resolution is correct, and working well.

Regards, Gabor

(CID:127535057)

[DCIM_Support]

Dear Gabor Novak,

Many thanks for the feedback 😀.

(CID:127535076)

[DCIM_Support]

HI,

The NetBotz sensor reading is correct, but I have find another problem. The NetBotz system on the device show the correct value, but when I generate a report in the DCE (7.2.6) than the readings are not in the correct format. For example I attach a few screenshots. The DCE show on the line chart just the whole temperature readings (23.0;24.0;25.0; etc. ), It’s the same when I open sensor readings(DCE) But when I open the desktop view in a web browser , there are the readings displayed well. So the question is where is the problem?

Regards, Gabor

(CID:128059716)

[DCIM_Support]

Dear Gabor Novak,

Thanks for the good screenshots: what version of the DDF-file for NetBotz-250 you use in DCE-7.2.6?

I have the current version v.17, I was able to analyze it and I want to ask you to make a snmpwalk file according to How to create a SNMP walk file for Struxureware Expert/InfraStruXure Central. This will help to understand where the cause of the problem is: in the DDF-file or in the new firmware of the device.

With respect.

(CID:128060192)

[DCIM_Support]

Hi,

The DDF version is “v16”. Tomorrow I will run the snmp_walk, and send you the generated file. I have requested a new DDF. If it’s newer I will test it.

Regrads, Gabor

(CID:128060325)

[DCIM_Support]

I have tested the new DDF (V17) and now the mentioned problem is solved. 😀

(CID:128060659)

[DCIM_Support]

Dear Gabor Novak,

Many thanks for the feedback 😀.

(CID:128060662)

[DCIM_Support]

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