Hello Sreenivasulu,
In LabVIEW 8.2, the MathScript node did not support automatic error handling. Thus, even though no errors appear when running your VI, there are still a few problems. You can help the situation by creating an error out indicator from the MathScript node.
The first error reported is that the range on line 8 is too large. This is solved by giving some default (nonzero) values to fc and fb on the front panel. Next you will see an error about m being an undefined variable. Defining m will fix the problem. Finally, you will see an error about bitgen being an unknown symbol. To fix this, you can do one of two things. You can place bitgen.m in your "My Documents\LabVIEW Data" directory. This is the default search path for .m files. Or, you can add the directory where your have your .m files to the MathScript search path. You can modify the search path with the "path" and "addpath" commands. If you plan to store the .m file next to the VI, a neat trick is to use the "Current VI's Path" primitive to obtain the path to the .m file. I do not see the problem you mention when using the input function. Could you modify the VI such that it exhibits the problem?
Grant M.
Staff Software Engineer | LabVIEW Math & Signal Processing | National Instruments