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

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

CITECT SCADA 2018 Slow runtime

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 SCADA 2018 Slow runtime
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

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Back to AVEVA Plant SCADA Forum
Anonymous user
Not applicable

Posted: ‎2020-12-17 03:26 AM

0 Likes
7
7390
  • 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: ‎2020-12-17 03:26 AM

CITECT SCADA 2018 Slow runtime

I am Using M580 PLC & Citect 2018 Scada. Between PLC & SCADA communication is taking Place on MODNET. I am facing a problem of Slow update of tags on runtime hmi. In that case I would also like to mention that I have observed tag is updating its value immediately when I update its value from scada. But in opposite case if tag value is changed in PLC side it is taking more than 10 second to update on same hmi runtime. Please suggest ???

  • 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 7
BevanWeiss
Spock BevanWeiss
Spock

Posted: ‎2020-12-17 09:04 PM

0 Likes
5
7370
  • 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: ‎2020-12-17 09:04 PM

When you perform the control action from Citect, Citect writes this tag 'immediately' (at the soonest possible time) and doesn't wait for a general scan to occur.

 

However when you are updating the variable in the PLC, then Citect will only recognise and update this when it next scans the tag.  I assume that this scanning is only occurring every 10 seconds.

 

So you should check what your scan rate is set to (and consult the driver documentation).

If your end device, and network, and driver can support a faster scan rate, and you do indeed need this faster update frequency, then you could change the Citect config to poll the device quicker.


Lead Control Systems Engineer for Alliance Automation (VIC).
All opinions are my own and do not represent the opinions or policies of my employer, or of my cat..
  • Tags:
  • english
Reply

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

Anonymous user
Not applicable

Posted: ‎2020-12-17 09:44 PM

In response to BevanWeiss
0 Likes
4
7368
  • 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: ‎2020-12-17 09:44 PM

Thanks for replying.

I have tried with some changes in ini file. can you please suggest what are the setting I have to check in citect  config to faster polling of device.

 

  • Tags:
  • english
Reply

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

RoozeeR
Lt. Commander RoozeeR Lt. Commander
Lt. Commander

Posted: ‎2020-12-18 01:20 AM

In response to Anonymous user
0 Likes
3
7356
  • 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: ‎2020-12-18 01:20 AM

Communication performance, and the performance to the operator screen is influenced by multiple factors:

- Client refresh rate (default is 250 mS)

- Driver used (modnet)

- Driver type setting (Modnet, Modnet[20], Modnet[30], see documentation)

- Network bandwith (100Mb ethernet?)

- Number of variables communicated continuously (?)

- PLC used (M580 CPU type)

- CPU scan time (unknown)

- Other devices communicating with the same CPU (?)

 

When taking only the driver into consideration and you're using Modnet, check the [Modnet] maxpending and maxoutstanding parameters. For example set the maxpending to 8 and maxoutstanding to 8 or higher (16);

 

Check the information in the driver documentation or in:

https://gcsresource.aveva.com/Citect/driverweb/MODNET/modnet.pdf

 

Also you might consider to use OFS instead of Modnet. For new applications, OFS is easier to use in combination with M580 CPU's.

 

 

R.Roozee
Sr Solution Architect (SAE Master)
  • Tags:
  • english
Reply

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

Anonymous user
Not applicable

Posted: ‎2020-12-21 12:39 AM

In response to RoozeeR
0 Likes
2
7346
  • 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: ‎2020-12-21 12:39 AM

@RoozeeR Kindly note the details as following:

 

- Client refresh rate (default is 250 mS)- If it is page scan time then it is 250mS 

- Driver used (modnet)

- Driver type setting (Modnet, Modnet[20], Modnet[30], see documentation) - here MODNET 30

- Network bandwidth (100Mb ethernet?) - 1GB

- Number of variables communicated continuously (?)-  Approx. 10K

- PLC used (M580 CPU type)- BME H58 2040 02.70

- CPU scan time (unknown)- 77mS

- Other devices communicating with the same CPU (?)- 2nos HMI Server, CPU 580-2 Safety PLC, 1 PRM with 8nos Profibus Node, 1 OPC Server

 

Also set maxpending to 8 and maxoutstanding to 8 , but problem remains. Please suggests.

 

 

  • Tags:
  • english
Reply

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

RoozeeR
Lt. Commander RoozeeR Lt. Commander
Lt. Commander

Posted: ‎2020-12-21 04:32 AM

In response to Anonymous user
1 Like
0
7333
  • 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: ‎2020-12-21 04:32 AM

According to your settings your application is limited in several ways. Most important: Modnet30 limits block read size to max. 64 words (see https://softwaresupportsp.aveva.com/#/okmimarticle/docid/tn8313)

Better to use OFS driver (OPC Factory Server) in combination with M580. For standard Modbus request, the block size is 125 registers and when max message length can be 1024 bytes (instead of 128 for standard Modnet30), thus decreasing the total amount of messages and increasing the performance.

OFS can also help optimizing the number of messages, specially when variable addresses are not in contiguous addresses.

 

As the max. number of messages processed per CPU cycle is limited, decreasing the max. number of messages will help, or increase the number of messages dedicated to Citect. The last is limited by CPU type.

 

In your 10K variables (if all %MW) could mean at least 10000/64= 156 messages. 8 per CPU cycle handled means 156/8= 20 CPU cycles (at least) to read them all. This means at least an update time of 20*77= 1.5 seconds (at least). But as you also have other communications, this number is the best case scenario.

 

Please read the TVDA "How Can I …Optimize OFS and Modicon M580 Ethernet Client/Server Performance?"

 

If you do not have this document, please contact your local Schneider Electric support organization. They can also support you to increase the overall performance.

R.Roozee
Sr Solution Architect (SAE Master)
  • Tags:
  • english
Reply

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

Anonymous user
Not applicable

Posted: ‎2020-12-24 10:13 PM

0 Likes
0
7298
  • 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: ‎2020-12-24 10:13 PM

When you perform the control action from Citect,

  • Citect writes this tag 'immediately' (at the soonest possible time) and doesn't wait for a general scan to occur.
  • However when you are updating the variable in the PLC.
  • Then Citect will only recognise and update this when it next scans the tag.
  • I assume that this scanning is only occurring every 10 seconds.
  • Tags:
  • english
Reply

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

BevanWeiss
Spock BevanWeiss
Spock

Posted: ‎2020-12-26 08:44 PM

In response to Anonymous user
0 Likes
0
7278
  • 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: ‎2020-12-26 08:44 PM

As noted:

  • Change Protocol Variant from MODNET30 to MODNET
  • Ensure latest compatible MODNET driver is being used
  • Set [MODNET.TCPPORTx] MaxPending =16 (or other as testing reveals suits)
  • Set [MODNET.TCPPORTx] MaxOutstanding =8 (or other as testing reveals suits

Other Citect.INI settings for the MODNET (both the generic driver, and port specific) should be left at their defaults (unless required specifically for successful communications)


Lead Control Systems Engineer for Alliance Automation (VIC).
All opinions are my own and do not represent the opinions or policies of my employer, or of my cat..
  • Tags:
  • english
Reply

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

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