Jump to content

ThomasGutzler

Members
  • Content Count

    173
  • Joined

  • Last visited

  • Days Won

    20

ThomasGutzler last won the day on February 24 2018

ThomasGutzler had the most liked content!

Community Reputation

54

About ThomasGutzler

  • Rank
    Very Active

Profile Information

  • Gender
    Male
  • Location
    Sydney

LabVIEW Information

  • Version
    LabVIEW 2016
  • Since
    2003

Recent Profile Visitors

1,993 profile views
  1. Turns out that deleting the VIPM cache (C:\ProgramData\JKI\VIPM\cache) fixes the problem. With the cache folder gone I restarted VIPM and it created it again with fixed permissions and running happily for myself and the system user which is used for CI builds.
  2. You're right, running VIPM as admin works but I'd still like to know how to fix the problem rather than work around it.
  3. No, the account is fine. The CI build (system account) still works. The problem is when I log in manually to debug a problem. I just don't know where to look for those files it's trying to access or which files those are.
  4. Hi, Over night something changed on my windows 10 build server and I can now no longer open VIPM. It just shows the splash screen and then closes again. Here's the log file: =========== START of VIPM 2018.0.0 (build 2025) Error Message =========== An internal VIPM 2018.0.0 (build 2025) Error has occured on: Tuesday August 20, 2019 at 03:19:48 PM = Automated Message Start = Error 8 occurred at Open/Create/Replace File in NI_LVConfig.lvlib:Parse Config to Queue.vi->NI_LVConfig.lvlib:Load.vi->NI_LVConfig.lvlib:Open Config Data (compatibility).vi->DDEFA056211BA4DA4D215C322E067D90->621BFCD461979D3C7127139A69154E03->762BBE85A007 171D5A65B48289D23361->46803A2448FAC5F85BFF8F5C199E9C6F->OGPM Class.lvlib:7D7C5CD8C5D361C01081DF5613237E15->OGPM Class.lvlib:D69AB3997B80ACD75689430E3922612C->OGPM Class.lvlib:OGPM Init.vi->VIPM Splash.vi Possible reason(s): LabVIEW: File permission error. You do not have the correct permissions for the file. ========================= DMA hardware error detected. C:\ProgramData\JKI\VIPM\cache\ngene_lib_deepltk_fpga_addon-1.0.0.45.spec = Automated Message End = = User Defined Message Start = Error(s) Generated in Splash Window = User Defined Message End = = Error Handler Call Chain Start = VIPM Splash.vi = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2025) Error Message =========== Any idea where the files are that it doesn't have the right permissions for?
  5. Or Get Volume Info if you're only interested in the "C:\" part of it
  6. Thanks for throwing ideas around. Let's debunk some of them. I don't think it's a hardware problem, because a power cycle of the DAQ wouldn't fix that reliably and a reboot of the PC wouldn't break it reliably. The DAQ is connected to an Intel NUC directly to the onboard USB port. I tried different ones with no luck. There is no funny software running that interferes with the USB ports PC is set to never sleep. Power management was enabled for USB hubs, so I turned that off and rebooted the PC. Same problem Status Code: -88705 The specified device is not present or is not active in the system. The device may not be installed on this system, may have been unplugged, or may not be installed correctly. Next, I unplugged the USB cable and plugged it into a different port and the DAQ showed up in MAX. Rebooted the PC and it was still there. Turns out not all USB ports are the same. Previously I only tried the ports at the front of the NUC. This time I tried one at the back. That fixed it on both PCs. Fix: Don't plug your USB DAQ into a "charging USB port"
  7. Hi, I'm having a problem with two of my PCs that have a USB-6356 DAQ connected. Every time the PC reboots the DAQ isn't recognised in NI MAX or LabVIEW or NI Device Monitor. The DAQ reappears after I power cycle it. Any thoughts what the problem might be? PC is running windows 10 Pro and LabView 16 Cheers
  8. Great, that helped. There's no installer but I've never been brave enough to look inside that file. Got what I need now. Cheers
  9. Hey Michael, Thanks for the insight. Could you release the installers for the older versions of VIPM so we can fix VIPM installations that got updated/broken by accidentally installing a new version of VIPM with an update of LabVIEW over the top? That would be awesome
  10. I'm on your side, I often do the same if I can be bothered. In rare cases I even edit the GetAttributes to entirely remove the cluster out; not sure if that actually helps but it does break the "GOOP/Add Method" a little. You should update the template and create a pull request. Interesting choice on ignoring the incoming error when you get the attributes.
  11. Hooovahh, as is so often the case, the best solution is the difficult one. Sending the entire content once and then keeping track of changes in a clever way transparent to the "user". Sending only 4 is definitely going to cause pain in user experience. Flavio, no idea why IE works and Edge doesn't, sorry Maybe just stick with Chrome if you can
  12. How about the OpenGDS way of things? Just put a property node on the BD that references a front-panel element. Like this:
  13. I've updated the repo on github with what was in your .zip Unfortunately, I'm still stuck on 2016 so I couldn't even open it ... one day
  14. You should check out master, make your changes locally in a new branch, push and create a pull request. Alternatively, I can add you as a contributor. Then you can go the nasty way of just merging your changes in without creating a pull-request. Or, if you give me some time, I can make those changes.
×
×
  • Create New...

Important Information

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