Jump to content

Bobillier

Members
  • Content Count

    209
  • Joined

  • Last visited

  • Days Won

    5

Bobillier last won the day on January 28 2014

Bobillier had the most liked content!

Community Reputation

14

About Bobillier

  • Rank
    Very Active
  • Birthday 01/23/1964

Profile Information

  • Gender
    Male
  • Location
    Rennes France

LabVIEW Information

  • Version
    LabVIEW 2011
  • Since
    2009

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks Antoine I have tested your version, but it seems that it did not work if you have more levels of stacked case structures. I think it's because you don't use "Traverse for GObject.vi " like me. My approach is to select tunnels before applying the change and not the case structure itself. Here my new version with few corrections about your first remarks Set Tunnels Default Values.vi
  2. Thanks Antoine I have not enough test it before propose it. Sorry I working on to correct bug when i receive your last message and modified version. Unfortunely, i can't test it because it's in LV2019 and I only have LV2018. Is there possible to have it in LV2018 ? Thanks
  3. Oups minor correction to avoid debug windows when loaded. Set Tunnels Default Values.vi
  4. Here the QD Instalation: Save it in quick drop plugins folder Usage: Select few unwired tunnels in one or few stached case structure and run the QD Short-cut [U] (can be modify in the vi documentation texte) LV2018 Set Tunnels Default Values.vi
  5. Yes, It's exactly what I'm looking for. Thanks Now I will try to do QD to automatically do this with few tunnels in few stacked case structures.
  6. Hi Do you know if there is a way to switch unwired tunnels to their default values by scripting?
  7. Thanks for this idea. Unfortunately this type of mechanism does not exist natively in the DQMH framework. A future evolution perhaps? I will suggest it on the DQMH forum. Either way, it would be nice if the LabVIEW IDE offered it natively without needing to code it in programs. It's like for the vi which have Modal windows and which we forget to close before launching their proprietary program and which blocks the front panel and prevents us from all actions. Also a small keyboard shortcut in the IDE would be useful.
  8. Ok I will make test with Task Manager, but like it's similar tool, I think than I obtein same result.
  9. Ok Thanks Ensegre. But I have forgotten one detail, The DQMH 5 uses "Start asynchronous call.vi", which load and forget clones. In normal usages, it's DQMH that includes a mechanism to associate the clone to one numerical identifier (ID) and not the clone ref. When you when stopping the clone, you send specific command with ID. But in some cases of problems, the ID can be kill without stopping the clone. In this case, the clone stays in memory, and there is no simple possibility to stop it. I show it in memory with this kind of tool, but when I ask it to kill clone Vi, that generates one
  10. Like this: https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Abort-Asynchronous-Called-VIs-when-the-parent-stops/idi-p/1734792?profile.language=fr
  11. Hello I would like to know if there is a way to kill vi clones that are running in the background without needing to close the project to which they belong. I am currently working on the development of an application based on DQMH and I happen to lose my hand and its VI clones keep references open but not accessible. Preventing me from editing the source vi of these clones. The only solution in this case is to close the project so that it permanently stops these clones.
  12. Hi Today i have one problem with simple TCP client connexion on one serveur. My test program is very simple: Open connexion, Send order, wait reply and close connexion. It work few day correctly, but today it bug and i always obtein error 56 when i run it. My server is ok because i have test in the same time with non LV program and with the same program on LV2011 and all run correctly. The only way is to restart LV2018 to un lock situation., but it's a bit strong as solution. Is there a way to avoid that and find a soft way to identity the blocking point and res
  13. Indeed the case indicated by the low screenshot only happens if we create a new Vi from a project.
  14. Hi hooovahh and ShaunR The old and New are created without project. I have tryed to add case "OS" but LV tell me than this word didn't exist. Is there a way to modify those options outside project? Small detail, the old vi is in LLB.
  15. I try to modify one program and add conditionnal Disable structure but i don't have same choice than if the vi is new. Old vi choice: new vi choice: I suspect it's about compilation because the second isn't compile. But is there one simple method to modify this on the old VI without recreating it?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.