LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

downconvert LV2011 to LV2010 problems

Solved!
Go to solution

Hi,

I have this VI that was written in LV2011, now I just have LV2010 to work. Yesterday I downconverted it to LV 2010, but now it doesn´t work...Can anybody help me here please?

 

Best regards,

Jimmy
Download All
0 Kudos
Message 1 of 8
(2,777 Views)

have you checked out the version conversion board? link at the top of this discussion page

Please remember to accept any solutions and give kudos, Thanks


LV 8.6.1, LV2010,LV2011SP1, FPGA, Win7
Message 2 of 8
(2,776 Views)

Hi Jimmy,

 

I told you before to use the Conversion board!

Why do you create a new thread again instead of using that board and instead of reusing your old thread? Why don't you put a link to that older thread?

 

"But now it doesn't work"

Ok, may happen. But what exactly doesn't work anymore? Any error numbers?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 3 of 8
(2,769 Views)

Hi GerdW,

sorry...you're right.

When I run the program now, it shows wrong results...results that are not physical possible...

Do you have a clue of what can be the issue?

 

Best regards,

Jimmy
0 Kudos
Message 4 of 8
(2,760 Views)

can you post a vi or png file of the code and some explaination of what you would like it to do?

Please remember to accept any solutions and give kudos, Thanks


LV 8.6.1, LV2010,LV2011SP1, FPGA, Win7
0 Kudos
Message 5 of 8
(2,757 Views)

I had downcoverted that code for you. That code relies on DAQmx. Did you create the tasks in the same way as they existed on the computer that ran the LV2011 code?

0 Kudos
Message 6 of 8
(2,751 Views)

Hi smercurio,

yes i know you downconverted it for me yesterday...and everything is like it was on the other computer...but somehow the data results are not right...

Thanks

Jimmy
0 Kudos
Message 7 of 8
(2,744 Views)
Solution
Accepted by topic author GoncaloPT

Well, we can't run your code, and we can't see into your computer, so we can't see what the data is, so you're going to need to do your own debugging. Run the VI with highlight mode on and use some probes to look at the values on some wires to track down which part "isn't right".

Message 8 of 8
(2,737 Views)