Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 04/18/2021 in Posts

  1. Working on the next JSONtext functionality, which is features to improve support of JSON Config Files. See https://forums.ni.com/t5/JDP-Science-Tools/BETA-version-of-JSONtext-1-6/td-p/4146235
    3 points
  2. VISA is ok but not everyone uses it so...
    3 points
  3. 2 points
  4. Boss: There's no "i" in team. ShaunR: There's no "u" either but there is "me".
    2 points
  5. I'm left to assume you are referring to VI Week, which was put together in a week or two, completely by the community.
    2 points
  6. We've been building executables and vipm packages on Azure for quite a while now and most builds work. Our driver package (6500 files) takes about 45 minutes on a pretty low spec PC. Applications usually build within 10 minutes. All our builds are LabVIEW 2018 64bit though, no multi-version doom. But there's no reason why you couldn't build multiple versions. With Azure build pipelines you have the choice of either self-hosting your build server or using an Azure VM which you have to install the complete toolchain on. Azure VMs can spin up/down on demand which is supposed to save you
    2 points
  7. The LabVIEW 2021 Beta is now available for download. https://forums.ni.com/t5/LabVIEW-2021-Public-Beta/LabVIEW-2021-Beta-Now-Available/td-p/4144143
    2 points
  8. Here is version 2. As far as I know, there are no issues with it Requires LabVIEW 2019 or later. Not compatible with earlier versions. Y Controls Support - Version 2.0.0.0 Installer.zip Y Controls - Version 2.0.0.0 Source.zip
    1 point
  9. Just saw Nintendo announce this programming game, and a few comments comparing it to LabVIEW. It looks pretty cool, and a fun intro to graphical programming. I don't have a Switch, otherwise I'd probably pick it up. https://www.nintendo.com/games/detail/game-builder-garage-switch/
    1 point
  10. The link will work if you remove the extra period at the end https://rat.hampel-soft.com
    1 point
  11. What do you mean "no significant new features"? 2017: Malleable VIs, 2019: Maps and Sets, 2020: Interfaces I'll give you the rest though. I have about as much hope in NI Connect as I did during NI's marketing event last year. And NI's communication lately has been lacking at best.
    1 point
  12. This link doesn't work. Maybe you need to setup an alias on your website. The correct location seems to be https://www.hampel-soft.com/release-automation-tools-for-labview/
    1 point
  13. Python has taken over the areas where LabVIEW traditionally dominated in test and measurement There are a couple of reasons for this not least that it's multi-platform and opens up more cost effective hardware options such as Raspberry PI's.
    1 point
  14. Have you seen Sam Sharp's presentation on Test Complete?
    1 point
  15. You're right, I was thinking about the 16-Jun-2020 "National Instruments is now NI" event. 😏
    1 point
  16. Maybe it will be a two-day version of last year's virtual event, with more new fonts, colors, and NI employees forced to repeat "so inspiring". 🙃
    1 point
  17. I reported that in 2018: CAR 605085. I don't think they are planning on fixing it. Must use C strings under the hood.
    1 point
  18. Do you have access to any hardware? "Technical task" is a bit vague... A few years ago I started playing around with https://projecteuler.net/ It was a fun way to practice algorithms with LabVIEW, I think I solved the first 50 or 60. I'm not sure if this is "technical" Any idea on what you like to do? Any special interest? What's your course?
    1 point
  19. Decided to update this to 2020 and release (this is 0.3; I never posted 0.2): jdp_science_lib_malleable_buffer-0.3.0.8.vip
    1 point
  20. So just adding info here for future googlers. There is an NI KB article on how to cleanup the cache here: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019KdtSAE&l=en-US In there it also mentions an ini token that eliminates cache creation completely:
    1 point
  21. Seems VIMs can no longer be used in polymorphic VIs either. I don't think this is a good idea. The VIMs I've played around with (before the type case structure was introduced) relied on at least one terminal having a type which would dictate the undefined types due to the nature of the internal polymorphic VIs (like a Queue or DVR). This is why I was trying to get a VIM to create a DVR which "should" define the type across all connected VIs which would solve this problem. In a nutshell, I'm expecting this set of VIMs (rightly or wrongly) to behave like the Queue, Notifier et. al. primi
    1 point
  22. I can't find them in the examples finder (tried a few different words). The button on VIPM shows the directory with them, though. FWIW. I hate the example finder. You neeed to know the right words for what you're searching for and it's a lot of clicks and typing to get there (ignoring the excrutiating pain of actually creating the Example Finder special files). It's much preferable to have them in the same pallet as the VIs; as you had originally. They need to take that requirement off of the tools network checklist.
    1 point
  23. So I wanted to make a VIM that was essentially "Convert input into 1D string array". If you passed it a 1D array of anything it would convert each element to strings (similar to the debug VIM that ships), but passing in any scalar would do assorted things depending on the scalar (single item array for things like numerics, but a Path would split into each component, and different methods for other types). I thought it would be a good idea to have an option that if an enum is passed it, the array passed out would be the list of all of the options converted to strings. They way to get thi
    1 point
  24. Good points all round, I actually never knew compact libraries couldn't be accessed by other labVIEW versions. I uploaded this work as a finished solution, which I think is very useful. I can't release the code for the Master or Client libraries, as I use a plethora of different COM libraries. But!, I will upload the .net45 library I built for Google Drive and Sheets (which is probably the bits you want), these are LabVIEW VI's with .NET assemblies, which control the API calls. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Edit: Library Att
    1 point


×
×
  • Create New...

Important Information

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