Neville D

Any reason why you are using UDP instead of TCP? There might be data loss with UDP. TCP is slower, but you are guaranteed receipt of the packets. Neville.

QUOTE (crelf @ Jul 18 2008, 12:17 PM) Might be in an older version of LabVIEW? I have it working all the time with some of my exe's in LV8.* onwards. Neville.

I don't know how you can do it through the web server, but if you have the LV internet toolkit, you can use the ftp VI's to build your own download solution. Those VI's and pallets haven't been updated in years so they are a bit clunky to use, with absolutely unhelpful documentation. Neville.

You might try the IVISION toolkit which is quite a bit cheaper than NI Vision. No point buying a $3k+ package to use with a $20 camera.. IVISION has a free trial period so you can check it out. Neville

QUOTE (NeilA @ Jul 17 2008, 01:53 AM) Hi Neil, I have never used TestStand before, but I suppose you should be able to build exe's out of it, to install on each separate rack system. You could have a startup app (in TestStand or LV) that queries all the instruments/harnesses available (whether its 1 or more connected racks), and based on this logic, decide what set of tests to expose to the user. Sort of like a *IDN? command in SCPI. These tests can then be ordered/run through TestStand. Writing a test sequencer (or test executive) is usually a LOT of work, and if you already have TS you should just use that. That decouples the problem of writing the actual test routines from worrying about how to call them, and organize the results etc. You might get your local NI Rep to come in and explain the capabilities of TestStand as applicable to your use-case. Neville.

Hi Louis, I'm glad you found my post useful, but I am not sure which one you are referring to, since the link in your post is broken. Its been a while since I did any DAQ, but I found that DAQmx is a super-set of the old DAQ capabilities. So whatever you learn reading the old DAQ manual should be applicable in the new DAQmx API. Note that you cannot use both API's simultanously. You have to disable one of them to use the other. There is a VI on the pallets somewhere that does that. DAQmx definitely isn't as well documented as the old stuff, but it is much more powerful and the multi-threaded nature of the driver allows you to do things which you couldn't before: for example software timing of DAQ applications is much more robust and faster than before. You can fake simultanous analog input and output using software timing on cheaper DAQ cards that only have a single DMA channel. I'm not sure that there is a neat way to share the trigger lines except using a breakout board accessory for each device and hardwiring the lines from the different modules. Take a look at this KB entry and this other one, talking about RTSI lines in PXI Neville.

From a quick reading of your post, you need a lot of test management, so I would suggest you take a look at TestStand which will allow you to concentrate on developing the specific tests in LabVIEW, and leave asset management (using the instruments efficiently and in parallel etc) to the Teststand end. It will also allow you to call your old HTBasic code if needed (maybe for initial debugging etc.) PS. You might get your local NI rep to give you a quick demo of Teststand and its capabilities. Note: I have never used it, but it seems like the tool for your application. Neville.

Are you sure you have activated your version of LabVIEW? Have you mass compiled your application to update all your VI's to 8.5.1? I have experienced no slowdowns in my applications which typically have about a 1000 VI's since LV 7.x onwards (I am at 8.5.1 currently) Neville.

QUOTE (lalo22 @ Jul 8 2008, 11:45 AM) I doubt you will be able to work with this directly through LabVIEW or the vision package. Use your camera's software to acquire an image, save it as a png file, and then use the vision package to analyze what you want. Or else get a camera that works with the Vision package. Check the NI website to see a list of supported cameras. Neville.

What do you mean network camera??? Is it FireWire/GigE/USB? USB cameras typically don't have great resolution or performance. They may need an additional driver downloadable from the NI website. If its a Gigabit Ethernet camera, make sure jumbo packets are enabled in the ethernet card. You can use the NI-MAX (measurement & automation explorer) to detect cameras connected to your pc and then even grab an image or two, to see that those parts are working. Then you can start to use Vision Builder for Automated Inspection or the NI Vision Assistant to start. I don't think you need the ActiveX container to view the images in your application. There is a Vision Display native to LabVIEW that can be used to display the images and any other features/regions of interest that you desire. Start by reading the NI Vision Concepts Manual to see what is possible. Neville.

You can't change default values of a running VI. You can change them for a VI that is idle, but then you have to save the VI to retain those values. Instead, write the last value to an ini file at the end of a run, then when you re-run the program, first read the ini file setting and initialize the ring/or any other control with that value(s) Neville.

QUOTE (Gary Rubin @ Jul 3 2008, 05:50 AM) Yes it does. I still get my daily digests. You should try to re-subscribe, or else check your SPAM settings. Neville.

As Mike suggested, store the current value in a shift register, then on the next iteration use the shift reg value (prev val) and subtract from current value, and add that to the chart. should be easy enough. Look at examples on shift registers. I would advise spending a few days with the LabVIEW introduction books and manuals that came with the software. Or look through all the basic examples to get your head around LV. Changing complex code without knowing what your doing can be catastrophic. Neville.

Never used those modules before, but have you tried grounding any unused channels? Also, are you getting 4ma when the pressure is 0? I've never had a pressure sensor give exactly 0 output when the input is 0 pressure. You might want to scale the values before presenting the output. Neville.

The Hilton is the best and right across the street from the Convention Centre.. it is not that much more expensive than the others.. go on the NI website and they have a list of hotels and a special code you can use for a discount. Have fun! Neville.

Haven't looked too deeply at the code, but you can, on the feedback node, move the initializer terminal to the outermost loop if required. Right-click the feedback node, and select "Move initializer one loop out" Or just us the shift-reg with the i=0 case. Neville.

I've seen some strange thigns with 8.5.x Sometimes I will change the connector pane of a VI in a project. This VI might be called in a couple of places. At one location, it will seem to use the changed VI but at another location, it will seem to use the unchanged VI without an error for a few iterations, until it finally crashes LabVIEW. On restarting, the top-level VI will open up correctly as broken since it now shows the second location as needing a re-link. Wierd.. but I have learnt to live with it as well. Neville.

QUOTE (marp84 @ Jun 23 2008, 10:43 AM) Open up NI-MAX (Measurement and Automation Explorer) Look Under My System>Software (hit F5 or click Refresh) Make sure NI-DAQmx is listed under there Note that DAQmx will NOT work with MCC hardware, and MCC software won't show up here. Also what package of LabVIEW do you have? Professional Development System? Basic? Student Edition? Probably Student Edition or Eval version may not have DAQmx stuff loaded. Neville.

POST your Code! Neville.

QUOTE (jbrohan @ Jun 21 2008, 02:47 AM) There is already a Median Filter VI and the Median Filter Pt-by-Pt VI (if using in a loop). I think they are in the Pro package of LV though.. Neville.

QUOTE (irpotential @ Jun 20 2008, 01:04 PM) Use the "Is first call?" function under the Data Communication>>Synchronization sub-pallet Neville.

QUOTE (Thang Nguyen @ Jun 19 2008, 07:55 AM) You usually get this error when the VI is already opened (or called as a subVI) and/or it is already running. I would suggest you simplify your architecture as a first step. Neville.

You could use shared variables to write info to a Host PC, and then display any kind of history you want. You could also use shared variables to write values to controls on the remote RT application. there are a number of such examples on the NI site zone.ni.com. Neville.

Look for examples using "Snap" or "Grab". these are simple examples illustrating how to get an image from a firewire camera. Look for examples with "vision" to show how to process images. Examples are under Help>Find Examples (I think, not at a LV terminal right now), and then type in the keywords in the example finder.. Neville

You might also consider that the NI memory will definitely support the extended temperature spec (if you have that option) in harsh environments. Neville.