We are pleased to announce the release of CygNet’s OPC UA Server 1.0, now offering another way to access CygNet data over the web. The OPC UA server communicates with a CygNet system to request and receive data via encrypted communication channels using our intermediary REST API application, CygNet Bridge API. The CygNet OPC UA Server 1.0 operates with CygNet v9.5 and CygNet Bridge v4.4.121.
CygNet Bridge API provides web-based access to CygNet data. See Eric's post for an overview of the debut Bridge API release. With the latest version, we've added many new features. We've added the ability to retrieve and acknowledge alarms, send and retrieve device data group transactions, send commands, and more. But the new feature I want to tell you about today is two-factor authentication (TFA).
TFA allows you to add an extra layer of security to your CygNet Bridge API. Instead of only requiring the user's login credentials for authentication, TFA requires the user to additionally provide a temporary 6-digit code that is generated by an authenticator app on their phone. See this video demonstrating how it works for the user.
Have you ever needed to send a message out to all your CygNet Studio users? Maybe you need to let everyone know about some planned (or unplanned…) server downtime. Or maybe you want to inform everyone about a change to a screen, field asset, or company policy. Or maybe you noticed free cake in the break room and you’re feeling generous. Sure, you could write an email, but does everyone in the control room have Outlook open? If only there was a way to send a message to all open Studio and Vision clients in your site…
Consider this scenario. I have an overview grid screen that has a list of wells with some high level information. I click on one of the wells and a separate screen opens with more detail. On that detail screen, I click on a button that opens another screen that has a trend with various well points. Cool, I have separate dedicated screens that I’m able to view the various bits of information I desire at the same time. Now I want to be able to select on a different well on the first screen and have the other screens follow. And, I want to be able to look at multiple sets of these screens for different wells at the same time. How can I do that
In my previous post How to change a tab strip selection, I discussed the use of HyperLinkSys as a means of passing data from a nested view screen to its parent screen. In that technique, the data passed from the nested view was used to change the selection of a tab strip on the parent screen. In keeping with the theme of initiating an action from a nested view, I will present a different technique using custom events for more complex interactions.
I’m not sure how many of you noticed, but with the arrival of CygNet 8.1.3 came a fresh face in town to help with all your API woes (well, some of them anyway). Our first round of .NET API assemblies were unleashed into the world to bring hope and joy to all who write their own integration applications on top of the CygNet system.
Up until this point, you’ve had a couple of different tools at your disposal. CygNet ODBC, the COM scripting API, and the Enterprise Integration Suite are some of the different options you have to select from when you want to build an application to interact with CygNet. Each of these tools has its own set of advantages and disadvantages.
Enter your email address to subscribe to this blog and receive notifications of new posts by email.