Anders Björk

Lavalily!

Is there a way to get how much memory that is allocated by the queue?

QUOTE (Aristos Queue @ May 26 2009, 11:47 PM) I meant that you should add new information (the new error code series) and for compatibility add the old code at the end of the source text eg. ":ENo:000-000-000; code 7", then with would have to live with that "old error system" used a "occupied" error code. Its translated wrong but it will less wrong by time. But thats for the layer were we have error clusters. From my point of view the basic error handling should not be to complicated, but it does not give engough information as it is.

QUOTE (Aristos Queue @ May 22 2009, 10:45 PM) Would it not be possible append a totally new errornum series to the end of the source field, introduce new error cluster definition side by side with old one and new error table? Or even better introduce a new error wire with "fields" status, Errcode, code, (time[optional]), source and Errsource, and have conversions between the new and old error handling. Then better we could have better error message in the new series, while still keep the old in place.

You need to put an additional relay there, I do not think the module who give enough current.

I had some similar problems the solution was to use "Variant to data" with no type wired! ... maybe it works for your problem as well.

One of my colleuges asked me where is the code :headbang: Although I showed him a working application, with lots of operations..

QUOTE (normandinf @ Apr 6 2009, 11:26 PM) Thanks Nancy and normandinf it was very helpful!

QUOTE (nhollenback @ Apr 6 2009, 10:40 PM) Maybe I gave it the wrong name, possibly QUOTE (nhollenback @ Apr 6 2009, 10:40 PM) Or is it related to determining the appropriate event for the event structure. If it is the latter, perhaps you should use cursors and create an event for the Cursor Release when the user releases the cursor on the point in question (unless someone else has a better idea). If it is the former, what is the scenario that is driving the use of the VI Callback as opposed to a standard Producer/Consumer type design pattern? Nancy An eventstructure is fine when have the engine to sense a click on a datapoint. Maybe cursor will do it, I tried to match the mouse position on clicking with the graph points after writing this, but seems hard to get it to work. I will probally post the code after cleaning it. Thanks for your ideas!

Does any of you have experiences in creating a callback on a click on a specific point in a graph using LabVIEW or Measurement studio? An example we calculate RMS values of time series and have plot with these RMS-values. On clicking on a point I would like to make a new window that time-series. Any hints are valueble.

It was like I expected one it is allowed to use feedback node on stacked sequence....

QUOTE (Cat @ Apr 3 2009, 02:13 PM) If one chose to use the stacked sequences it is for stepvis math algorithms and using local variables tend to get messy. I think would be very nice with shift registers instead of locals. By the way would feedback node do the work in this case? If so is the case why would not shiftregisters too. So I agree totally the locals contribute to the spagettiness. Regarding state machine why use something that is more complicated than needed for a specific task, I dont see the rationale for that. That is if the task have predefined steps and well defined steps, that do not change with time.

Make a new VI. This time focus only get the signal from the temperature measurements. When you have solved that you write a VI for the cooling and heating outsignal. Then you read up on PID-controllers. Then think how make the first bit finnished.

What hardware do you have for the temperature control? Have you written code for heating and cooling without control? Have you succedded to do manual control? After looking at your code, I strongly recommend you to read a good labview book, it will save you time. If you are having serveral tasks in parallel use parallel while loops!

Where is your specification of the task? The subproblems that needs to be solved which are those?

Something like this to read when the buffer have enough content. In the false case you should have a delay.

Well if you dont want to use the matlab-node (not the mathscript node). You could always make a "mail-box" solution. Write a MAT-file, with data and write a file indicating new data available. Have matlab scan this in box is new data exist read data-file and erase the file indicating new data available. Do the calculations write out the data file that labview can read. Have Labview scan this "mail-box".

The only real fast way to implement this is using subplot in the mathscript node. Personally I am lacking a similar functionality to subplot in native Labview, that is fast to use for several plots.

QUOTE (Kubo @ Feb 12 2009, 05:19 PM) Look under string functions and lookup the examples on serial port use!

In an exemple on GPS on NI there are VIs for spliting up such messages. http://zone.ni.com/devzone/cda/epd/p/id/2197

QUOTE (Yun @ Feb 7 2009, 12:31 AM) Where are your image indicators? You need to connect them to the IMAQ vis that outputs, is not an image control. Then drag them to the right tab on the tab control. Check IMAQ examples for ideas.

QUOTE (BobHamburger @ Feb 1 2009, 02:40 PM) I think NI should provide index/-es as an output not only the median value. Certainly it is in their computations, why not gives us that data too.

QUOTE (Laur @ Feb 1 2009, 12:54 AM) A workaround: You could sort your data first and take out index at 50% (of max index) of your sorted data. Aha! If you think of the definition of median... you will realize why you get -1.. You need to be very lucky to get a element that is equal to an average of the two elements in the middle.

QUOTE (jojo_lapin @ Jan 28 2009, 10:59 PM) Ok Read mat-file while run DAQ in parallel, yes it is possible!

QUOTE (vultac @ Jan 28 2009, 11:26 PM) I would look up state machines. The major components of a state machine is: While loop, Case structure and shift registers.