This is an anomaly I had all day yesterday and have since resolved this morning. As busy as I am of late, I thought I'd share it with the Forum to hopefully save others the same lost time...
Prerequisite information:
Studio 5000 v27.00.00 installs View Designer v2.01 FW:2.001
Studio 5000 v28.03.00 installs View Designer v2.02 FW:2.002
Studio 5000 v29.00.01 installs View Designer v2.03 FW:2.004
Studio 5000 v30.00.00 installs View Designer v3.01 FW:3.001
Studio 5000 v30.01.01 installs View Designer v4.01 FW:4.001
Studio 5000 v31.00.00 installs View Designer v4.02 FW:4.001
I don't think this anomaly is OS dependent, but either way I'm using Windows 7 Professional x64 Service Pack 1.
Last year I had installed a PanelView 5500 at firmware 3.001 on a production line in the plant, referencing a Logix controller at firmware 30.11. I had used Logix Designer v30.00.00 and View Designer v3.01 to create both project files and all was fine. In April of this year I installed Studio 5000 v31.00.00 and this in turn installed View Designer v4.02, as per the above list. I created similar projects for the same type hardware using v31 and v4.02 for another updated production line and all was well.
Yesterday I had wired in a new air ioniser system (ESD) to the previous production line and created interlocks (4 off) and alarms in the Logix controller. The alarms to the HMI worked fine immediately because I'm using the ALARM_DIGITAL data type and ALMD instruction which allows you to embed the alarm message in the instruction's properties i.e. no HMI application edit required. When the alarm condition is true the HMI Alarm Summary object automatically displays the message in the controller instruction. Nice. However, we also wanted to graphically represent the new ioniser system on the line and add a steady "Ready" and flashing "Fault" object for when one of the 4 interlock conditions are not healthy. This of course does require a HMI edit...
When I opened the v3.01 View Designer application file I got some strange warnings I had not seen before, but the application did open. I added the required graphical objects and proceeded to Verify the project. When I tried to Download it to the referenced controller it also threw an error, stopping me proceeding. After doing some Repairs under Control Panel to various Rockwell Software products and certain other prerequisites, I would still receive errors while opening and while attempting a Download. I then reinstalled View Designer v3.01 - Nope. I uninstalled Logix Designer v31 - nope. I then converted the v3.01 project to v4.02 (open file via v4.02) and the project would open with no errors, except my tailored Predefined Banner would not convert (Predefined Screens or edits of them do not convert). Aside from having to recreate the Banner manually, I would also have to flash the terminal firmware to 4.001, which I did not want to do at this point in time.
I left it for the day after a lot of tinkering around - last status before leaving was that View Designer v3.01 would hang on opening each time, requiring a Task Manager End Task. So I left it hung for the night (laptop closed over) to see would something eventually happen when I came in this morning? Nope, it was still hung with the spinning circle cursor. I End Task'd it again and went to the AB Knowledgebase, not expecting to find anything, to be honest. But, as it turns out, I did...
1072344 - Product Notice 2018-03-001 - Studio 5000 Logix Designer V31.00.00 Compatibility with Studio 5000 View Designer V2 and V3 (201803001)
Access Level: Everyone
(See the technote for the typical errors you may receive)
One of the things I had strongly suspected yesterday was the installation of Studio 5000 v31.00.00 since last using View Designer v3.01. I did uninstall it during my efforts (one of the options in the technote) but it didn't solve the problem. It's possible that certain other components of the installation, which may be the cause here, do not get uninstalled. Another option they provide is to use v4.01 instead, which as I said, I do not want to do right now.
Long story short - this morning I downloaded Studio 5000 v31.00.01, which the technote states corrects this anomaly. I installed it and the problem has now gone away. I have opened the v3.01 project with no errors and have successfully Downloaded the mod to the terminal. I can also open older v2.03 projects, and of course the converted v4.01 project (only one I have).
So, if using Logix Designer v31, and view Designer v2/v3, make sure to use v31.00.01 specifically.
Note: v31.00.00, which causes the anomaly, is still available for download, so make sure you choose v31.00.01.
Another thing I've noticed, which doesn't help when checking which version you already have installed, is that whether you have v31.00.00 or v31.00.01 installed, they both display as "31.00.00" under Help>About Logix Designer. If you have the installation package (downloaded files), I would check the file name as this does have the correct version - 31.00.01-Studio5000-Web.
Side Note: View Designer v2.01 & v2.02 do not support side by side installations with other versions of View Designer. You can only have v2.01 or v2.02 installed at any one time on a system. v2.03 and later introduced side by side support - you can have v2.03/v3.01/v4.01 or v4.02 installed side by side and work with any version of View Designer/Logix Designer combination you wish (or so I've read) -
Example: View Designer v2.03 PanelView FW:2.004 / Logix Designer v31 Controller FW:31 should work with each other
...but...
I have also read in the Release Notes for v31 that View Designer v3.01 or earlier will not work with v31 Tag-Based alarming. You must use View Designer v4.01 minimum. So that's another (little?) caveat there.
Right, back to work!
Regards,
George
Prerequisite information:
Studio 5000 v27.00.00 installs View Designer v2.01 FW:2.001
Studio 5000 v28.03.00 installs View Designer v2.02 FW:2.002
Studio 5000 v29.00.01 installs View Designer v2.03 FW:2.004
Studio 5000 v30.00.00 installs View Designer v3.01 FW:3.001
Studio 5000 v30.01.01 installs View Designer v4.01 FW:4.001
Studio 5000 v31.00.00 installs View Designer v4.02 FW:4.001
I don't think this anomaly is OS dependent, but either way I'm using Windows 7 Professional x64 Service Pack 1.
Last year I had installed a PanelView 5500 at firmware 3.001 on a production line in the plant, referencing a Logix controller at firmware 30.11. I had used Logix Designer v30.00.00 and View Designer v3.01 to create both project files and all was fine. In April of this year I installed Studio 5000 v31.00.00 and this in turn installed View Designer v4.02, as per the above list. I created similar projects for the same type hardware using v31 and v4.02 for another updated production line and all was well.
Yesterday I had wired in a new air ioniser system (ESD) to the previous production line and created interlocks (4 off) and alarms in the Logix controller. The alarms to the HMI worked fine immediately because I'm using the ALARM_DIGITAL data type and ALMD instruction which allows you to embed the alarm message in the instruction's properties i.e. no HMI application edit required. When the alarm condition is true the HMI Alarm Summary object automatically displays the message in the controller instruction. Nice. However, we also wanted to graphically represent the new ioniser system on the line and add a steady "Ready" and flashing "Fault" object for when one of the 4 interlock conditions are not healthy. This of course does require a HMI edit...
When I opened the v3.01 View Designer application file I got some strange warnings I had not seen before, but the application did open. I added the required graphical objects and proceeded to Verify the project. When I tried to Download it to the referenced controller it also threw an error, stopping me proceeding. After doing some Repairs under Control Panel to various Rockwell Software products and certain other prerequisites, I would still receive errors while opening and while attempting a Download. I then reinstalled View Designer v3.01 - Nope. I uninstalled Logix Designer v31 - nope. I then converted the v3.01 project to v4.02 (open file via v4.02) and the project would open with no errors, except my tailored Predefined Banner would not convert (Predefined Screens or edits of them do not convert). Aside from having to recreate the Banner manually, I would also have to flash the terminal firmware to 4.001, which I did not want to do at this point in time.
I left it for the day after a lot of tinkering around - last status before leaving was that View Designer v3.01 would hang on opening each time, requiring a Task Manager End Task. So I left it hung for the night (laptop closed over) to see would something eventually happen when I came in this morning? Nope, it was still hung with the spinning circle cursor. I End Task'd it again and went to the AB Knowledgebase, not expecting to find anything, to be honest. But, as it turns out, I did...
1072344 - Product Notice 2018-03-001 - Studio 5000 Logix Designer V31.00.00 Compatibility with Studio 5000 View Designer V2 and V3 (201803001)
Access Level: Everyone
(See the technote for the typical errors you may receive)
One of the things I had strongly suspected yesterday was the installation of Studio 5000 v31.00.00 since last using View Designer v3.01. I did uninstall it during my efforts (one of the options in the technote) but it didn't solve the problem. It's possible that certain other components of the installation, which may be the cause here, do not get uninstalled. Another option they provide is to use v4.01 instead, which as I said, I do not want to do right now.
Long story short - this morning I downloaded Studio 5000 v31.00.01, which the technote states corrects this anomaly. I installed it and the problem has now gone away. I have opened the v3.01 project with no errors and have successfully Downloaded the mod to the terminal. I can also open older v2.03 projects, and of course the converted v4.01 project (only one I have).
So, if using Logix Designer v31, and view Designer v2/v3, make sure to use v31.00.01 specifically.
Note: v31.00.00, which causes the anomaly, is still available for download, so make sure you choose v31.00.01.
Another thing I've noticed, which doesn't help when checking which version you already have installed, is that whether you have v31.00.00 or v31.00.01 installed, they both display as "31.00.00" under Help>About Logix Designer. If you have the installation package (downloaded files), I would check the file name as this does have the correct version - 31.00.01-Studio5000-Web.
Side Note: View Designer v2.01 & v2.02 do not support side by side installations with other versions of View Designer. You can only have v2.01 or v2.02 installed at any one time on a system. v2.03 and later introduced side by side support - you can have v2.03/v3.01/v4.01 or v4.02 installed side by side and work with any version of View Designer/Logix Designer combination you wish (or so I've read) -
Example: View Designer v2.03 PanelView FW:2.004 / Logix Designer v31 Controller FW:31 should work with each other
...but...
I have also read in the Release Notes for v31 that View Designer v3.01 or earlier will not work with v31 Tag-Based alarming. You must use View Designer v4.01 minimum. So that's another (little?) caveat there.
Right, back to work!
Regards,
George