move mouse over image to see more
Q: How can I do a quick check that CA Lab-installation works properly?
A: Use the full installion and run "startDemo.bat".
Q: I get a lot of warnings on first start of your VI. What's the problem?
A: The CA Lab-VIs need the absolute path to caLab.dll. This absolute path varies from computer to computer. LabVIEW looks for the right path at first run and reports that library paths have been changed. You should save these changes.
Q: CA Lab-VIs aren't executable, what can I do?
A: Check following:
Q: What is the maximum number of PVs monitored, tested up to now?
A: We have simultaneously monitored up to 1.000 PVs. But we're sure the limit is higher. A large number of PVs takes significant time to initialize when a PV is passed to the other. It's better to pass the PVs as an array. Reading, writing and monitoring after initialisation is no problem.
Q: Can CA Lab generate its own EPICS channels, or only connect to already defined channels?
A: CA Lab is a pure client application. If you want to generate your own channels, you can use "softIoc.exe". You can find an example in the demo application of caLab.
Look at /db/demo.db for variable definitions.
Q: Will caLab work with any version of LabVIEW 64bit?
A: Yes, CA Lab does since V1.3.0.3. Please be sure to download the 64 bit version.
Q: I'm wondering what the timeout parameter does.
A: The timeout is the timeout for initializing and for retrieving the value for the FIRST call. After first call of any PV a background task monitors PVs and every call will be served by cached values from this task.
Q: I use caLabPut. When should I set the parameter "synchronious" to TRUE?
A: If it is necessary to wait til all record processing of written PV has been finished before next value can be set then you should set the connector of caLabPut "synchronious"=TRUE.