chriscoxtx

I'm having the same issue on both 2016/2017. Labview 2017 - 32 bit Labview 2016 - 32 bit Win 7 - 64bit I uninstalled the entire GPower toolset, uninstalled LVTM. Rebooted. Installed LVTM 1.10.0.71 from VIPM. Tested that it worked (it does). Upgraded "GPower - Error & Warning" to 2012.0.0.31 (the next step up from 1.2.0.14 in VIPM). LVTM is now broken. The GPower dependencies I see it look for are <vilib>:\GPower\Error\Error_ClearError.vi <vilib>:\GPower\Error\SubVIs\Filter\Error_FilterMulti.vi <vilib>:\GPower\Error\Error_FilterCodes.vi I have software that relies on GPower Error to be up to date, so I can't avoid upgrading GPower.

I'm also learning/using a 3706A with Labview, and might be able to provide some insight. There are two main ways to programmatically take measurements (that I'm aware of). Calling the DMM directly, with dmm.measure(), and using the Scan Model with scan.execute(). When you create a scan, scan has two properties that will determine how many readings you will take. scan.scancount, and scan.measurecount. Scan.scancount = how many times to run the scan Scan.measurecount = how many measurements to take per channel per scan Also, make sure you set the buffer size to appropriate number with bufferVar = dmm.makebuffer(n), and set the buffer to append with bufferVar.appendmode = 1 (actually, this may not be necessary on a single scan). dmm.measurecount is how many filtered (in your case) measurements to take when you execute dmm.measure(bufferVar). When you set the dmm.filter.count, that is for how many readings to take to create one filtered reading, using dmm.filter.type. You apply dmm configurations to channels, and then implement a scan to iterate over the channels in the scan list. You don't have to use a scan, you could directly call dmm.measure(bufferVar) The 3706A also has Lua, a scripting language, on it. Personally, I'm using scripts that define Scan methods, which I can pass parameters (like the channel list, scan count, etc), to execute scans flexibly, and then reading the buffer back. In Labview, I'm using the Script Execute .vi to execute the scripts. Let me know if this information makes sense edit : Oh, this is from 2015...

I'm currently in the middle of a complete reinstallation of everything. Everything. After multiple issues with 2017 crashing, and DAQ-mx not recognizing hardware (I re-installed it after installing 2017, and it was working fine for a couple months). wish I had seen this post yesterday, but c'est la vie.