List of Contributions

The other posts in this thread tell more of the story, but here is an update: Good news! The second series B controller arrived and I was able to update its firmware to v31.14 and copy to it the v31.14 program I had converted from the copy from the series A v20 controller. The then used this series ...

Short answer, no, we didn't first update the series B processor to v31, for reasons described below. I was working remotely with a technician at the PLC and the technician does not have Studio 5000, but I could access the PLC remotely. The hope was to burn the SD in the series A PLC with the option ...

I should have mentioned it (for sake of the post) but, yes, I did try the reset button, holding it for an extended period (45+ sec one time, about a minute another time) when powering up the controller. It did not seem to make a difference. The LEDs cycle after a while, then the NS and Link1 LEDs flash ...

Recently we tried replacing a 1769-L24ER-QBFC1B Series A controller with a new Series B controller. The Series A controller was configured with firmware 20 and the SD card was loaded with the program and the option to load the program and the firmware on power up. The card was then placed in the Series ...

I am using FactoryTalk Linx 6.3 so this is likely the reason.

I have an existing FactoryTalk ME application that I had to update a couple of the displays. On another unrelated display that I did not have to update I noticed a strange issue. On the this display there are several pushbuttons and multistate indicators. One of the pushbuttons and one of the indicators ...

I have created two global objects using embedded variables to display the range of an instrument in 20% increments. In the image above the left column is created following the standard format of selecting the number of digits and decimal places, the right column has embedded variables for the number ...