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.

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

Small Bugs

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.

Lt. Commander Lt. Commander
Lt. Commander

Small Bugs

Hi Robert,


The new version seems to work with the PM8's. I only had two to try it on but there was no issue with the alarm portion of the templates.


There are some other issues.


First, I can't edit any properties of devices unless I am displaying them as 'site information', the other display mode the properties context is greyed out.


Second, you can't get into a CM2 meter unless you change the display template to CM2450. Can you make that the default template selected for CM2's? MAY be a JDX issue - when translating from JDX to ION Setup this occurs. If so, it still would be nice to have the default behavior of Setup to be selecting CM2450 as the default.



1 Reply 1
Captain Captain

Re: Small Bugs

Hi Jeff,

Glad to hear that the new version seems to be working for you now.  As for the other two issues, the first is a known restriction that if you are viewing the devices using the "Group" designation, I didn't want to allow you to be able to change the device properties (things like unit ID is needed to be unique in some cases and if a user was just using the Group view, there might be an instance where they are unaware of some type of overlap without being able to identify what other units are on the same daisy chain).

As for the older CM2 devices, ION Setup will typically send out a series of requests to try and identify the device (likely a Modbus Ident one 0x2B and possibly some reading of some other known =S= product ID registers in an attempt to identify the type of device).  I do remember that the older CM2 communicate using SYMAX protocol (and not standard Modbus) and may require that it be connected to an EGX that has been properly configured for the CM2 (so it can do a Modbus TCP <=> Symax conversion) in order for ION Setup to communicate to it (you won't be able to directly communicate to a CM2 without an EGX I believe due to this).  Another possibility is that the older CM2 models are not communicating as I expect and thus ION Setup is unable to identify the device when prompted.