Smartphone support in LabVIEW 8.2 ?

I've exported the program on to pocket pc and it works fine by building the application with windows mobile 5.0 for pocket pc device module in LabVIEW 8.2. However, "not windows CE application" message appears while i run the same application on smartphone. How can i build an application which can run on Windows Mobile 5.0 for smartphone platform?  The labview 8.2 pda module only contains pocket pc module, how can i add smartphone module as target device?   By the way, I've installed Visual studio 2005 and windows mobile 5.0 sdk for smartphone in my pc, but still cannot find the solution to the problem.

Try LV 8.2.1 & PDA Module 8.2.1.
It's free.
Plz call NI local office to get free.

Similar Messages

  • NI-DAQmx support for labview could not be found

    Hi, I am pretty new to LabView. I was using VC++ to programming for my USB-6215. Just curious how LabView works, so I try to follow the "Introduction to Taking an NI-DAQmx measurement in LabView" and configure my USB-6215 in LabView. However, when I try to gererate codes for the DAQmx task name control, an error message pop up as "Error:NI-DAQmx support for labview could not be found. Please reinstall NI-DAQmx".  I did reinstall NI-DAQmx, but it doesn't help. This error occurs anyway. Any idea how it happens and the solution is highly appreciated. Thank you.
    Jingyu 

    See attached
    Paul Falkenstein
    Coleman Technologies Inc.
    CLA, CPI, AIA-Vision
    Labview 4.0- 2013, RT, Vision, FPGA
    Attachments:
    MX picture.PNG ‏35 KB

  • Is the Aardvark OEM I2C Host Adapter supported with Labview?

    Hi All,
    I am now looking forward to use Aardvark OEM I2C Host Adapter (http://www.totalphase.com/products/aardvark-oem-i2c/)
    in LabView2013.
    Question:
    Is this device supported with LabView?
    How can I use this device?
    Best Thanks,
    Jessie

    Yes
    We have plan to buy and use Aardvark OEM I2C Host Adapter and use it with LabView2013.
    I am searching if this device already has LabView VI's for I2C communication.
    I am not sure If we can use the VI's for Aardvark I2C/SPI Host Adapter to Aardvark OEM I2C Host Adapter.
    Before we decide  to buy Aardvark OEM I2C Host Adapter we just want to make sure that we can use it.
    Best Thanks.
    Jessie

  • Upnp service support in labview

    I'm looking for info on uPnP support in LabVIEW. Anyone know of any existing support for this out there? Any help is appreciated. Thanks, JH

    Hi Jason, I have attached a .llb (V7.1) which should discover UPNP devices on the network. The ini file will need modified on the NI folder with the following line:
    SocketSetReuseAddr=TRUE
    Also, during development I would disable the Win XP firewall.
    The vi is taken from NI's examples under networking with a couple of mods - nothing spectacular I'm afraid. After discovery you can use the NI web browser (specified IP and Port number for the device) and XML parser to extract the info from the xml files that each UPNP device holds. This should give you all the actions and variables required to control the device. I used TCP vi's for this action - the only pain was formatting the SOAP messages to the correct format.
    Hope this may be of some help!
    PC.
    Attachments:
    UPNP DISCOVER Root Devices.llb ‏1051 KB

  • Usrp driver 1.3 do not support for Labview 2013 64 bit ??

    Hello, dear all
    Is anyone install the latest USRP driver 1.3 for LV 2013 64 bit ?  I found there is no version for 64 bit LV 2013. 

    Currently the 1.3 driver supports only LabVIEW 2013 32 bit (even on 64 bit computers.)
    The LabVIEW 2014 version will support 64 bit and will be available to download very soon.
    Please check here within the next week or so:  http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/ssnav:drv/q/usrp/

  • Install datasocket support for labview 8.6

    Hi,
    Can I get a link to download a Datasocket Support for Labview 8.6 or higher?
    Thanks
    Ken

    Installing the Latest Version of DataSocket and DataSocket Server
    Problem: 
    I would like to download and install the current version of National Instruments DataSocket and/or DataSocket Server on my computer. Where can I find the latest version of this to download it from National Instruments' website?
    Solution: 
    The latest release of the DataSocket libraries and the DataSocket Server is installed with the LabVIEW Run-Time Engine. Go to the Drivers and Updates web page at ni.com and search for "LabVIEW Run-Time Engine" and sort by Version to find the most recent version of the LabVIEW Run-Time Engine.
    http://digital.ni.com/public.nsf/websearch/40295802535E31B686256E91001859AB?OpenDocument
    Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
    If you don't hate time zones, you're not a real programmer.
    "You are what you don't automate"
    Inplaceness is synonymous with insidiousness

  • GPIB support on LabVIEW-RT

    I would understand why the GPIB interface on the PXI-8175-RT is not supported with LabVIEW-RT.
    The same interface is supported on the PXI-8146-RT.
    As I have some performance problem to communicate with the Ethernet link, I would use the GPIB link to transfert data between 2 systems.

    Hello,
    That is correct. At this time, GPIB is only supported on the 8146 RT and 8156B RT controllers. LabVIEW RT does not support the GPIB controllers on the 8175 and 8176; also, PXI GPIB cards are not supported.
    There are a few easy alternatives to using the ethernet link. One easy solution is to use your serial ports. Another solution is to use your I/O modules, like Analog or Digital lines on a Data Acquisition board to share information between systems.
    I hope this information helps.
    Regards,
    Dafna

  • NI-DNET support for LabVIEW 2013

    We are using currently NI-DNET 1.6.6 with LabVIEW 2011. I installed now also LabVIEW 2013 on my computer and tried to sync the set of drivers with my LabVIEW 2011 installation.
    Well, it seems that NI-DNET doesn't support LabVIEW 2013, at least officially. The NI-DNET and LabVIEW Version Compatibility shows that NI-DNET 1.6.6 supports LabVIEW 2011 and NI-DNET 1.6.7 supports LabVIEW 2012.
    The NI System Driver Set November 2013 list NI-DNET 1.6.7 as part of the driver set. When I try to install it, there is no LabVIEW 2013 support.
    My question is actually, if there is a plan to include NI-DNET support for LabVIEW 2013 or later in the driver set?
    I copied the vi.lib\DeviceNet and vi.lib\nidnet directories from LabVIEW 2011 to 2013 and I can load my programs without any problems. I still didn't build an executable and didn't run them on the test fixture, but the projects can be loaded in LabVIEW 2013 without any brocken VIs. Should I expect any problems running LabVIEW 2013 with the NI-DNET 1.6.6 or 1.6.7 driver?
    Nick
    Solved!
    Go to Solution.

    I would update our drivers right away, but unfortunately the NI-Industrial Communications for DeviceNet doesn't support the PCI-DNET cards. We have probably close to 30 of those in the test fixtures. So, we need to use the NI-DNET 1.6.x driver anyway.
    It will be nice if the NI-DNET installer can copy the NI-DNET VIs and supporting files to any LabVIEW version, well maybe any 201x. I hope until 2020 we can replace the old cards :-)
    Nick

  • "Import string" method not supported in LabVIEW 7.1

    We have made an application that support multi-language (English, French, etc.). In LabVIEW 6.1, we used the "import string" VI method to support this option. The method was executed just before to open front panel. The code was based on this example found in NI Developer Zone:
    Translation/Localization Tools in LabVIEW
    (http://sine.ni.com/apps/we/niepd_web_display.disp​lay_epd4?...
    But surprise in version 7.1, this method can't be loaded without the diagram block. So the built application doesn't support it! It works only in the development interface. Why this change?
    If someone has an idea to solve this, let me know.

    If you build that example into an EXE under LabVIEW 7.1, it should work fine as long as you add the non top-level VIs as Dynamic VIs and add the language files as Support Files when you create the executable, making sure to specify in "Custom Destinations" that you want the string files to end up in the same directory as the EXE.
    Your point about the method requiring the block diagram is correct, according to the help for the method. However, I think the diagrams will be available to the run-time engine as long as you haven't purposefully removed them prior to creating the EXE in the manner described above. Maybe someone else can chime in on this point, because I know the App Builder changes a lot with every new major LabVIEW version (and sometimes, with minor versions too!).
    In any case, I just did a test where I downloaded the example you referenced, created a .BLD file as I indicated above, and got a successful executable that was able to use the Import VI Strings method to load the desired language at run-time.
    Regards,
    John

  • I have some B/W video cameras(analog) are they supported by Labview

    i have some B/W video cameras that I wanted to use with LabView but they are not in the list of supported cameras under LabView, but they are still very new and they work great and they are small and light weight which are two important things that I need. Can I still use these? Or should I look into buying some new ones? The website for these cameras is www.x10.com, model number SC21A, thanks.

    Hi magnusrules,
    The National Instruments Framegrabbers can adquire video formats like RS-170 or CCIR, it depends on the model of the framegrabber. Here is information about the analog video signals:
    http://zone.ni.com/devzone/conceptd.nsf/webmain/0c19487aa97d229c8625685e00803830
    I saw the datasheet, but I did not find the type of signal. It says RCA, so maybe this can be of some help:
    http://digital.ni.com/public.nsf/websearch/A247A92A91FDEFAE86256BA50051F28B?OpenDocument
    http://sine.ni.com/nips/cds/view/p/lang/es/nid/11356
    Since the camera has a RCA connector, and it's BW, it could be RS-170, but we need to confirm it with the manufacturer.
    Tania Lozoya

  • DAQmx support for Labview 8.0

    I am having a problem with the current DAQmx Drivers,
    The system used to run perfectly when using labview 8.0, however, after the installation of labview 2009
    The DAQ library in the labview 8.0 folder is missing.
    I tried to install the older version of the DAQmx (Legacy) but i still can't get the library back in labview 8.0 folder.
    Would it possible to get those files ?
    Thanks,
    Ahmad Aladdasi
    Mechatronics Engineer
    Solved!
    Go to Solution.

    Hello again,
    I tried to uninstall everything related to labview on the computer using msiblast, but still having the same problem, even after removing every labview newer than 8.0 files.
    When I try to install DAQmx 8.6 it says a newer version is available.
    I deleted the registry stuff to.
    I had to keep labview 8.0 because it is the version i want to use plus i don't have the CD to install it, so i kept it and it's support files.
    Can anyone send me the DAQmx library for labview 8.0?
    Makesure it is the Vi files not the installation setup because that one will give me the same problem, " Newer Version is installed" problem.
    Don't refer me to any extra links about installing, cuz honestly i have seen them all....
    Thanks,

  • Changes to Unicode support in LabVIEW 8.6

    There seems to have been a change in the way LabVIEW handles alternative text input between 8.5.1 and 8.6.
    In 8.6, if I try to use type something in Hebrew (alt+shift in Windows changes the input language), the words come out in the wrong order (the first word appears on the left instead of on the right). The actual order of the letters in the word appears correctly (right to left), although sometimes the first letter in the text gets stuck on the left size.
    If I try to use Hebrew in a label, I get a message telling me that I can't type a Unicode string into labels and enums.
    In all of these cases, copying a string from Notepad and pasting it into LabVIEW displays it correctly (including in labels).
    I have tried doing this with UseUnicode INI key set both to T and to F and it happens in both cases.
    This SUCKS. Big time. Really.
    I know that LabVIEW doesn't officially have support for right to left languages, but at least in previous versions it would sort of behave. I'm pretty sure this isn't what people who were expecting more Unicode support were thinking about.
    Does anyone have any idea for a workaround? The only two I can currently think of is copying and pasting or writing a small VI which will reverse the text on demand, both of which are bad solutions.
    If there's a patch planned, fixing this will definitely get my vote as something that deserves going in there.
    P.S. I'm not sure why the Hebrew input is treated as Unicode. If I'm not mistaken, changing the input language in Windows should still result in ASCII characters and in previous versions it does (the Hebrew chars in the code page LabVIEW uses in 7.0 start at ASCII E0 and in 8.6 it starts at D005 with the next letter being D105).
    P.P.S Did I mention this sucks?
    Try to take over the world!

    I'm going to suggest something really strange as a workaround, but, trust me, I have historical precedent for suggesting this...
    Try editing the keyboard shortcuts for LabVIEW and change Quick Drop to be something other than ctrl+spacebar. 
    Why might this help the problem? When I developed the  alignment grid, I thought that ctrl+# was a very intuitive shortcut key for toggling the grid on and off (since the hash symbol looks like a grid). What we found was that when the OS language was set to French, users could no longer type many of the extended grammer characters. The reason was that a critical scan code for the extended character sets overlapped with the scancode for ctrl+shift+3. In LV 8.6, we added ctrl+space, which is the first non-alphabetic shortcut key we've added since the ctrl+#. It might be that whatever keyboard scancode is used for Hebrew happens to overlap, and the code is being translated into a shortcut key for LV instead of a typed character.
    I have no evidence that this is what is happening, but it is the only analagous situation that I know of, so I suggest it as something to try. 

  • What are the protocols supported by LabVIEW

    i want to know whether SNMP and lanwark protocols are being supported by LabVIEW

    The following webpage should answer your question about SNMP:
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/4cd3625a939a77de852564050047d3bd?OpenDocument
    Don't know about lanwark.
    Chris_Mitchell
    Product Development Engineer
    Certified LabVIEW Architect

  • Traditional DAQ support in LabVIEW 2010?

    Hello,
    Been researching this a while and I must admit, I am quite confused. I am trying to run a program written in LV 7.1 using traditional DAQ vi's in LV 2010. I think what I need are traditional DAQ drivers, but I cannot find the correct drivers. Plus I'm unsure if I will run into compatability issues. If someone could point me in the right direction I would very much appreciate it!
    Old machine:
    PCI 6040E
    LV 7.1
    Win XP
    New Machine:
    PXI 6251
    LV 2010
    Win 7
    Thanks
    Solved!
    Go to Solution.

    Dirk H. wrote:
    ...  Finally, due to errors, I was forced to LabVIEW 2010.
    What errors?
    Finally, due to errors, I was forced to LabVIEW 2010.  Now I'm looking for the traditional DAQ(to minimize my work) for the old software.
    LabVIEW 2010 would require Traditional DAQ 7.4.4. http://digital.ni.com/public.nsf/allkb/F4E76EC05118F72D8625773000672298
    Dirk H. wrote:
    I have a PCI-6503 and a PCI-MIO-16E-4(along with a PCI-GPIB board).  ...  Am I forced to upgrade any or both of the DAQ cards?  All of the cards appear to be installed successfully by viewing them in Measurement and Automation.
    This page lists the required DAQ software for each device: http://zone.ni.com/devzone/cda/tut/p/id/6910. That page indicates both of your devices are supported by Traditional DAQ 7.4.4.

  • DAQmx support for LabVIEW 2010

    FYI to those downloading LabVIEW 2010 from NI web site:
    After Installing LabVIEW 2010 (download from web site), I noticed that there is no support for DAQmx (i.e.. VI libraries) in NI_DeviceDrivers-February2010 DVD (my latest copy).  Your have to download and install DAQmx 9.2 drivers (the first to include LabVIEW 2010 support).
    Additionally, If you were using Traditional NI-DAQ (Legacy) 7.4.4 VIs in a prior version of LabVIEW, you must do one of the following:
          1. Uninstall current Traditional NI-DAQ (Legacy) 7.4.4 installation and re-install after completing LabVIEW 2010 installation.
              Reason: Traditional NI-DAQ (Legacy) installs support only for the latest version of LabVIEW found on the system.
    Or
          2. Copy the the "<previous LabVIEW>\vi.lib\Daq" directory and all it contents to a new "<LabVIEW 2010\vi.lib\Daq directory.  This way you can use Traditional NI-DAQ in both versions of LabVIEW.

    I didn't have DVDs, I had to download.
    Yes it was a mess.  The device driver download took forever (NI can't help that).  The installation took beyond forever (what else can be done?). 
    I was disappointed that I had to do all of this backing up of legacy folders and restoring them after installing the device drivers.  Why does NI always have device drivers and toolkits install to the latest version of Labview only?  Why couldn't they leave the legacy stuff alone??  I still use LV2009 and wanted to try LV2010.  This involved a whole lot of trouble and time. 
    NI needs to provide a much easier way to upgrade, while still allowing previous versions to work without modification.  Most people who upgrade will not completely abandon the older versions.
    - tbob
    Inventor of the WORM Global

Maybe you are looking for