DBDOC 11.5 -- The journey continues!

The 11.5 release of DBDOC makes improvements across a variety of areas. Major updates include direct support for ABB 800xA graphics, enhancement of AC 800M support, and improved presentation of CLDs and BATCH programs. 

Hyperview in a Web Browser has also been made more accessible with the addition of a "No Login" mode, and it is now much easier than before to compare Error Browser errors between builds.

Improved support for 800xA graphics

A very significant change in 11.5 is the fact that DBDOC's support for 800xA graphics is now derived from the full AFW backup. This is more correct and complete than our previous approaches to 800xA graphics support. Full tag information information is also extracted from the AFW backup, and the graphics are presented in chapters that follow the actual project structure. It is easier than ever before to include 800xA graphics in your DBDOC project, and their presentation is more intuitive, correct, and complete than ever before.

 

Growing support for AC 800M systems

11.5 continues to rapidly increase DBDOC's support for AC 800M systems. Search and navigation are fully supported, and detailed support continues to improve as we gain experience with client systems and get feedback. DBDOC supports mixed Harmony/ AC 800M and systems that are exclusively AC 800M. We want to provide support that complements your existing ABB software, and we welcome feedback about what is (and could be) most useful.

Improved support for SPlus Operations graphics

DBDOC's handling of SPlus graphics continues to improve, with adjustments to details of hotspot, font, and text placement on graphics. Screenshots and feedback from your systems are invaluable to us -- please let us know when you see something that's not quite right. Chances are that when we fix the problem for you, it will simultaneously be fixed for a dozen other systems!

Merged EWS Taglist to facilitate configuration vs graphics comparisons

Each SPE or Composer project now automatically combines the associated taglists into a single taglist. This makes it much easier to synchronize with the graphics and see clearly what is going on.

Automatic exports of tags with database info plus specs

In DBDOC 11.5 builds, taglists are automatically exported with specs during the build process. This makes it possible to identify situations where there is a mismatch between the running system and settings in the database. For the first time, you can analyze tags with respect to the logic in the modules.

SPE 2.x and Composer systems updates

CLDs are now presented in the ABB document index order to be consistent with general usage, while BATCH programs are now organized in a single chapter by program name.

Hyperview can export all graphics

Hyperview can export full-sized screenshots for use by other programs. Relevant metainformation (size, title, location of links, etc) is also exported. Contact us for detailed information on how to use this capability.

No-Login mode for Hyperview in a Web Browser

A no-login mode has been added, so that Hyperview pages can be viewed without user accounts. This means that anyone (within the acceptable network context) can simply use links to DBDOC web pages and use Hyperview in a Web Browser with no further setup necessary.

Faster and more usable search

Topic title search in Hyperview is completely reworked to be much more usable. Searches now match to anywhere in a title string (not just the start), and each character you add to the search string restarts the search. Since longer search strings match faster than shorter ones (fewer matches), this enormously improves the performance and usability of this search. In addition, you can now export the results of a text search, with all the associated search result metadata, into a TSV file. 

Much easier to identify errors introduced between builds

The error browser automatically compares errors to the previous version opened and identifies new ones. Now, if you open an older file, the error base is reset. When you view a newer version, the errors introduced by the new one are highlighted. Using these techniques, you can easily identify how many, and which, errors were introduced between DBDOC builds.

DBDOC Calendar 2025

All friends of DBDOC should be receiving 2025 DBDOC calendars shortly. If you don't have yours by late January, please contact support@gmcl.com and let us know!

New! DBDOC for AC 800M

We have been working hard to add support for AC 800M to DBDOC.  Whether your system has both INFI 90 and AC 800M, or AC 800M only, DBDOC is now ready to provide full navigational and search support.  Simply export your AC 800M documentation using ABB tools, and DBDOC will do the rest.

Just as with INFI 90 systems, signals and documents are hyperlinked and interconnected. You can see all the uses of a function block at a glance, and double click to the block's location in the configuration.

If you have AC 800M, and are interested in finding out more, contact support@gmcl.com.

Double-click to go from graphic to the function block in the configuration.

Just as in INFI 90 systems, click on a function block hotspot to see all the places the function block is used.

Double click to get to the I/O channel source.

Hyperview in a Web Browser -- Now with No Login Needed

DBDOC 11.3 contained the initial release of Hyperview in a Web Browser.   This is a web browser based implementation of the most essential features of Hyperview, in a format suitable for use on a touch screen tablet.  More and more DBDOC clients have been trying it out, and finding it very useful.

The first version of Hyperview in a Web Browser required user logins in order to access the Hyperview "website".  Based on feedback from users, DBDOC 11.4 (the current patched version) and forward have a "no login" mode available.  This makes it extremely easy and convenient to use Hyperview in a Browser.  If you are in the correct network context, URLs for DBDOC documents will just work. 

This gives the seamless ability to include URLS like

http://legolas.gmcl.internal:8000/hyperview?cmd=bmk&toc=dbdoc%3A%2F%2Fchapter%2FSODGCHP%2FL%2FI90demo%2520new%2Fsodg%2FOperators&topic=dbdoc%3A%2F%2Ffile%2FL%2FI90demo%2520new%2Fsodg%2FOperators%2FG20.DR

in emails, documents, notes, etc. and have the links open without additional fuss in whatever web browser is available.  Of course, the port serving Hyperview must be open, and these links will only work inside of the intranet where a Hyperview Service is running. 

To get a URL to use this way, simply navigate to the desired document in Hyperview in a Web Browser, and copy the URL from the address field.

To run a Hyperview Service in no login mode, check the "No Login Required" option when configuring the service.

Note that to use this feature, you need the Hyperview from at least the most recent patched version of DBDOC 11.4, which you can download from the GMCL website: DBDOC Download (gmcl.com)

If you already have an earlier version of DBDOC 11.4 installed, you can obtain this updated Hyperview functionality by just updating the Hyperview Kit.

Back to Basics -- On-Site DBDOC Training

After a lengthy hiatus kicked off by the pandemic, we at GMCL are back to providing in-person classes and training for DBDOC users.  That being said, over the last four years we have become quite expert at providing online training as needed -- typically through Teams sessions -- and that is also a very effective way of providing one-on-one support and even introductory sessions for multiple DBDOC users.  But fundamentally, nothing compares with being on-site and in-person, in terms of the quality of interaction which is possible

In late April, Geoff and I were delighted to present an on-site Hyperview course to participants at Merck in West Point, Pennsylvania.  The day-long course was run three times, with about half a dozen students on each day.  There was a good mix of attendees -- mostly operators and technicians. but also engineers, managers, and contractors, all interested in getting a better understanding of how DBDOC could be useful to them.  Our contact Joe was a tremendous resource in organizing the sessions, and took an active role in helping to relate Hyperview's capabilities to areas of practical interest at the plant.

Speaking as lead Hyperview developer, teaching a class like this one is an exceptional opportunity for us as well -- our team is constantly trying to improve the usefulness and usability of the software, and there is no better reality check than observing a group of fairly novice DBDOC users getting off the ground with respect to basic functionality -- what works well, and where might there be opportunities for improvement.

This class was actually a lot of fun.  To begin, we introduced DBDOC, and how it fits into the context of the Harmony INFI 90® DCS system -- not everybody attending was familiar with the configuration layer (function blocks, CLDs), so understanding the framework of how DBDOC connects graphics to the hardware via the logic was essential.  We then introduced the DBDOC applications and how they work together, and then proceeded to teach basic Hyperview functionality interactively.  Participants had laptops with Hyperview installed, and were able to try for themselves the techniques being demonstrated.

Probably the best and most meaningful part of this particular class was the "quiz" that Joe had put together for the participants.  It consisted of practical questions about operations that could be answered quickly and easily using DBDOC -- this was an invaluable contribution to the group and to the effectiveness of the training.  Here are a couple of the questions:

• If boiler feed water pump 9 is yellow on the graphic, what are the 4 feedbacks that could be causing this?
• How long will the waste neutralization tank discharge if the pH is too high or too low?

Halfway through the day, the attendees worked through these questions and others, individually at first, and then collaboratively, using the DBDOC approaches they had just been introduced to.  Joe, a highly experienced DBDOC user, reviewed each question with the group afterwards, and the ensuing discussions with us and within the group were extremely effective at relating DBDOC's capabilities to the kinds of  tasks and questions that come up in practice.

In the latter part of class, we presented some of the more advanced Hyperview capabilities, and engaged in question & answer and discussion with participants. All in all, it was a very productive three days. It was also quite a wonderful leap forward into spring.   Up in the Great White North, April is still pretty much winter, but in Pennsylvania, it was green and stunningly beautiful -- blue skies and flowering trees of every description. 

Puzzles in Symphony Plus

To mark my return to blogging about DBDOC and INFI 90, I pose some puzzles.

FC 116 - Jump/Master Control Relay

I have always been curious about this function code. It is able to "jump" over block processing and

1. and leave the skipped blocks unchanged S3= 0
2. or zero the skipped non-forced rung blocks that are jumped S3= 1

We have data from 600 active and prospective DBDOC builds over the years. Fewer than 5% of these INFI 90 had this function block. Furthermore, many that had it at some time in the past no longer use it.

The block appears to still be supported in SPlus Engineering.

Can anybody add insight to the current thinking about FC 116?

UCB and SPO/PGP Graphics

Once upon a time, SPO SPlus Operations graphics were PGP and used files with extensions .UCBG, .UCBV and so on. This continued into SPO, where the WORK folders used them.

It is obvious that the UCB initials meant something. Can anybody indicate what those letters stood for?

Chaining of FC 126 RDEMUX Blocks

We find numerous FC 126 blocks that have the value of S3 "Block address of next block in link list" incorrect. Here is an example:

Is this an issue? Is it not an issue because the chained RDEMUX block is not used? Are there ramifications that are not apparent from the documentation?

In DBDOC builds, the error codes [316] through [319] and [325] are have the attributes that they report things that violate the rules, but we do not know if they actually cause a problem other than not actually working. If the result is not used, who cares? 

What I could check had the badly linked blocks unused generally. The puzzle is if this ever is worth reporting.