Showing posts with label RoviSys Turbo. Show all posts
Showing posts with label RoviSys Turbo. Show all posts

Friday, May 8, 2020

Accelerate your live data with RoviSys Turbo!


Whether or not you have DBDOC, your INFI 90® System can use RoviSys Turbo. RoviSys Turbo makes DBDOC live data five to ten times faster. Composer alone is typically ten times faster when monitoring. There is no extra communication loading.

How does it work? RoviSys is the first to make use of capability in the CIU and IET800 to fetch up to 16 analogs or 16 digitals in a single GMI fetch. Setting up your IET800 with OPC90 to gain the advantages of turbo polling is straightforward and uses standard ABB parts. 

10x faster with no extra load!

RoviSys Turbo gets up to 16 analog or digital values from a module in one message, improving monitoring significantly at no extra communications load.

Put spare CIUs to good use

RoviSys Turbo can handle multiple CIUs and IET800s - serial, SCSI and ethernet. Make use of spare CIUs by providing added cabability for power users, or increasing the amount of data fetched.

Share a CIU or IET800

Use what you’ve got! RoviSys Turbo can support Composer and DBDOC at the same time using one CIU or IET800. Composer is given priority over DBDOC, while DBDOC makes good use of the CIU when available.

Try RoviSys Turbo!

Accelerate today! Visit gmcl.com or rovisys.com for more information and start your free trial of RoviSys Turbo.




Friday, October 25, 2013

Thoughts on 10.5

The most important feature in DBDOC 10.5 for everyone with INFI 90 is the Error Browser. We continue to find issues that cannot be found any other way, as we have done for the past seventeen years. Now, finally, we let the user examine, comprehend and resolve our messages. You will hide many, but mark some for attention. When you rebuild the DBDOC document, new issues will be highlighted. Things you have hidden will stay hidden. Finally, you can converge to a system with no significant errors.

We continue our search for a system with more than 200 sheets that has no errors worth fixing. So far, only systems that have used DBDOC and heeded our messages are even close.

AutoCAD 2012 is now supported as well as previous versions. XLS file support has been extended to handle more and wider columns.

Of course, we finally have released initial support for ABB SPlus Graphics, 800xA PG2 and IET800 CIU. You will still get the most data out of your INFI 90 system for DBDOC with the least load out using a conventional CIU with RoviSys OPC90Server Turbo. An unprecedented 100 values per second at 10 GMI fetches can be achieved.

Tuesday, July 5, 2011

RoviSys OPC90Server - Turbo90 - Have Your Cake and Eat It, Too

Summary

Use of RoviSys OPC90Server Turbo with DBDOC CIUMon gives you the ability to read up to 16 analog or digital values from a module in one fetch, with average performance up to 100 values per second at 10 fetches per second.  Performance this strong has never existed before for INFI 90.  Both serial and SCSI CIUs can give this performance.

Details

Our DBDOC CIUMon product uses direct or multiplexed access to a CIU - any old CIU - to get live, read-only, data from an INFI 90 system.  The performance limitations are severe - typically as few as 15 values per second.  This is a problem shared with any polled data interface to INFI 90.

The new version of a software product RoviSys OPC90Server uses well-established techniques to get in the range of 100 values per second from the INFI Loop.  It does this in a way that improves the safety of the system at the same time.  We call it "Turbo90" affectionately.

What Turbo90 means for INFI 90 users is that, for the first time, it is possible to get much more polled data from a system.  DBDOC WatchWindow, for example, is much more valid with the new bandwidth.  You can monitor analog and digital values with greatly increased precision.  Use a dediczted CIU and you can even get fairly reliable 250 ms data.  Although the absolute time is indeterminate, the data rate is very high.
It is not prudent to put too high a load on a single PCU / node.  The quantity that should be limited is the number of GMI fetches.  The reason for being cautious is that too many of these high priority requests can slow down or stall the generation of exception reports (XR) in the node in older NIS/NPM versions (except for NIS21/NPM22).

Turbo90 gets as many as 16 values per GMI fetch.  We have measured 120 values per second at 13 GMI fetches per second.  Another data run of 25 minutes averaged 62 values per second with 10 GMI fetches per second for the entire period.

Analysis and validation of the above statements is possible if you wish to get data from us, or to run the tests yourself with our assistance.