QUOTE (Raydragon @ Jul 12 2009, 07:32 PM)

QUOTE (paulengr @ Jul 13 2009, 04:42 AM)

RS-Linx Classic has no such problem. It's truly a protocol bridge. Load it without a license and you get the "Lite" (free) version which will support RS-Logix and let's you browse/run diagnostics on your network but you won't be able to use it to replace Enterprise (but you can run them side-by-side). If you want to get rid of Enterprise altogether, the minimum you need is the "OEM" version which supports an OPC server. The next upgrade (Gateway or Pro or whatever they are calling it these days) also allows you to interface to it remotely (from another PC). The next upgrade beyond Gateway is RS-AssetCentre which essentially includes a "buried" RS-Linx Gateway license as well as handling document control and PLC access controls.
When you look into those various "bridge" boxes, watch out! Some of them are protocol gateways and not true bridges, so you won't be able to browse across them like you can with a 1756 backplane. If you can find a KF-2 box (discontinued), there is another option. Use the serial port and connect it to a DF1/Ethernet protocol bridge such as the IAP sold by Digi or Lantronix. This solution is about the cheapest way that I've come up with to do what you are asking. If you only have a few PLC's though you can also go with either the Digi or Lantronix devices and upgrade your existing PLC's to Ethernet via the serial port. The speed will not be great (19.2kbps max) but it sure solves a lot of problems. By the way, the "NET ENI" device sold by AB is a Lantronix protocol bridge in reality that has been rebranded and a couple extra features were thrown in, but it costs twice as much.
Thanks Paul. I am not really all that familiar with the ins and out's of the various RSlinx versions. You saying that by going to a higher level such as OEM of Rslinx that i will be able to get rid of Enterprise altogether. Won't that bugger up Factory Talk View's ability to create paths to devices etc when creating runtime files for PV+ terminals etc? I had an issue with this a while back before i realised i NEEDED Enterprise installed to be able to set the paths. How would having OEM Rslinx change that?. The rest of the features you mention with the Higher versions of Linx are probably things i won't need, or probably can't even use as they are probably control logix specific ( and we have none of that unfortunately ).
Also using the serial solution's you mentioned will help in a couple of cases ( I already knew this as we are using a couple of Net-ENI's already and those ones i can set up the trends perfectly.) but some of the processors i want to log data from don't have a free serial port, generally they have been used for connection to PV or PV+ as RS485.
When you are in the "configuration" menu for the paths in FactoryTalk View, you're really not in RS-View ME at all. You're actually viewing the Enterprise window. In fact, it is very unfortunate that they called it RS-Linx because Enterprise and RS-Linx Classic are truly totally different applications. You can't really store/configure paths in the same way since obviously you're not accessing Enterprise if you run Classic. However, you were talking about a specific problem that RS-Linx Classic does not have. Other than the tenacity and tendency for Enterprise to secretly grab your serial ports and not let go without a fight, and resource conservation considerations, there's no reason not to leave both Classic and Enterprise running at the same time.
The more expensive features that I mentioned in RS-Linx are NOT Control Logix specific. They've been there since the PLC-3/5/SLC days. In fact there are some things about the Control Logix drivers that will drive you up the wall in RS-Linx Classic.
As to the free serial port problem...that's a real problem with the NET ENI's. The Digi One IAP implementation has 2 serial ports AND an Ethernet port. You could for instance put it in series with your existing serial device (it becomes a passthrough) and you then get remote access via Ethernet out the third port. Digi advertises this pretty heavily and puts it prominently on their web site. In fact I see no reason that you couldn't also use a second IAP bridged to the first one to use it as a port multiplexer (adding 2 additional serial ports), other than bandwidth considerations.