Ftdi chip and Labview

Hello,
I'm new using Labview and FTDI chips. It's being hard for me to figure out how to start. For example, I have no idea how to program the chip with Labview. Which driver to use: VCom or D2xxx? Should I use normal serial port commands if i use the Vcom driver? Can I use both drivers simultaneously?
I use Labview 7.0 and I have made a PCB as stated in the sample project:"USB to SPI interface". So i use chip FT2232C in MPSEE mde.
Does anyone has an example vi that could provide me? It would be a great help for a starting point.
Regards,
Pedro
Ps:Even if is for another chip it would be good !

Hi Pedro , I have used a similar chip the FT232 , I used the virtual com driver from the FTDI site. This gave me a USB on COM3 ( viewable in MAX ) . I then used the VISA vi's specifying COM3 as the port, you will also need to know the baud rate .
A useful site if you dont want to do DIY is
www.i2cchip.com. There i2c to PC adaptor also does SPI
Hope this helps
dht

Similar Messages

FTDI virtual com port driver (VCP) and Labview 2009 - random connection loss

Hi,
I am using an FTDI chip to go from USB to serial communication (FTDI Driver: 2.06.00). It seems to work at first but then after some time the connection gets lost ("connection for the given session has been lost" or "I/O error"). This happens in MAX as well as the built executable of the program I am running. Latest VISA drivers are installed - 4.6. I have tried flushing the buffer before and after communication with both visa clear and visa buffer flush vis. The lost connection seems to happen randomly.
I have seen other threads about this issue but they never reach a resolution. One thing i notice is that there are two FTDI devices in this system and only one fails, however when I unplug the working device the one that fails is able to connect again.
To sum up here are the system specs:
Windows XP SP3
FTDI 2.06.00 and older 2.04.02 drivers both fail.
2 FTDI devices on the system - they do get assigned different COM ports
Labview 2009 run-time
VISA 4.6 run-time
Thanks for any help.

We use Targus ACH63US Super Mini USB 2.0 4-Port Hub. It doesn't require external power but if you have a high power device you will have to plug the Targus hub into two usb ports on your pc (one provides power and the other does power and data transfer). They provide the usb Y cable to do this.

Ftdi read in LabVIEW

I am hoping for some assistance with reading data via a USB FTDI device. I am using the LabVIEW driver to attempt to read back data provided to me via a USB connection to a FTDI FT232HQ on a module connected to an Altera DE2-115 development board. The FPGA is currently sending packetized data every 1mS. I simply want to read the data back and parse the contents of the packets and display it in a graph. During the read in my LabVIEW code (see screen shot included), the data being collected seems to be corrupt or maybe overwritten. The data seems to repeat and only includes data in the fourth quadrant. If I open the D2XXtool.exe and run it on the same hardware and data, I can get clean data that represents the data I expect. I’m wondering what I am doing wrong in my read VI. The jpg file included here shows my LabVIEW source code and screen shots of my data and the D2XXtool data from a log file.
Solved!
Go to Solution.
Attachments:
FTDI_Read_Problem_LabVIEW.jpg ‏509 KB

If you are intending to use the FTDI chip to read/write an EEPROM I believe you need to use an I2C/EEPROM library (e.g. libmpsse dll?) to do this and not VISA Read/Write (VISA Read/Write does not mean EEPROM Read/Write). VISA Read/Write will just send serial data out of the FTDI cable and not I2C commands to read/write the EEPROM.
Unless the FTDI cable you have does something differently but when we have used FTDI leads to read/write EEPROMs in the past we have had to use an FTDI I2C -> EEPROM library.
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

Rational Robot and LabVIEW PDA collaboration

Does anybody have any experience/ideas for use of Rational Robot and LabVIEW? We have both software and hardware and were wondering if anyone had any ideas/suggestions/experience interfacing between these two.
Thanks ~ EUPECkat

Re-boujour,
Après une recherche un peu plus poussée, il apparaît que ce genre d'erreur est lié à des fichiers (DLL) manquants pour un chip du fabriquant FTDI. Serai-je complètement dans le faux?
Vous avez donc plus de chance de trouver des infos relatives à ce genre de soucis ici, et plus précisément dans la partie "support" auprès de personnes ayant déjà utilisé ce genre de DLL. Des exemples d'utilisation de ce genre de chip avec Labview sont disponibles ici.
En espérant que cela vous aide
Cordialement,
Mathieu STEINER
Mathieu Steiner, Test System Engineer, Safran Engineering
CLD, ISTQB

FT232R from FTDI hangs/freeze LabVIEW randomly

Hi.
I've been creating a program to display and log humidity and temperature sensors using the FT232R chip from FTDI (http://www.ftdichip.com/)
To build the DAQ.vi I've used the example 1 from FTDI which can be downloaded here: http://www.ftdichip.com/Support/SoftwareExamples/CodeExamples/LabVIEW.htm
The DAQ.vi I'm having trouble with is attached here.
What is happening is that from time to time (could take 10 minutes or could take 10 hours) the program suddenly hangs/freeze, and to solve it I have to diconnect and connect the USB-cable to the FT232R. When I have done so, the program starts working again, but I've lost all the data from the freeze-time.
Have anyone else experienced this problem using FTDI chips, or have any idea what could be wrong? And is there an easy way to find out if the bug is hardware or software-related?
I appreaciate the help!
NB:I know the attached .vi doesn't have wait times between write and read, but I've been having the same problem when using wait times as well.
Is my avatar the dog from the fraggle rock?
Solved!
Go to Solution.
Attachments:
DAQ3.vi ‏36 KB

This sounds like Windows power management shutting off power to the USB HUB but you have any of the common problems in this FAQ article:
USB Plug-n-Play Devices (Windows)
Options
Mark as New
Bookmark
Subscribe
Highlight
Print
Email to a Friend
Report to a Moderator
‎01-22-201202:20 PM
In this topic we will discuss some of the common problems that have been observed using USB devices with LabVIEW on Windows operating systems. Many of these points are also applicable to other environments but the examples will be use the Windows 7 OS.
FAQ 1 : My USB device stops working unexpectedly.
The first thing to look at is the OS power saving options. There is a global trend towards developing "Green" electronics and energy star ratings are getting fairly common. "If its not being used shut it off" is nothing new. Cavemen learned how to bank a fire to preserve energy that would otherwise be wasted. Likewise, the Windows OS has a power saving feature to shut down power to the USB hubs when no user activity is present. In Automated systems this feature can cause problems since removing USB hub power will shut down the USB device. Solution: Use the device manager to change the USB hub Power Options.
FAQ2: I set the power options and my device connection is still unreliable: Remember, those computer USB ports are often the cheapest that can be mounted on the chassis and share the PC system power supply to supply USB Power. Most uses of USB are temporary connections like a thumb drive or a camera. These connections do not require high reliability since the user is right there interacting with it. Power surges and fault tolerance at worst cause the operator to retry the data transfer. Automated systems require a bit more robustness. Solutions:
1) ALWAYS use an external self powered hub. Perform your engineering due diligence and inspect the devices specifications too- If you can't find them for that device that should clue you to seek an product from a vendor that WILL publish their specs.
2) High noise environments require the use of ferrites on the USB cable- and don't buy the cheapest cable either! The cheap ones are poorly shielded.
3) PROTECT the HUB connections- If you have a USB2.0 device and Joe User plugs in a 1.0 device in a open slot managed by the same hub- Bingo every port on the hub may back convert to USB1.0. WORSE there are a lot of damaged or marginally engineered USB devices out there. Joe User's device may cause power fluctuations when it is inserted or removed from the hub just don't let it happen!
FAQ3: I am testing USB devices and the OS can't find them anymore.
This is a Plug-n-Play feature that deserves some exposure. When you connect a P-n-P device the OS remembers its serial number in a HKEY (Hive-Key) registry entry. This is helpful when (for example) you want a specific instrument, Say an NI-USB-6008, to show up as a DAQmx Device with VISA Alias "MyDAQ1" every time it is plugged it. On the other hand, If you want to test a line of USB-Serial converters this can be problematic since the P-n-P driver will mount the first serial number as "COM3" and the next as "COM4" add infinitum until the enumerator controller in the registry and VISA recognized aliases get used up. Solution: Use the Windows registry API and the Hardware Configuration API in LabVIEW to clear unused VISA Aliases and HKEY entries. Speak with your staff IT professional about HKEY structure and possible side effects before developing
Jeff

Commands to FTDI virtual COM port via NI VISA interfere with communication with FTDI chip using D2XX drivers

Hello!
I am trying to communicate with a DLP Design module DLP-USB1232H which uses an FTDI chip. My program uses the D2XX drivers. It works, but...
In another program that runs at the same time, I'm communicating with another instrument via a virtual COM port (VCP) that uses an FTDI UART. In this program, I use the VISA Serial Port functions. It works, too, but...
The first program has the capability of listing all the FTDI devices in the system prior to choosing the right one to communicate with. When the VCP is plugged in, it lists it (FT232R USB UART) along with the DLP-USB1232H and communication with the latter device works. But as soon as the second program sends a command through the VCP, the first program no longer "sees" any FTDI device. It stops working.
I have tried 2 different FTDI VCPs; one a standalone cable and the other built in to the instrument.
I’m using Windows 7 32-bit. My programs are both LabVIEW 8.5 executables.
Is VISA "taking over" the channel to the DLP-USB1232H? Does someone who understands NI's implementation of VISA have any ideas on why VISA is doing this? Or if something else is going on?
I'm also interested in workaround ideas. I've tried a "Prolific" VCP, but most drivers don't work and the one that doesn't give an error in Device Manager doesn't communicate with the instrument.
Cheers
Halden
Solved!
Go to Solution.

Halden,
It really sounds like you have a resource conflict. That occurs when two programs or parts of programs try to use the same device or port at the same time. Your Get Device Function probably tries to open a session with each port (as you increment the index). When it hits a port which is being used by the other driver, it cannot open the session and stops working? Have you examined the errors returned by each program? The VISA drivers will return an error when the port is in use. I do not know about your program or drivers, but I would expect some kind of error. Automatic error handling in LabVIEW will not catch errors from a driver if it does not translate them to LV error clusters. So do not count on automatic error handling, if you use it, to display all possible errors.
Lynn

SCXI-1321 Bad Chips and Function Calls

8-4-04
This message is intended for the PSE of the SCXI-1321 and that person�s manager. Please route it accordingly. I would appreciate a phone response to 8**-2**-2*** so that I might share some specific experiences.
To the managers of the SCXI product line,
I have used the SCXI-1121 with the SCXI 1321 for some time now, approximately 6 years. Our company generally uses them for full bridge pressure transducers and similar applications. I have some suggestions that would make them more saleable. I also believe that you will never know how many customers you have already lost on this product line, for the reasons given below.
1. For many years the shunt resistor on the 1321 has been vastly unusable. What SHOULD be possible is to command the shunt resistor through a Labview command, and then read the virtual channel to see the shunted value. That IS the purpose of the feature. What happens is that once you set the shunt command, then read the virtual channel, the very act of reading the channel UN-shunts the resistor. What you read is some value part way between, because the chip relay from Clare actually ramps open and closed, unlike a mechanical relay. If your timing loop to read the value is consistent, you will consistently read a BAD value. Several VI�s tried to command the shunt, then quickly read the virtual channel, then loop and do it again, and thought they had solved the problem. Further investigation showed that all that was really happening is that the readings appeared to be stable because of the fast loop time, but were actually mid-release of the shunt for all readings.
2. NI eventually starting saying �don�t use virtual channels with the shunt�. In fact, there is a channel string that starts with the word �shunt� that was recommended. The only problem with this is that the data that comes back is not scaled! Keep in mind that NI has been pushing �virtual channels� on users for many years as the way to do business, and so entire test stands are developed around them and MAX. Because we depend on MAX to do the scaling, how are we supposed to be able to read the data scaled? Does NI expect customers to duplicate the efforts of MAX for every virtual channel and scale it separately? Do I have to keep duplicate tracking of scaling information so that my virtual channels will work in the main code, but again elsewhere so that my calibration routine can read the data? This is messy, and for most customers, untenable.
3. I was told, literally, year after year and release after release, that the problem would be fixed in future versions of NI-DAQ. Each release proved that the problem was not resolved. I am sure that many customers were not repeat customers as they found the problems associated with using a simple shunt on the board. I myself needed this hardware due to the 1121/1321 parallel operation capability.
4. After years of trying to fight with the issues above, and what seemed like random problems with the shunting of channels, a second hardware related issue has finally been identified. See SRQ#600753 with Michelle Yagle. The Clare solid state relays installed on the 14 different 1321�s I bought ALL had the same defect. Imagine what this means for troubleshooting! You swap boards to try to troubleshoot, but they are all defective and so you falsely rule out the board, the problem didn�t resolve with a different board. The lot# 0027T12627 of chips covers a wide range of 1321 serial numbers (see my SRQ for details). That means this impacts a lot of potential customers. The part is rated by the manufacturer to 80C, 176F. This particular lot stops functioning as low as 96F! A great deal of testing with heat guns, shop air, and a thermocouple showed that all the chips in this lot fail somewhere between 96 and 110F, well below manufacturers specs or NI�s specs on the board. I also tested lot 98, from a board two years older, as well as new chips from lot 03, which both worked perfectly all the way up to 212F (100C).
Conclusions:
I believe that the people that have tried to use your 1321 have generally had a miserable time of it, unless they already do their own scaling (like some of the Alliance members do.) This is because the shunt feature is not compatible with virtual channels, because NI did not offer a reasonable fix for this problem over a four+ year period, and does NOT advertise this limitation when people are making hardware selections. Further, I believe there are many people that have boards with the same bad lot of chips on them that don�t know it. They may have elected to hardwire their own resistors after fighting with random problems (temperature related). They might have elected to hardwire their own resistors to get around the NI-DAQ limitation. They might not even use the shunt resistor. But one thing is certain: NI needs to clean up this board�s operation, make sure that customers of the serial numbers in my SRQ named above are notified of the bad chips, and fully test that the use of the relays is transparent to LV virtual channels in the future. People will not trust NI products with this type of problems, and will not buy the product again if all the features don�t work!
I have helped NI resolve similar issues with the SCXI-1126 years ago, which had a number of scaling issues in NI-DAQ (the board read great when you used 1k, 2k, 4k, 8k, etc. even ranges, but if you set a virtual channel to 0-2200, the readings were off.) I plotted the problem, documented it with my sales rep, and worked at length with tech support. The boards also had a lot of bad buffer amplifier chips that allowed cross talk between channels, causing a lot of other spurious problems. Those experiences were horribly frustrating, but I now buy the product with confidence. It took a lot of push on my part to convince NI there was a real underlying problem. This 1321 board is similar.
I want NI products to be the best they can be, as I have dedicated my career around them. Please take this feedback to heart, and contact me at 8**-2**-2*** to talk about these issues. Additionally, I am speaking at NI week this year and will be available for discussion. Contact me at the same number.
Sincerely,
Tim Jones
Test Equipment Design Engineer
Space Shuttle Program
Space, Land and Sea Enterprise, Hamilton Sundstrand

Tim
Thank you for your feedback for the SCXI-1321 terminal block.
I wanted to see if it would be possible for you to move your application to NI DAQmx, the new driver for DAQ and SCXI as of NI-DAQ 7.0. I have tested the shunt calibration using a SCXI-1121 and SCXI-1321 and it works as it should. There are two ways to do the shunt calibration with DAQmx.
The first is to use the Calibration feature in the DAQ Assistant. When creating a DAQmx Task in either MAX or LabVIEW, you can select the �Device� tab and click on the Calibration button. It will then ask you if you either want to do a null or shunt calibration, or both. It will then do the calibrations selected and save the values to the task.
The other option to measure the shunted value is to use the AI.B
ridge.ShuntCal.Enable property node in LabVIEW. By setting this property to True, the driver will enable the shunt for the current measurements. If you are taking a strain measurement, the value will be converted to strain.
We are currently looking into the issues you are seeing with the Clare relays to see if other users could be affected.
Brian Lewis
Signal Conditioning PSE
National Instruments

Getting errors and LabView with ARM project won't compile

Hello there, I am currently turning to make a project run on a STM32f103C8 chip using LabView with ARM. I am currently trying to compile a ARM project but I have no been successful.
I have tried using the STM32F10x template uploaded by Joshua, and it tries to compile. At first I was getting the "stm32f10x_tim1.c" file missing error, but that was solved by downloading the file from firmware v1 and adding it to the includes folder. but now i am getting a new error saying "profile_timer.h" is missing.
I am using:
Windows 7
LabView 2010 evaluation
NI ARM module
and I am trying to compile a empty project
Here is the error code message, any hepl will be useful, thanks:
[12:39:37 PM] Status: Error
Build target 'LabVIEW'
compiling RTX_Config.c...
F:\National Instruments\LabVIEW 2010\CCodeGen\include\os\rtx\LVDefs_plat.h(17): error: #5: cannot open source input file "profile_timer.h": No such file or directory
compiling Retarget.c...
F:\National Instruments\LabVIEW 2010\CCodeGen\include\os\rtx\LVDefs_plat.h(17): error: #5: cannot open source input file "profile_timer.h": No such file or directory
compiling TargetInit.c...
F:\National Instruments\LabVIEW 2010\CCodeGen\include\os\rtx\LVDefs_plat.h(17): error: #5: cannot open source input file "profile_timer.h": No such file or directory
compiling ARM_Serial.c...
F:\National Instruments\LabVIEW 2010\CCodeGen\include\os\rtx\LVDefs_plat.h(17): error: #5: cannot open source input file "profile_timer.h": No such file or directory
compiling LVTree.c...
F:\National Instruments\LabVIEW 2010\CCodeGen\include\os\rtx\LVDefs_plat.h(17): error: #5: cannot open source input file "profile_timer.h": No such file or directory
compiling Pict.c...
F:\National Instruments\LabVIEW 2010\CCodeGen\include\os\rtx\LVDefs_plat.h(17): error: #5: cannot open source input file "profile_timer.h": No such file or directory
compiling arrresize.c...
F:\National Instruments\LabVIEW 2010\CCodeGen\analysis\development\include\platdefines.h(321): error: #35: #error directive:
Target not created
Status: Build failed.

blank projects using other included boards seem to compile fine
and i have added a mock "profile_timer" to the keil library (just as a quick fix) and it seems to have stopped a lot of the errors, however i am still getting a few
these seem to be:
compiling CCGDatalogSupport.c...
F:\National Instruments\LabVIEW 2010\CCodeGen\libsrc\comms\CCGDatalogSupport.c(23): error: #5: cannot open source input file "CCGFileSupportPriv.h": No such file or directory
compiling CCGFileSupport.c...
F:\National Instruments\LabVIEW 2010\CCodeGen\libsrc\comms\CCGFileSupport.c(22): error: #5: cannot open source input file "CCGFileSupportPriv.h": No such file or directory
compiling CCGFileSupport2.c...
F:\National Instruments\LabVIEW 2010\CCodeGen\libsrc\comms\CCGFileSupport2.c(22): error: #5: cannot open source input file "CCGFileSupportPriv.h": No such file or directory
compiling CCGIrDASupport.c...
compiling CCGNetConnRefNum.c...
compiling CCGSerial.c...
compiling LVTree.c...
compiling Pict.c...
compiling arrresize.c...
F:\National Instruments\LabVIEW 2010\CCodeGen\analysis\development\include\platdefines.h(321): error: #35: #error directive:
Target not created
Status: Build failed.
i'll see if i can find a file for the ccgfilesupportpriv.h but the error directive worries me a bit

Modbus error 1073807194 with FTDI CHIP RS485

Hi,
I am using modbus library to control a Lumen temperature controller. The controller is connected trough RS485. I am using a FTDI chip with VCP driver to interface this component.
The modbus transfer is in RTU mode.
On each step :
I am reading the temperature on a device's register.
I am writing relay set point depending on time and consign.
My program is working fine during one hour (sometime 2 or 3 hour). next I have this error :
Error -1073807194 occurred at VISA Write in MB Serial Transmit.vi:7->MB Serial Master Query.vi:6->MB Serial Master Query Read Holding Registers (poly).vi->read-register-safe.vi->boucle-temp.vi
Possible reason(s):
VISA: (Hex 0xBFFF00A6) The connection for the given session has been lost.
This error occurs during a reading period.
I attache the VI :
Boucle-temp-safe is the main program.
Read-register is the sub program generating this error.
I hope you could help, i am using this program to control the temperature cycle when i press ski (handmade ski build with friend). I have to set the set point manually for the moment.
Attachments:
boucle-temp-sqfe.vi ‏36 KB
read-register-safe.vi ‏25 KB

Hello,
I think i solve my problem.
My usb transducer was buy on ebay with a ftdi chip.This transducer isn't stable in time (2-4hour).
I buy a new ftdi transducer on ftdi web shop and now it seem to work (22h). I have to test it on a longer period.
Thank you for help.

Xbee pro 60mw wire antenna and Labview guidance needed

I have some questions regarding zigbee and labview interface. I'm currently working on a project and this is my first time using zigbee and labview.
In my project, I want to transmit data wirelessly between two zigbees where data is the output that sensors generate by reading humans body temperature and heart rate(pulse).
I want to use the labview to display the values and data in a graphical way and ultimately to a TFT display. Right now, I'm using Mega pro 2560 and XBee Pro 60mW Wire Antenna - Series 1 (802.15.4).
All the sensors are off the shelf sensors from Sparkfun and they are connected to microcontroller.
I want to know if my steps are correct.
First, I have succeeded in sensors trasmitting its output to microcontroller. Then microcontroller stores data in SD card connected to microcontroller before tramitting them to the receiver..
Second, by using X-ctu, set up some configuration between two zigbees such as baud rate.
And this is kinda where I'm stuck at. My receiver(Xbee pro) is connected to ftdi then to PC using the USB cable. My transmitter(Xbee pro), sensors and microcontroller are connected to breadboard powered by lithium ion battery.
Could you please give me some tips or steps how you would go about using the labview at this point? Do you need some code for labview and zigbee interface?
I'm sort of new to this. If you can help, I would really appreaciate it.

I got stuck in this part. Can you check out the last reply I made in this forum : https://decibel.ni.com/content/message/49209
Also, from my receiver end(xbee pro) that is connected to PC through ftdi,
I was wondering how you would go about designing the serial communication from the receiver to Labview display.
The file attached is kind of thing I want to do. I have three major sensor data to display(heart rate, body temperature, and motion speed).
I want to show them to three graphical disaplay at the same time.
Can you give me some tips on designing the labview part? and also I would really appreacite if you could give me some tip on fixing the error I first stated in another forum. Refering any related forum would be helpful. Thanks a lot.
Sam,
Attachments:
reading data.vi ‏20 KB

Camera Vision Loop Snap will be 1% right and left inverse in Vision2013 and Labview 2013.

Hello,
I use a Camera to Loop Capture Vision Snap in Vision2013 and Labview 2013.
(see the right-up picture that is the needle in the right side, but the right-down picture it is in the left side.)
The right-up picture that is the current snap image shows normally.
The right-down picture is after en-queued and de-queued image.
But the image will be 1 % Randenly Chance to show right and left inverse.
Could someone tell me how to solve the problem?
Thanks.
Attachments:
IMAQ_Mirro_)_(.JPG ‏149 KB
IMAQ_realtime_image_snap_queue.JPG ‏196 KB

Good-day.
2 Cameras are both the same "AVT GUPPY F033B" , Connected to the IEEE1394 interface PCI Card (2 ports, Controller Chip is Texas Instruments).(See" cam_driver.JPG")
Both Cameras are 1 % Randenly right and left inverse.(See" IMAG_Mirro_)_(2.JPG")
The Labview 2012 program is the attached file called "IMAGE_LOOP_SNAP_Queue As a Multiplexer_LV2012.vi.zip"
Thanks.
Attachments:
cam_driver.JPG ‏55 KB
IMAQ_Mirro_)_(_2.JPG ‏159 KB
IMAGE_LOOP_SNAP_Queue As a Multiplexer_LV2012.vi.zip ‏769 KB

Error involving Report Generation Toolkit and Labview Run Time Engine

Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
I displayed my App.Property of APP.DI
R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
Any ideas ?
Greg Klocek

Upgrade chip and memory

Can I upgrade the chip and memory? if so what can I use. The system is a little too slow. Yes I have all the software to speed it up. Thanks
HP 2000 Notebook PC Windows 8.1 64-bit [Edited for Personal Information] AMD E-300 APU with Radeon(tm) HD Graphics microprocessor 4GB SODIMM Kinston 800MHz memory 188B KBC Version 69.18 system board F.37 system bios HGST HTS545032A7E380 SATA Disk Device Product number: E0M17UA#ABA AMD E-300 APU with Radeon(tm) HD Graphics

Here is the Service Manual:
http://h10032.www1.hp.com/ctg/Manual/c03763129.pdf
Go through Page 16-17. Each different processor is soldered to the board, so you've to replace the whole motherboard for that, you can see that their part numbers are different according to three different boards.
I suggest RAM upgrade from 4 to 8GB by adding another 4GB in the other vacant slot, with configuration DDR3 1333MHz dual channel boost.
thanks,
++Please click KUDOS / White thumb to say thanks
++Please click ACCEPT AS SOLUTION to help others, find this solution faster
**I'm a Volunteer, I do not work for HP**

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

I have a problem with simulation in Matlab 6.5 and LabVIEW for PID controllers

I have a problem with simulation in Matlab 6.5 and LabVIEW. I have some methods for granting PID controllers in MATLAB to go but not LabVIEW. International Teams degree to transfer two but when I go past the fourth degree no longer work. We changed the formula for calculating the parameters for grade four and gave me some good values for Matlab award but when I put on LabVIEW have not settled. formulas are available in PDF and are. Please help me and me someone if possible. Thanks
lim.4 generation parameters in MATLAB program and comparison methods are for second-degree transfer function.
Solved!
Go to Solution.
Attachments:
Pt net.zip ‏2183 KB

This is the VIs what i try to make,but is not work. This pdf. document was used to create last VIs PID. thenk you for your colaboration.
Attachments:
PID create by me.vi ‏312 KB
tut_3782.pdf ‏75 KB

Ftdi chip and Labview

Similar Messages

Maybe you are looking for