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!

Citect 2016- ModbusTCP communication

AVEVA Plant SCADA Forum

A support forum for AVEVA Plant SCADA (formerly Citect SCADA). Share new and exciting product information, connect, learn, and collaborate with the ecosystem of Plant SCADA Users. AVEVA Plant SCADA a reliable, flexible and high-performance Supervisory Control and Data Acquisition software solution for industrial process customers. This forum is to connect, share, learn and collaborate new and exciting product information. Feel free to join and share to your Ecosystem of Plant SCADA Users.

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
  • Industrial Automation
  • AVEVA Plant SCADA Forum
  • Citect 2016- ModbusTCP communication
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
olivier_vallee
Lt. Commander olivier_vallee
28
Oncom
Commander Oncom
6
BevanWeiss
Spock BevanWeiss
2
RoozeeR
Lt. Commander RoozeeR Lt. Commander
2
View All
Related Products
product field
Schneider Electric
Citect SCADA

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Back to AVEVA Plant SCADA Forum
IngPianetti
Ensign IngPianetti
Ensign

Posted: ‎2021-01-22 03:18 AM

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

Posted: ‎2021-01-22 03:18 AM

Citect 2016- ModbusTCP communication

Hi everybody!

 

I'm working with Citect 2016 (update 38).

 

We need to establish a Modbus TCP communication with a PLC in plant. Nevertheless, the SCADA never gets to communicate to this PLC. After running many tests, we found out that the SCADA never sends any kind of request to the mentioned PLC (we used wireshark).

In order to rule out any kind network problem, we run a ModbusTCP Server in a PC which was at reach of the SCADA, but the results were the same.

After that we proceed to create an empty new project pointing just to the same testing ModbusTCP Server on the PC. But to our surprise, it worked perfectly well, even though the parameters (port, protocol, device, variable addresses) were the same as the ones in our original project.

 

It is the first time something like this happend to us. We have many Schneider M340 using ModbusTCP without any kind of problems.

 

Any ideas?? Thanks in advance

Labels
  • Labels:
  • Asset Performance
  • Tags:
  • english
Reply

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

  • All forum topics
  • Previous Topic
  • Next Topic
Replies 8
kingslim
Lt. Commander kingslim Lt. Commander
Lt. Commander

Posted: ‎2021-01-22 06:15 PM

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

Posted: ‎2021-01-22 06:15 PM

What you did on using Wireshark is brilliant. And how you try to isolate the issue by setting up a new project and saw that MODBUS TCP actually works on new project but not the existing was also the correct way of isolation. This was the troubleshooting procedure I often did some 15 years back on Citect when faced exactly what you describe (and in many projects, not juts one). I would have thought such problem will not occur anymore, unless your project has a long history of migration from a very old version. 

 

I hope this will work for you as it did for me. In the existing project, delete the IODevice, the Port and the Board. Then add them in again. This somehow worked for me. There seems to be something else at play behind the IODevice, Port and Board settings we can see. Good luck. 

 

 

  • Tags:
  • english
Reply

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

IngPianetti
Ensign IngPianetti
Ensign

Posted: ‎2021-01-26 03:15 AM

In response to kingslim
0 Likes
1
7135
  • 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.

Posted: ‎2021-01-26 03:15 AM

Hi!

 

Sorry for the late resposne, I've been off the office these last days.

 

Thank you very much for your piece of advice. I'll give it a try a let you know what happens. It sounds promising.

  • Tags:
  • english
Reply

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

Anonymous user
Not applicable

Posted: ‎2021-01-26 05:45 AM

In response to IngPianetti
0 Likes
0
7130
  • 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.

Posted: ‎2021-01-26 05:45 AM

Also looking forward to the result, whether it helped or not?

  • Tags:
  • english
Reply

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

IngPianetti
Ensign IngPianetti
Ensign

Posted: ‎2021-01-27 05:33 AM

In response to kingslim
0 Likes
4
7115
  • 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.

Posted: ‎2021-01-27 05:33 AM

Hi everybody !!!

 

Unfortunately I cannot say the problem is solved. Dispite of that, we discovered some interesting things.

 

As we had already ruled out any network problem, we are running now our test modbus server ( simulated IOdevice ) on the same pc the scada server is.

 

Before lauching the SCADA, we started Wireshark on the background. After checking out the log, we found out that Citect sends only one request to the simulated IODevice (which sends a response back), There are no more messages from that instant on. After 100seconds, the IODevice closes the TCP connection and that's it.

 

We tried creating again the interfaces, ports and devices but there was no luck.

"config.ini" does not configure any parameter related to MODBUS either.

  • Tags:
  • english
Reply

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

kingslim
Lt. Commander kingslim Lt. Commander
Lt. Commander

Posted: ‎2021-01-27 07:16 AM

In response to IngPianetti
0 Likes
3
7111
  • 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.

Posted: ‎2021-01-27 07:16 AM

Sounds to me like your device does not response to a Read Digital Input @ address 40001. When Citect starts, if you look at the Wireshark traffic, you will see it always sends a poll for that. If the device does not response, Citect thinks the device is dead. This was my experience again from ages ago. And I did raise the issue to the Citect guys in the good old days.    

 

Look into the MODNET Driver Help.. .  See InitVar and InitVarType. Set them to something that your device will response to.  

 

Hope this helps...  

  • Tags:
  • english
Reply

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

IngPianetti
Ensign IngPianetti
Ensign

Posted: ‎2021-01-27 09:40 AM

In response to kingslim
0 Likes
2
7105
  • 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.

Posted: ‎2021-01-27 09:40 AM

This problem is really driving me crazy.

 

I've just checked again the Wireshark logs of both the production (which doesn't work) and testing (it works) projects and I can see that the Citect first poll and Device response are exactly the same in both cases, but somehow Citect refuses to keep sending requests in the production project.

 

I'll check again the "config.ini" to see if there are any differences.

 

Thanks!!

  • Tags:
  • english
Reply

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

kingslim
Lt. Commander kingslim Lt. Commander
Lt. Commander

Posted: ‎2021-01-28 06:03 PM

In response to IngPianetti
0 Likes
0
7078
  • 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.

Posted: ‎2021-01-28 06:03 PM

Well, when all else fails, we have to turn to AVEVA support. Hopefully your customer had purchased Customer First support.

  • Tags:
  • english
Reply

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

ismailozinan
Lt. Commander ismailozinan Lt. Commander
Lt. Commander

Posted: ‎2021-01-29 12:50 AM

In response to IngPianetti
0 Likes
0
7073
  • 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.

Posted: ‎2021-01-29 12:50 AM

Hello,

Wireshark controls the ethernet line. It does not check the integrity of the Modbus TCP protocol. For modbus control, you need to examine the packets coming and going to port 502. You can do this with Modbus poll software.
If there is no Modbus communication, connect your PC directly with the PLC. Switches in between may be closing the port. Or, when you make a Citect modbus query, if a query is sent to a register that is not on the PLC, there may be a problem in communication. For this reason, expand your modbus register table on the PLC side. Write a any value to the highest modbus address of plc.
Normally, I did not encounter any problems with the citect in modbus driver. 

Best Regards,

  • Tags:
  • english
Reply

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

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