Bug in new DDF-file apcsmartups.xml from DCE 7.3.0?

[DCIM_Support]

Hi all!

After the updating DCE to 7.3.0 I found a bug in the DDF-file apcsmartups.xml.

Bug essence: for single-phases APC Smart-UPS (for example, Smart-UPS 1500VA or Smart-UPS RT 3000VA with NMC2 AP9630/AP9631 v6.4.0) two zero sensors are displayed of "Total Output Active Power" and "Total Output Apparent Power" even then, when the considerable power loading is connected to UPS. A problem that in apcsmartups.xml the two OID is specified for single-phase APC Smart-UPS:

.1.3.6.1.4.1.318.1.1.1.4.2.8.0 - Total Output Active Power
.1.3.6.1.4.1.318.1.1.1.4.2.9.0 - Total Output Apparent Power

And these values for single-phase APC Smart-UPS are always equal to zero. In prior version of DCE 7.2.7 of this bug wasn't and zero values above the specified OID simply were suppressed in case of display in DCE.

Conclusion:

-- or it is necessary to correct in apcsmartups.xml, that above the specified zero OID again were suppressed,

-- or it is necessary to add operations of arithmetical computation of two above the specified sensors, proceeding from OID of output voltage and an output current for single-phase APC Smart-UPS.

Very thanks for the support.

(CID:105461079)

[DCIM_Support · Accepted solution]

apcsmartups.xml

Hi Spezialist,

What version of the Smart-UPS DDF do you have on the current system. I believe the one that came with 7.3 (which was pulled by the way) did have a few issues. If you have the 7.3 version of the DDF which I believe was 57, I have attached version 59 which you should be able to upload to the server. Newer versions should also be available on upcoming releases of DCE which the replacement for 7.3 should be upcoming soon. Let me know how this works for you. 

I believe the DDF does not show or hide a value based on the UPS model, I believe it is looking for a -1 output which should tell the DDF that it is not supported.  If you're still seeing the issue with version 59 of the DDF, I'll see if I can replicate the issue. It appears that you're up to date on the fw on the UPS as well. Have you tested / verified that the NMC's firmware upgrade did not effect this value as well?

Steve

(CID:105461104)

[DCIM_Support]

Hi Steven,

Yes, everything is right: on the current DCE 7.3.0 system I have apcsmartups.xml version 57. And how it is possible to download the new version of this DDF-file?

I carried out check, using the Smart-UPS RT 3000 XL (SURTD3000XLI) with NMC2 AP9630 (v6.4.0). And I can confirm, that above the described bug appeared right after migration on DCE 7.3.0 and still before I executed updating firmware of NMC2 AP9630 to the v6.4.0. I.e., it is possible to tell authentically, that the bug doesn't depend on firmware NMC2.

Very thanks for the support.

(CID:105461182)

[DCIM_Support]

Hi spezialist, The file was attached at the beginning of my last response. There's a link at the top of it. Were you not able to download it? If you can download it, please let me know if it works for you. Steve

(CID:105461281)

[DCIM_Support]

Hi,

Not sure why you can't see the link...I have it:

Either way, I was told you called in and I provided it to the folks in Europe that are assisting you.

Steve

(CID:105461362)

[DCIM_Support]

Hi Steve, It might be due to website itself that certain files may not be shared with everyone. I will shortly post it by direct email (to spezialist ) Kind regards

(CID:105461321)

[DCIM_Support]

Steven, Here is how it is displayed at me:

Bug_in_DCIMSupport.png

(CID:105461366)

[DCIM_Support]

Steven,

The new DDF-file apcsmartups.xml version 59 already separately sent me by email and I could test it: everything is normal, two above stated sensors with zero values now are Disabled and they can be simply removed.

Very thanks for the support.

(CID:105461358)

[DCIM_Support]

Yea, that's what support mentioned to me. I sent them the file and they should have in turn sent it to you. Let me know if it works. Steve

(CID:105461364)

[DCIM_Support]

Thanks for the update!

(CID:105461357)

[DCIM_Support]

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