Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


MikaelH last won the day on November 27 2023

MikaelH had the most liked content!


Profile Information

  • Gender
  • Location

LabVIEW Information

  • Version
    LabVIEW 2016
  • Since

Contact Methods

Recent Profile Visitors

14,758 profile views

MikaelH's Achievements

  1. I think you have multiple Y scales, so the plot that don't seems to be correct is probably using the 2nd scale that you are not showing. FYI, if you zoom in the Excel export will only show that data, and it's very strange that it using 1k and 10k instead of 1000 or 10000
  2. FYI, we have switch back to 2023Q1, which don't hate VIMs. We can now finally build our applications without any LV crashes and any modifications to get the build to work.
  3. Also try running the DLL in any thread. That will probably speed up the execution >100 times, but if the DLL is not thread safe you might get crashes.
  4. BTW, can you also update this library to make LV2023Q3 to build applications with these VIMs to work ;-). We use these VIMs a lot, and in LV2023Q3 several VIs stops the builds complaining that "VI is not in memory". And to get the App building to accept these VIs I have to replace your VIMs with the old style OpenG version :-(.
  5. We just migrated to LV2023. and I thought we should update this library as well to the latest. That did break a lot of code. E.g. So the new version didn't accept the old non-typedef sort direction, so I've modified it. Also the array filter vim, don't support reference wires anymore (e.g. Ctrl Refs). I also had to add I32 here The old version did handle it
  6. Do you want it in Normal Display format like thsi: BTW this loop of generating the HEX string is not fast, there are much faster ways of doing it
  7. Change the limit to 65535 instead of 10000 in the Windows Registry I have a file named: Max GDI Objects.reg With this content: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows] "GDIProcessHandleQuota"=dword:0000ffff
  8. Mostly we use 3 levels for the instrument driver (InstrumentBase <- InstrumentType(e.g. PowerSupply) <- RealInstrumentDriver (but also a simulated type) We currently have 398 classes in our instrument hierarchy, 60 different InstrumentTypes such as: (TemperatureControllers, Robots, WeldingLasers, GlueDispensers, StepperMotors)
  9. I've had issues on Windows 7, but no issues on Windows 10 yet. When our SW needs it and can't find it we let the user install it on the fly running this exe file: MicrosoftEdgeWebView2RuntimeInstallerX64.exe ..and that has never failed yet, maybe it could cause issues if you've installed the 32 bit version first?!?
  10. FYI, I've found the WebVIEW2 WebBrowser integration into LabVIEW + a fancy DataGrid JavaScript library is a much flexible approach. We've posted the LV-64 bit supported WebView2 support here: https://github.com/ANSCenter/LcWebView2 I use http://tabulator.info/ to make nice DataGrids in LabVIEW.
  11. Here is a start of the color selection, can someone see if we can make it faster? ColorPicker_GUI_DrawColorRectangle.vi
  12. I just have to implement it first 🙂 Not sure which UI style would be the best
  13. I would make my own popup, so it looks better, something this:
  14. You just need to add a magical VI here to get it working:
  15. I have several instances where I get null back for different datatypes, what I have to do is just to ignore the Errors from the JSON VIs. So it will convert everything it can' but when trying to convert NULL to a string it will be empty or for an int it will be zero. Ideally it would be good to be able to say when you find Null for: A strings use "" or "NULL" A INT use 0 or -1 For DBL/SGL it uses NaN and that is prefect.
  • Create New...

Important Information

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