Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!

Using multiple PM5320 devices via Modbus TCP – how to distinguish between devices?

Metering & Power Quality

Schneider Electric support forum about Power Meters (ION, PowerTag, PowerLogic) and Power Quality from design, implementation to troubleshooting and more.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • EcoStruxure Power & Grid
  • Metering & Power Quality
  • Using multiple PM5320 devices via Modbus TCP – how to distinguish between devices?
Options
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Experts
User Count
Charles_Murison
Picard Charles_Murison Picard
498
Ramasamy_N
Captain Ramasamy_N Captain
115
Mehran_Mehrnia
Captain Mehran_Mehrnia Captain
98
Robert_Lee
Admiral Robert_Lee Admiral
92
View All

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Solved Go to Solution
Back to Metering & Power Quality
Solved
Phil_38552
Phil_38552
Cadet

Posted: ‎2025-06-04 01:29 AM

0 Likes
2
240
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2025-06-04 01:29 AM

Using multiple PM5320 devices via Modbus TCP – how to distinguish between devices?

Hello,

I am currently testing a PowerLogic PM5320 device, which is directly connected to my PC via Ethernet. Using a Modbus test tool (Baseblock ComTest Pro), I’m able to successfully read data from the holding registers via Modbus TCP.

In the final application, however, multiple PM5320 devices will be used in the same network. A Modbus TCP client (Anybus Communicator – Modbus TCP Client to PROFINET IO Device) will be responsible for cyclically reading data from all connected PM5320 devices.

My key question is:

👉 How can the Modbus TCP client distinguish between the individual PM5320 devices in the network?
As far as I understand:

  • The Unit ID for Modbus TCP is fixed to 255 and

  • It cannot be changed via the front panel or ION Setup.

I couldn’t find any reference in the manuals indicating that the Unit ID can be configured for Modbus TCP operation.
Does this mean that the only way to distinguish between multiple devices is by assigning unique IP addresses to each PM5320?

Or is there any method to configure a different Unit ID per device, to allow multiple devices to be queried from the same client?

I would appreciate any official guidance or recommendations, as this question is crucial for planning the communication setup in our project.

Best regards Phil

Labels
  • Labels:
  • ION Setup
  • PM5000
  • PowerTag Energy
Tags (1)
  • Tags:
  • english
Reply
  • All forum topics
  • Previous Topic
  • Next Topic

Accepted Solutions
akash_das
Ensign akash_das Ensign
Ensign

Posted: ‎2025-06-04 03:17 AM

0 Likes
1
230
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2025-06-04 03:17 AM

Hi@Phil_38552 If you're trying to identify multiple PM5320 meters on a network, using their IP addresses is the standard method. Any Modbus TCP client can poll each meter using its unique IP. The Unit ID remains 255 for all, but it doesn’t matter because the IP is different. This is the recommended and simplest solution.

See Answer In Context

Reply
Replies 2
akash_das
Ensign akash_das Ensign
Ensign

Posted: ‎2025-06-04 03:17 AM

0 Likes
1
231
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2025-06-04 03:17 AM

Hi@Phil_38552 If you're trying to identify multiple PM5320 meters on a network, using their IP addresses is the standard method. Any Modbus TCP client can poll each meter using its unique IP. The Unit ID remains 255 for all, but it doesn’t matter because the IP is different. This is the recommended and simplest solution.

Reply
Phil_38552
Phil_38552
Cadet

Posted: ‎2025-06-04 04:01 AM

1 Like
0
222
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2025-06-04 04:01 AM

Hi @akash_das ,
thank you for the quick and clear reply!

That exactly confirms what I was assuming, and it's good to know that identifying the PM5320 meters via their IP addresses is the recommended approach.

I’ll proceed with the setup accordingly.

 

Thanks for your support!

 

Reply
Preview Exit Preview

never-displayed

You must be signed in to add attachments

never-displayed

 
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of