Allen Bradley OPC problems in version 7.2.6 release

Hi Gents,

Since upgrading from 7.2.6 beta 11 to 7.2.6 released version i now have several tags that wont be read.
The message in the log is as follows:
"Not including tag named XXXXXXX in browse results because tag offset is invalid.
I have tried to delete the tag and recreate it in the plc with no luck.

Help here would be great
Am using the Allen Bradley control logix driver Returned browsed tags are 25177.

Regards
Sascha

I went and renamed those tags in question.
Created new ones in place within the controller tags. then change them out. That seemed to have fixed the issue.
However if i create a tag within a Routine in RSLogix 5000 by right clicking create tag it seems to bring up the above issue.

Strange

It almost sounds like the driver didn’t finish reading tag information from the processor before the OPC browse data was created.

  • Please restart Ignition and then turn on the ABControlLogixBrowseRequest trace.
  • Next, click the refresh browse in the device page of the Ignition Gateway.
  • Wait for the browse pending status to disappear.
  • If the SQLTag quality is still bad, try creating a new SQL Tag by dragging it from the OPC Browser.
  • Turn off the trace and send the wrapper log or console export to support@inductiveautomation.com

When you say “create a tag within a Routine in RSLogix 5000 by right clicking create tag”, do you mean in RSLogix 5000 or Ignition?

Tom

I meant create a tag in RS Logix 5000.

All the tags were working fine in previous beta version.
Since we changed to the official release version there is something funny going on in the OPC side of things in Ignition.

When the error came up it just had a folder in ignition opc for the tag group but no tags in it.

I will do the log file tomorrow and send it.

Regards
Sascha

It now wont read tags from one of the plc’s at all.
On the device page it says browsing all the time and never finishes browsing.
I have set the browse timeout time to 45000ms.

This is starting to get problematic.

Hi everyone,

i have installed the latest version of ignition (7.2.6 b128) and the original problem still persists.
approximately every 10 minutes i get the following error.

[WARN] 	13:47:19 	ABControlLogixReadRequest 	[MixTanks] Read Request timeout. First item: (null)MainProgram.TANK_H_STATES_INDICATORS.TANK_H_STATES_INDICATORS[2], Timeout Count: 1, Transaction: 1443, duration: 5578
[WARN] 	13:47:19 	TimeoutDaemon 	ScheduledRequest[[ABControlLogixReadRequest]] request with key "1443" failed due to timeout.
[WARN] 	13:47:13 	BasicRequestCycle 	Message arrived for key "0" but no request found.
[ERROR] 	13:47:13 	MixTanks 	[MixTanks] Key equals 0: length=342, [70 00 3E 01 01 1C 00 41 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 A1 00 04 00 C2 FC AC 62 B1 00 2A 01 00 00 8A 00 00 00 0F 00 20 00 38 00 54 00 74 00 7C 00 8C 00 98 00 A0 00 AC 00 CC 00 D4 00 E0 00 00 01 08 01 14 01 CC 00 00 00 00 00 01 00 01 00 01 00 01 00 00 00 00 00 00 00 0C 00 00 80 CC 00 00 00 01 00 01 00 00 00 01 00 01 00 01 00 01 00 00 00 00 00 00 00 0C 00 00 80 CC 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 F0 F0 46 00 00 00 00 00 00 C8 42 00 00 00 00 CC 00 00 00 00 00 00 00 CC 00 00 00 00 00 00 00 C0 27 09 00 00 00 00 00 CC 00 00 00 00 00 10 03 0A 00 00 00 CC 00 00 00 F8 03 00 00 CC 00 00 00 00 04 00 18 0A 00 00 00 CC 00 00 00 03 00 00 00 03 18 00 00 00 00 00 00 00 F0 F0 46 00 00 00 00 00 00 C8 42 8C 74 9F 41 CC 00 00 00 00 00 00 00 CC 00 00 00 00 00 10 03 0A 00 00 00 CC 00 00 00 07 00 00 00 00 00 00 00 00 00 00 00 00 F0 F0 46 00 00 00 00 00 00 70 41 00 00 00 00 CC 00 00 00 00 00 00 00 CC 00 00 00 87 04 62 00 01 00 0A 00 CC 00 00 00 00 00 00 00 00 00 C8 42 00 00 00 00 ]

It alwasy starts with the error Key equals 0, the length is never the same.
It then follows with timeouts of various tags which are never the same.

This is on a PC with an intel atom N270 1.6 ghz dual core processor and 2gb of ram running windows xp.
I have tried various settings in the timeouts, scan rates, minimum request cycles etc. all with pretty much the same outcome.

I have tried a virtual machine on my laptop with the same problem.
I have tried running this on another laptop with an intel core duo and the same problem
Ignition HMI is directly connected to a moxa managed switch.
L63 CPU is connected directly to the same moxa managed switch and are all on the same subnet.

Hope someone could shed some light on this.
Kind Regards
Sascha Hlubek

Hi Gents,

I have now done some further testing on this.
I increased the minimum request times and reduced the multiplier.
This allows me to run this project in a virtual machine without errors. However i still have the issues described earlier when running it on a pc with the intel atom cpu.

Kind Regards
Sascha Hlubek