I suspect that your very very old LabVIEW program used data acq device hardware counters and that the subvi's in question are part of the old traditional NI-DAQ API.
I'm among the old-timers still around here who used to do counter/timer stuff under that old driver, but not in about the last 15 years now. It looks like some kind of counting/timing function was being done in hardware on this old app, but there's not much clue as to what it might be.
What do you know about the needed functionality of this application? What are the signals, what must it *do*? What Data Acq hardware do you have available to use?
Being very new to LabVIEW is an additional complicating factor. Some of what I see there would make me want to scrap the whole thing and start over from a blank page. This might be more than you're ready to tackle. However, being new to LabVIEW *also* means that you can get yourself into trouble trying to make small mods to existing code too.
If someone needs a program to do whatever that program did, they should be able to define the functionality and behavior. That's step 1. If that requirements definition sounds too complicated to tackle yourself, you might want to consider hiring help for the implementation.
-Kevin P
P.S. You should plan to transition to the DAQmx driver, even if it requires you to buy new data acq hardware. Traditional NI-DAQ has already reached its dead end.
CAUTION! New LabVIEW adopters -- it's too late for me, but you *can* save yourself. The new subscription policy for LabVIEW puts NI's hand in your wallet for the rest of your working life. Are you sure you're *that* dedicated to LabVIEW? (Summary of my reasons in this post, part of a voluminous thread of mostly complaints starting here).
