Data to SQL

I think you'd be looking at the SQL Bridge "module" ($1500) and the Allen-Bradley Driver Suite ($300).

SQL Bridge "limited" ($1000) did data logging only (lacked bi-directional and other feature sets). I'm not sure if that is still available - I'd contact Inductive Automation for details. Here's a pricing sheet from their web site:

https://s3.amazonaws.com/files.indu...78/Ignition-HMI-SCADA+Pricing_09-18-15_en.pdf

You can download a fully functional version to evaluate. The software is exactly the same, but it stops every 2 hours, then you have to manually click a button to start it again. I recommend setting up the project and only purchasing the license if it works for you.

They also have free videos that show you how to use the software.
https://inductiveuniversity.com/

J E said:

Thank you for the responses.


What is the difference between the SQL Bridge Module Standard Edition and the Limited edition? Can I get these "modules" standalone, or do I have to purchase a full HMI package first?

I installed Visual Studio Community 2015 and downloaded the Advanced HMI. I always get a SocketException when I try to run the project, even if I build and run a fresh copy with no drivers set up. I must be missing something.

Click to expand...

There are two versions of SQL Bridge
SQL Bridge Limited: The limited version of SQL Bridge only allows the use of Historical Groups
SQL Bridge: This version allows access to all four types of groups: Historical, Standard, Block, and Stored Procedure groups.
This explains in more detail:https://docs.inductiveautomation.com:8443/display/DOC/SQL+Bridge+Module.

You can buy each module individually.

Given the gap between the initial responses and the information provided and where we are today, much has happened in 7 years. I say this because there was concern with ODBC as an option. However, I believe with further software development, ODBC can be considered an option in that the server being used would be Kepware's KepserverEX.

It is an extremely reliable connection.

Based on the information provided you would require two drivers...ODBC and Allen Bradley. Here are links associated with what you would need:

http://www.eternity-sales.com/Kepware/ODBC_Client_Driver_OPC_Server.htm

http://www.eternity-sales.com/Kepware/kepserverex.htm

If you have any questions, feel free to post, pm or email.

Disclosure - ESI is an authorized Kepware Distributor.

If you can still get the PLC data through OPC (option 4 in your old post), you can use an off the shelf product that moves OPC data to a SQL database without requiring any custom coding. Check out the OPC Easy Archiver here: http://integrationobjects.com/products/opc-data-archiving/opc-easy-archiver/

Thanks for all the responses. The customer just gave us a PO for the project. I have had pretty good luck in testing with the AdvancedHMI. I imported an old SQL interface class I wrote years back and it seems to still work well.

I have been using the SLC/Micro driver in conjunction with the Datasubscriber2 class to feed me data to write to SQL. Is this a preferred strategy or is there a better way?

J E said:

I have had pretty good luck in testing with the AdvancedHMI. I imported an old SQL interface class I wrote years back and it seems to still work well.

I have been using the SLC/Micro driver in conjunction with the Datasubscriber2 class to feed me data to write to SQL. Is this a preferred strategy or is there a better way?

Click to expand...

The way you are doing it is the easiest way.