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.
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.