Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by chriscoxtx

  1. On 10/3/2017 at 2:10 PM, TimVargo said:

    Hi Ron,

    I haven't actually tried this, but I can see no reason why you shouldn't be able to update both packages without breaking LVTM.  Sure, the package will complain about "missing dependencies", but that shouldn't matter because by then you've already done installed it and no longer need the package.  The order in which this is done IS important however.  First install LVTM along with the older dependent packages, THEN (optionally) upgrade the GPower and SmartBalloon packages.

    >> So I've downgrade the two support packages so your Task Manager will run.<<
    Are you saying that after the two package upgrades LVTM wouldn't run?  In what way did it complain?


    I have rechecked the package build specs, and both bitness of the OS and bitness of LabVIEW are set to allow both 32 and 64-bit -- so everything SHOULD be compatible, unless it is one of the dependent packages that is the problem (I've not tried this myself on 64-bit LabVIEW).  When you got that error, did the error message explicitly state which "package is not compatible"?

    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 from VIPM. 

    Tested that it worked (it does).   Upgraded "GPower - Error & Warning" to 2012.0.0.31 (the next step up from in VIPM).   LVTM is now broken.  

    The GPower dependencies I see it look for are 



    I have software that relies on GPower Error to be up to date, so I can't avoid upgrading GPower. 



  2. 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... :(

  • Create New...

Important Information

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