I think there is something going on in version 7.0. I run a SE project with several clients and when I upgraded I started seeing the same issue. We use some VBA within some groups and they were set up as command buttons. It was set to 1 on press, 0 on release and 1 on repeat. We saw the issue right away and it was crashing the clients. What I found was that when I shut down just the client application and restarted it, it would lock up on the loading screen at "starting command server".
I was able to create the condition and what seems to cause it is when you click the button serveral times fast, it would lock up the client. It would also leave the tag at the last state which would cause motors not to shut off or valves to stay open.
I tried several things but what seems to have corrected it was going into the button properties and removed the repeat action. I also told the operator that they dont need to click the button 10 times to get something to work! I contacted Rockwell and they were not much help. It seems to have corrected the issue and have not seen it in a month now.
I know very little about what the command server does but with it hanging the restart of the client and the name of the button, they seem to be connected. Restarting the client PC always seemed to fix the issue.
One other interesting thing is that in version 7.0, they have the "current program updater" that connects to check for updates. I run a server that doesn't have a connection to the internet and I have been called in several times because of slow clients and the last one was the HMI tags stopped working. I was able to track the problem back in the event logs and at the exact same time as the problems started, it logged an error that it could not connect to windows update. It was trying once a day but after about two weeks it caused issues.
I called Rockwell and they said that the error was that the "current program updater" could ot connect. They were not aware of any issues and I thought I might be crazy, but after three calls at three different times a day I am sure that this was my issue.
Good Luck,
Kevin
Thanks for the reply. I'm not using repeat action at all. Using command on press and command on release seems to reduce the frequency of the problem but not make it go away completely. One of the most maddening things about it is that it only happens on one screen, and only on a couple of buttons.
I looked at the display properties and found that the one I had problems with had 'show last aquired value' unchecked. It doesn't seem to me that this should make a difference, we never had any issues with outlined indicators rather than actual data displayed. I did check it anyway, though.
I suspect it may have something to do with the button being pressed and released too quickly. The operators can sometimes be under a lot of pressure to move quickly because the drivers get paid by the ton and will express their displeasure if things move too slowly for them. Both of the buttons I have issues with are used at the end of the load. Rockwell didn't have anything to say about this possibility, or really about the entire issue.
When the button sticks the tag stays on, and clicking it a second time always seems to release it. I've temprarily set them to be green when the tag is on so the operator knows to click it a second time.
A couple of people have replied that they always put some coding in the ladder to unlatch the bit, and I'll do that but it's going to take some time and seems like a lousy way to handle the situation, and it will be difficult in some cases to pick an event to trigger the unlatch.
Regarding the current program updater, I disabled it. We have installations all around the great lakes, and I'm the only person who works on them. Version 7.0.0 works, and I'm concerned about some future update that causes a problem forcing me to travel a couple of thoudsand mailes as quickly as possible to correct some stupid clitch at 12 terminals and on 4 marine vessels.