|
Thanks for the screen shots.
I can confirm from looking in those sub-VIs that it is calling a process that runs on the command line, so is a separate process.
You do have a virtual circuit warning at the bottom, there will be a text box that may give you the information. This is working correctly, but I think your expectations are for something different to what it actually does. I can't find the VI with the X on
it in the version of CaLab I'm using, but I'd say it is doing exactly what it should and telling you that the PVs aren't available, but I'd need to see that text at the bottom to be sure.
Although I think the Status and severity of COMM INVALID may well be telling you that the PV isn't connected.
Regards,
Kathryn
I have Long Covid, and work an adapted pattern to allow me to give my best to work, please respond to any emails as fits your own working patterns, and I will respond within my own as soon as I am able.
I am Autistic, and this can impact my communication with others, please be patient with me.
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Dariush Hampai via Tech-talk <tech-talk at aps.anl.gov>
Sent: 23 June 2025 16:18
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Re: Some questions about CaLab (Dariush Hampai)
Hi Kathryn,
thank you for your answer. Yoyu're right (Labview on windows). However I don't see any process in Task Manager that can store all the PV informations.
In order to explain better, i Started the SoftDemo.vi, so all the PV presented are stored.
I stopped it and closed it.
Then I create a very simple VI (in attachment the front panel and the block diagram) in order to explain better which is my problem. As you can see, I tried to disconnect in two ways the PVs (by name and all togheter). However the PVs remain stored.
Dariush
<snipped image for sake of those looking in digest, once is enough>
Il 23/06/2025 16:52, Kathryn Baker - STFC UKRI via Tech-talk ha scritto:
Hi Dariush,
I may have been wrong with the caching aspect, but as I say a quick look at the LabVIEW code for CaLab Info has a case structure and feedback nodes which I'd say are in keeping with a functional global variable (this is a LabVIEW VI of a specific type, the
VI doesn't follow that style properly, but I'd say does much the same thing.) So what I think it is doing is asking for the information the first time it is called, and then keeping that information in memory and returning it - depending on how you are calling
it. (Would need to the LabVIEW code to do more than make this as a random stab in the dark guess.) This is supposition based on minimal information. But that might only be the case if the IOC is actually stopped, otherwise, if the IOC is running the PVs will
be there, you can't stop or disconnect a PV at the IOC side easily from the LabVIEW side.
(For the experts, yes, I'm aware of the DIS fields, but I'm not certain the use case here is involving them, and they may be an additional complexity that isn't needed.)
CaLab is certainly the option I've found best when integrating on the LabVIEW side, but you do need a reasonable understanding of what each side is expecting and how they behave to be able to get the best results.
Please note, I have assumed that LabVIEW is running on a Windows system rather than the Linux system, which is again something that would make a difference to how things might be interacting.
So starting CaLabSoftIOC.vi will spawn the IOC as a separate process, that process knows nothing about LabVIEW, it will just run on the same computer that LabVIEW was running on all on it's own. Check out the task manager, you will see it in the list. So simply
stopping LabVIEW won't stop the IOC. I'm intrigued that it survived a restart of the computer though. However, it would restart as soon as you start the VI, so it might be worth trying that again and checking in task manager before starting the IOC.
Regarding the architecture, you need to run the version that matches the OS you are on, as there are DLLs underneath which care about that.
--
************************************
Dr. Dariush Hampai, PhD
INFN - LNF
X-Lab Frascati
Via E. Fermi, 54 (ex 40)
I-00044 Frascati (RM)
Italy
Mail Address:
XLab-Frascati
LNF-INFN
Casella Postale 13
Frascati (RM)
Italy
Room: +39.06.9403.5248
Lab.: +39.06.9403.2286
Mob.: +39.06.9403.8025
Fax.: +39.06.9403.2597
************************************
|
