Jump to content

Antoine Chalons

Members
  • Posts

    955
  • Joined

  • Last visited

  • Days Won

    34

Posts posted by Antoine Chalons

  1. [cross-post]

    I'm starting to use LabVIEW 2020 Sp1 on OpenSuse 15 and the event structure editor - I mean the dialog to add / edit handled event - seems to have localization issues.

    Also, a difference from Windows LV, if a constant is connected to the timeout terminal, LV requires that you handle the timeout event... weird.

    Is it normal / known to have these "issues"?

  2. I've been there a few times.

    The treasure hunt is not really fun.

    2 suggestions :

    - if MAX is installed, you can see from there the NI drivers - and versions - installed, that's a good starting point. Careful though, if it's installed doesn't mean it's required for the application to run.

    - if MAX is not installed, I would go to the uninstall utility of Windows and select National Instruments Software, this will launch the uninstall utility of NI, it displays everything installed

     

    Also, you say the customer doesn't want to share the source, but if they have it, maybe you can tell them how to get the information you need.

  3. 1 hour ago, Francois Normandin said:

    Different topic... If the statement below were a regular expression, wouldn't a "?" be more appropriate? It would stand a better chance of matching at least one element 😉

    image.png.a0381a215b2a7237fad026f4841671b5.png

     

    I couldn't help noticing this, when the presenter said "what we're working on for LabVIEW 2022 and - beyond."

    But hey... Let's be positive and hopeful.

    I'm looking forward to playing with G Web Dev Software.

  4. This is not a montage.

    This VI was running and giving expected results.

    I suspect the malleable VI (Get config section from TOML file) to be somehow responsible for this visual artifact.

    After hitting ctrl + B, the broken parts of the wires were removed, I reconnected and that's it.

    Is this a known issue ?

    LV2020 v20.0.1

    image.png.ba575f204353d26c1d4f2f018c616538.png

  5. Here's a versions with a few modifications :

    - fixed the undo

    - do nothing if launched from panel

    - if selection is a case structure, take all tunnels and enable  "use default..." if not already enabled

    - if zero tunnel were effectively modified, fail the undo

    - if at least one tunnel was effectively modified, force recompile the VI to make sure LabVIEW will re-assess the broken arrow

    Set Tunnels Default Values_modified.vi

  6. I have an issue when using this QDP :

    - before using it, my VI has a broken arrow because a tunnel has some missing assignments

    - after using it, the VI still has a broken arrow although my tunnel is set to use default if unwired

    - if I click on the broken arrow, it turns into a non-broken arrow

    What's the best way to force LabVIEW to re-assess the broken / non-broken state?

     

    EDIT : also, as you close the I referenc too early (in the false case), the undo doesn't work.

  7. I'm not sure what you mean... I never install VIPM via NIPM, it only offers an out of date version.

    But being stuck now, I've completely un-installed VIPM and VIPM runtime, and re-installed it from NIPM and I get the same error.

    I guess I should un-install LV2019 and re-install only up to 2019 f3... but that's going to take a long time :(

  8. Well... It's your  -or your employer's- choice really.

    I'm sure you know all the potential benefits of open-sourcing your code. Really, appart from improvement suggestions, what's gonna come at you?

    In my current activities I don't have a need for a sequencer but I'm sure many people would love to take a look and get inspiration, if not more.

     

    Edit : after posting the above I just read again ShaunR's signature : "A positive attitude may not solve all your problems, but it will annoy enough people to make it worth the effort. (Herm Albright 1876-1944)."

    ;D

  9. 4 hours ago, pawhan11 said:

    Has anyone here successfully migrated from TestStand to some open source automation frameworks?

    In our hardware test we have a lot of things happening in parallel and so far I haven't found reliable alternative for TS. 

    What is driving you away from TestStand, just the cost or some technical reasons?

    I mean, you're saying you want to migrate from it, if it's just to cut costs, finding an alternative.. well even if you find cheap/free one, the cost for doing your migration will be proportinal to the size of your existing projects, so think carefully.

×
×
  • Create New...

Important Information

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