#1 |
HI There
Are there any further settings or tricks that can employed for the following issue reading tags from a AB PLC?
Have AB Compaclogix (L320ERMS..) and have about 400 Tags to be read and sent to a cloud service. (which works)
The eWon only seems to capable of reading 70 odd tags; before it won't read tags and marks these as "no communication."
Really seams to hit UDT based tags more than native.
If I delete some working ewon variables, some more previously marked "no communication" can then be read; But that is not a hard rule. If I delete the majority of the variables, then there are still a range of tag variables that won't read.
I know the PLC Tag names and addresses are correct because the generation is all via a script feed a TAG export from the PLC. (using eWOn tag generator)
The logs are full of the following pattern
I know the PLC data in those tags is correct, and the name does certainly exist.
Work arounds I've tried
Are there any further settings or tricks that can employed for the following issue reading tags from a AB PLC?
Have AB Compaclogix (L320ERMS..) and have about 400 Tags to be read and sent to a cloud service. (which works)
The eWon only seems to capable of reading 70 odd tags; before it won't read tags and marks these as "no communication."
Really seams to hit UDT based tags more than native.
If I delete some working ewon variables, some more previously marked "no communication" can then be read; But that is not a hard rule. If I delete the majority of the variables, then there are still a range of tag variables that won't read.
I know the PLC Tag names and addresses are correct because the generation is all via a script feed a TAG export from the PLC. (using eWOn tag generator)
The logs are full of the following pattern
- stdios-Protocol Error reading Tag (ABLOGIX - SV012_DisEngageMin - Polling disabled for this tag)
- ablsrv-CIP Error Code in Reply: (30)
I know the PLC data in those tags is correct, and the name does certainly exist.
Work arounds I've tried
- I've tried setting the "disable tags in error"
- Changed the timeout
- Tried splitting tags across different severs
- Changed the pole rate of the servers