PJM_labview

QUOTE(Herbert @ May 1 2007, 09:00 AM) Thanks for pointing to that thread. Unfortunately the described workaround (Check the found output) does not work. In the example I provided, If you probe the SubVI (Read Data Header from TDMS.vi) found output of the TDMS Get Property, you will see that it return True when reading a TDMS file with no header, meaning in return true when the property does not exist (See Below). http://forums.lavag.org/index.php?act=attach&type=post&id=5687 QUOTE(Herbert @ May 1 2007, 09:00 AM) ...Thanks for catching that. I had never seen that one. It seems to crash only if the output is a variant. CAR# 4909S6WJ. Thanks for the CAR. PJM

The attached VIs demonstrate 2 bugs with the TDMS Get Property primitive 1) Attempting to read properties that do not exist from a TDMS file return whatever was last read from the TDMS get property primitive (from whatever was the last TDMS file the TDMS get Property was invoked on). This is VERY confusing. Severity: High Work Around: Sort of one: Generate an explicit error with the property you are attempting to read prior you read them (see attached example). 2) Attempting to invoke TDMS get Property with a blank property name input on a TDMS file does crash LV Severity: Medium Work around: don't read blank property name To see both these bug in action, extract the attached zip in a folder and run "demo bug.vi" and use the provided TDMS files "No Header Info.tdms" and "Has Header Info.tdms" in the TDMS file Path Controls Note1: The "No Header Info.tdms" contains a sinusoid waveform Note2: The "Has Header Info.tdms" contains a header with file type="Trace Data to TDMS" and file version="2.0" http://forums.lavag.org/index.php?act=attach&type=post&id=5675 http://forums.lavag.org/index.php?act=attach&type=post&id=5677 http://forums.lavag.org/index.php?act=attach&type=post&id=5676

I think you could do that using a standard XY graph. Since LV 8.0, there are 3 additionals image plot that you could use to draw your compass picture. So here how it goes: -Rotate & Plot your XY data -Rotate & Plot your Image on the PlotImage Front (you might have to use a mask to get some transparency [see through]) Note: This will require some work but this is doable Note2: Search the NI Forum for routines to rotate images PJM

I felt generous today. I rewrite your VI to do what I think you want (I am far from certain that this is the case though). http://forums.lavag.org/index.php?act=attach&type=post&id=5666 http://forums.lavag.org/index.php?act=attach&type=post&id=5665 I add quite a few comments that should answer most of your questions. PJM http://forums.lavag.org/index.php?act=attach&type=post&id=5664

This is correct for the supported type. Currrently the set TDMS property primitive does not support every type, therefore, converting to string is a good stop gap solution until the time where all types are be supported. PJM

QUOTE(bbean @ Apr 24 2007, 08:51 AM) Brian Currently, the float number format is beeing used for writing numbers. The types are not store natively. PJM

If you can get your hand on LabVIEW 7.0 or greater, you could use the input device control utilities that are built in. They allow controls of keyboard, mouse and joystick. http://forums.lavag.org/index.php?act=attach&type=post&id=5646 Bonne Chance PJM

QUOTE(bbean @ Apr 23 2007, 04:03 PM) Yes QUOTE(bbean @ Apr 23 2007, 04:03 PM) I was thinking the "channel and group" write/read functionality would be additional VIs not replacements for the default option which would be to write/read everything automatically. I noticed you created separate VIs for channel/group. This does expand the API. I am not sure at this time what is best, separate VIs or additional input on the original VI (if possible). PJM

QUOTE(kate @ Apr 24 2007, 03:21 AM) Use the reshape array primitive in the array palette. http://forums.lavag.org/index.php?act=attach&type=post&id=5620''>http://forums.lavag.org/index.php?act=attach&type=post&id=5620'>http://forums.lavag.org/index.php?act=attach&type=post&id=5620 PJM

QUOTE(tibobo @ Apr 24 2007, 01:14 AM) Since LV 8.0, you can build applications with remote debugging enable (which allow you basically to debug a build app). If this option is also available for mac, I would suggest you use this. PJM

QUOTE(Tomi Maila @ Apr 24 2007, 07:02 AM) I used to work in research too (for about 9 years). While the work was challenging (understatement here), the end result was basically as follow: Do research so we can get more funding to do research so we can get more funding do to ... I eventually got tired of this and decide to join the other side where people are actually using my work for doing stuff, not just for getting more funding. PJM

Attached is a new version (1.2) of the utiliy that read write variant data to TDMS file. Change Log: - Fix bug when numeric were written to TDMS. Now evrything is read back as string then converted to the appropriate type. Read Write Variant Data to TDMS V1.2: http://forums.lavag.org/index.php?act=attach&type=post&id=5610 QUOTE(bbean @ Apr 23 2007, 07:14 AM) Brian, The group/channel example is interesting. The only draw back is that it increase the complexity quite a bit, but I can see use cases where I would want to do that. PJM

QUOTE(bbean @ Apr 23 2007, 07:14 AM) I think we should mouve back the discussion to the original thread, since this one is about a bug report. About the numeric issue, good catch. I will work more on this today. PJM

Oh my goodness, he started another thread here... Asharma: Please do not cross post to multiple forums. Post all your responses to this particular thread and not the other thread PJM

I guess I should have elaborate more. I like the idea of beeing able to get rid off some post in a "sand box" as Tomi put it, or in an some other place. I don't necessary have to be the one doing it. PJM

QUOTE(Tomi Maila @ Apr 21 2007, 06:42 AM) I like this idea. PJM

I'll be original there: I couldn't agree more. PJM

Thanks for the feedback. If there are unsupported data type, may be the help for "TDMS Get Property" should be updated to reflect that. Is there any other unsupported types? PJM

Good catch. Thanks for the bug fix too. By the way, there is also a bug in TDMS Get Property when type input is a complex number (CXT Type). PJM

There is a bug in the TDMS Get Property when type input is a complex number (CXT Type). Trying to connect the CXT data type to the data type input and a string to the property name input keep braking either one of the wire. http://forums.lavag.org/index.php?act=attach&type=post&id=5563 Note: It is sometime possible to get it connected through some undo combination but the the type does not propagate to the property value output in any situation. http://forums.lavag.org/index.php?act=attach&type=post&id=5564 PJM

I did experienced the very same bug (Broken VI Tree used to make a source distribution) while using OpenG builder a few weeks ago. I though this was an OpenG Builder Bug. This is apparently not the case. PJM

QUOTE(sam @ Apr 14 2007, 10:52 AM) Sorry, I have no information about imaq or ni-Vision. My use case required to have DAQmx working, so this is where I spent my energy at the time. May be others will have more info. PJM

I made a reader as well based again on the OpenG Variant Configuration Tools. http://forums.lavag.org/index.php?act=attach&type=post&id=5518 PJM Note: The attached llb does not required that the OpenG tools to be installed. http://forums.lavag.org/index.php?act=attach&type=post&id=5519

I just tried it a couple week ago with LabVIEW 8.20 LabVIEW 8.20 run fine but you can't install the device drivers (even manually). For example I was unable to get DAQmx to work. So unless things have been changed with LV 8.2.1, I would recommend that you do not do it. PJM

Modifying the OpenG Variant Configuration Tools works like a charm. I quickly made a writer based on the write ini cluster. PJM VariantDataToTDMS.llb