Device not recognized by FactoryTalk

nievesdelimon

Member
Join Date
Mar 2018
Location
Queretaro
Posts
35
There's a device (1756-L72 LOGIX 5572) which was not recognized by either RSLinx or Factorytalk (5.1). I got the EDS files and used the EDS Hardware installation tool. The device is now recognized by RSLinx, but not by FactoryTalk and I can't use its path to create a shortcut. What can I do for it to stop being a yellow question mark?
 
Welcome to the PLCTalk Forum community !

RSLinx Enterprise (the data server for FactoryTalk View) does not have a modular device identity subsystem like RSLinx Classic does (using EDS files).

So you have to install a patch or update for RSLinx Enterprise to recognize a controller it doesn't have support for. FactoryTalk View 5.1 would be about six years old by now, so I'm not surprised that it doesn't recognize this 1756-L72.

You can try to figure out which patch or compatible version of RSLinx Enterprise will work with your specific firmware revision of 1756-L72 and your specific version of FactoryTalk View. RA Tech Support is the appropriate venue for that.

Or, just insert a 1756-L6x controller into the network schema manually, and point the shortcut to that controller object.
 
There's a device (1756-L72 LOGIX 5572) which was not recognized by either RSLinx or Factorytalk (5.1). I got the EDS files and used the EDS Hardware installation tool. The device is now recognized by RSLinx, but not by FactoryTalk and I can't use its path to create a shortcut. What can I do for it to stop being a yellow question mark?
What is the model of the device?
 
I was fighting a very similar problem today, but with a CompactLogix controller. I was able to manually add the closest Ethernet device to RSLinx Enterprise, and then use its IP address as the downstream shortcut. Applications relying on that shortcut would then work OK.

(In this case the actual device was a 1769-L33ERMS rev 28, and I was using 1769-L33ERM rev 20.)

However, if I later went back to the FT Administration Console and then opened up the Communications configuration, RS-Linx Enterprise would automatically start browsing the nework and detect an unknown device at that IP address. It would then replace my manually-added device with an unknown device (yellow question mark). This carried through to the shortcut and broke it.

The workaround that seems effective is to go back to Communications, Stop Browsing, Delete Device, manually Add Device, and repair Shortcut -- all while avoiding a trigger to browse. So it is a very fragile workaround, subject to failing whenever the network is browsed. Unlike with RS-Linx Classic, I could not find a way to turn off "auto browse."

Attempting to install the proper EDS file was not effective as per Ken Roach's description of EDS usage. But I did get the impression from this technote:

Products show Yellow or Gray Question Marks after Upgrade

that if we upgrade to RSLE version 5.51 that it would use the EDS database. Unfortunately this server has only a very limited time window for patching, and FT patches never make the cut.
 

Similar Topics

Hello Everyone, I am using an Ethernet Driver and have added the IP addresses manually. There are a few IPs that I can ping in command...
Replies
7
Views
334
Hello Everyone. I'm doing this for the first time and got stuck so, I'm posting here. RS links is showing my HMI on the network but as an...
Replies
3
Views
1,649
After being power cycled rapidly several times by an unhappy power supply 3 out of 6 1756-IB16/A modules are now shown as Unrecognized Device...
Replies
2
Views
1,611
Good Evening All, I'm having a bit of trouble getting my 1756-ENBT to be fully recognized on my Windows XP SP2 Vmware Workstation virtual...
Replies
15
Views
5,359
Hi guys, I'm a little confused. My software was running very well by the last months. But yesterday I've tried to connect to one of the system and...
Replies
6
Views
2,384
Back
Top Bottom