Francois Aujard

Ok, thank you very much ! And sorry if my question is stupid..... I learn by myself 🙄 And there are some very good people here whom I trust to answer my questions. 💪

OK I have read your link. But what happen with the select? Labview create 2 copy : one for the case True and one for the case false and choose after the correct response?

Thank you very much for your explanations @LogMAN 🙏. It's clearer for me. as I understand it I can do that : Synchronization is managed by the mutex, which is called up a IPE structure (accessible as a one-to-one like a FGV). This mutex serves only as a “semaphore”. 😊 What exactly happens during the memory copy if you don't use an IPE structure?

Thank @cordm for your reply. OK, It's the same as a semaphore ? And how you decided what type of value to put in the opening of the VI "New Data Value Reference"?

Hello everyone, Is someone can explain me. How works this modbus VI? Two questions : I never used the "in place element structure" what's the point of using this type of structure? Is it better FGV? Is it important connect "Modbus master out" at the end of this structure VI or, if it plug to the input "Modbus master in" it will do the same? This VI use a memory control, how it work ? (three question sorry 😊) Kind regards. François A.

Thank for your reply. I have use recetly a Windows tablette and I don't have this problem. I don't kown where is the Windows setting for this paramter

Hello everyone, I have a button boolean with mecanical action : Switch Untin Released. I used the Event Value Change, when the Boolean is True I move my motor, and when is false I stop my motor. This it's OK when I use the mouse. But when I used my touch screen, I receveid the 2 events when I remove my finger. I add the 2 events Mouse Down and Mouse Up, and exactly the same problem. When I click on my button, the button don't go to the true position. But when I remove my finger, I received the four events : Mouse Down ; Value Change ; Mouse Up ; Value Change. Is someone have an idea why I have this problem?

It's a good idea ! 😊

Yes, I knew I could wire the error directly, but I have another condition with booleen. In the end, after thinking about it for a while, I don't really need it anymore, the queue state is enough for me. And it's also true that I'm not 10ms away from closing this sub-VI. Thanks for your advice

Hello @Mads, Thank you for your reply. I followed your advice. I destroyed the queue in the main VI, and used the error output from the state of this queue to terminate the dynamically called VI. It works fine, thank you 🙏. I hadn't thought of that 🙄.... do you know why I'm looking into : View=>Browse Relationships=> Reentrant items I see the number of VIs that I've actually called, in running. But sometimes I also see some that are stopped. Should I add a close reference at the end of the VI? Can a VI close its own reference?

Hello @crossrulz, I presume you meant to write 2024, not 2014. For the moment we're stuck with the 2021 and 2022Q3 versions. We are not a fan of the subscription system. We find it relatively expensive (NI has made up for its hardware losses due to COVID on the software side), and we've never really had the information we needed to go the perpetual license route. We used to work directly with National Instrument, but now we have to go through a reseller. And I have to say that I have a lot of trouble with the reliability of the answers they give us. They're salesmen... We're a small special machines company, and there are mainly 2 of us working with labview. On the other hand, we need to activate a lot of licenses during development. There are several machines in the workshop at the same time, sometimes more than 10. The reseller told us we could only activate 3 PCs per license. We'd like to upgrade labview, but if I can't activate more than 3 machines at the same time, without having to pay for additional development licenses, it's not interesting for us....

I have another question about the attached image. I have a VI (I'll call it Test.vi) that dynamically calls an error monitoring VI. The function of this VI is to stop the calling VI in the event of an error. If there is no error, the calling VI closes the called VI using a boolean reference. In my main program, the "test.vi" VI was in a condition structure, and my code worked. I decided to call test.vi dynamically, and was surprised to find that my error VI never closed. The reason, I think, is that the reference is destroyed when the VI is no longer in memory, so I never see the true state of the Boolean. So I added an OR with not reference. And it works. I replaced the boolean reference with the reference of the calling VI, and looked at the Execution.State prorpiety node VI. Again, it worked. I tried to put my VI test.vi back into the main program without a dynamic call, and it no longer worked. The Execution.State always returns a running state, even when the VI is not executing. I have two questions: - Why is the VI running when it's not executing? Even if I close the reference, it doesn't change anything. - Is there a method or property node other than Execution.State that lets me know if the VI is actually running? I don't know if I've made myself clear...

Thank you all for your answers In the end, only the first one is useful. Is there a case where I might prefer the 2nd or 3rd solution over the first? In fact, the 2nd solution will always be waiting for the end of execution, even if you set the option to call and forget

Hello everyone, Can someone explain to me the difference between these three possibilities of calling a VI? I don't quite understand the difference, especially between the top 2... Thank you

Hello everyone, I have in my possession a NI PCIe 6346 card. I want to do fast acquisition both on a counter input and on several analog inputs. Ideally, the threshold of one analog input should trigger fast acquisition on both. 1) I've managed to do this for the analog input task, but it doesn't work for the counter task (conditions 4 and 5). Does anyone have any ideas? 2) I've replaced my analog trigger with a digital trigger. Can anyone tell me why condition 2 is NOOK, but condition 1 is OK? For me it was two methods doing the same thing. 🤔 3) Does my VI start the 2 tasks at the same time (I've seen examples of condition 3, but I'm not familiar with them)? Translated with www.DeepL.com/Translator (free version) Acquisition Rapide.vi