Jump to content

Antoine Chalons

Members
  • Content Count

    818
  • Joined

  • Last visited

  • Days Won

    24

Antoine Chalons last won the day on May 27

Antoine Chalons had the most liked content!

Community Reputation

94

About Antoine Chalons

  • Rank
    The 500 club
  • Birthday September 10

Profile Information

  • Gender
    Male
  • Location
    Lausanne Area

LabVIEW Information

  • Version
    LabVIEW 2019
  • Since
    1999

Contact Methods

Recent Profile Visitors

8,960 profile views
  1. Wow, ok, thanks for the warning! Not sure my feather weight will be enough to change anything but I'll be sure to ask NI to fix this bug via my own channels.
  2. I think I found the solution from this post on NI forum
  3. Can we set the data type of a CLFN parameter via scripting?
  4. I see. Indeed it's a different approach. Traverse for GO ignores the BD selection. My version could be modified to deal with nested case structures.
  5. here it is in 2018 Set Tunnels Default Values_modified.vi
  6. 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
  7. 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.
  8. Found a solution : https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019Ru8SAE&l=fr-FR Luckily, my colleague has the same laptop with similar NI softs installed so he sent me his tdtable.tdr file and then it all works fine again.
  9. this screenshot comes from a co-worker who has not yet installed 2019 SP1 f4 > no option for VIPM
  10. I don't remember if there was a separate option for VIPM, but I'm sure that if there was I disabled it.
  11. 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
  12. yes it is : https://www.ni.com/fr-fr/support/documentation/bugs/19/labview-2019-sp1-bug-fixes.html
  13. After installing LV2019 SP1 f4 using NIPM I can't launch VIPM (20 or 21) anymore If anyone has an idea to solve this...
  14. Zaphiro Technologies is looking for an experienced LabVIEW Software Developer (full time position) Details and application here : https://zaphiro.ch/career/
  15. 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
×
×
  • Create New...

Important Information

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