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

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Too long register response time with Total Active Energy Import iEM3000

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
  • Too long register response time with Total Active Energy Import iEM3000
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
477
Ramasamy_N
Captain Ramasamy_N Captain
113
Robert_Lee
Admiral Robert_Lee Admiral
92
Mehran_Mehrnia
Captain Mehran_Mehrnia Captain
85
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
Jak_Saut93
Jak_Saut93
Cadet

Posted: ‎2024-01-23 07:36 AM

0 Likes
2
911
  • 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.

‎2024-01-23 07:36 AM

Too long register response time with Total Active Energy Import iEM3000

Hello,

 

All registers except the energy consumption register are read correctly. Every 10 seconds I have a reading in the BMS system (this is how it was set in the controller). Unfortunately, register 45100 is read after 24 hours or longer.

 

I directly checked the reading through the Moxa U-port in the modscan32 program, the reading of this register was correct. Each change in the value of this register was read, I did the same using our driver. We can set the serial port through the controller and then we can read Modbus registers using other programs, for example modscan32. Similarly, we had a correct reading.

 

Register 45100 is read by our system as register 45098, similarly we need to shift the remaining registers down by 2. Everything is read at a given interval, unfortunately we still have problems with total consumption. I would like to ask for advice on how we can deal with this problem.

 

Below I am sending screenshots of the Modbus configuration in our system:

 

modbus.png

Jak_Saut93_0-1706023921614.png

We read data by main channel 9600 RTU/8/None/1

 

Regards

Jakub

 

 

Labels
  • Labels:
  • iEM3000
Tags (1)
  • Tags:
  • english
Reply
  • All forum topics
  • Previous Topic
  • Next Topic

Accepted Solutions
Robert_Lee
Admiral Robert_Lee Admiral
Admiral

Posted: ‎2024-08-22 02:01 PM

1 Like
0
675
  • 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.

‎2024-08-22 02:01 PM

Register 45100 for most PowerLogic devices is stored as a IEEE-754 single precision FLOAT32 register value.  This means any Modbus request would likely need to send a Read Holding Register request asking for 2 registers and interpret the response accordingly.

I have no idea why you would reduce the address by 2 unless that is some strange requirement in the BMS software.  When using most standard Modbus software like MODSCAN32, addressed entered via the ui are expressed in PDU+1 addressing (as is Schneider documentation).

This means if we state the register is located at address 45100 the PDU register address (i.e. the one sent to the device is that minus 1 so 45099 is sent to the device).  Most applications like MODSCAN32 hide this fact and expect you to enter the published PDU+1 addressing.

Robert_Lee_0-1724360495872.png

 



See Answer In Context

Reply
Replies 2
Ramasamy_N
Captain Ramasamy_N Captain
Captain

Posted: ‎2024-08-22 07:19 AM

0 Likes
0
695
  • 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.

‎2024-08-22 07:19 AM

Hi @Jak_Saut93 

Can you connect with tech support team with the screenshots? I am unbale view this attachment. 

Reply
Robert_Lee
Admiral Robert_Lee Admiral
Admiral

Posted: ‎2024-08-22 02:01 PM

1 Like
0
676
  • 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.

‎2024-08-22 02:01 PM

Register 45100 for most PowerLogic devices is stored as a IEEE-754 single precision FLOAT32 register value.  This means any Modbus request would likely need to send a Read Holding Register request asking for 2 registers and interpret the response accordingly.

I have no idea why you would reduce the address by 2 unless that is some strange requirement in the BMS software.  When using most standard Modbus software like MODSCAN32, addressed entered via the ui are expressed in PDU+1 addressing (as is Schneider documentation).

This means if we state the register is located at address 45100 the PDU register address (i.e. the one sent to the device is that minus 1 so 45099 is sent to the device).  Most applications like MODSCAN32 hide this fact and expect you to enter the published PDU+1 addressing.

Robert_Lee_0-1724360495872.png

 



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