Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


ThomasGutzler last won the day on February 24 2018

ThomasGutzler had the most liked content!

Community Reputation


About ThomasGutzler

  • Rank
    Very Active

Profile Information

  • Gender
  • Location

LabVIEW Information

  • Version
    LabVIEW 2016
  • Since

Recent Profile Visitors

1,912 profile views
  1. Or Get Volume Info if you're only interested in the "C:\" part of it
  2. 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"
  3. 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
  4. 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
  5. 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
  6. 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.
  7. 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
  8. How about the OpenGDS way of things? Just put a property node on the BD that references a front-panel element. Like this:
  9. 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
  10. 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.
  11. No me neither. Looking at the BD example, it seems the in-place structure was blown up by the Bundle by Name node. Is it even possible to change the font used in those? Yeah, I'll report it. All build machines have scaling set to 100%. It's only my laptop screen that is set to 200% and I can't take that out of the equation. All our developers have high DPI (200%) laptops and regular (100%) 2nd monitors. I can't edit the scaling on the build machine because it's headless and the setting is grayed out when remoting in.
  12. I do. Code is developed on a surface tab with high DPI (200%) screen plus a 1080p 2nd monitor. I wonder if it matters which screen the BD was on last... Unfortunately, my eyes are too old to run the tab at 100% I'm already building on a different machine - in fact, I've tried two different ones. Same mess for both. The only time I don't get a problem is when I build locally, but that's not an option since all our builds go through Jenkins. I do use application font but I was hoping not having to go through thousands of VIs to change their font setting. But it seems that's the only way Has anyone scripted that? Thanks guys
  13. Hi, I'm using VIPM to build my device drivers and project templates into vi packages which are then used by other developers. During the build process some of the front panel elements get blown up as if the text size was changed and then reduced again but the size of the control doesn't return to its original size. A similar thing happens on the block diagram. Some structures (set to auto-grow) end up wider in the package than in their original source as if a BD element inside the structure was increased in size and then decreased again. While that's not a terrible thing to happen in the drivers, it really kills the templates because the first hour is spent to fix up cosmetics... I've attached some screenshots. Anyone know how to fix that?
  14. OpenGDS does a good job with updating VI icons. It lets you design your class icon and then automatically updates all VIs in that class. Uses the file names to generate text in the lower part
  • Create New...

Important Information

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