In my ongoing theme to further educate you all on the reasons to use token based polling (otherwise known as Request New Device Data) we find ourselves on our 2nd installment of the series. In my previous post we covered the Reduced Overhead of the command. This time we’ll cover Partial success and Command synergy
CygNet Applied Engineering is pleased to announce the release of the CygNet Depot. This tool was created to simplify interacting with CygNet file storage services. With the Depot, you have easy access to any file stored in your APPS or BSS and also your Group services. You can download, upload, drag-and-drop, delete, rename, copy, and paste. In addition, you can preview files (Studio screens, PDF documents, Excel spreadsheets, image files) and make in-place edits to text-based files (.txt, .xml, .vbs, etc.) without having to bother with downloading, editing, saving, then uploading.
The CygNet Report Module just got even better. 2015 version 2 contains our most significant enhancements to the Report Module since its initial release, including a new report type, streamlined UI, column sorting, customizable email subject lines, and more.
We want this blog to continue to provide our customers with the information you need to be successful with CygNet. To that end, we’d like your help.
Are there specific topics you always wondered about but haven’t found enough information on?
Do you have technical questions that you’ve never been able to get answered?
Are there parts of the CygNet product that remain a mystery to you?
Here is a scenario that I’ve seen crop up several times in the last few months:
A point enters the alarm state and an SMS notification has been sent, but several hours later no one has acknowledged it yet. Investigation begins into this issue and I notice that the notification service (GNS) has logged a successful send to my field techs’ wireless carrier’s email address, there are no errors reported, but no one has responded to the callout. I call the tech and he says he never received the notification.
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.
Have you ever run into a situation where a single value on a device could represent multiple values at the same time? How would you display a nice string representation for all the potential values? I recently saw this problem solved on an Emerson device where a TLP contained multiple values packed into a single byte. The solution used a combination of multiple reference DEIDs and a few associated enumerations.
Scripting in CygNet is great…when it works.
Debugging script issues in Studio (especially without a just-in-time debugger like Microsoft’s Visual Studio) is like a game of Battleship: “Is there a bug at B9? No? OK, let’s try a MsgBox at H2…” And don’t get me started once you have to deal with Nested Views.
But even worse is debugging script issues in the HSS. That’s like playing a game of Battleship while blindfolded, ten miles from your opponent, and you can only make your guesses via Morse code. And did I mention your opponent can move the ships around? It’s enough to make HSS and VBScript (and maybe CygNet for that matter) four-letter words in many a SCADA admin’s vocabulary.
Maybe we can help.
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.
Since WESC is now ancient history, I wanted to give you all an update on our new mobile product. For those who haven’t heard, we started a research project back in April 2014 to understand what our customers wanted from a CygNet mobile solution. The research told us that lease operators were most in need of an app to view data and acknowledge alarms from the field. That is what we have been working towards ever since and I’m pleased to announce that we are now feature complete! That being said, the official release date is still Q4 as we have some minor issues to address and want spend some time focusing on performance.
Search the CygNet Blog
Subscribe to the CygNet Blog
Enter your email address to subscribe to this blog and receive notifications of new posts by email.