PlantPax Global Object corrupting?

BillRobinson

Member
Join Date
Oct 2006
Location
Sydney, Nova Scotia
Posts
185
I've been using the PlantPax add-ins for RSLogix5000/FTV and I've been having the ongoing problem of the supplied global objects going crazy on me. What's happening is that instances of global graphics are randomly distorting their size (see attached). What is really puzzling is that even though it is a global object, not all instances of that object doing this; the same object will be distorted on one page but ok in another. Anybody have an idea what's happening here? It has occurred on factory talk studio 5.10, running on xp via VMWare and also running on a xp via windows xp mode.
 
Bill, I've had that happen over and over again on every installation of FTView 5.10 and up. Some things grow, some shrink, all look normal (usually in studio), but then become corrupted on the client...

I do manually go back and edit, which fixes that, and usually corrupts something else. It seems once an element gets corrupted, it becomes worse every time you save a display in Studio. In one case, I had all my buttons on a display shrink to the size of one pixel. I deleted that display and re-loaded from a backup.

It's just some of the fun built into that pile of **** that is FTView. Rockwell should be paying US to use it.
 
Rockwell IT told me that there is a patch. Search for [FONT=&quot]66056 [/FONT]on their knowledgebase. Not sure if it works though.

I'm 100% behind your pile of **** comment. Man that product is bad. My favorite is VTS by trihedral, they are based out of Nova Scotia but have alot of installations in Southeast US and Atlantic Canada.
[FONT=&quot][/FONT]
 
Rockwell IT told me that there is a patch. Search for [FONT=&quot]66056 [/FONT]on their knowledgebase. Not sure if it works though.

I'm 100% behind your pile of **** comment. Man that product is bad. My favorite is VTS by trihedral, they are based out of Nova Scotia but have alot of installations in Southeast US and Atlantic Canada.

I've installed that patch to no avail. It reduces how often the problem happens, but when it happens, it is even worse. I actually backed out that entire rollup, after running into many other additional problems, and not being able to isolate the patch that caused them.

For the most part, I've found that the 'patch roll ups' never seem to help, and only make things worse.
 
Last edited:

Similar Topics

Hi folks, I'm looking for some help trying to get my graphics to load a bit quicker. At the moment if I pull up a motor faceplate for example it...
Replies
0
Views
1,757
Hello, i need to use P_Intlk and feed the Status interlock OK bit to a P_DOut block. However, there's 17 interlocks for this output. How can I...
Replies
1
Views
109
Hello All We have 3rd party vendors that run on older versions of PLC (Plc2.0) while we run the main system using plantpax and PLC 3.5-10. Plantpx...
Replies
0
Views
95
Dear Members, Hello, we are working on a project and facing an issue with the plantpax 5 PMTR library, we have a bidirectional motor, which has 2...
Replies
6
Views
247
The PMTR has a timeout parameter for run feedback during a start, but once the motor has been running for a while and loses that run feedback (to...
Replies
0
Views
223
Back
Top Bottom