Jump to content

Antoine Chalons

Members
  • Posts

    819
  • Joined

  • Last visited

  • Days Won

    24

Everything posted by Antoine Chalons

  1. 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
  2. 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.
  3. I think I found the solution from this post on NI forum
  4. Can we set the data type of a CLFN parameter via scripting?
  5. 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.
  6. here it is in 2018 Set Tunnels Default Values_modified.vi
  7. 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
  8. 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.
  9. 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.
  10. this screenshot comes from a co-worker who has not yet installed 2019 SP1 f4 > no option for VIPM
  11. I don't remember if there was a separate option for VIPM, but I'm sure that if there was I disabled it.
  12. 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
  13. yes it is : https://www.ni.com/fr-fr/support/documentation/bugs/19/labview-2019-sp1-bug-fixes.html
  14. After installing LV2019 SP1 f4 using NIPM I can't launch VIPM (20 or 21) anymore If anyone has an idea to solve this...
  15. Zaphiro Technologies is looking for an experienced LabVIEW Software Developer (full time position) Details and application here : https://zaphiro.ch/career/
  16. 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
  17. The initial question was : is there an open source alternative. You won't make a commercial product, good. Now... are you going to publish the source?
  18. 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.
  19. I've had some difficult clients in the past but it never got to that point 🤣
  20. I've fixed quite a few bugs and changed the way timestamps are handled, now using JDP Science Common VIs for RFC-3339 You can follow on GitHub
  21. I haven't checked how he handled comments. I started thinking about variant attributes to handle them (text and position) but it quickly gets tricky so for now I've accepted to either only read or lose comments.
  22. Oh, and by the way, the VIP is now available on vipm.io : https://www.vipm.io/package/lv_toml/
  23. Let me make sure I understand what you mean by this : You mean, they are ignored and don't mess up with extracting the data, right? (appart from the case in issue #1) Because for me one thing that is a bit annoying is if you load data from a TOML file that has some comments, as soon as you write using this lib, you lose all the comments, or am I missing something?
  24. Just released v2.0.0 There's not a lot in it really, I'm hopping that the effort in improving the error reporting will help future developments like adding support for new data types and comments.
×
×
  • Create New...

Important Information

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