I have problem when using togel bottons/Push bottons, when the botton is pushed the indications light light up and it go's off (Status from plc, showing off) then on after next updating. The point is set up I/O put with an updating when on screen and 5 sec( if i set it to 100msec it works ok for 3-4 but not when I have all 50. Problem with to much communications) The bottons have to be I/O do to that they can be switched off from the plc. The system have about 60-70 bottons and totaly 900 tags(To plc), and under normal use about 340 active.
Need a solotion to avoide the indication not to flash.
System set up:
CX-superviser V2.11 Plus Running on WinXP
PLC; CJ2H-CPU64-EIP
OPC Server from Omron.
When running the runtime file in the monitor I can see that the
<CIP - TCP:2\192.168.50.34\BACKPLANE\0> have a overload status in use from 116% up to 180%.
Is there someone that have the same problem or have an good idee to do this??
Page 1 of 1
Toggel switch / Toggel bottons Problem with toggel bottons
#2
Posted 17 March 2010 - 02:52 PM
rhtaa, on Mar 17 2010, 05:13 PM, said:
I have problem when using togel bottons/Push bottons, when the botton is pushed the indications light light up and it go's off (Status from plc, showing off) then on after next updating. The point is set up I/O put with an updating when on screen and 5 sec( if i set it to 100msec it works ok for 3-4 but not when I have all 50. Problem with to much communications) The bottons have to be I/O do to that they can be switched off from the plc. The system have about 60-70 bottons and totaly 900 tags(To plc), and under normal use about 340 active.
Need a solotion to avoide the indication not to flash.
System set up:
CX-superviser V2.11 Plus Running on WinXP
PLC; CJ2H-CPU64-EIP
OPC Server from Omron.
When running the runtime file in the monitor I can see that the
<CIP - TCP:2\192.168.50.34\BACKPLANE\0> have a overload status in use from 116% up to 180%.
Is there someone that have the same problem or have an good idee to do this??
Need a solotion to avoide the indication not to flash.
System set up:
CX-superviser V2.11 Plus Running on WinXP
PLC; CJ2H-CPU64-EIP
OPC Server from Omron.
When running the runtime file in the monitor I can see that the
<CIP - TCP:2\192.168.50.34\BACKPLANE\0> have a overload status in use from 116% up to 180%.
Is there someone that have the same problem or have an good idee to do this??
How have you setup your OPC tags structure? From experience, if you put too many tags in one single group, comms performance goes down. Better is to divide the tags over multiple groups.
*update 06/02/2010 - Added link to Routing table instruction video
check out www.myomron.com - our knowledge at your fingertips
#3
Posted 18 March 2010 - 12:58 AM
Why use OPC with CX-Supervisor anyway, can you not just use in-built CX-Server?
#4
Posted 18 March 2010 - 04:42 AM
lostcontrol, on Mar 18 2010, 06:58 AM, said:
Why use OPC with CX-Supervisor anyway, can you not just use in-built CX-Server?

LOL good point, I just jumped right in way to late at midnight
*update 06/02/2010 - Added link to Routing table instruction video
check out www.myomron.com - our knowledge at your fingertips
#5
Posted 18 March 2010 - 06:17 AM
PdL, on Mar 18 2010, 05:42 AM, said:
The OPC was there before we started to use CX-superviser, but have disconected the OPC and still the comunications are
CIP - TCP:2\192.168.50.34\BACKPLANE\0> have a overload status in use from 116% up to 180%.
The main problem is the toggel switches, since we did not have that on the NS-screens.
Any idee who to av avoid thes?
#6
Posted 18 March 2010 - 01:02 PM
rhtaa, on Mar 18 2010, 11:17 AM, said:
CIP - TCP:2\192.168.50.34\BACKPLANE\0> have a overload status in use from 116% up to 180%.
Is this figure from Performance Monitor? If you're using EtherNet/IP and your comms bandwidth is anything over 30% I would say you have problems - maybe this is why the Write commands take some time to be sent and refreshed (also confirmed as you say works OK for 3-4 buttons at 100ms but not all 50).
Suggest you need to optimise your commes to reduce bandwidth.
Regards,
BB
#7
Posted 18 March 2010 - 01:09 PM
Quote
LOL good point, I just jumped right in way to late at midnight blink.gif
Ahh, the midnight MrPLC fix....
Quote
The OPC was there before we started to use CX-superviser, but have disconected the OPC and still the comunications are
CIP - TCP:2\192.168.50.34\BACKPLANE\0> have a overload status in use from 116% up to 180%.
The main problem is the toggel switches, since we did not have that on the NS-screens.
Any idee who to av avoid thes?
CIP - TCP:2\192.168.50.34\BACKPLANE\0> have a overload status in use from 116% up to 180%.
The main problem is the toggel switches, since we did not have that on the NS-screens.
Any idee who to av avoid thes?
Are you using arrays, all individual tags per point? I would 'assume', that if OPC was used instead of CX-Server, then arrays are probably not used.
I am pretty sure in the manuals & tooltips, the use of arrays is recommended.
It will require a bit of re-work, but I am pretty sure that this will improve your performance.
#8
Posted 22 March 2010 - 01:23 AM
Berti Baker, on Mar 18 2010, 01:02 PM, said:
rhtaa, on Mar 18 2010, 11:17 AM, said:
CIP - TCP:2\192.168.50.34\BACKPLANE\0> have a overload status in use from 116% up to 180%.
Is this figure from Performance Monitor? If you're using EtherNet/IP and your comms bandwidth is anything over 30% I would say you have problems - maybe this is why the Write commands take some time to be sent and refreshed (also confirmed as you say works OK for 3-4 buttons at 100ms but not all 50).
Suggest you need to optimise your commes to reduce bandwidth.
Regards,
BB
The figurs are from the performace monitor, but on the on the ethernet bandwidth is at max 25%, but on the CIP-TCP is in use from 116%->
Have redused the aktive tags that are in communications with the plc, but it do not help me.
Have a look on the movie to see the toggel problem.
Regards,
TAA
Attached image(s)
Attached File(s)
-
Showtoggel.avi (658K)
Number of downloads: 184
#9
Posted 22 March 2010 - 10:23 AM
lostcontrol, on Mar 18 2010, 01:09 PM, said:
Quote
LOL good point, I just jumped right in way to late at midnight blink.gif
Ahh, the midnight MrPLC fix....
Quote
The OPC was there before we started to use CX-superviser, but have disconected the OPC and still the comunications are
CIP - TCP:2\192.168.50.34\BACKPLANE\0> have a overload status in use from 116% up to 180%.
The main problem is the toggel switches, since we did not have that on the NS-screens.
Any idee who to av avoid thes?
CIP - TCP:2\192.168.50.34\BACKPLANE\0> have a overload status in use from 116% up to 180%.
The main problem is the toggel switches, since we did not have that on the NS-screens.
Any idee who to av avoid thes?
Are you using arrays, all individual tags per point? I would 'assume', that if OPC was used instead of CX-Server, then arrays are probably not used.
I am pretty sure in the manuals & tooltips, the use of arrays is recommended.
It will require a bit of re-work, but I am pretty sure that this will improve your performance.
Thanks for the tips, but have try it, and it still gives me the flashes, if you press the botton on the wrong time...
The CIP-TCP went down down by 10-15%
Share this topic:
Page 1 of 1
Sign In »
Register Now!
Help



Back to top









