You are not registered yet. Please click here to register!

plc storereviewsdownloads
This board is for PLC Related Q&A ONLY. Please DON'T use it for advertising, etc.
Try our online PLC Simulator- FREE.  Click here now to try it.

New Here? Please read this important info!!!

Go Back - Interactive Q & A > - Interactive Q & A > LIVE PLC Questions And Answers

Thread Tools Display Modes
Old November 6th, 2018, 09:08 AM   #1
Lifetime Supporting Member

Geospark is offline
Geospark's Avatar
Join Date: Feb 2012
Location: Kildare
Posts: 2,934
Studio 5000 v31.00.00 - Anomaly with View Designer v2/v3

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


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!

"A little nonsense now and then is relished by the wisest men".
  Reply With Quote
Old November 19th, 2018, 06:32 PM   #2
Lifetime Supporting Member
United States

harryting is offline
harryting's Avatar
Join Date: May 2002
Location: Puget Sound
Posts: 2,284

One of my guys just emailed me saying that he couldn't work with a vendor supplied system with Studio 30, that it is asking for View Designer 4. Now I see why.

Why would you do a major version update in View and not in Logix is beyond me.

ETA: I'm just starting to work with PV 5500. So how's the firmware version work? I already see that I can't open a project made in 4 with Version 3. But can version 4 open and upload prior versions? Does the hardware firmware have to match as well?

Last edited by harryting; November 19th, 2018 at 06:57 PM.
  Reply With Quote
Old December 30th, 2020, 06:07 PM   #3
Lifetime Supporting Member
United States

harryting is offline
harryting's Avatar
Join Date: May 2002
Location: Puget Sound
Posts: 2,284
Bump, can someone give me the cliff note on version manager with View Designer?

I know PV+ fairly well and in that, newer version can create run-time in older version but that's obviously not how 5000 series works.

ETA: I'm RTFM... and it still doesn't quite answer the question. I have version 3,4, and 5 installed and trying to covert 3 to a 5 but since I have 3 installed it doesn't do the conversion to 5.

From the manual
Open the last saved project or any previously saved projects. Open a View
Designer project using the same or later version of View Designer used to
save the project. Opening a .vpd file of an earlier version than the installed
version of View Designer converts the .vpd file to the installed version of View
Well, found my answer. The trick to create an "placeholder" project with the version you are going to. Close the project but don't close the program then open the project you want to convert from. It will then ask you to convert.

Last edited by harryting; December 30th, 2020 at 07:07 PM.
  Reply With Quote
Jump to Live PLC Question and Answer Forum


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Topics
Thread Thread Starter Forum Replies Last Post
Install Rslogix 5000 with Studio 5000 DVD? LowRange LIVE PLC Questions And Answers 7 September 16th, 2016 08:21 PM
RSLogix 5000 Studio ver. 26 jkerekes LIVE PLC Questions And Answers 12 April 29th, 2015 05:32 PM
New guy here, question about 1756-L72 and studio 5000 Jasondelane LIVE PLC Questions And Answers 8 March 12th, 2015 05:10 PM
RS View Studio (RSV Enterprise Edition V4.0) -> FT View Studio V7.0 SE husnain.mahmood LIVE PLC Questions And Answers 1 December 18th, 2013 04:16 AM
RSLogix 5000 V15 Features Samneggs LIVE PLC Questions And Answers 18 April 20th, 2006 06:45 PM

All times are GMT -5. The time now is 03:43 PM.