LabView PDA and Pocket PC2003

I am using Pocket PC 2003 with the LabView PDA.All the documentation deals with Pocket PC 2002. Are there any changes with the Pocket PC 2003? Also I wrote a test application and downloaded to the PDA and that does not seem to execute!Is it bcos of the 2003?
Thanks
Sprasad

I have exactly the same question. I have LabView PDA 7.0 and a Pocket PC 2003, VIs run ok on Pocket PC 2003 but the problem is when I try to run VIs that call DLLs. The ones that work perfect in Pocket PC 2002 don't work in pocket PC 2003.The DLLs were created using EVC 4.0 SP3.
Are these incompatible?
Thanks
BTW: the link does not work

Similar Messages

  • LabVIEW PDA and WinCE

    Greetings all,
    My latest stab at the bleeding edge of LabVIEW capabilities has brought me to yet another question for which I haven't found an answer... Does the PDA module take advantage of the fact that Win CE is a deterministic OS or are thread prioritization and interrupt servicing isolated by the RTE from the OS? My hunch is that LV PDA doesn't make use of the deterministic capabilities of CE, but I really hope I'm wrong.
    Chris
    Chris
    Practical Physics, LLC
    www.practicalphysicsllc.com
    National Instruments Alliance Partner
    Certified LabVIEW Developer

    Thanks for the input, JLC.
    I probably should be a little clearer... I was concerned that the thread prioritization in PDA on CE worked like it does when running standard LV on XP (for example). It is my understanding that the prioritizing is only applicable within the RTE. Additionally, I don't believe there is any way under XP to set the interrupt for a DAQ card to a higher priority than the mouse, for example, without extensively reconfiguring the system after disabling ACPI.
    Upon further contemplation, however, it would seem that if WinCE is guaranteed to service an interrupt within 5ms, the pressure is on me to write code in the PDA module that can deal with the data within the required system response time minus the 5ms used to acknowledge the interrupt. 
    Please let me know if I am not interpreting something correctly.
    Chris
    Practical Physics, LLC
    www.practicalphysicsllc.com
    National Instruments Alliance Partner
    Certified LabVIEW Developer

  • Problem with the Labview PDA and file transfer.

    I�m using PALM Tungsten T3 to run some applications. The OS environment is Windows XP. When I try to download a data.txt or data.dat file to the pc using the Hotsync, it gives me an error. There is installed datalogmgr that is the application that allows files exchange between Palm & PC.
    Error message
    Se ha iniciado la sincronización HotSync 03/09/04 16:12:12
    Aceptar Calendario
    �
    fopen(C:\PDAdata\19_samples.txt) failed
    LabVIEW Datalog Conduit ha fallado la sincronización
    I have installed the LVPDA_Patch_70f1.rar file (in the correct order). I tried also with another file generated by PDATempData (in the examples) and it didn�t work. I tried Also to delete datalogmgr and download it again. I tried to instal
    ll Labview COnduit again. Any idea?

    I know its been a long time since your post. Did you make sure to have the directory that you want the file transferred into created on your PC before the sync. If the folder isn't there you will get that error.
    Dan
    Don't drive angry. Don't drive angry!

  • LabVIEW PDA gives error 12 when opening file

    I can create a file with LabVIEW PDA with Pocket PC 2003, but when I try to open the file I always receive error 12 "Some system capacity necessary for operation is not enabled."
    Can someone help me to solve this error ?
    thanks in advance for your help.
    Nico

    On the PDA, File Open returns error 12 when you are trying to open a datalog file and the datalog type you specify on the funtion does not match the datalog type on the file header.
    Regards,
    miko

  • LabVIEW PDA reports COREDLL.DLL error when using Call Library Function Node

    I'm trying to build a LV PDA app that calls an external DLL file built using embedded visual C. When configuring the Call Library Function node I select the stub DLL, configure the I/O parameters and select OK. When the configuration dialog closes I get the following error:
    LabVIEW: LabVIEW.exe - Unable to Locate Component
    This application has failed to start because COREDLL.DLL was not found. Re-installing the application may fix this problem.
    I do not get this error when using the configuration dialog in the example VIs.
    Any suggestions as to the cause and/or the solution?
    Thanks,
    Ryan

    Hello -
    When you create a PDA VI that calls a DLL, you must include the .c or .lib file that corresponds to the DLL. Take a look at these documents:
    LabVIEW PDA Module Build Errors with VIs that Call DLLs
    Why Do I Receive Errors When Calling a C++ DLL from a Call Library Node Using the LabVIEW PDA Module...
    How To Call External Code in LabVIEW PDA for Palm OS
    H
    ow To Call External Code in LabVIEW PDA for Pocket PC
    Hope this helps!
    S Vences
    Applications Engineer
    National Instruments

  • How to build a dll for labview pda, which uses the intel ipp primitives in it

    Hi all,
    For my application, I need to call a c dll from Labview PDA, and in the c function i need to use intel IPP function. When i call my dll, i get an error saying the ippfunction i use, say "ippsCopy_16s missing c or vi file". Can someone tell  me what I might be doing wrong?

    Hi Vani,
    When using a DLL in a PDA there are some special considerations you have to take. Please take a look at the following knowledgebase describing the process.
    Eli S.
    National Instruments
    Applications Engineer

  • Labview PDA module 7.1 and Windows Mobile 5.0

    Hi!
    In spite of reading that Labview PDA module is compatible with Windows Mobile 5.0, I've tried to compile an application for Pocket Pc 2003 in my device (which has a Windows Mobile 5.0 OS) and it doesn't work. It seems that the process fails when the executable is being sent to the device. Does anybody know what happens and what can I do to solve it? It's strange because the same application compiles properly with a device with Windows 2003 OS!
    If it was not possible to solve, could I create an executable directly in my Pc and then copy it in the device?
    Thank you very much for your help!!!!
    Greta

    I believe it was said that the problem with writing for CE 5 is only with downloading the application, which you need to do manually. You can do this by copying the EXE to the device's shared folder. ActiveSync should automatically recognize that and synchronize the folders, so you will have the file on the PocketPC. Another option is to copy it to the Mobile Device folder, which should appear under My Computer.
    Try to take over the world!

  • Anyone worked on LabVIEW PDA module for Pocket PC?

    LabVIEW 7.1 PDA Module is claimed having the new features:
    * DMM support for helps you build portable instruments using a PDA
    * Tab controls, graph zoom, and additional control customization improve development of professional applications for PDAs
    Does anyone has any working example for the ZOOM and for DMM4050? The NI website's example for DMM does not work for LabVIEW 7.1 PDA Module.

    Installing the driver for the NI PCMCIA-4050 is a little more complicated than other installations. You will have to follow the exact procedure stated in the "NI 4050 for PDA Readme.htm" file. I pasted the important information here:
    Installing PDA files:
    Place nirlpdriver.dll and NI4050DLL.dll in the \Windows directory
    Place the NIRLP 4050.exe in the \Windows\Start Menu directory
    Installing LabVIEW support:
    Copy the LabVIEW\NI4050 folder into the C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\PDA folder
    Copy the ni4050.mnu file into the C:\Program Files\National Instruments\LabVIEW 7.1\user.lib folder
    Installing LabVIEW examples:
    Copy the LabVIEW\Examples\NI4050 folder into C:\Program Files\National Instruments\LabVIEW 7.1\examples\PDA
    Getting Started
    Before the NI-4050 will be recognized by the PDA, you must run the NIRLP 4050.exe. This EXE will install the registries needed by the PDA to recognize the hardware as well as a test routine which allows you to verify that the device is properly installed.
    Once the device has been tested, you are ready to begin building your own LabVIEW PDA application with the NI-4050.
    If you are new to developing PDA applications with LabVIEW, read the LabVIEW PDA Module User Manual.pdf for getting started. You can find the manual by going to Start>>Program Files>>National Instruments>>LabVIEW 7.1>>Module Documents>>LabVIEW PDA Module User Manual.
    There are several examples which come with the NI4050 for PDA. You can find these examples in the C:\Program Files\National Instruments\LabVIEW 7.1\examples\PDA\NI4050 directory.
    When building code for your PDA which includes the NI4050, make sure to manually add the NI4050DLL.lib file in the LabVIEW 7.1\vi.lib\PDA\NI4050\Include directory. To do this, in LabVIEW go to Tools>>Build for PDA and then select the “Source Files” tab, press the Add File button and browse to the NI4050DLL.lib file.
    Without these actions, your application will not work. Make sure that you install the NI PCMCIA-4050 driver AFTER an optional NI-DAQmx Base install.
    Please let me know if you are still having issues after following all the directions from the readme-file.
    - Philip Courtois, Thinkbot Solutions

  • Labview pda module: how can I resize image dynamicall​y in an applicatio​n?

    Hello every one,
     I am currently working on the development of an application on a PDA (brand Nomad) and whose OS is Windows Mobile. So I am using the PDA module of Labview 8.6.My problem is the following one: in my application I would like to be able to load images (thanks to their path) in pictures indicators. I load images with the labview “function PDA Image File Load.vi” and then my problem is that images don’t fit with the size of the indicator, and so I am only able to see the left top corner of the image…Of course, I would like to see the entire picture, but I don’t know how I can modify or resize a picture with the PDA Module, where most of the property nodes (zoom factor, scrollbars…for picures) are not available.Has someone ever faced and fixed that problem?? Any help would be really appreciated!!   PS: Attached is one part of my application!
    Attachments:
    cameracapture.vi ‏21 KB

    Hi,
    Indeed, like Romain D. said you have some interesting discussions where you can find some customer's experience like yours :
    How Do I Put A Picture or Image On My LabVIEW PDA for Palm Front Panel?
    How to Resize a picture 
    Scale image on PDA (Pocket PC)
    Placing an image or picture on Labview PDA pocket PC 
    Picture and PDA 
    PDA Picture Control Scrollbars
    Let me know what happens.
    Regards,
    Steve M.
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    >> Vidéo-t'chats de l'été : présentations techniques et ingénieurs pour répondre à vos questions

  • Winsockread Error in LabVIEW PDA

    Hi all. I am currently trying out the VI server example given in the LabVIEW PDA toolkit but i keep getting this error "WinsockRead error Error Code: 10054.
    The LabVIEW example project I am using is "VI Server- Pocket PC.lvproj" and I have loaded the "CallByRef Wave - Pocket PC.vi"  into the PDA. I have a WIFI connection to a PC and have manually assigned IP address to both the PDA (192.168.100.101) and PC (192.168.100.100). I have verified my WIFI connection is working by using the "ping 192.168.100.101" command on my PC.
    Also, I am configured my VI server correctly by selecting the enabling the TCP/IP protocol and ActiveX under the VI Server Configuration. The port number I used is 3363. I have also added the PDA IP address (192.168.100.101) to the Machine Access List.
    When I try to run the example program on the PDA with the IP address "192.168.100.100" and a port number of 3363, I will get the error. Can anyone give advice on what I have missed out or done wrongly?
    I forgot to mention that the remote program "TargetWave.vi" on the PC is loaded in memory and opened in LabVIEW also.
    Thanks in advance.

    D.Com,
    I just thought of something else to try. You said you are using port 3363. The program was initially set up to use Port 3865. Did you change the VI server properties (From the project, right click on the my computer icon>>properties>>VI server: Configuration) to port 3363 or just the control on the front panel of the CallByRef Wave.vi? Both must be set to the same port.
    Secondly, you may have to open a port in your firewall if you are using WindowsXP SP2. Initially I would completely disable the firewall and see if that solves the problem. If it does, then enable the firewall and create an exception of the port you've specified (3363).
    As for using the trial version, this should have no impact on the performance of the toolkit.
    Best Regards,
    Chris C
    Applications Engineering
    National Instruments
    Chris Cilino
    National Instruments
    LabVIEW Product Marketing Manager
    Certified LabVIEW Architect

  • LabVIEW PDA

    Hi! Everyone
    I have to develope an application for PDA in LabVIEW. Can someone tell me how and where to start....the interface is with RS485. The PDA needs to scan for attached devices and report devices available.
    There are some parameters to be acquired
    and data to be displayed.
    I am not sure if it is a palm or pocket pc. If I start with the development of the Vis on LV Express, do I need to know the OS before hand....will that affect the VIs?
    Can I use LV express base package to develop the VIs or do I need LV PDA toolkit for the development?
    And if once I have deployed the program on the PDA, can I run it in debug mode and can I delete the program from the PDA or not?
    If there are link which I could go through or programs to be taken as the star
    ting point...will be appreciated.
    Thanks!!

    You Could develop your applications using LV express. The only problem is that all the features are not supported on the Palm or the PDA. You also need to know before hand as to what your execution target is as LAbview has a Palm module and a PDA module that are sold seperately. The link below has the PDA manual.
    http://digital.ni.com/manuals.nsf/websearch/948645EDBFA39E1786256D2C0066B381?OpenDocument&node=132100_US
    You could also look up the knowledge base for specifics for the PDA and Palm.
    You can delete the program from the PDA. There are some example code and documentation at
    http://www.ni.com/support/

  • Labview pda+filesaving

    I am writing a labview pda vi to allow an ipaq 3630 to act as a receiver for an external serial device so that datalogging can take place.
    Serial comms works ok but I'm now looking at file storage on the PDA so that I can create, read or write to a file (in a datalogging capacity as an extension to the above serial software) but I'm having some problems with this. Ideally I'd like the file to be created in a format that can also be opened and edited in Pocket Excel. I've scanned the help stuff but its very limited in this area. Has anybody had success with this?
    Fadenoid

    bobster,
    Modules must match up with the version of LabVIEW you are running. In your case, you will have to upgrade the PDA module(now known as mobile module) to version 2009.
    You can use our Online Upgrade Advisor to get a quick quote using your serial number(not part number) or you can give us a call at (888) 280-7645

  • Function of the further Programms when I use LabVIEW PDA

    Hi,
    I write my Bachelor Thesis over a PDA Application where I´ve create with LabVIEW PDA.
    Before I could use the LabVIEW PDA I must install few programms.
    1)VisualStudio 2005 Standard         
    2)Visual Studio 2005 Command Shell
    3)Windows Mobile 5.0 SDK for Pocket PC
    4)eMbedded Visual C++ 4.0
    5)eMbedded Visual C++ 4.0 SP 4  
    Anybody knows what functions this Programms have? I don't need it for the whole time.
    Thanks for your answer  
    capunze
    Message Edited by capunze on 05-16-2006 10:40 AM

    The way I understand it (I don't have any official knowledge, and I wouldn't mind hearing an explanation either), LV PDA converts its code into C code and then uses eVC to compile the code for the PDA. I assume you're using LV 8.0 because Visual Studio wasn't required in previous versions. Maybe it's also needed now in order to compile the code.
    Try to take over the world!

  • Error message when building an application for Labview PDA

    When using LabView PDA module to build an application for a PDA target, I receive the following message: "Error building executable. Unable to create file". Why is this happening?
    When looking at the error log, it reads "The system cannot find the file specified."
    This happens even when looking at one of the Labview PDA example VI's, so it is not a result of the VI containing functions of features not supported by Labview PDA.
    When installing Labview PDA, I installed files as follows, and in this order:
    (i) Labview 7.1 (installed previously)
    (ii) Microsoft eMbedded Visual C++ 4.0
    (iii) Microsoft eMbedded Visual C++ 4.0 SP 3.0
    (iv) Microsoft SDK for Windows Mobile 2003-based Pocket PCs
    (v) Microsoft ActiveSync 3.8
    (vi) NI Labview 7.1 PDA module for PocketPC
    (vii) DAQmx Base 1.0 for PDA or later
    Any ideas?

    Did you attempt to add the _wordsub.llb and _excelsub.llb files to the application as support files?  I believe in LabVIEW 8.0 instead of adding the entire LLBs you should just add the _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi as dynamic VIs.  I think I've seen a similar post on the discussion forums in the past that recommended this.
    If this suggestion doesn't help, please reply, and attach a simple VI and .lvproj file demonstrating the problem so I can investigate further.
    Good luck,
    -D
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • Palm and Pocket PCs with bluetooth cards

    Has anyone had any experience of using LabVIEW 7.1 PDA with Pocket PCs or Palms fitted with a bluetooth card?
    Most Palms I've come across e.g. the Tungsten series are bluetooth enabled internally, so is it a case that LabVIEW can only see the internal BT device when the native BT vis in LabVIEW are being used to create apps?
    Similarly, I've used the same BT VIs for Pocket PC 2003 devices with BT hardware already inside (specifically Ipaq H2210,which ran faultlessly) but I am unsure whether a Pocket PC running 2003 with say a CF card can be utilised using those same BT comms VIs (same goes for a Palm with OS5 and a Bluetooth SD card)?
    Cheers

    Hello Bill,
    I've used the tdk go blue usb adapter hooked up to a PC and have been able to communicate bi-directionally with it using an Ipaq 2210 pocket pc. I'm waiting for the bluetooth card for my Palm 515 so I can replicate this functionality.
    The TDK uses the Cambridge Radio chipset which is also used by other dongles, such as the D-Link DBT-120 and these work with the XP service pack 1 generic bleutooth drivers (Q328183 I think), also SP2 and hence LabVIEW. If you are intending to use the TDK, you don't need to load up the suite as long as you have these drivers. (The TDK blu2i development kit incidentally has these drivers on the CD, but not sure if the dongle alone comes with these).
    If you do have the driv
    ers its just a case of using the high level Vis for both PDA and PC to communicate with each other as client and server.
    If the PDA is the client you would set up this using the Open Connection VI and serial service UUID eg:
    00001101-0000-1000-8000-00805f9b34fb
    For the PC you'd make this the server and use the create listener VI with the above UUID then carry out a Wait on Listener function, and as soon as the other device comes into range you should be in business.
    You can also use standard serial comms if you have a virtual port set up for the dongle, but timing can then become an issue. The native bluetooth VIs in LabVIEW take care of all that, and you don't need to set up a serial port in "My Bluetooth Places", as you effectively use the UUID which creates the serial port service you require.
    Hope this helps but please drop a line if you have any more questions.
    Cheers

Maybe you are looking for