Please convert to LabVIEW 6.1

The attached VI is for LabVIEW 7.0 or higher. I have LabVIEW 6.1. Can anyone please convert it for me?
Thanks, Arno
Attachments:
CalculateOffset_forforum[1].vi ‏139 KB

The three subvi's (Cross Correlate, Mean, Peak Detect) could not be saved to previous version. I deleted these and saved the main to 6.1. You will have to insert the three subvi's from your 6.1 function palette.
- tbob
Inventor of the WORM Global
Attachments:
CalculateOffset_forforum%5B1%5D[1].vi ‏119 KB

Similar Messages

Please Convert from LabView 2013 to 2011

Hello, Could someone please convert these VIs from LV13 to 11 please?
Thanks,
Laura
Solved!
Go to Solution.
Attachments:
Syringe Pumps New.zip ‏953 KB

Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
Syringe Pumps New.zip ‏364 KB

Convert from LabVIEW 2011 to LabVIEW 9.0

Please convert from LabVIEW 2011 to LabVIEW 9.0
Attachments:
Watlow Vis.zip ‏76 KB

Looks like somebody forgot to attach the zip file. Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
Watflow.zip ‏57 KB

Please Convert Vis from Labview 2013 to Labview 2011

Please convert the attached Vis from Labview 2013 to Labview 2011
Solved!
Go to Solution.
Attachments:
Convert from2013 to 2011.zip ‏255 KB

Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Attachments:
Converted to 2011.zip ‏176 KB

Please convert Labview 2011 file to Labview 7.0

Please convert Labview 2011 file to Labview 7.0. Thanks alot!
Attachments:
FreqResponse.vi ‏104 KB

attached
You will need to replace the front-panel graph. Downconversion sometimes corrupts graphs.
Attachments:
FreqResponse.vi ‏299 KB

Please Convert tktds5xx from LabView 2012 to LabView 2011.

I was directed here to have an instrument driver converted from LabView 2012 to LabView 2011.
Thanks in advance!
Solved!
Go to Solution.
Attachments:
tktds5xx.zip ‏777 KB

Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Attachments:
tktds5xx.zip ‏529 KB

Reference Library for Converting Between LabVIEW and XML Data (GXML)

Please provide feedback, comments and questions on the Reference Library for Converting Between LabVIEW and XML Data (GXML) in this thread.
The latest version of the NI GXML Library is availble in VIPM on the NI LabVIEW Tools Network repository.

Francesco, Thank you for the feedback. With this component it was my intention to make a more "terse" version of the LabVIEW Flatten to XML VI that was also supported on RT and that gave the user more flexbility regarding the structure of the parsing type definition. I think you are right that the XML parser is not compliant to section 2.11 of the XML spec. The parser does specifically looking for a #D#A and this appears to be an oversight on my part. Please confirm for me, the specifcation is saying that the XML parser should be able to recognize three possibilities as an "end of line" character: #D#A, #D, or #A. Am I reading this right?There are more efficient (and in some cases much more efficient) ways of sharing data between LabVIEW and LabVIEW: some examples are flattened binary strings and the datalog binary format. XML is slower than these optons but the upside is that it is human readable. Furthermore XML is inherently hierarchical which is convenient for complex data structures like clusters of arrays of clusters, etc. If you don't care about human readability then you are correct XML doesn't make as much sense.I will return to the GXML source code and try to fix this in the near future but I would hope that instead of creating yet another custom VI from scratch that you could reuse what I have provided for you. I included enough documentation in the source code so that users could make some modificiations themselves. The target application for this reference library was LabVIEW to LabVIEW communication. As such I documented the schema on the dev zone document from a LabVIEW perspective. It includes all the supported datatypes and all the supported data structures (cluters, arrays, multidimensional arrays, clusters of multidimensional arrays, etc.) I do see some value in making a more conventional XML spec but the time investment required didn't really line up with my intended use case. Were there any other downsides to GXML that I have missed? Best Regards, Jeff TippsSystems Engineer - Sound and VibrationMessage Edited by Jeff T. on 04-21-2010 10:09 AM

Heidenhain IK220 drivers - please convert from 5.1.1 to 2011

Hi,
I have some drivers for a Heidenhain IK220 PCI card - according to an error message in LabVIEW 2011, the drivers are too old to use. Could someone please convert them to a LabVIEW version I can use?
Thanks
Ben
Solved!
Go to Solution.
Attachments:
IK220.llb ‏1362 KB

Hi,
Here is is also in LV 2010
Kees
Attachments:
IK220.llb ‏703 KB

Please convert from LV2013 to LV2011

Hi, can someone please convert the following LabVIEW 2013 file to LabVIEW 2011? Thanks!
Edit: Thanks for the quick response!
Solved!
Go to Solution.
Attachments:
Actuator Control.vi ‏22 KB

Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Attachments:
Actuator Control.zip ‏11 KB

Convert from Labview 5.1 to labview8.6

Hello Everyone,
Can any one please convert this vi from labview 5.1 to labview 8.6 or labview 2009
Thanks in advance
Nadim
[email protected]
Attachments:
4-Channel Power Spectrum with estimate.vi ‏750 KB

Hi,
Here it is in LV 8 but there are some VI's missing (DAQ)
Kees
Attachments:
4-Channel Power Spectrum with estimate.vi ‏402 KB

Need to convert to labview 11 from labview 12

hello
I need to convert the following Labview 12 VIs to Labview 11.
thank you in advance
Attachments:
QAM Demodulation.vi ‏30 KB
QAM Modulation.vi ‏30 KB
rx QAM.vi ‏57 KB

The conversion was done here: http://forums.ni.com/t5/Version-Conversion/need-to-convert-from-Labview-12-VI-to-Labview-11/m-p/3021...
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Converting from LabView 4.0 to 8.5

I have a Pico Technology TC-08 thermocouple datalogger (RS232). It has drivers for Labview 4.0 but I use Labview 8.5, which says it can't convert the drivers. From the help pages I have understood that there is separate software that can convert from Labview 4.0 to 8.5. Can anyone tell me where I can download or otherwise obtain this software?

Hi EKY,
converted to LV7.1 - should be ok now
But: there's a "missing dll"-error. You have to check this in LV8.5.
There is also no guarantee the dll will work with LV8.5 or maybe new operating system (from Win95 to WinXP or Vista?)
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome
Attachments:
TC081_LV71.LLB ‏29 KB

Please convert the attached vi's from V8.6 to V8.5

Hi,
Please convert the attached vi's from V8.6 to V8.5.
Thanks so much!
Ed
Solved!
Go to Solution.
Attachments:
COMSelect_86.zip ‏21 KB

Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
COMSelect_85.zip ‏20 KB

Please convert this query to update.

Hi Experts,
Please convert this MERGE statment to UPDATE.
MERGE INTO CUSTOMER_DTLS CDT
    USING
        SELECT CDT.CDT_ID, CDT.CDT_ITEMREQ_NO, CDT_UNIT_NO, CDT.CDT_UPDATE_DT, OST.SalesName, OST.Team, OST.Team_ID
        FROM CUSTOMER_DTLS CDT
        INNER JOIN REVEN_MAP RMP ON CDT.CDT_ID = RMP.ORG_ID
        INNER JOIN SALES_DTLS OST ON RMP.WB_IBU = OST.IBU AND OST.Rep_Code = CDT.CDT_SECSALESREP
        WHERE CDT.PRODUCT_SEC = 'M'
        AND CDT.CDT_ID = 600
    ) SALES_QUERY
    ON(
            CDT.CDT_ID = SALES_QUERY.CDT_ID
        AND CDT.CDT_ITEMREQ_NO = SALES_QUERY.CDT_ITEMREQ_NO
        AND CDT.CDT_UNIT_NO = SALES_QUERY.CDT_UNIT_NO
        AND CDT.CDT_UPDATE_DT = SALES_QUERY.CDT_UPDATE_DT
        AND CDT.PRODUCT_SEC = 'M'
    WHEN MATCHED THEN
    UPDATE SET CDT.CDT_SALES_REP = SALES_QUERY.SalesName,
            CDT.CDT_OutSide_SALES_DTLS     = SALES_QUERY.Team,
            CDT.CDT_OutSide_Team_ID        = SALES_QUERY.Team_ID
    WHERE CDT.CDT_SALES_REP IS NULL
    AND CDT.PRODUCT_SEC = 'M'
    AND CDT.CDT_ID = 600;
Please help me.
    Thanks.

Hi All,
The merge query first doing join and make it as a SALES_QUERY query.
        SELECT CDT.CDT_ID, CDT.CDT_ITEMREQ_NO, CDT_UNIT_NO, CDT.CDT_UPDATE_DT, OST.SalesName, OST.Team, OST.Team_ID
        FROM CUSTOMER_DTLS CDT
        INNER JOIN REVEN_MAP RMP ON CDT.CDT_ID = RMP.ORG_ID
        INNER JOIN SALES_DTLS OST ON RMP.WB_IBU = OST.IBU AND OST.Rep_Code = CDT.CDT_SECSALESREP
        WHERE CDT.PRODUCT_SEC = 'M'
        AND CDT.CDT_ID = 600
    ) SALES_QUERY
On top of it using the result of SALES_QUERY checking the following matching.
ON(
            CDT.CDT_ID = SALES_QUERY.CDT_ID
        AND CDT.CDT_ITEMREQ_NO = SALES_QUERY.CDT_ITEMREQ_NO
        AND CDT.CDT_UNIT_NO = SALES_QUERY.CDT_UNIT_NO
        AND CDT.CDT_UPDATE_DT = SALES_QUERY.CDT_UPDATE_DT
        AND CDT.PRODUCT_SEC = 'M'
But in your update it's just joining and after that not used any of these values for comparison.
CDT.CDT_ID, CDT.CDT_ITEMREQ_NO, CDT_UNIT_NO, CDT.CDT_UPDATE_DT, OST.SalesName, OST.Team, OST.Team_ID
How this works.
Please explain.
Thanks.

Please convert decode query to case expression

Please convert decode query to case expression
Decode(Sign(id), 1, id, null) positive, Decode(Sign(id), -1, id, null) negative from dual;

this is a serious forums that help people, if you want that we do your "homeworks" i must told you that you should pay us for that.
Edited by: Fran on 05-jun-2013 23:41
1002966
Handle:      1002966
Status Level:      Newbie
Registered:      Apr 28, 2013
Total Posts:      20
Total Questions:      12 (12 unresolved)

Please convert to LabVIEW 6.1

Similar Messages

Maybe you are looking for