OPC development in F#
QuickOPC makes it easy for you to integrate OPC client functionality into your Visual F# solution. Reading a value from OPC Data Access or OPC Unified Architecture server, or writing a data value can be achieved in just one or two lines of code. You can also set up subscriptions and receive event notifications about data changes. What's more, in your OPC F# program, connections to OPC servers do not have to be created and recreated in case of a network failure or similar problems - QuickOPC handles this automatically, behind the scenes.
Component interfaces hide the complexities of OPC, are designed specifically with Microsoft .NET and F# developer in mind, making you feel right at home when referencing and using them.
The components can be used from various environments: Code libraries, ASP.NET pages, console applications, Windows services, etc. are all supported. The F# development tool we have targeted primarily is Visual Studio 2012, 2013 and 2015.
- New: QuickOPC now also supports OPC UA Alarms&Conditions.
Simple OPC-UA F# Example Using QuickOPC
The code below (in F#) reads and displays a monitored item value, using QuickOPC:
// Obtain value of a node and display it
let client = new EasyUAClient()
let value =
The code below subscribes to changes of a monitored item value, and displays the value with each change:
let easyUAClient = new EasyUAClient()
// The callback is a delegate that displays the value
let handle =
fun sender eventArgs -> Console.WriteLine(eventArgs.AttributeData.Value:obj)))
OPC "Classic" Data Access, or Alarms&Events
The code below (in F# language) connects to an OPC server, and reads and displays an item value, using QuickOPC.NET component. It works in Microsoft Visual Studio 2012, 2013 and 2015.
// Read item value and display it
let client = new EasyDAClient()
let value = client.ReadItemValue("", "OPCLabs.KitServer.2", "Demo.Ramp")
No other product can do this in such a clear and concise code! The programming is straightforward, and the developer can focus on getting the work done and not on fighting the intricacies of OPC protocols.