NetBotz external port configuration

DCIM_Support · ‎2020-07-06

This question was originally posted on DCIM Support by Gabor Novak on 2020-01-22

I would like to configure NetBotz570 external sensor ports. The sensors are temperature and humidity sensors.

What is the correct sensor name when I add custom analog sensor to the system?

I would like to add this temperature and humidity data to the DCE virtual sensor option. Where I can get the average of this sensors. There is a predefined sensor, Temperature Detector TS-100 where the sensor is identified like a temperature sensor via the NetBotz systems.

How to configure the system to show a temperature sensor is connected to the 0-5V external port?

DCIM_Support · ‎2020-07-06

This answer was originally posted on DCIM Support by Steven Marchetti on 2020-01-24

Hi,

The proper values for the 0-5v device should show properly in both NetBotz and DCE regardless of what icon is displayed in the UI. There is no way to force the icon to show up as the temperature icon. Yes, they will always show up as the generic blue sensor icon.

As for reports in DCE, I added a 0-5v cable on an appliance:

DCE can see it as the "Temperature (temperature_forum)" sensor:

As with your report, I do not see it available under the temperature report:

The only thing I can suggest is to create a "custom" report in DCE instead of a temperature report to see these values. As you can see here, I am able to filter by the partial word "temp" and I see not only my temperature (temperature_forum) sensor but the other temperature sensors in that group as well:

I can add this as an enhancement request but I can not promise it will make it into the system.

Steve

See Answer In Context

DCIM_Support · ‎2020-07-06

This comment was originally posted on DCIM Support by Gabor Novak on 2020-01-22

If I choose the predefined sensor Temperature Detector TS-100 the NetBotz recognize that is a temperature sensor. You can see the icon before the label text.

When I create a new custom sensor. I set the sensor type to temp or temperature, there is no change. The icon is set to default sensor. (blue icon)

I don’t know what is the proper name for the sensor type to be recognized it as a temperature or humidity sensor.

DCIM_Support · ‎2020-07-06

This comment was originally posted on DCIM Support by spezialist on 2020-01-22

Dear Gabor Novak,

Thank you very much for the explanatory screenshots to your main question:

What is the correct sensor name when I add custom analog sensor to the system?

This is an interesting question and I would also like to hear the =SE= staff answer.

I suspect that's how NetBotz software works with custom analog (0-5V) and custom current (4-20mA) ports. This means, that they will always appear as a blue circle no matter what name you give them.

By the way, what is your version of NetBotz software?

With respect.

DCIM_Support · ‎2020-07-06

This comment was originally posted on DCIM Support by Gabor Novak on 2020-01-23

Dear @spezialist, system and radio engineer

I suspect that's how NetBotz software works with custom analog (0-5V) and custom current (4-20mA) ports. This means, that they will always appear as a blue circle no matter what name you give them.

I don’t think so, because there is the predefined sensor which is called Temperature Detector TS-100 is 0-5V sensor. The screenshot above was made, when I changed the 0-5V sensor form the list.

When we look the DCE system, you can view this kind of “blue icon” as other numeric sensor. You can’t create report for temperature and humidity. Because the systems doesn’t recognize it as temperature and humidity sensor. You can’t create virtual sensor from this “blue icon”, the temperature and humidity doesn’t appears in the DCE system.

For example when I look into the DDF file, there is the same sections.

(num=numeric) for the temperature <type>temp</ temp> etc.

The type of the sensor is telling the systems, which kind of sensor is that.

	       <type>num</type>
			<sensorId>MANUFACTURER_CODE</sensorId>
			<value>
				<getOid>MANUFACTURER_CODE</getOid>
			</value>
			<valueInc>1</valueInc>
			<label>Manufacturer Code</label>
			<sensorSet>Status Information</sensorSet>
		</numSensor>

When we add a new custom sensor, if I’m correct we tell the same information to the netbotz system. The type of the sensor (temp, hum, etc.). The label and the working parameters. (scaling, units)

By the way, what is your version of NetBotz software?

It is the newest, 4.6.4.

Gabor

DCIM_Support · ‎2020-07-06

This comment was originally posted on DCIM Support by spezialist on 2020-01-24

Dear Gabor Novak,

You correctly noticed everything, but DDF-files of the DCE software have nothing to do with this, since you have a NetBotz appliance, and not a NetBotz device - this is an important difference.

Nevertheless, when you select a predefined by developers sensor model from the NetBotz appliance menu, I suspect that the appropriate template for it is selected inside (i.e. hardcoded). When you choose just add custom sensor 0-5V, then an appropriate template is created for it, as for a numerical sensor and no more.

Maybe Steven Marchetti can help us understand this important issue?

With respect.

DCIM_Support · ‎2020-07-06

This answer was originally posted on DCIM Support by Steven Marchetti on 2020-01-24

Hi,

The proper values for the 0-5v device should show properly in both NetBotz and DCE regardless of what icon is displayed in the UI. There is no way to force the icon to show up as the temperature icon. Yes, they will always show up as the generic blue sensor icon.

As for reports in DCE, I added a 0-5v cable on an appliance:

DCE can see it as the "Temperature (temperature_forum)" sensor:

As with your report, I do not see it available under the temperature report:

The only thing I can suggest is to create a "custom" report in DCE instead of a temperature report to see these values. As you can see here, I am able to filter by the partial word "temp" and I see not only my temperature (temperature_forum) sensor but the other temperature sensors in that group as well:

I can add this as an enhancement request but I can not promise it will make it into the system.

Steve

DCIM_Support · ‎2020-07-06

This comment was originally posted on DCIM Support by spezialist on 2020-01-24

Steven Marchetti, very thanks for the detailed explanation on this issue.

DCIM_Support · ‎2020-07-06

This comment was originally posted on DCIM Support by Steven Marchetti on 2020-01-24

Welcome

DCIM_Support · ‎2020-07-06

This comment was originally posted on DCIM Support by Gabor Novak on 2020-01-27

The proper values for the 0-5v device should show properly in both NetBotz and DCE regardless of what icon is displayed in the UI. There is no way to force the icon to show up as the temperature icon. Yes, they will always show up as the generic blue sensor icon.

The icon type is not so important for me, but the meaning is. When I setup a new custom 0-5V sensor, the first field is the type. My guess is that this field is not working properly, it doesn’t recognize the specified sensor.

I mentioned it before the predefined 0-5V sensor (Temperature Detector TS-100) works fine, it’s shows as a temperature sensor. If I use this kind of sensor definition for the 0-5V sensor. The DCE can see the value as a temperature and I can create from this temperature value virtual sensor for the average temperature.

My problem is just that I can’t create virtual sensor for average temperature and humidity.

DCIM_Support · ‎2020-07-06

This comment was originally posted on DCIM Support by Steven Marchetti on 2020-01-28

Sorry, I addressed the image and report mentioned (in reply to spezialist) but missed the virtual sensor aspect of your question. I've specifically noted this aspect of the issue to the enhancement request I created on the initial response. Again, as with the report, you can choose to create a different virtual sensor. In this case, you can add these as "Other Numeric" sensors.

Here, you can see I haven't yet deleted the "temperature_forum" 0-5 volt sensor I created for the initial response and it is available as different type:

I know this is not exactly what you're looking for but if you have multiple sensors of this type, you can still get a virtual sensor for them.

Steve

DCIM_Support · ‎2020-07-06

This comment was originally posted on DCIM Support by Gabor Novak on 2020-01-28

Dear Steven Marchetti

Sorry, I addressed the image and report mentioned in reply to spezialist) but missed the virtual sensor aspect of your question. I've specifically noted this aspect of the issue to the enhancement request I created on the initial response. Again, as with the report, you can choose to create a different virtual sensor. In this case, you can add these as "Other Numeric" sensors.

Thanks, I have missed that option.

Tomorrow I will check it.

DCIM_Support · ‎2020-07-06

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