PanelView Firmware

Slwagner73

Lifetime Supporting Member
Join Date
May 2017
Location
Bellevue, MI
Posts
53
Help!


We have a PanelView that is running Firmware Version 5.10, and even though we have a TeleConnect contract with A-B, I cannot find a firmware update that will work.


I was wondering if there was anyway to find am update that will work.


We need to change the .mer file and it will not let me do so with the current versions I am running.


I have all the newest patches installed, and still no luck.


It keeps telling me that it does not support the CompactLogix PLC we are updating to.
🔨
 
You need to post the catalog number of the Panelview and of the CLX processor in order to get any kind of meaningful help. Firmware revisions of both couldn't hurt either.
 
A PanelView Plus with the hardware to support version 5.10 firmware won't support any higher firmware revisions (6 or later).

You can generally create a PV+ runtime for any older firmware revision, no matter what version of FactoryTalk View Studio you're running.

I've had very good luck manually adding a 1769-L35E to the communication schema in place of a newer ControlLogix or CompactLogix that wasn't supported by the network device list in an older version of RSLinx Enterprise.
 
A PanelView Plus with the hardware to support version 5.10 firmware won't support any higher firmware revisions (6 or later).

You can generally create a PV+ runtime for any older firmware revision, no matter what version of FactoryTalk View Studio you're running.

I've had very good luck manually adding a 1769-L35E to the communication schema in place of a newer ControlLogix or CompactLogix that wasn't supported by the network device list in an older version of RSLinx Enterprise.




Okay Ken:

So, we have a PV+ that we are trying to retask, (it worked with the old processor) but we are updating the PLC to a 1769-L27ERM. The firmware we have now is 5.10, and much as you said, it will not allow me to update it so that it will work with that processor. Cannot update the version any higher.
I create a Runtime App. for the version I have, but it fails due to the processor. (Not supported buy this version, during the creation of a RunTime App.)
You say you can manually add it, so I am gonna ask...HOW?


Thanks:
Scott


This is a 2711P-RDT10C, and a 1769-L27ERM-QBFC1B
 
Last edited:
I will try to walk through this in detail because I agree that it's not obvious and there are some rabbit holes you can step in.

In the RSLinx Enterprise configuration (called FactoryTalk Linx in the FTView 11 that I have installed), select the Runtime tab. I recommend that you delete any shortcuts other than the one pointing to this controller.

In the network schema on the right, right-click on the Ethernet driver and select Add Device.

In the dialog box, expand the EtherNetIP Devices folder, then save time by typing "1769-L35E" into the search field and click "Find Device".

Select the "Ethernet Bridge (1769-L35E), Major Revision 20" object and click OK.

I recommend re-naming the object "L27_Placeholder_Enet" or similar. Type in the IP address. Leave the "Slot" number as 3.

That will result in an object in the schema that shows the "daughtercard" and the CompactLogix backplane. Select the backplane and right-click again to Add Device.

Scroll down or Find Device until you find the "1769-L35E/A, CompactLogix L35E Processor, Major Revision 20".

Select that, and re-name it "L27_Placeholder_CPU" or similar. Leave the "Slot" number as 0.

Once you have the Shortcut highlighted on the left, and that CPU object highlighted on the right, click the "Apply" button at the top to associate them with one another. There's an "OK" button on the lower right of the RSLinx Enterprise window to save the whole schema into the project before you close the window.


This method is described in the RA Knowledgebase as Answer ID # 476489

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/476489

A note that I experienced; when you do this for the first time, RSLinx Enterprise correctly suggests Slot 3 for the Ethernet daughtercard object and Slot 0 for the CPU. Those aren't real physical locations, just addresses in a virtual object that emulates a Logix family backplane. If you delete the Controller object and go back to try again, the software incorrectly increments the default slot number. This can mess you up if you're not familiar with the inner workings of the backplane object.

The solid and stable firmware for that generation of PanelView Plus is 5.10.08. I stick with that exact firmware revision for the terminals I have installed because it seems to work well with the "L35E" shortcut trick, and because it contains a specific bug fix that affects the ControlNet daughtercard.
 
Last edited:
If we could pause for a moment, please?...

Slwagner73 said:
...We have a PanelView that is running Firmware Version 5.10...It keeps telling me that it does not support the CompactLogix PLC we are updating to...

And it always will (I'll explain in a minute).

Slwagner73 said:
we have a PV+...we are updating the PLC to a 1769-L27ERM. The firmware we have now is 5.10...

5.10.xx <<< This is important here - what is the sub-minor revision (.xx)?

Slwagner73 said:
...it will not allow me to update it so that it will work with that processor. Cannot update the version any higher...

Whether this is true or not will depend on the answer to that last question above?

Slwagner73 said:
...I create a Runtime App. for the version I have, but it fails due to the processor. (Not supported buy this version, during the creation of a RunTime App.)...

OK, I'll flesh out where I'm going with this...

My reading of this so far is that you have added a newer 5370 CompactLogix controller as the shortcut in a 5.10 application and while creating the MER application file you are receiving a specific message indicating that the shortcut PLC might not be compatible, if the terminal has not been patched, correct?

If so, then this message is always embedded in the Validation Results text file once a 5.10 application's shortcut is to any of the newer controllers which support firmware revision 20 or higher. This is because, for PanelView Plus 5.10.xx firmware revisions, there is a specific revision which introduced native support for these newer controllers. If your PanelView Plus terminal is running firmware revision 5.10.08 or higher, then the newer controllers will be supported. Anything lower and they are not.

However, because all that FactoryTalk View Studio knows is you are creating a "5.10" application with a newer controller, it does not know which specific 5.10.xx firmware revision will be running on the target HMI terminal. Therefore, it defaults to always warning you that there "might" be an incompatibility at runtime. You must know the above, and determine if the terminal's firmware is at or above the supported revision of 5.10.08. If the terminal is running firmware revision 5.10.06, for instance, then the "might" in the warning message becomes "will". If the terminal is running firmware revision 5.10.08 or higher, then you can ignore the warning message and proceed to transfer the MER application to the terminal and it "should" successfully communicate with the newer controller.

A caveat to all this is the controller firmware revision being used...

The native support, added in firmware revision 5.10.08, was introduced for the newer controllers released at revision 20. However, a PanelView Plus terminal at 5.10.08 will not communicate natively with a controller at any firmware above revision 20. The PanelView Plus terminal must be flashed to firmware revision 5.10.16 (latest/last?) in order to add native support up to controller revision 24 maximum. Beyond that, the PanelView Plus terminals no longer natively support communications to these newer controllers.

Note: By "native" I mean you can select a newer controller as a shortcut in a 5.10 application, create the application while receiving the warning, ignore the warning, and use the application file successfully.

If using terminal firmware revision 5.10.08 and controller revisions higher than 20...

...or...

...if using terminal firmware revision 5.10.16 and controller revisions higher than 24...

...then you must implement the method Ken is describing.

So, what firmware revision the 1769-L27ERM is currently flashed to is also important here in deciding whether you can simply ignore the warning, or you must substitute the controller in the shortcut with an older supported model/revision. We could assume you might just have levitated towards the latest revision 32? But, in reality, the firmware revision that users tend to flash to a new controller is the current highest version of software they have installed and have been using, and that is not always the latest. So, if you were to say that you are still using RSLogix 5000 v20 highest, I would not be surprised. But also, as you have mentioned you have a TechConnect Contract, it is entirely possible you have downloaded the latest, or a quite late, version of Studio 5000?

Here are a couple of similar threads we've had on this before...

Panelview Plus 600 and 1769-L30ER

Panelview Plus 7 didnt work with compac Logix L24er

You can, of course, just simply ignore "me" here instead and proceed to create the "proxy" 1769-L3x shortcut, as Ken has kindly suggested, as it should also work. Especially if you cannot, or do not, want to flash the terminal's firmware, if it needed it, or, if the controller is too "new" a firmware revision and you do not want to backflash it (I would not be recommending this). That is why I only asked that we "pause" here, and not "stop". But if the terminal's and the controller's firmware are already at compatible revisions, natively speaking, then you need do nothing more than transfer the application file as is, and it should also work.

One more important thing to point out...

Slwagner73 said:
...This is a 2711P-RDT10C...

The older PanelView Plus terminals are what are known as an "Assembled Terminal". As such, they are made up of one or more components, each having their own catalog number. Example: Display, Logic, Communications modules. However, when "Assembled", they are combined into one "Assembled Terminal" catalog number.

What you have listed for us is only the Display module catalog number - 2711P-RDT10C (1000 touch color display). This is a common mistake as the sticker on the back of the Display module is rather large and prominent, compared to the sticker on the back of the Logic module. It is the Logic module sticker you should refer to. On this sticker, you also have to be careful, as it contains both the Logic module catalog number...

Example: 2711P-RP (without flash/RAM memory, DC input), which is nearer the bottom of the sticker...

...and at the top, the Assembled Terminal catalog number...

Example: 2711P-T10C4D

Where...

2711P = Family: PanelView Plus

T10C = Display: Touch 1000 (10") color

4 = Communications: Ethernet, RS-232 & (2) USB ports

D = Supply: DC

As you have told us your terminal is running 5.10.xx firmware, it is perhaps not so critical here that we must know the Assembled catalog number for the PanelView Plus terminal.
But just in case, it is always better to provide it, and now you hopefully know how to?

Regards,
George
 
Last edited:
Gentlemen:
Well it has been a very long two weeks since I have had a chance to revisit my issue, way, way too many other problems have arisen in the plant, but I will be able to get back at this next week,"fingers crossed", and I am going to give Kens idea a try first. "wish me luck"!


Geo, to answer your question, the assembled model number is "2711PC-T10C4D1/SER A". The firmware version is 5.10.06.09 (CR 9 SR2).


Not sure if this helps me, or hurts!


But thanks to both of you!
Scott
 
Sorry, I only saw your update today...

Firmware revision 5.10.06 is before native compatibility was added at revision 5.10.08 for the newer CompactLogix controllers, so that's a given that you must use an older CompactLogix controller as a placeholder.

You didn't mention the firmware revision the controller is using, but that would only have been relevant if you were using firmware revision 5.10.08 or newer.

If you are not going to upgrade the terminal's firmware to add native compatibility, then "unpause" my "pause" and proceed as though I was never here...

Regards,
George
 
Sorry to resurrect an old thread, but wanted to add another data point to this scenario for frantic Google searchers out there.



Had a PV Plus 1250 (Original, not 6 or 7) that would not communicate with a 1769-L33ER at FW version 32.


Upgraded firmware of PV Plus to 5.10.16UP from Rockwell's download portal.


Patched Factorytalk View Studio 11.0 to the latest patch rollup from Rockwell. This was a big help.


Used Ken's directions above to set up a comm path to a 1769-L35E in design and runtime tabs. Did this with ethernet cable unplugged from programming laptop to avoid devices on the LAN from auto-populating.


Created the 5.10 runtime mer file.


Loaded and worked.


Not only did PV Plus communicate with L33ER, but the RSLinxNG.exe fatal error that would typically appear on the PV Plus went away.
 
Hey All. I think i jumped the gun earlier. I had hoped my problem is solved, but i i now realise i was only half way to the finish line.

Background.

I am running a panelview plus 1000. Firmware V5.10.06.09.

Previously i was creating screens using FTView studio V6. Everything was working OK. But the version is really old and i was running it on Demo version as i knew i needed to organise something better.

I finally organised FTView V11.

I was able to create screens OK in FTView V11. The runtime tested OK through my PC.
When i download to the panelview, there are a lot of losses. Almost every tag link is broken. I did not test all the links. It is possible ALL the links are broken.

I figured i needed to do a firmware update on the panelview.

This PLCtalk thread helped me figure out how to find and install firmware associated to my panelview.

I installed panelview firmware V5.10.16. This is the latest version of the firmware.

The issue is, when i download from FTView to the panelview, the outcome is the same as before. (described above). Many losses and no links work.

My question.

Did i install the correct version? Did i overshoot? Should i have installed maybe V5.10.11?
 
I was able to create screens OK in FTView V11. The runtime tested OK through my PC.

When i download runtime app to the panelview, there are a lot of losses. Almost every tag link is broken. I did not test all the links. It is possible ALL the links are broken.

Additional information since i wrote this post this morning.

The reason why all the tag connections are broken is because the panel is unable to communicate with FTLinx (RSLinx). I have spent all day today trying to re establish communication to no avail.

The worst part is without communication, i am unable to downgrade the firmware to the original.

So the new problem.

PVP 1000 does not communicate with FTLinx.

I fired up another laptop with RSLinx installed to see if it could see it. No luck there either.

Has anyone experienced anything like this before? If so, what did you do?
 

Similar Topics

Hi I have a number of the older PanelView Plus 600 HMI's (2711P-T6C20D, Ser D) that I want to update to the latest firmware. I believe that the...
Replies
10
Views
391
Had an interesting experience this morning. An old Panelview 600, 2711-K6C5X series B to be precise, comes up as error 32. Unfortunately it...
Replies
0
Views
195
Ive got an existing panelview plus 1000 with a logic module of 2711P-RP and an assembled pn of 2711P-T10C4D1 running out in the field. Its in an...
Replies
5
Views
1,128
The panelview in question has been installed for over 2 years with no issues. Our facility has an extensive SE installation with a handful of ME...
Replies
4
Views
1,203
My panelview runs firmware 9 just fine. I would like to understand the justification to upgrade the firmware to the latest. I've been asked to do...
Replies
7
Views
1,578
Back
Top Bottom