I recently had a customer call with a very strange issue: His PanelView Plus was taking over 5 minutes to boot. Calls to tech support and several other troubleshooting steps lead nowhere.
Not knowing what else to do, I asked the client if he could send me his HMI and PLC programs so I could do some testing in house.
He graciously agreed, and what I found was pretty strange – something I had never seen before.
On boot, I was getting a message saying, “Loading symbol from RSLinx Enterprise, please wait.”
This message seemed to coincide with the clients suspicion that the large number of end user aliases in the controller may have been the culprit. And the next message I received (after over 5 minutes) seemed to be confirming that.
It said, “Updating controller symbols has timed out. You may choose to continue updating controller symbols or run the application. Start-up macros and datalogs may not operate correctly…”
Adjusting the processor’s (L73) overhead time slice to 50% did provide some improvement. At that setting, I no longer got the timeout message.
However, something really bothered me about the message I was getting… the client only have about 30 tags in his project, so what was RSLinx Enterprise taking over 6 minutes to load?
Surely 30 tags would load in a fraction of a second, so it must be trying to load something else, but what?
Having exhausted all my ideas, and with the system issue successfully duplicated, I once again contacted tech support.
This time the tech I spoke with found an undocumented note about PVPlus slow boot times coinciding with large numbers of devices in the Target Tab in RSLinx Enterprise.
Now you may ask, why would anyone have anything besides the target PLC in the target tab?
Well not everyone is able to commission their HMI’s prior to installation. And if you’re connected to the plant network when you browse for your PLC in RSLinx Enterprise’s local tab, you’ll also see ALL the other Rockwell devices on the network too.
An unfortunately, the “copy from local to target” button doesn’t just copy the devices that have a “shortcut assigned.”
No, for some unknown reason (well, unknown to me at least) it copies everything from the local tab to the target tab…
With this little tidbit of information, I deleted all the “extra devices” from the target tab, leaving just the PLC assigned to the shortcut.
And presto, the PanelView Plus booted up in a normal amount of time.
Hopefully after a little prodding from myself, Tech Support will write up a public tech note so others who run into this issue won’t have to go through as many hoops to find the solution.
Until next time, Peace ✌️
If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.
Shawn M Tierney
Technology Enthusiast & Content Creator
Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.
- SLC-500 Migrations Compared: SoftPLC vs Studio 5000 (S2E10) - November 21, 2024
- Copia’s Ai Copilot Documents, Converts & Writes PLC Code (P228) - November 20, 2024
- Automation Q & A for November 15, 2024 (QA023) - November 15, 2024
Discover more from The Automation Blog
Subscribe to get the latest posts sent to your email.
Not counting the PDP-11 mainframe that I learned to program Fortran IV and then Basic on (punch cards, coding sheets, etc.) in 9th grade thanks to an Explorer post that a scientist at the USGS ran, the VIC-20 was my first “PC” with a whopping 4k of RAM and used a cassette tape player to save and load programs. I blew quite a few fuses on that thing trying to run a stepper motor via the parallel port before learning about transistors! It was an exciting time but I’d never want to go back to those days!
Thanks for sharing your knowledge with us!
Walter,
Thanks for your story and kind words!
Due to being a bit younger, I skipped the “punch card” and Fortran era and jumped straight into the VIC-20, and have many great memories of writing Basic programs on it and the Apple IIe’s we had at school 🙂 Good times to be sure!
Thanks again and Happy Holidays!
Shawn
The condition described above for PV not booting up and awaiting upload of PLC tags and symbols with the two options of 1)Continue upload or 2)Run program are a result of the PLC having no program loaded, option 1 will cause a time out and option 2 will cause a No Screen Loaded display. Verify that the PLC program is resident in the processor as a first check. If no battery in PLC, the add a filter into the power supplied to the PLC to mitigate power surges which will cause a loss of program in ControlLogix processors.
Nope, this article is about a different issue:
“Updating controller symbols has timed out. You may choose to continue updating controller symbols or run the application. Start-up macros and datalogs may not operate correctly…”
I found the fix myself: As I detailed above, I had to delete all the extra PLCs in the Target Tab.
I reported this to Rockwell at the time (2014,) and it likely has been patched since then.
Shawn
Join my free community to follow along! You can also become a member and support our work at: Automation.Locals.com