Leaderboard

We also use DSC for NSV events and Citadel logging and find it to be a powerful tool. The DSM and MAX interfaces are helpful (DSM much more so) but for complex data we still have to write our own methods. We have had issues with Citadel reindexing databases on occasion (which can pretty much bring the computer to a halt temporarily) but we are implementing strategies to avoid this (most notably, archiving and deleting databases every day). (It is worth noting that we are writing a lot of data at relatively high logging rates. The performance here is really pretty good.) For the record, we have separately implemented dynamic events in RT on VxWorks (not supported by DSC) by using the "Read Variable With Timeout" method and generating a user event when we read something. Surprisingly simple.

I think GregR means that you provide a function that produces an event registration for just the encapsulated User Event, and that registration is clustered with another registration for any other events before being passed to the event structure. Thus you only need one member VI. However, this doesn't keep the User Event encapsulated, because it can be accessed in the event structure frame itself. See below: -- James BTW, I learned only recently that one can use a cluster of multiple event registrations for handling by the same event structure; does anyone know if there are any performance differences with using multiple registrations instead of a single one?

"Items incorrectly claimed by a library" is perhaps a bad description. A better term might be "Items that are claimed by the library that do not reciprocate the claim". These items are ones where the library has been saved to disk and records "the item at this path location is a member of me" but the items themselves (VIs or sublibraries) were saved not claiming to be part of the library --- they may claim to be part of no library or another library. This sort of thing generally happens when you move files around on disk instead of inside LV or when you rename the library but don't save the VIs in the library. It can take a while to untangle.