Warning: FactoryTalk Linx 6.60 May Break Your Studio 5000 Uploads

If you recently updated your software and suddenly can’t get a project out of a controller, you might be dealing with a specific bug in FactoryTalk Linx 6.60. Many of us update our software hoping to fix minor UI issues or profile errors, but this latest version seems to be causing a major hang during the upload process.

The Symptom: The "Extended Properties" Hang

Everything looks normal at first. You go to "Who Active," find your PLC, and hit upload. The progress bar starts moving, but then it stops dead. Specifically, it gets stuck on "Uploading Extended Properties." You can ping the PLC. Your hardware is fine. Your cables are fine. But FactoryTalk Linx 6.60 simply refuses to complete the handshake required to pull those properties from the controller.

Why Downgrading Isn't Always the Answer

Your first instinct might be to revert to FactoryTalk Linx 6.50. Be warned: this is a messy process. Uninstalling 6.60 to go backward often results in:

  • Wiped Drivers: Your entire list of configured Ethernet and USB drivers may disappear.

  • Broken Browsing: Even after recreating the drivers using "Broadcast" or "Device Range," the software may still fail to see the hardware.

  • Reboot Cycles: You’ll likely spend more time restarting your computer than actually fixing the communication path.

The Workaround: Return to RSLinx Classic

The fastest way to get back to work is to bypass FactoryTalk Linx entirely. By navigating to: Communications > Select Communication Software

You can switch Studio 5000 back to RSLinx Classic. In our testing, switching to the "Old Reliable" allowed the upload to finish instantly, zooming past the extended properties without a single hiccup.

Final Verdict

Until a patch is released for version 6.60, you might want to hold off on the update or keep RSLinx Classic configured as your primary backup. When you have a machine down or students waiting for training, you don't have time to fight with your drivers.

Next
Next

Why Your PLC is in RUN Mode but Nothing is Working: The Empty Program Trap