09-02-2011 06:10 AM
You can convert your 2D variant array directly into a 2D string array with the Variant to data if you wire a 2D string constant to it. 🙂
Congrats on the solution, those issues are horrible.
/Y
09-02-2011 11:42 AM
Thanks for the suggestion Yamaeda. I actually had already implemented that, and also pulled the call to LV Numeric Types out of the double loop, as part of minor optimizations.
While talking to someone else over here I decided to do a silly experiment, which is to convert everything to double (I know it won't work) and then format into string to put the results back into the cluster.
Surprisingly, if you do it as one call, like Yamaeeda suggests, the code bombs out very fast as it errors out and returns an empty double array of double values.
However, if one converts one at a time in a double loop, the code goes into the bad behavior that I saw, taking for ever to try and convert the values to doubles.
It looks like the conversion from OLE_VARIANT VT_NULL to LabVIEW double has some major problems...
And yes, these issues are horrible. And they're not the only problems I have with LabVIEW, but those belong in other threads if anyone wants to hear...
01-10-2012 04:12 PM
I have the same code running the whole sequence in 70sec : labview 8.2, win xp 32 bit, 2GB memory.
But, the same code run 16min in a new computer , 2GB memory, 4 core intel, labview 2011, win 7/...
REally, doesnt make sense.!!!
01-10-2012 04:58 PM
Well, I would suggest to you that LabView is perfectly geared for factory automation whether it be processes, testing, assembly, or whatever you can dream up. And yes, plenty of uses in the Lab as well.
01-10-2012 04:59 PM - edited 01-10-2012 05:01 PM
@craftindo wrote:
I have the same code running the whole sequence in 70sec : labview 8.2, win xp 32 bit, 2GB memory.
But, the same code run 16min in a new computer , 2GB memory, 4 core intel, labview 2011, win 7/...
REally, doesnt make sense.!!!
I'm sure that if you find the root cause it will make perfect sense. Are you asking a question? You should give some details about your application. What kind of resources does it use? GPIB, serial, Ethernet?
[Edit: You might want to post a question along with those details to a new thread. If possible you should also post your code. Someone will help you find the problem]
01-10-2012 05:02 PM
hi CLAD,
saying good but no solution, is as good as nonsense....
1. can you solve my issue?
i've been working with many tech support engs...but so far no success to solve my problem...
the problem is very simple...
upgrade the old system labview 8.2 ....
but, now since daq hardwares are nt supported anymore by 8.2 version, so i have to upgrade the code of 8.2 which is running well into labview 2011 version, where all stupid problems come up with no solution!!!!
the project seems to be simple...:
but i really warn all guys out there, becareful... many stupid problems ahead!!!!
01-10-2012 05:04 PM
Take a breath
Did you just upgrade your OS and LabVIEW version? I got the impression you got a whole new computer. It could be some kind of driver issue with your new hardware.
01-10-2012 05:05 PM
well, i have talked with many tech support engs....
but many suggesstions i have tried...one of them is to re-install labview...
but no success.....
even i can't compile to exe,, because some of the functions are not there...but strange it runs well under labview....
and there are many more problems......
can i get a competent tech support????
you can email me, find my details in NI....
it's useless to post questions here, as i have tons of questionss.....
01-10-2012 05:05 PM
nonsense answer!!!!
look....stupid answerss....
01-10-2012 05:15 PM