Does the EGX300 support the BCPME?

[sesa56580_bridg]

Need this for the Tenant Monitoring solution (eSight)

[JamesJeanette]

Hello Harvey.

No, today we support the following BCPM's:

• BCPM-Model A
• BCPM-Model B
• BCPM-Model C

We do not have BCPM-Model E planned for the EGX300 roadmap.  Can you tell me more about the business case for Tenant Bill?  How many BCPM-Model E's do you encounter?

All supported devices: https://powersolutionscommunity.schneider-electric.com/docs/DOC-2443

James

[sesa10844_bridg]

From my brief research, it looks like the BCPME uses the same Modbus map as the BCPMA.  I haven't compared the Modbus maps to verify, but in the marketing literature they're both described as having the 'Advanced' feature set.  If that's the case, and the Modbus maps are identical, is there any reason we wouldn't be able to define the BCPME as a BCPMA in the EGX300 setup?

[JamesJeanette]

Good question.

: Are you familiar with the BCPM E and A comparison?

[sesa77974_bridg]

I agree with about the BCPME register list. It seems to me that setting it up like the BCPMA would work.

Here's a quote from this topic (it's in regards to using the BCPME in PME)...

Hal Etheridge Oct 2, 2014 1:10 PM (in response to William McLemore)

The BCPME is the same as the normal BCPM A,B,C types with the exception that an ethernet gateway is embedded into the physical device.  Thus just use the same BCPM driver as before.

Note that the latest Veris BCPM firmware has been updated to have basic on board logging (a 1 deep data recorder) and per circuit calculations with arbitrary channel to circuit groupings.  An updated BCPM driver is being tested now and should be included in PME 8.0.  The old driver should work fine with the new firmware but you will not have access to all the new per circuit values (only the per channel values available previously).

[Hal_Etheridge · Accepted solution]

I have confirmed with the FW developer at Veris that the E and A types are the same.

In fact, we are actually having a very hard time in the PME driver determining which is which.  The current plan is to not mention the E type and just stay with the A, B, C variants (an E type device would just automatically pick the A feature set in the driver).  I don't think it is currently possible to have an E type that is not an A internally but that is a Veris marketing decision and thus it may change in the future.