bjarket

Hi! Unfortunately, I'm limited to the base package... Does anyone have a VI doing linear fitting? Any help is appreciated. Thanks! /bjarket

QUOTE(Mike Ashe @ May 13 2007, 02:31 AM) Actually, the piping system is (and should be) very easy to reconfigure. This is an essential feature of the system, so one could imagine that a setup is used a week after which it is changed according to another chemical process. Crelf; thanks for pointing me to Lookout. I'll have a look at it! /Bjarket

Thanks for your reply! As I suspected, there's no easy solution /B

Hi LabVIEW users! I've been given the task to develop an application which should monitor and control a system with pumps, thermocouples, pressure sensors, valves and storage/mixing tanks. The problem is that the mentioned components can be interconnected in every possible way (any pump can be connected to any tank and so on). The user should have the option to configure the software such that a graphical representation of the setup is shown in the frontpanel. Now, the perfect solution for the setup view would be a view much like the block diagram where the user can drag and drop components and connect them with wires. The blocks should then be pumps/tanks/sensors or the like and the wires should be pipes. Is there any toolkit out there that would give me such a functionality? I've been looking at the DSC module but I guess that the provided graphics essentially just is a library of figures... Thanks! /Bjarket

QUOTE(jpdrolet @ Feb 26 2007, 10:09 PM) Just what I was looking for! Thanks!

I would like to change the increment steps in a slide from 1's to 0.1's. The NI homepage describes a solution for LV 8.2, but it doesn't seem to be applicable for LV 7.1, which I'm using. http://zone.ni.com/reference/en-XX/help/37...crement_and_de/ Is there a solution for LV 7.1? Thanks!

Thanks for the replies! I'll try the software solution when I'm near my development PC again... When looking for the "DAQmx Flatten Channel String.vi" I found the "DAQmx connect terminals.vi" which allows for connection and inversion of signals. Unfortunately, there is no information about optional routing in the product documentation for the NI 6010. Guess I'll have to test this also on the hardware :-)

Hi LabVIEW users! How can I generate a pulse train that is the inverted signal of another pulse train? I know how to start pulse trains with proper configuration of time and frequency, and that I can start two trains with inverse idle states, but how do I ensure that they are properly synchronized? I'm using a NI PCI 6010 with two counters... /BjarkeT

Thank you all for great replies!!! Now it's time for reading :-)

So true! I'm building both the transmitter and receiver, so I can pretty much decide everything... The data to be sent is both measurements taken from a DAQ device and commands to start and stop measuring. I see a lot of different possible solutions and could go from there. However, my question was intended to be more general than that. I'm interested in dos and don'ts such that I can improve the quality of my code...

Hi! I've studied the simple serial communication examples in LabVIEW and knows how to set up and close a connection. But how do I take the next step? What is good programming practice when developing a routine for serial communication? My application is about streaming data via RS232, and I would appreciate references for further development /Bjarke

Thanks for the answers! I'll try to add a control to the Express VI as suggested. Best Regards Bjarke

Hi! I'm building an executable which is to be distributed on a number of different machines. The top-level VI includes a number of Express VIs with channels to a connected DAQ-pad. My worries is about the configurability of the channels when the executable has been build - if another computer has registered the DAQ-pad with a different name (e.g. "Dev2") I suppose I won't be able to run the executable? Any suggestions for a solution? I don't see any input parameters on the Express VIs that allows for changing the device name at run-time...