LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

NI OPC server vs. KEPDIRECT

Solved!
Go to solution
I am in the process of setting up an industrial PLC project.  I am wanting to use Labview for communication with my Automation Direct PLC system.  Automation Direct offers an OPC server KEPDIRECT for $295.00.  NI OPC server is quoted at nearly $2,600.00.  Money is not a factor in my situation and I want to purchase the best and most efficient server.  Can someone explain to me the difference in the two servers (why one is more expensive than the other) and which one is better for working with labview and a PLC.  I currently have my system programmed with Automation Directs Direct Soft 5 and Lookout Direct and want to completly switch over to Labview if this makes any difference.  Thanks for any input and help.
0 Kudos
Message 1 of 7
(4,913 Views)

atlasengineer wrote:
...NI OPC server is quoted at nearly $2,600.00. ...

THat sounds like you are talking about LabVIEW DSC which is an OPC server but is much more "Dataogging and Supervisory Control" offers (in addition to teh OPC server) data-logging and archieving to an SQL compliant DB* along with multiple levels of alarms, trending along with a suite of security and historical control fincutions that are 21-CFR-11 complient. So if you just are looking for an OPC server, then DSC is over-kill.

 

Ben

 

* Yes Mike its not a "tame database" Smiley Wink

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 2 of 7
(4,909 Views)

NI OPC Servers provide drivers for connectivity to many different PLCs.  This would be beneficial if you had several PLCs from different manufacturers in your system or if you plan on expanding your system to include other PLCs later without having to purchase another server for another PLC.

LabVIEW can communicate with any OPC server that adheres to the OPC Data Access protocol.  For the most flexibility for different connections, NI OPC servers would be the best choice.  If you only plan on using one type of PLC, the Direct Automation OPC server should be just fine.

Donovan
0 Kudos
Message 3 of 7
(4,898 Views)
I appologize, the NI OPC Server is quoted at $1,049.00 not $2,600.00.  So the only difference is that the NI server is compatible with any PLC system while KEPDirect is only compatible with the Automation direct line of PLC's? 
0 Kudos
Message 4 of 7
(4,894 Views)
Solution
Accepted by topic author crockengineer

If you click on the Overview tab of the product page posted above, there is a link to the drivers that can be used with NI OPC Servers.  So, you can’t connect to ANY PLC, but there are quite a few.  However, you are correct.  The KEPDirect server will only allow connectivity to AutomationDirect PLCs.  That will be the main difference between NI OPC Servers and the KEPDirect server from AutomationDirect.

Donovan
0 Kudos
Message 5 of 7
(4,890 Views)

Hi All,

 

 I'd suggest going with the NI OPC server to connect to the Automation Direct PLC if money is not a big issue.  The reason is that you will definitely find it easier to test and integrate other brands of PLCs if needed.  Basically more flexibility.  The Kepware driver is great as well.  Here's the interesting thing, I am 99% sure that the OPC servers NI use are actually from Kepware!  You will even find that NI is listed as a customer of Kepware on the kepware site!  Rockwell do the same and repackage Kepware in some of their products.  Does not take away from good products from both Rockwell and NI in my opinion.

 

 My 2 cents...

 

cheers!

Peter

0 Kudos
Message 6 of 7
(4,807 Views)


Blue Ridge Test, a certified NI Alliance Partner, has successfully implemented a control / monitoring system with LabVIEW which interfaces to networked Automation Direct PLCs through ethernet (ECOM modules) and OPC.  If you are interested, we would like to talk with you about your application to see how we might partner together to achieve an elegant, cost effective solution which meets your goals while removing months from your timeline.

If you decide to approach this on your own, there will be configuration challenges (e.g. extracting the correct tags from DirectSOFT 5, setting up OPC, etc.).  Before addressing those, though, you may want to think through your programming requirements such as those listed below.

After the setup phase of your project (i.e. configuring hardware & signal conditioning, verifying connectivity, demonstrating various portions in LabVIEW, etc.), you might consider your architecture before moving forward.  How will you store your data?  How will you view / analyze the data later?  Is the architecture readable, scalable, and maintainable?  What will happen when you want new features (e.g printing reports, user logins, or controlling other external equipment or processes while saving data and displaying results)?  What kind of user interface will you use?
 
Set yourself up for success long term by thinking about the right architecture today.  We frequently have customers whose "simple engineering experiment" grew on them.  And, interpreting bad LabVIEW code a year into a project can be a lot like deciphering abstract art (and equally expensive).

 

Jason B

434-525-7312 x114

Message Edited by Support on 02-10-2009 05:17 PM

Certified LabVIEW Architect
TestScript: Free Python/LabVIEW Connector

One global to rule them all,
One double-click to find them,
One interface to bring them all
and in the panel bind them.
0 Kudos
Message 7 of 7
(4,719 Views)