Labview 8 SE, Mac OS X, Fluke 187

Hi, I'm new to Labview but not to programming and instrumentation.
I've got a G4 Powerbook with 1Gb and Mac OS 10.4. I've installed Labview 8 SE and it appears to run correctly.
I also have a Fluke 187 DMM which has a USB connection to a computer. I'm trying to use the 187 with Labview.
I found an IVI for the 187 (Fluke 18x series) on the NI Driver board, and have copied the files to the instr.lib directory. This leads
me to believe that Labview can communicate and control the 187.
When I run the 187 example, I am unable to connect to 187 because the Visa resource pick list does not contain any USB entries, only serial entries.
After searching around, I downloaded the NI-DAQmx base package and installed it, hoping it would fix the apparant USB problem.
When I run the NI-VISA configuration utility, it shows 3 Serial resources and 4 USB0 resources.
Any ideas on why NI-VISA doesn't recognize USB?
Thanks,
Russ Harper

Hi Russ,
What version of VISA are you using?  If you aren't using the current version, you should install the latest version.  You need to setup the USB device first before it will show up correctly.  The USB Instrument Control Tutorial discusses this.  If you aren't using the latest version of VISA, updating it could also fix it so that USB is not greyed out on the Driver Development Wizard.
Hope this helps!
Adam W
Applications Engineering
National Instruments

Similar Messages

  • LabVIEW on the Mac at Macworld Expo 2008

    National Instruments had a very small booth at Macworld Expo this year. They were there nonetheless and I asked them a few questions about the current state of LabVIEW on the Mac.
    I also wanted to find out how, and if, a current Windows user like
    myself could use a Mac exclusively and still manage to satisfy Windows
    based LabVIEW project clients. According to Mike Neil, LabVIEW product
    manager, you can have your cake, er… Mac and eat it too. With the use
    of virtual machines (vmware fusion, parallels) or bootcamp
    (which boots the whole machine into Windows), you can now run your
    windows development environment on a Mac and satisfy any Windows
    project requirements. Which leaves me asking myself, why am I still on
    a PC?
    Watch the video:
    http://vishots.com/2008/01/24/labview-on-the-mac-is-alive-and-well-macworld-expo-2008/
    Michael Aivaliotis
    VI Shots LLC

    Hey Michael,
    With Parallels, VMWare, and Boot Camp, there are certainly fewer excuses to not own a Mac!
    Take a look at this article as well:
    Developing Data Acquisition Systems on the Mac with Virtualization Technology
    It dicusses some of the testing done here with Parallels and VMWare.
    Regards,
    Kevin H
    National Instruments
    WSN/Wireless DAQ Product Support Engineer

  • File drag and drop with Labview 7 and Mac OS X Tiger?

    Hi folks,
    I've lost the ability to drag and drop files into front panel file path
    controls, since I upgraded to a new OS X version. Specifically:
    What used to work:
        - Labview 7.0
        - Mac OS X 10.3.x
        - drag file icon from desktop and drop onto file path control (file path control shows path to dropped file)
    New action taken:
        - lost old Mac (Titanium) with OS X 10.3.x
        - bought new Mac (Aluminum) with OS X 10.4
        - installed OS X 10.4 "over" 10.3 disk (did not build from scratch)
    What happens now (three days after birth of new system):
        - all my past Labview apps still seem to run
        - but, if I drag a file from the desktop and drop it onto the file path control I see:
              - file path control
    "outlines" indicating that it understands the intended drag and drop
    action
              - when the file is dropped the file path control does not report the new value
              - And the file path control still has it's old value
    Anyone else seeing this? Am I missing something obvious (Labview or OS X preferences)?
    Thanks in advance,
    RMP

    Hello,
    I don't know how seriously Apple sees the problem, but it doesn't seem plausible that they would rev the OS on account of just this problem with LabVIEW, particularly since we worked around it for the latest version of LabVIEW.  I understand you are working with another engineer at NI via direct email regarding this issue, and that is going to be a better forum for discussing the possibility of obtaining the Apple bug report number.  In the event R&D is willing to reveal it, I presume they will be more comfortable doing so on a case by case basis, as opposed to posting it on the external discussion forum.
    Thank you, and sorry for the inconvenience you have encountered due to this issue.
    Best Regards,
    JLS
    Best,
    JLS
    Sixclear

  • Labview Path to Mac OS X

    Is there any information on the path from Labview 5x or 6x for Macintosh OS
    9x to the unix-like Mac OS X expected in 2001? If I purchase/register Labview
    now, will I be able to upgrade to Mac OS X without buying a whole new $2K
    package next year?
    Thanks.

    I don't know about purchasing issues, but I did see an early alpha of LabVIEW running on Mac OS X during the NI Week convention (2000).

  • LabView for Linux/Mac: integrate external UI controls

    Hello,
    for Windows, there's the posibillity to integrate (UI-)controls written in annother language using ActiveX or .NET. Is there an equivalent solution for Linux and Mac?
    I.e., can I use a GTK or Carbon/Cocoa based control in LabView on Linux or Mac? I know I can utilize external libraries, but this will not allow me to display any UI elements alongside LabView controls on the same Panel without putting considerable effort in subclassing the window, which is also not so easy on Mac.
    Thanks in Advance
    Alexander Hofmann

    Hi Alexander,
    there is no such functionality that allows you to integrate external UI controls under Linux or Mac.
    However you can call Frameworks or Shared Libraries under Linux and Mac in order to communicate with external applications.
    Alternatively you can go the other way round and create Shared Libraries of your LabVIEW application, that can be called within external applications.
    Below you can find some helpful links reagrding this topic:
    Creating a Framework on a Mac for Use in LabVIEW:
    http://digital.ni.com/public.nsf/allkb/A6A6371FE0EA333B86257015005E3400
    Integrating External Code with the Import Shared Library Wizard:
    http://www.ni.com/white-paper/2818/en/
    Best Regards
    Christian

  • MathScript and LabVIEW Student Edition (Mac OS X version)

    Hi,
    Am I right in thinking that in order to "import" or run Matlab .m files in a LabVIEW VI, I need to use the Mathscript feature?
    I have LabVIEW 8.5.1 Student edition installed on Mac OS X 10.4.11 and can't find the Mathscript feature anywhere in the functions pallet - do I need to install something else in order to get this?
    Thanks for the help. 

    Hello,
    The support for Mathscript on a Mac OS X 10.4 (and higher) for Intel-based machine (only) is available for version 8.6. That is the reason you can't find this in previous versions.
    Hope this helps,
    Barp - Control and Simulation Group - LabVIEW R&D - National Instruments

  • File dialog crashes LabVIEW 2014 on Mac OSX Yosemite

    I know that Mac OS 10.10 (Yosemite) is not technically supported by LabVIEW 2014. If that's the only answer to this question, then so be it.
    The following causes LabVIEW 2014 to crash on Mac OSX 10.10 (Yosemite):
    1. Run the native File Dialog in LabVIEW 2014 (Express VI) , using "New or Existing File" as the selection mode
    2. Select "New File..." when the file dialog appears
    3. Enter anything as the file name and click OK
    4. LabVIEW either crashes immediately, or hangs indefinitely and must be force quit.
    Is there an update for LV 2014 (and the RTE) that does support Yosemite?
    This bug makes deploying apps to the Mac basically impossible, Yosemite is the latest OS. Does anyone have a workaround for the issue?
    Thanks.

    LabVIEW 2014 SP1 seems to solve that problem here on my Mac OSX 10.10 system.
    Now Apple may be nice for end users, but all those Apple fan boys sure would think a little different about it, if they had to write programs on the Mac. Apple keeps changing its APIs and their behaviour continously, inventing new APIs (which is fine) in a rapid pace, only to depreciate and remove older APIs at almost the same speeed!
    Microsoft sometimes goes to the other extreme with maintaining backwards compatibility but working with Apple systems surely isn't easy as a programmer (unless maybe when one uses their high level click and point together web design applications, but I don't know that).
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Using MathScript in LabVIEW eval for Mac

    Our university has been slow in getting the LabVIEW 2010 site licensed copy, so we have been forced to use LabVIEW 2010 eval for mac to work with some externally sourced 2010 code that we had to rewrite.
    Recently, I requested and received a copy of the free MathScript module for Mac/Linux (2010). Unlike the experience of a NI engineer with 2009 eval, it installed cleanly with LabVIEW eval 2010. However, the MathScript VI does not appear to available in the palette. Restarting LabVIEW does not seem to make a difference.
    In case this is an eval version / installer bug, it would make sense to wait for our site license to arrive. However, the site license will probably be available after the holidays and I do not want these two weeks wasted in waiting by the students.
    Any ideas ?

    Sorry, I don't have any Mac experience, but if you have access to a virtual windows machine (e.g. parallels desktop) you could just use the windows evaluation version instead.
    LabVIEW Champion . Do more with less code and in less time .

  • Windows virtual machine with labview on a Mac

    I am about to buy a Mac laptop with virtualization software (either VMware or Parallels), then create a Windows 7 virtual machine and put Labview for Windows Professional on it.
    I searched the board and found some discussion of this configuration but it is several years old.
    I would just like to hear from people who have done this and learn from their experiences.  Are there any pitfalls, features that don't work, performance problems, setup difficulties, whatever.  Also, do you prefer VMware or Parallels. 
    One other thing:  I would like to create at least four virtual machines (Windows with Labview development, Windows without LV to test the applications in a non-labview environment, and similar for MacOS}.  Is this a reasonable thing to do?
    Regards,
    David

    Hi David,
    As indicated above I have been running a windows virtual machine using VMware on a 17 inch macbook pro for quite a while now.  I have not experienced significant problems.  Labview and labview generated apps work fine in the virtual environment.
    But would I do it again?  I think not.  The economics don't work.  You can buy a quite capable Windows laptop for less than $500.  The virtual machine alternative costs $200 for a copy of Windows, $80 for virtualization software (Parallels or VMware) plus extra memory on the Mac (I have 8 gb) plus a more powerful machine, etc.  I ended up paying over $3,000 for the Mac hardware and extra software.  The alternative would have been $1,500 for a 15 inch Mac plus $500 for a Windows laptop.
    Also, there is definitely a performance penalty.  Virtualization is not free.  Start up and shutdown times for Windows are more than twice as long under VMware than with a cheap HP laptop.
    It is nice having all my files (Mac and Windows) on the same machine but I could have easily networked the Mac and Windows and had effectively the same result.  Expected benefits, such as a single backup disk for both operating systems didn't work out.  Apple's time machine software views the entire Windows environment as a single lump, so I am still stuck with two backup drives.
    So the good news is that it works.  The bad news is that the costs (in my opinion) exceed the benefits.
    David'

  • LabView 8 and Mac --- no more reliance on Real-Time engine?

    Does Labview 8.0 for Mac now support data acquisition WITHOUT having to export code via the Real Time engine? I've been using Labview 7.0 with E-series DAQ boards on Mac G4s, but have had to boot the mac in OS 9 for proper function of Labview with the DAQ boards. I would LOVE IT if I could now perform data acquition via OS 10.4 with my boards!

    You can definitely use NI data acquisition devices with Mac OS X and
    not rely on the real time cross-compiler.  In January 2005, NI
    released NI-DAQmx Base for Mac OS X.  It currently supports about
    80 plug-in DAQ devices, including M Series and the low-cost USB
    devices, and development is similar to using NI-DAQmx.
    Find out more about NI-DAQmx Base from the DAQ software page or ni.com/mac.
    Also, you may want to check out the new LabVIEW tools for Tiger on
    ni.com/mac.  NI create a widget for viewing VIs, Automator
    actions, and a plug-in to Spotlight for VIs and LLBs.
    -scraggs99

  • Help configuring Thermocouples in LabView for a Mac

    I am trying to set up a LabView program that will read 4 T-type thermocouples attached to a NI 9211 Thermocouple Input and in a NI USB-9162 Hi-Speed USB Carrier. I had no issues when using a PC to set this up with the DAQ-Mx software, but I need to configure a program on a Mac for a laboratory experiment which can record and display the temperatures read by 4 thermocouples. Since Macs do not have the DAQ Assistant, all the tutorials do not work on how to set up an appropriate program. Similarly, Mac only supports the DAQmx Base software, which I have been unable to get to read more than 1 thermocouple at a time (I need to be able to record and display a graph of the 4 thermocouples simultaneously. I was wondering if anyone could offer any assistance on how to appropriately use LABVIEW 2009 to read the thermocouple temperatures, record their temperatures, and display the 4 temperatures on one graph in real time. Thanks.

    I would like to make a clarification about DAQmx Base. Adnan is correct that DAQmx Base is not multi-thread safe, but that limit does not prevent you from acquiring data from more than one channel. Rather, it prevents you from making parallel calls into the driver and forces you to make sequential calls instead. When programming in LabVIEW, make sequential calls by using only one error cluster to connect all of the DAQmx Base calls. You can still have other parallel threads in your VI, but the DAQmx Base calls must all come from the same thread.
    Without seeing your code, my guess is that you're trying to create one DAQmx Base task for each thermocouple channel, which won't work since the 9162 only has one timing engine and the first task will reserve it and lock the others out. Try using the example '<LabVIEW root>/examples/daqmxbase/dynamic/ai/Cont Acq&Graph Voltage-Int Clk.vi' and changing the channel string to "Dev1/ai0:3" and see what happens ;-)
    Joe Friedchicken
    NI VirtualBench Application Software
    Get with your fellow hardware users :: [ NI's VirtualBench User Group ]
    Get with your fellow OS users :: [ NI's Linux User Group ] [ NI's OS X User Group ]
    Get with your fellow developers :: [ NI's DAQmx Base User Group ] [ NI's DDK User Group ]
    Senior Software Engineer :: Multifunction Instruments Applications Group
    Software Engineer :: Measurements RLP Group (until Mar 2014)
    Applications Engineer :: High Speed Product Group (until Sep 2008)

  • Repeatable LabVIEW crashes on Mac

    Confounded by this new problem.
    Platform: Mac OSX 10.6.5 (this problem first cropped up while I was using 10.6.4 - I had previously no problems with 10.6.4)
    LabVIEW 2010
    I cannot suddenly open any instrument subVIs (subVIs created by me open fine) without crashing LabVIEW. It does not matter when the VI was created. I just cannot open the subVIs. I was able to, only last week (and before that).
    Solved!
    Go to Solution.

    Same here, update from 10.6.4 to 10.6.5 and then every time I open a VI a try to create a VISA resource name control LabVIEW crashes. Both LV 2009 and 2010 exhibit the same behavior. 
    By looking at the crash log, it seems that nipal has some problems when loading libSystem.B.dylib.
    I'll try to reinstall VISA and be back to you about the result.
    Ch
    (BTW, look at the funny way the editor interprets the crash log by replacing ": D" with smiley)
    Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
    0   libSystem.B.dylib             0x91362176 __kill + 10
    1   libSystem.B.dylib             0x91362168 kill$UNIX2003 + 32
    2   libSystem.B.dylib             0x913f489d raise + 26
    3   libSystem.B.dylib             0x9140a9bc abort + 93
    4   com.ni.framework.nipalu       0x2679d7df _palPrintToLog + 1547
    5   com.ni.framework.nipalu       0x267a8fc3 0x2671f000 + 565187
    6   dyld                           0x8fe0ed6d ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 235
    7   dyld                           0x8fe0d31e ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int) + 246
    8   dyld                           0x8fe0d2c2 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int) + 154
    9   dyld                           0x8fe0d3d1 ImageLoader::runInitializers(ImageLoader::LinkContext const&) + 61
    10  dyld                           0x8fe0200b dyld::runInitializers(ImageLoader*) + 34
    11  dyld                           0x8fe0b299 dlopen + 558
    12  libSystem.B.dylib             0x913078a8 dlopen + 66
    13  com.apple.CoreFoundation       0x96f8413a _CFBundleDlfcnLoadFramework + 218
    14  com.apple.CoreFoundation       0x96f49b13 _CFBundleLoadExecutableAndReturnError + 1523
    15  com.apple.CoreFoundation       0x96f49511 CFBundleLoadExecutable + 33
    16  com.apple.CoreFoundation       0x96f4a189 CFBundleGetFunctionPointerForName + 57
    17  com.ni.framework.VISA         0x2409cf9c visaLibSymbol + 68
    18  com.ni.framework.VISA         0x2409d4a9 visaLibFree + 1267
    19  com.ni.framework.VISA         0x240a1247 viFlush + 2194
    20  com.ni.framework.VISA         0x240b484e viOpenDefaultRM + 1262
    21  com.ni.framework.VisaCtrl     0x1cff5080 GetIOControlNames + 2570
    22  com.ni.framework.VisaCtrl     0x1cff46f8 GetIOControlNames + 130
    23  com.ni.labview                 0x0086267e TagDriverNameProvider::GetIOControlNames(unsigned long, unsigned char const*, _LStrArray***, LvVariantArray***, LvVariant const*, long, void*) + 98
    24  com.ni.labview                 0x0000fc22 TargetTagNames(LVContext*, unsigned char const*, _LStrArray***, LvVariantArray***, LvVariant const*, long, void*) + 94
    25  com.ni.labview                 0x0000e886 TargetAsyncTags::UpdateAsyncTargetTags(LVContext*, unsigned char const*, LvVariant const*, long, long) + 348
    26  com.ni.labview                 0x0000ed82 UpdateAsyncTargetTags(ObjectHeap*, BasicObject*, long) + 146
    27  com.ni.labview                 0x00f643a9 AsynchUpdateIOControlNames(ObjectHeap*, BasicObject*, long) + 107
    28  com.ni.labview                 0x00f64520 AsynchUpdateIOControlNameLists(ObjectHeap*, BasicObject*) + 22
    29  com.ni.labview                 0x00b4cae8 StdTag:raw(void const*, BasicObject*, long) + 170
    30  com.ni.labview                 0x00b272e2 StdRefNum:raw(void const*, BasicObject*, long) + 266
    31  com.ni.labview                 0x00a556b8 Pane:raw(void const*, BasicObject*, long) + 618
    32  com.ni.labview                 0x00b58530 SuperCluster:raw(void const*, BasicObject*, long) + 100
    33  com.ni.labview                 0x0078ac5c DrawWithoutBackup(ObjectHeap*) + 82
    34  com.ni.labview                 0x0145835b VIDraw(WEvent*, ObjectHeap*, void (*)(void*), void*) + 2223
    35  com.ni.labview                 0x01463826 VIWinProcCore(WEvent*, ObjectHeap*) + 12200
    36  com.ni.labview                 0x0146682a VIWinProc(WEvent*, long) + 448
    37  com.ni.labview                 0x00cf6f46 InternalEventProc(WEvent*) + 32
    38  com.ni.labview                 0x00cfd52a WSendEvent + 296
    39  com.ni.labview                 0x00cf9699 TopLevelUpdate(Wind_t**) + 193
    40  com.ni.labview                 0x00cfb02d WUpdate + 71
    41  com.ni.labview                 0x000092bc OSEventProcessor_MacUI::HandleEvent(EventRecord*) + 372
    42  com.ni.labview                 0x000093e7 OSEventProcessor_MacUI::HandleEvent(bool, long*) + 53
    43  com.ni.labview                 0x00c69033 MainLoop_Default::Run() + 75
    44  com.ni.labview                 0x0000c6c6 MGMain(long, char**) + 272
    45  com.ni.labview                 0x0000cb10 CommonMacMain + 364
    46  com.ni.labview                 0x00002102 _start + 216
    47  com.ni.labview                 0x00002029 start + 41

  • Adding NI VISA RunTime to a LabVIEW app on Mac using PackageMaker

    I would like to create a Mac installer that installs NI VISA Run-time in addition to my application.  Actually, it would also include a 3rd party USB/UART bridge driver.  I'm trying to figure out how to get the NI VISA RT and the bridge driver included in my installer package.  I'm close--I can create a package that throws up 3 installer wizards. The problem is that both the NI VISA RT installer and the bridge driver installer wizards end with "Reboot" buttons.  If a user clicks either of those reboot button too early, not everything will be installed.
    Has anyone come up against this kind of issue?
    Thanks 

    Yup.  Install VISA after your program.  If you set your own installer to NOT require a reboot, then you'll only have the requirement after VISA installs.  This is how I did it I think.
    Either that or I took out part of the VISA installer and re-incorporated it into my own installer.  I'm not in the office now so I can't check.
    I so wish NI would offer an installer package for LV on the Mac.  Having to do this stuff manually is really not worthy of a $$$ product.
    Shane.
    Ps i should read better.  I see you have two packages requiring a reboot.  I think you can extract at least part of the installer package and re-incorporate it into your own installer.  I haven't done an installer on Mac for a while so my memory may be rusty.
    Message Edited by Intaris on 11-11-2009 04:22 PM
    Say hello to my little friend.
    RFC 2323 FHE-Compliant

  • Anybody have an old copy of labview for 68K Macs they don't need?

    I have a few NI NUBUS cards I wanted to use with a 68K version of Labview
    just to mess around. Anybody have an old 68K compatible version of Labview
    in the US they dont want (I think 4.x is the last version made).

    Hi Lastmile,
    I cannot provide you with an old version of LabVIEW, but hopefully I can help you find some useful documentation.  Take a look at the Manuals search on our website to try to locate specific manuals.  When looking for older versions, I suggest searching by the year of release.
    LabVIEW for Macintosh Upgrade Notes (version 4.1)
    LabVIEW Release Notes for Macintosh (version 4.1)
    LabVIEW Function and VI Reference Manual (version 4.1)
    LabVIEW User Manual (version 5: should be very similar)
    Regards,
    Lauren
    Applications Engineering
    National Instruments

  • How to get a windows-created labview file to work on a mac

    I'm trying to open a pretty simple data acquisition vi that was written on Labview 2009 for Windows, using the USB 6211 hardware. I've installed Labview 2010 for Mac OS X (full) with NIDAQMX-base for MAC. The problem is that none of the DAQMX sub-vi's are opening properly. I think it's because they have different names, e.g. in windows labview "DAQmx Create Channel" now becomes "DAQMXbase create channel" or something like that. What is the problem? Have I installed the wrong DAQMX for Mac OS X? 
    Solved!
    Go to Solution.

    Hello oilyfingers,
    As other users have posted, DAQmx Base and DAQmx are two different drivers.  It is recommended that Windows users install DAQmx on their PC.  However, a version of DAQmx Base is also available for the Windows environment.  Your VI should need less changes after installing this driver.
    NI DAQmx Base 3.4: http://joule.ni.com/nidu/cds/view/p/id/2126/lang/en
    If you do not want to install DAQmx Base on the Windows PC, there is a conversion utility which should help automate the conversion of your VI from DAQmx Base to DAQmx code.  This can be found in the link below:
    Conversion Utility: http://joule.ni.com/nidu/cds/view/p/id/446/lang/en
    As smercurio_fc suggested, submit your interest for and update DAQmx version of Mac OS X in the Ideas Exchange.  In LabVIEW 2010, over 10 different user suggestions were implemented from the Ideas Exchange.
    Regards,
    George T.
    Applications Engineering Specialist
    National Instruments UK and Ireland

Maybe you are looking for