Problem initializing phd 2000 pump in LabVIEW

I am a LabVIEW rookie and I am trying to write a small programe controlling a Harvard Apparatus PHD 2000 pump. (I did find the driver for the pump from NI and it works fine, but it is too complicated for my purpose)
I ran into problems at the beginning. I tried to use "simple serial.VI" found in LabVIEW examples and see if I can initialize the port and get any response from the pump. However, I cannot get any expected response from the pump though I set up the parameters right (baud rate 9600, stop bit 1, flow control none, etc).
The commands I tried out are all from the pump manual, including some very basic commands such as VER (showing software version of pump), etc. The port is working fine through checking using HyperTerminal. Anybody has idea why this happens?

When you configure the serial port, did you enable sending a termination character? When you use HyperTerminal, and you hit "Enter" at the end of a command, that "Enter" gets sent to the PHD pump. LabVIEW normally sends exactly the characters you provide. If you wire a single-line string, it won't include an end-of-line termination character (Carriage Return in this case). You can configure VISA to append a termination character after each transmit, as shown here: http://forums.ni.com/t5/LabVIEW/PHD-2000-Pump-driver-change-infuse-rate/m-p/2637177#M788074

Similar Messages

  • Communication problem with FP-2000 and Labview 7.1

    I am using the FP-2000, DO-403 and TC-120 modules with Labview 7.1, being run on a host computer via an ethernet connection.  The setup has operated flawlessly for ~2 years; recently, I have noticed that while a VI is running on my PC, connection to the FP module ceases.  There is no pop-up "connection error" in my VI, and the all the power and status LEDs on the FP modules are normal.  I can still interact with the VI on the front panel while it is running, but nothing is passed to the FP module.  I have tried communicating with MAX when this occurs and receive a "no connection" message.  Is there a simple solution here, such as rebooting the FP module?  Or is it time to invest in new hardware?
    Justin

    I am having a very similar problem with my cFP-1804 and Labview 7.0.  I have no problem initiating communication over ethernet, and the vi will run perfectly for hours or even days.  Inevitably, however, at some point there is no longer communication with the cFP-1804.  Data is no longer being passed either to or from the cFP-1804, and MAX will show that the device is not connected.  I also will not see any pop-up error message that says the connection has been lost, either from Windows or from Labview.  The vi will just continue to run as if nothing has happened.  Turning the power to the cFP-1804 off and then on will always resolve this problem.  Since I am using the cFP-1804 primarily for data logging, however, this behavior is particularly problematic as the system will record nothing but zeroes until I discover that the communication has been severed and perform the manual power cycling.
    I have been unable thus far to determine the cause of this problem.  Any help would be greatly appreciated.
    Thanks,
    Derrick

  • Shuffle problem going between 2000 and XP?

    I recently got my girlfriend a shuffle and it worked fine with my computer, which is running 2000 and has the latest iTunes updates and iPod updater. The only problem I have on my computer using her Shuffle or my Nano is the amount of songs I can transfer at once (which is usually 20, 10 on shuffle).
    Anyway, I'm not sure if Shuffle was the latest version out of the box or not, but it didn't need updating from my computer, unless it was automatic. She took it home to try it on her computer (running XP) and iTunes wanted to format it. I gave her the updates off the site (since she doesn't have internet) and told her to try them since I didn't think it was needed. She tried that and it still managed to screw it up. So I had her restore it and that worked, but she decided after she got it to work to plug it back in again to play with the songs and it had to be restored again and then restored a few more times after that.
    So I was wondering if there was anything I can do to fix it, like uninstall everything that deals with iPod and install the version that came with Shuffle then reinstall the new version over it along with the updater? Take it away because she's apparently bad with technology and have her only deal with my computer for updating her song list? Or was there another way to make it so she won't be restoring shuffle everytime she changes computers? Since I figure it should be compatible enough to go between different versions of windows with different versions of iTunes and still work with no problems.
      Windows 2000  

    That's probably it, since she didn't have any of the music because it was with me. From what I remember, she went around that, and used restore after she backed up all the music. But from what I remember it takes no time at all to a few minutes to restore my Nano, but the Shuffle doesn't have a screen to tell you what's going on (and I find the updater is unreliable with info sometimes).
    She has told me she did the same thing about 20 times before it started to work. So she must've been restoring and thinking 'this isn't doing anything' and ripped it out and eventually gave up and let it do it's thing.
    But I'll have to deal with it next time when she tries to sync it up with my iTunes, so maybe it won't be a big problem this time around.

  • Oracle 8i EE Install problems on Windows 2000

    Problem 1 - LENGTH OF INSTALL FILES PATH.
    The Oracle Universal Installer was coming up fine, but the "Next" button wouldn't do anything. After much trial and error, I discovered this to be related to the path of the install files. Rather than burning to CD, I had copied the install files into a directory C:\ORA816 - when I renamed this directory to just C:\O, the "Next" magically began working. This problem only occurs on Windows 2000, not NT4.
    Problem 2 - CREDENTIAL RETRIEVAL FAILED.
    I got this error (ORA-12638) from the Database Configuration Assistant. This just happened, so I haven't had a chance to figure it out. Has anyone encountered/fixed this problem in Windows 2000? I am running the install as Administrator.
    null

    Re: Problem 2. Just found out that this problem is resolved by removing the line SQLNET.AUTHENTICATION_SERVICES from
    %ORACLE_HOME%\network\admin\sqlnet.ora
    (see: http://technet.oracle.com//tech/migration/workbench/htdocs/relnotes.htm)

  • [PXE][IPv6] WdsClient: There was a problem initializing WDS Mode‎

    PXE/IPV6 show error after load boot image: WdsClient: There was a problem initializing WDS Mode‎ ; boot via IPV4 is pass and success to insall win8 to clent
    1. Server 2012(DHCP+WDS): fail at some times
    2. Server2012(DHCP)+Server2008R2(DHCP): fail always
    The test environment is pass before, i don't know what happened or any setting is changed.
    Hope your help, thanks.

    Yeah, same here.  Did you ever fix this?

  • Problem in creating DLL for a LabVIEW VI

    Hi
    I am facing problems in creating DLL for a LabVIEW VI. Previously i had no problems in creating DLL for the VI that transmits a message from serial port to NI - PXI 7831-R Reconfigurable I/O card (configured by FPGA MOdule). When i try the same VI with a customized port developed using IVI drivers i am not able to create the DLL. It gives me error as follows:
    Fatal Internal error: "datamgr.cpp", Line No: 1882
    Please somebody help me out to fix this error.
    Regards,
    Subramania Bharathi

    Hi,
    Thanks for your curiosity in replying my questions. I am really sorry for replying so late. Actually the problem was with the NI SWITCH 2503 functions. Actually i was multiplexing the channels of my customized serial port using NI Switch module. This switching is done before i start my communication. My VI follows a sequence as follows.
    1. Connect two channelss using Switch functions
    2. configuration of both FPGA and the customized port
    3. Transmit data from the port
    4. Receive it in FPGA.
    5. Reset the channels using Switch functions
    I never expected that the error was because of NI Switch. When i removed them from my VI i was able to create the DLL and able to create sequence successfully to run in the Testsand. And
    further i am using Switch Executive for swithcing the channels in TestStand.
    But now i am very curious why it posted me that error when i used my NI Switch function?? I tried to create DLL for a VI that switches two channels and i was successful. But the error occurs only when i combine i with my FPGA functions!! If you could trace out the reason, please let me know
    Once again thanks a lot for your support
    Regards,
    Subramania Bharathi

  • Problems installing FP v4.1 with LabVIEW v6.1 application

    We have a LabVIEW v6.1 application that interfaces to a FieldPoint FP-1000 Network Module for its I/O. We have been distributing it to customers for about 18 months with the FieldPoint v4.0.1 driver - no problems other than some difficulty getting the Watchdog Timer setup properly via MAX.
    The latest purchase of FieldPoint hardware came with FieldPoint v4.1 driver. There are three issues that have arisen with the advent of FP v4.1.
    1.) There occurs several (identical) warning messages during the FP v4.1 installation on Windows XP SP2 (the exact number depends on the selection of features to install). The message is "Error 1931" and it says that Windows stopped the installer from updating the stdole2.tlb file. It suggests that we update the OS, which has been done, but the messages continue.
    Question: is it critical that the stdole2.tlb in the FP v4.1 distribution be installed, or is this an error with no consequences?
    2.) When installing FP v4.1, we select LabVIEW v6.1 support, but disable the Real-Time v6.1 Support and the Examples. We also disable the LabVIEW v7.0 and v7.1 Support and the LabWindows/CVI Support. We keep the Documentation and MAX features. We have gone through the install/uninstall cycle several times and each time when uninstalling the list of features includes LabVIEW v7.0 Support - not v6.1.
    Question: does this indicate that the installer is erroneously installing v7.0 support and omitting the selected v6.1 Support? Or is this just an error in what is displayed by the uninstaller?
    3.) After FP v4.1 is installed (with LabVIEW v6.1 Support selected) our LabVIEW v6.1 application runs but fails to communicate with the FP-1000 Network Module. Upon quiting the application, there is an error message stating that the FP.Open.vi failed to run because the FieldPoint Server .dll was not found (no filename for the server- just ".dll").
    Question: Is this an issue of the installer not putting the proper FP Server .dll file on the computer (see question 2) or is this a matter of compatibility (do I need to install FP v4.1 on the development computer and remake my application)? Something is wrong here, FP v4.1 doesn't support a LabVIEW v6.1 application that runs fine under FP v4.0.1. Do I need to install the LabVIEW v7.x Support in addition to the v6.1 Support?

    Hi lkj,
    There has been few reported problem with installing FP4.1 in LabView 6.1, but none of them are similar to what you are experiencing. According to the 4.1 driver documentation certain vis from this driver version cannot be installed and used in LabView 6.1. What I would suggest is to uninstall the current driver and revert back to the ver. 4.0.1 since we know for sure it works in the LabView 6.1 environment. If you you'd like to use the 4.1 driver, then if would suggest upgrading to LabView 7.0 or 7.1.
    Regards,
    Natasa

  • Problem of security using ADO from Labview to connect to Access 2000 Data Base

    I have a problem using ADO from Labview to connect to Access 2000 Data Base.
    First I open a ADO_DB_Engine and create a Workspace as an ODBCDirect. After I execute the open_data_base using the workspace. Here you can specify the parameter connect with /type of connection / user / password.
    The problem is the following:
    Although you configure a password for the Administrator user in Access, you can read/writte to data base from Labview using ADO without any security and without putting the user and password in the parameter connect. I need to access with security to data base using users and permissions but it seems that the parameter connect does not operate.
    I attach
    you a example of the vis and database. Remember create a ODBC connect with BD3.mdb
    Thanks a lot
    Peter Mst
    Attachments:
    SECURITY.zip ‏70 KB
    BD3.mdb ‏112 KB

    Hi Kahn,
    If you use ADODB_connection -> Connection.Open and set in connection string :
    "Provider=Microsoft.Jet.OLEDB.4.0; Jet OLEDBystem Database=c:\.....\Protegida5.mdw; Password=pepe;user ID=jose; Data Source:c:\......\BD5.mdb";
    and after connection.execute ->
    INSERT INTO tabla1 VALUES (5,'XXX'
    you will be able to access to the database with security using the provider=Microsoft.Jet.OLEDB.4.0. With this provider you have to use the path and the name of the database file c:\.....\mdb file. From this way the problem is solved. (SEE SAMPLE_ADO_W2_JET.VI).
    BD5.mdb have the following administrator user: user:jose / passwordepe (Protegida5.mdw)
    The problem is when you want to
    use ODBC and DSN. The name of this ODBC Provider is MSDASQL;. If you use this type of connection you can not enter to the database I attach you.
    This database has a new administrator owner. I deleted the default administrator. If you support the default administrator you can connect to database by ODBC / DSN but the security disappear because you can always enter to database with any password, user o PC.
    FINALLY I HAVE 3 QUESTIONS FOR Application Engineers of National Instruments or someone who knows these subjects before deciding the best way to connect locally o remotely with security to Access from Labview:
    1.- Is it possible to enter to Database BD5.mdb from ODBC and DSN with this owner?
    2.- I want to connect remotely to Access database too. Is it possible to use Microsoft.Jet.OLEDB.4.0 using the path (.mdb file) without DSN?
    3. Which is the optimal Provider for Microsoft Access?
    I thank you beforehand for your technical support.
    Peter Mst.
    Attachments:
    BD5.mdb ‏116 KB
    Protegida5.mdw ‏112 KB
    sample_ADO_W2_JET.vi ‏45 KB

  • Problems with the installati​on of LabVIEW 6.1 on Windows 2000!

    Windows 2000 crashes while installing LabVIEW 6.1, and the computer is unusable after the installation!

    This also happened to me. Hopefully you are attempting to run LabView on a dedicated computer. Ours had "issues" with some of the other software we were running. Here's what we did: We re-imaged the computer (backed up everything and re-loaded the OS). Computer has been up and running excellent ever since. There was a lot of useless software originally on it, we took it all off. If you are able, only run what you need on it. Also, we have found that LabVIEW 6 runs strangely on computers with less than 128 MB of RAM. Our project computer currently has 320 MB of RAM (and 40 GB HD) and it runs perfectly.
    Hope this helps. If you have a specific error code, let me know. Otherwise, from what you have posted, I believe this is the answer.

  • Report generation toolkit problem with office 2000 and office XP

    Hello, I am having a problem with running my vi after it is compiled with application builder. The dev machine is an XP box and the targer is windows 2000. I included _Excel Dynamic VIs.vi and _Word Dynamic VIs.vi from the office 2000 section of the install cd (for the report toolkit) in the compile but did not include those files for XP. When I run the application on the target machine (2000), the reporting functions call Excel just fine and the program does not come up with any errors. The program however, is not loading the approprate template and inserting the approprate data. Did I leave some neccessary files out of the compile? Thanks in advance!
    Greg
    Gregory Osenbach, CLA
    Fluke

    Hi Acer,
    The recommended procedure in your case is to install Microsoft Office 2000 on the development machine and then reinstall the LabVIEW Report Generation Toolkit. When the toolkit is installed, it will check for the current version of Office and install the corresponding VIs to support it. The VIs include different ActiveX calls according to the version of Office. Therefore it is not enough to change the support manually without having the correct version of Office installed first.
    However, I would recommend that you just try to run your executable on a machine that has Office 2000 installed. The difference in the ActiveX API for Office XP and 2000 is not that significant, so your application might work perfectly on an Office 2000 machine. If you try to run the executable on a machine with Office 97 installed I'm willing to bet my right arm that you will experience errors.
    Good luck Acer!
    - Philip Courtois, Thinkbot Solutions

  • Problem with an old version of LabVIEW 4.0.1

    Hi,
    I'm rather new to this, so I appreiciate any help that you can give me. Our lab has an old computer running Windows 95 and LabVIEW v. 4.0.1. I would like to take one of the progams on this computer and run it on a newer computer in a different lab. This newer computer is running Windows 2000. I installed LabVIEW 4.0.1 on the Win2000 machine, and then copied the needed file onto this machine. However, when I try to run the program, I get the following error messages:
    Error 7 occurred at Open File+.vi: Open File
    Possible reasons:
    LabVIEW: File not found.
    OR
    NI-488: Non-existant Board.
    after that error I get this one:
    Error - 10401 occured at AO Group Config.
    Possible reasons:
    NI-DAQ:LV The specif
    ied device is not a National Instruments product, or the driver does not support the device (e.g., the driver was released before the device was supported).
    Now, there are a couple reasons that I can think of that would cause these problems. First, LabVIEW 4.0.1 is not compatable with Windows 2000. Second, I had to install the Windows 2000 driver for my PCI-MIO-16XE-10 board, and this driver is not compatable with LabVIEW 4.0.1. Third, that there is something else that I need to copy over from the old computer. Once again, thank you to anyone that can help me out.

    Raven3182 wrote:
    > Hi,
    >
    > I'm rather new to this, so I appreiciate any help that you can give
    > me. Our lab has an old computer running Windows 95 and LabVIEW v.
    > 4.0.1. I would like to take one of the progams on this computer and
    > run it on a newer computer in a different lab. This newer computer is
    > running Windows 2000. I installed LabVIEW 4.0.1 on the Win2000
    > machine, and then copied the needed file onto this machine. However,
    > when I try to run the program, I get the following error messages:
    >
    > Error 7 occurred at Open File+.vi: Open File
    > Possible reasons:
    > LabVIEW: File not found.
    > OR
    > NI-488: Non-existant Board.
    >
    > after that error I get this one:
    >
    > Error - 10401 occured at AO Group Config.
    > Possible reasons:
    > NI-DAQ:LV The
    specified device is not a National Instruments
    > product, or the driver does not support the device (e.g., the driver
    > was released before the device was supported).
    >
    > Now, there are a couple reasons that I can think of that would cause
    > these problems. First, LabVIEW 4.0.1 is not compatable with Windows
    > 2000. Second, I had to install the Windows 2000 driver for my
    > PCI-MIO-16XE-10 board, and this driver is not compatable with LabVIEW
    > 4.0.1. Third, that there is something else that I need to copy over
    > from the old computer. Once again, thank you to anyone that can help
    > me out.
    You pretty much summed it up. NI-DAQ which is compatible with LabVIEW
    4.0 won't support Windows 2000 almost certainly. And NI-DAQ supporting
    Windows 2000 won't have VI support for LabVIEW 4.0. There was a
    significant change in the way LabVIEW interfaced to NI-DAQ between
    NI-DAQ 5.x and 6.x which happens to be around LabVIEW 4.x as well. So
    you are most probably stuck with either a LabVIEW
    upgrade or downgrading
    to a Windows 9x computer.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Should I be able to reliable automate Excel 2000 on a Windows 2000 PC using Labview 7?

    I am trying to automate Excel 2000 from Labview 7. I want to open an Excel application, open an existing workbook or create a new workbook, create a new sheet, save and exit. When using the Labview 7 .vi's I can create a new workbook, etc, and everything works fine. When the case in my program for existing file executes I can start Excel but I cannot open an existing worksheet (error -2146959355). I've selected a file using the labview file dialogue just to ensure spelling, case, etc but it always fails on the "open specific workbook" sub .vi and the first error is on the output of the "invoke node".
    Out of curiosity I tried doing this in Labview 6.1 and after a cursory check ev
    erything seems to work ok using the exact same sequence of .vi's. I am running Excel 2000 on Windows 2000. Should there be a compatibility issue? Would using the version 6.1 vi's within Labview 7 be a clean solution?
    Thanks in advance

    Thanks for responding.
    I made a little vi to illustrate the problem.
    The two sub .vi's I'm including with the main .vi are simply the renamed Version 6.1 and Version 7 "open specific workbook" .vi's. The main .vi was made in Version 7. All the other sub .vi's are V 7.
    On my PC (Windows 2000 and Excel 2000) when the switch is set to "Version 6.1" it consistenly runs fine, set to "Version 7" it consistently fails.
    I am very stumped! I've gone so far as to copy the V7 .llb from a different installation just in case something got corrupted somehow.
    Attachments:
    ExcelError.vi ‏44 KB
    Open_Specific_WorkBookV6.vi ‏37 KB
    Open_Specific_WorkBookV7.vi ‏37 KB

  • Installation problem on windows 2000

    Hi,
    Please help!
    I've been tring to install oracle on windows 2000 machine unsuccessfully. the setup program aborted without error message. I've tried many versions of oracle database, 8.1.7 all editions, 8.1.6ee, 9iAS. the only message error I got when 9iAS failed to install (iSetup.exe). the problem seems to be with the java runtime environment. the jre 1.1.7 came with 9iAS would not run properly. I've tried to install java2 and jdk1.1.8 from javasoft, still no luck.
    Any idea?
    Thanks,
    Jay Lee
    [email protected]
    null

    Hi,
    The problem of installing Oracle Product on P4 computers comes from the symcjit.dll (Java Jusit in time compiler) which doesn't recognize the P4.
    I installed Oracle products on my P4 just by copying the CD's on a harddisk and manually replacing the dll (which is Version 3...) by a one I found to be Version 4.0.0.7.
    It is maybe not the best solution as it can result some instability (I don't know yet) but at least I didn't bought a brand new computer for nothing.
    The question is to know when Oracle will deliver some patches to allow a normal installation on P4s.
    Let me know if you want me to send you the dll.
    Regards,
    Jacques.

  • Oracle Installation Problem on Windows 2000

    Dears
    I have the Windows 2000 Advance Server and Windows 2000 Professional. I install the Oracle8 on Windows 2000 Advance Server and Windows 2000 Professional. I have a lot of problems while i install. If i install it successfully after two or three days it gives me some errors. like it give errors the services. It could not start the Instance.
    If i upgrade the NT 4.0 to Windows 2000 which is also an ORACLE server. It upgrade the OS but not upgrade the Registory. It have the same problem
    Please tell me is the Oracle 8.0.4 is compatible with Windows 2000 Advance Server and Windows 2000 Professional or not.
    Please Please.
    Yours
    Muhammad Munir
    [email protected]
    null

    This resolved my problem as well. I am on Windows 2000 server, SP2. The problem installing Oracle 8.1.7.0.0 standard edition exhibited itself by briefly changing the cursor to an hourglass and then returning to ready. The executable JREW.EXE would briefly execute in processes and then stop.
    I copied the installation media to a server drive and renamed symcjit.dll and the installer worked correctly.
    Thank you to Yugandhar for this solution.
    We too faced some of those problems ie setup.exe wont even run in Windows XP pro, p4 system..the culprit is symcjit.dll. Its the problem in p4 to run this dll. After lot of research, just rename it and all is set to go.
    regards
    Yugandhar

  • Oracle 8.1.7 installation problem on Window 2000 Professional

    Hi everyone, I have a problem of intalling Oracle 8.1.7 on Window 2000 Professional. When I started to install Oracle 8.1.7 when I click install I get this error message
    "Jrew has caused error in Javai.dll"
    and restart the computer, I restarted again and again and the same problem occured, would you please tell me how I resolve this problem. Thanks in advance.
    Mesfin
    [email protected]
    [email protected]

    Intel says there is a bug in oracle's OUI as well other swing based programs. The solution is to copy the CD to local drive and add -nojit as first parameter to JRE_MEMORY_OPTIONS e.g. JRE_MEMORY_OPTIONS="-nojit -mx32m"
    This will enable OUI to run. Even after installing oracle Net80 conf. asst won't start due to same reason.
    Go to HOME\admin\tools\ and edit netca.cl and netasst.cl to add same -nojit before -classpath.
    Do this for every tool that gives this prob such DBA studio...
    Ashish

Maybe you are looking for