Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84398members
353586posts

EGX300 4.370 & PM5341 v01.20 problem

Metering & Power Quality

Collaborate with multiple experts and discuss various topics about Power Meters and Power Quality. From design & implementation to troubleshooting and more, get support from experts and share your experiences by subscribing to the Schneider Electric Exchange forum today.

Philippe_Morel
Commander Commander
Commander
0 Likes
9
564

EGX300 4.370 & PM5341 v01.20 problem

Hi,

I can't add the PM5341 to the EGX300.

The PM5341 has only an Ethernet port for communication. (IP 10.10.10.206)

My StruxureWare Power Monitor 7.2.2, ION Setup and PMC Modbus do work with the PM5341.

For ION Setup and PMC Modbus I need to fill in Modbus address 255.

But the EGX300 does not accept Modbus address 255 as remote ID.

It changes automatically to 1 after I hit the apply button.

Is this a firmware problem?

Best regards,

Philippe

Tags (2)
9 Replies 9
Hal_Etheridge
Janeway Janeway
Janeway
0 Likes
4
473

Re: EGX300 4.370 & PM5341 v01.20 problem

Unit id 255 is the broadcast address so technically it will not work though a gateway.  When communicating directly to a device with an on-board ethernet card this is not a problem.  When going through a gateway this is not a valid unit id anymore.

Find out what the device's unit id is on the serial connection and use that in both the gateway and PME and things should start working.

Philippe_Morel
Commander Commander
Commander
0 Likes
3
473

Re: EGX300 4.370 & PM5341 v01.20 problem

Hi Hal,

Using unit ID 255 in PME, ION Setup and PMC Modbus is working great.

Because we don't use the EGX here.

I just want to add the PM5341 to the EGX300 for real-time measurements and logging.

Both the PM5341 and the EGX300 are connected to the same Ethernet network (= Switch).

4425

Hal_Etheridge
Janeway Janeway
Janeway
0 Likes
2
473

Re: EGX300 4.370 & PM5341 v01.20 problem

The device must have an unit id on the serial loop.  Find that value (probably through the front panel) and use that value in the EGX and PME and it should work fine.

If this is the only device on the serial loop (effectively this is the same as a direct TCP connection) then 255 should work (ignoring the EGX restriction) as that is the broadcast address so there is no worry about collisions on the serial bus.  With multiple devices then using the proper unit id values is required because there is no other way to select which device you are communicating with otherwise.

Philippe_Morel
Commander Commander
Commander
0 Likes
1
473

Re: EGX300 4.370 & PM5341 v01.20 problem

The meter PM5341 does not have an RS485 connection, only an Ethernet port. (So it is always the only device on the "serial loop".)

On the front panel I can't find the unit ID.

When I read the register 6501 I do get the unit ID 1, but that does not work in the EGX300. (and also not in PME, ION Setup,...)

Unit ID 255 works in every software except in the EGX300 because I can't fill it in.

If I fill in for example Unit ID 300 then I get the message on the screenshot.

4439

I think this is a bug in the EGX300. So can someone check it? Thanks!

JeroenDeville
Lt. Commander Lt. Commander
Lt. Commander
0 Likes
0
473

Re: EGX300 4.370 & PM5341 v01.20 problem

I've a customer with the same problem?

Suggestions?

Daniel_Brandao
Lt. Commander Lt. Commander
Lt. Commander
0 Likes
3
473

Re: EGX300 4.370 & PM5341 v01.20 problem

Hi guys,

The EGX team just told me the issue will be fixed on the next EGX firmware release in November 2015. The EGX will accept 255 as remote address.

Daniel.

JeroenDeville
Lt. Commander Lt. Commander
Lt. Commander
0 Likes
2
473

Re: EGX300 4.370 & PM5341 v01.20 problem

I hope you mean November 2014


Daniel_Brandao
Lt. Commander Lt. Commander
Lt. Commander
0 Likes
1
473

Re: EGX300 4.370 & PM5341 v01.20 problem

Yes, November 2014!

JeroenDeville
Lt. Commander Lt. Commander
Lt. Commander
0 Likes
0
473

Re: EGX300 4.370 & PM5341 v01.20 problem

Thanks