Turn on suggestions

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page

05-22-2008 08:51 PM

Options

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report to a Moderator

Hi guys

I need to convert some program from mathlab to LV.

However, I have little idea which to node to use.

So, i will have a few question for u guys

1) Because I m a lazy person, I dun wan to start to write the code from scratch in LV.

I heard about

05-22-2008 08:56 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report to a Moderator

oops =.= lets continue here

basically, which one is more easier? whats the difference?

2)whats is the preparation i need to do

3) i have done some reading up on matlab script node; basically all function in matlab can b used there because of script server.

so, does that mean we need a matlab in the pc. Do i need to set any path while to connect or sth?

4)math script node. based on my understanding, we need to save the m file of that function in labviewdata. then we can call the function as usual. so m i right? tell me more.

if possible, can u guys sent me an example. just use a particular function from matlab in labview.

thank you

05-23-2008 12:12 AM - edited 05-23-2008 12:12 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report to a Moderator

Yes, to use the matlab script, you need matlab installed.

You can also chose **scilab** as a script server for a free alternative (see http://www.scilab.org/download/index_download.php?page=SLG.html), it is similar to matlab.

Open the example finder and e.g. search for mathscript. Maybe one of the examples will answer your questions. Have you tried?

What is your LabVIEW version?

Message Edited by altenbach on 05-22-2008 10:12 PM

05-23-2008 10:52 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report to a Moderator

For more details, please continue in the mathscript forum:

05-24-2008 02:14 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report to a Moderator

labvie 8.5. why? is there any problem?

05-24-2008 11:46 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report to a Moderator

sean1985 wrote: labvie 8.5. why? is there any problem?

No, but it is generally a good habit to always mention what version you are using.

Mathscript is a relatively recent addition to LabVIEW and has received increased functionality with every new release. Have a look at the LabVIEW 8.5 release notes to see all the newly added functions and features. Over six pages worth!! 😄

For this reason, the version information is important so we can be sure we are talking about the same thing. You have 8.5, so you're all set. 🙂

02-05-2010 07:32 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report to a Moderator

Hello Sir Knight AltenBach:

Some comments on capabilities of MathScript versus Matlab and recently the new ScieLab 5.2. I started using it for LV8.2 for work involving quantum noise statistics in image sensors . Although it has increased more analysis functions and speed for each new LabVIEW release, there are serious limitations of this tool. So its probably only good as some small code insertions between codes for hardware calls for processing signals when they become available as arrays. First, "not all functions is supported in LabVIEW Runtime" e.g. get (), set () etc. so scripts stays as long as LV Development environment stays with it to execute it. Second is - it still does not support "multi-dimensional arrays" - consider for example converting an RGB image to an array in LabVIEW and wiring the result as input node array here [nn,mm,nc] = size(array); can't work but [nn,mm] = size(array); don't receive a complain - in other words we can't go beyond 2D array math with MathScript. The third, is Mathlab will not work entirely with calls to Matlab or Scielab toolkits (Scielab nodes only works on LV8.0 to 8.2 for lower than 5.2) . So m-scripts should be written carefully inside these nodes! Forget cell arrays {}, forget structs, forget multidimensional arrays. Fourth, is that you can define m-functions and actually execute it but only on a MathScript Window, you need to actually wire in every text on the script inside a MathScript in a new VI identifying all the entries and exit node variables to connect to. If your trying to save ~USD$5K for a Matlab license and felt you need to do it in "hybrid style programming" interfacing the IO instrumentation capability of LabVIEW with the efficient array processing in Matlab - you probably need to work with them together anyway because you need to cut and paste every command you did in Matlab to the command window of MathScript - type help for each keyword built-in function and observe how they behave if at all they do the same thing or not.

Bernardino Jerez Buenaobra

Senior Test and Systems Development Engineer

Test and Systems Development Group

Integrated Microelectronics Inc.- Philippines

Telephone:+632772-4941-43

Fax/Data: +632772-4944

URL: http://www.imiphil.com/our_location.html

email: Bernardino.Buenaobra@ph.global-imi.com

Senior Test and Systems Development Engineer

Test and Systems Development Group

Integrated Microelectronics Inc.- Philippines

Telephone:+632772-4941-43

Fax/Data: +632772-4944

URL: http://www.imiphil.com/our_location.html

email: Bernardino.Buenaobra@ph.global-imi.com

02-10-2010 02:04 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report to a Moderator

We have used the matlab script window heavily out of necessity. Our lab equipment and some initial analysis was done in LabView. The whizbang "algorithmists" did their work in matlab. For us to meet some deadlines, it was necessary for us to make the things work together and still maintain their seperate maintenance envrionments. What we did was to bring all the input variables into the matlab script window, make a directory definition line of code and then call the function in matlab, passing in all the variables defined at the input edge of the script window. When the function call to matlab completed, it wrote the output variables to the output variables we had defined in the function call and then returned the MatLab directory to where it had been before the call. (This is Texas, always close the gate after you go through or you get to go find the cows...). By doing it this way, we allowed the matlab developers to work "independently" from the LabView developers....each using the latest version of their software. MatLab has some powerful tools in its development environment.

If you do it this way, you should be able to break down the functions within Matlab and convert / test them a little at a time.

Hope that helps

Hummer1