Jump to content

MikaelH

Members
  • Content Count

    801
  • Joined

  • Last visited

  • Days Won

    43

MikaelH last won the day on November 23 2020

MikaelH had the most liked content!

Community Reputation

179

1 Follower

About MikaelH

  • Rank
    The 500 club
  • Birthday 12/25/1972

Profile Information

  • Gender
    Male
  • Location
    Sydney

LabVIEW Information

  • Version
    LabVIEW 2016
  • Since
    1996

Contact Methods

Recent Profile Visitors

8,196 profile views
  1. You can do this. I thought that was the main reason for adding interfaces ☺️. BTW, if you're using LV2020 and classes, the new OpenGDS beta version makes it easy to work with interfaces 🙂
  2. We modify code while LV is running all the time 🙂 We even have a Quick Drop shortcut that toggles a Sub-VI's Loading Option between "Load with callers" and "Reload for each call".
  3. Hi, I just posted my GOOP Training course material here: https://forums.ni.com/t5/GDS-Goop-Development-Suite/GOOP-Course-Material/td-p/4101113
  4. Same here. It locked the whole OS for some reason when I start NXG.
  5. And when can we add G code extension to NXG's IDE? I'll move over when I get GDS running there 😉
  6. I would use Active objects. Using the OpenGDS tool I created this in no time, see attached project. ActiveObjects.zip
  7. We use 5000-5999 for project/application specific Error codes, and then different ranges for other common components. But for an instrument drivers, we might use one of the existing LV-error codes, and for that we use a small tool to find a good error code. ErrorCodes.vi
  8. Company made version, based on Ref-based OO and active objects.
  9. I remember that I had to change my code using the "cmd /c" when changing over to Win10 from Win7. Before I didn't have the "working directory" wired instead I specified the full path in the command. e.g. cmd /c "c:\Temp\file.bat" Are you running WIn10?
  10. There is a brown/private property node that can suppress all dialogs. If you don't have access to this property node, you can find a sub VI that does this for you here.
  11. Yes you can...if you did build the exe file with debugging on.
  12. Thanks guys, yes the option: "2018 SP1 Patch" is indeed the f4 patch
  13. Where did patch LV2018SP1 f4 go? http://www.ni.com/product-documentation/55001/en/ I could download the f4 patch using these URLs (just by taking the f3 patch and rename the url): http://download.ni.com/support/softlib/labview/labview_development_system/2018 SP1/Patches/f4/LV2018SP1_f4Patch-64.exe http://download.ni.com/support/softlib/labview/labview_development_system/2018 SP1/Patches/f4/LV2018SP1_f4Patch.exe But there is no official download link on NIs webpage, and I can't find it in NI Package Manager, but I'm sure it was available there a few days ago. Does anyone know?
×
×
  • Create New...

Important Information

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