Jump to content

Bobillier

Members
  • Posts

    209
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by Bobillier

  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 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.

  3. 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 error message. The reason, I think, is that the clones are in "Load, run  and forget" mechanism and it's not possible to kill them directly.

    And like until one clone ref run, I can't pass source clone vi in edit mode.

    The only way stay to close the project, but it's a bit not practical.

      

  4. 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.

  5. 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.

    image.png.14a5103ee14092603494e70368c6ef5d.png

    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 reset low level tcp connexion ?

  6. Hi All

    Since few times (14/12/2020) and few addons /plugins/ toolkit and  QD installation, i observe sometime crash and/or error rapport génération when i close LV. Just today 0 crash , but 23 "Dump" in error rapport when i close LV.

    Is-there some specialistes who could help me to identify problem source. I send you  today crash rapport to see details.

    Thanks

    Eric

    lvlog.txt

  7. Aristos Queue: I understand than it's not meaningful and if you see instance like all strings or num who have same appearance .

    But i found your proposition to create heritage class a bit excessive. If in your diagram you need 10 intances, you need 10 sub-class.

    Just to visually distinguish them. 🤪 . Perhaps one better Labview feature will be to add one specific Layer on icon with instance number when you place class on the diagram , or have possibility to just modify wire color in the diagram (without  modify class wire color )

  8. Hi Neil

    Your cameras are powered by USB or other power supply ? USB is very delicate when there is different power sources for devices. Few time ago i have encounter lot of problem with this , and solve lot of it with one galvanic converter added on USB Link.

    Something like that https://electronics-shop.dk/usb-isolator

    It's a bit difficult to know if USB link are fall because with this kind of problem is low level protection who are activated and only windows can detect and restart it. Sometime on old PC you need to shutdown PC' power-supply to restart USB Link.

    The only wait i show to see if it fall, is to cyclically request something to camera, and detect when there isn't reply.

    Eric 

  9. Hi, thanks for this upgrade, but I think there is one problem with your VIPM package. When I try to install it, it refers to VIPM2017 who not exist and refuse to install the package.

     

    Oups sorry for my error. VIPM2017 seem existe, but like on JKI site they refer to VIPM2016 .

    Thanks again

×
×
  • Create New...

Important Information

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