speed difference between running mathscript node on LabVIEW and on cRIO

[tarzanyu]

My system are CRIO-9024, LabVIEW2009 with RT Mathscript Module.

I am developing some structure fatigue analysis LabVIEW interface, and using the Mathscript node to do the principal stress and rainflow counting calculations.

I am not sure if I need to install the RT Mathscript Module to the CRIO to make the mathscript code as fast as when they are executed on my laptop. I also couldn't find an option to install them through the MAX.

The principal stress code only takes less than 6 seconds to process 12 stress channels and 30000 records, but after it is deployed on the CRIO, it will take more than 2 minutes to process the same amount of data.

Any ideas? Thanks guys. 

Message Edited by tarzanyu on 02-25-2010 04:47 PM

[Hueter]

You should upgrade to LabVIEW Service Pack 1. Real-Time SP1 has some big performance improvments for deterministic math.

Check out this KnowledgeBase for more details.

LabVIEW 2009 SP1 MathScript RT

You can download SP1 in the Services Resource Center

ni.com/src

[tarzanyu]

Thanks Heuter. I will give a go.

There are three downloads related to my work, LabVIEW 2009 SP1, LabVIEW 2009 SP1 Real-Time Module, LabVIEW 2009 SP1 Mathscript RT Module. Should I install all of them or just the last one.

But they seems not be able to explain the reason of the execution speed diffference between the LabVIEW windows and CRIO platform.

[jattas]

Hello,

You should install all three SP1 products.

Depending on the kinds of things that your code is doing, it could make sense that MathScript in LabVIEW 2009 is significantly slower on cRIO than Windows. Resources (memory and CPU) are much more limited on cRIO than on a desktop machine. Compounding this, the 2009 MathScript RT Module was not optimized for memory or CPU usage. We fixed many of these inefficiencies in 2009 SP1.

Please give SP1 a try and let us know how it goes. If you still see problems, the SP1 release has some new tools for tracking down the cause of timing and determinism issues.

jattas

LabVIEW MathScript R&D

[tarzanyu]

I managed to use LabVIEW code to do the rainflow counting instead of the mathscript code. The speed is fine now and I can do 500 Hz under scan mode without any problem. As there is a deadline to meet, I haven't got a chance to try the three SP1 upgrade packages, but definitely will try it when I finish off the things in my hand. Thanks again guys. 

[ttrr]

Rainflow counting ...

Have you ever checked this page?

Rainflow Counting Algorithm

http://decibel.ni.com/content/docs/DOC-6553