Possibly. But there’s not much you can do about tags @ 100ms going stale when you have max response times from the PLC as high as 3,000ms, other than a larger than advisable stale threshold setting. Or running at a slower rate than 100ms.
However, if you are having problems with the tags @ 1,000ms then yes, this could help things out.
7.2.4-beta3 is building and uploading right now. When it’s done it would be great if you guys could grab it and see if it addresses each of your issues.
I’m not really worried about the 100ms tag. I only have one and it really doesnt have to stay at that speed. The 1000ms tags are the ones im concerned about.
Ok 7.2.4-beta3 is up. If you are still having stale values we’ll take a closer look and try to figure out what’s going on. If it comes down to it would you be able to call into support and do a GoToMeeting?
Kevin, You were going to check this on a local OSX machine. Any update on this? I loaded the beta4 and it actually increased my max times. The 1000ms is up to almost 9 sec max. Thats almost 3 seconds more than the beta3 that you and I looked in our web meeting.
I have twice tried to do the upgrade and have had issues both times. The first time was due to the active X issue but last Friday I upgraded and all seemed ok until last night when stale tags was an issue with some of my devices. I have no scan class below 1000ms as was mentioned as a possible issue in earlier posts. 2 out of four exact same devices on the same network had stale tags. I could not get them to come back on line no matter what I did. I also tried refreshing and deleting/re adding the device but it threw up an internal error and similarly it would not allow the editing of existing devices. I had to go back to 7.1.8 and all is ok again.
I brought my MacBook Pro in today, I'll try it out and let you know.
[quote="aidamcg"]Hi
I have twice tried to do the upgrade and have had issues both times. The first time was due to the active X issue but last Friday I upgraded and all seemed ok until last night when stale tags was an issue with some of my devices. I have no scan class below 1000ms as was mentioned as a possible issue in earlier posts. 2 out of four exact same devices on the same network had stale tags. I could not get them to come back on line no matter what I did. I also tried refreshing and deleting/re adding the device but it threw up an internal error and similarly it would not allow the editing of existing devices. I had to go back to 7.1.8 and all is ok again.
Aidan[/quote]
There have been some issues around the driver re-establishing a connection after one has gone down for any reason. These issues have been resolved as far as all testing has shown in 7.2.4-beta5, which is uploading right now. If you install this and still have issues the support guys would be glad to do a GoToMeeting with you and take a look.
I will not be able to test it out again until the weekend at the earliest as it is in a production environment and is relied upon heavily. It also causes me loads of issues with inaccurate and missing data when it does not work correctly. A go to meeting is not really an option for me as I am on GMT and the system is in use during the week.