order analysis, executable and LabVIEW 8.0 RT

[Kallis]

Hi,

I'm facing a peculiar problem. I have a LV RT code which uses VIs from order analysis toolkit. The program as source code works perfectly. But when I create an RT startup application and deploy it with debugging enabled, the application gives a broken arrow. I was able to track down to some four VIs.  All these four VIs use functions from order.dll (like OAT Single Stage Interpolation with IC). There are no description for the errors. I tried to build the application after installing OAT runtime in the host PC. But that also didn'thelp. I am using OAT 2.1, with LV RT 8.0. Hope someone knows whats going on...

Thanks in Advance

Kallis

[Prashanth]

Hi Kallis,

Have you followed the procedure mentioned in the 'System and Software Requirments' section of the OAT 2.1 Readme file? The read me file is attached below as well. Have a great day!

Regards,
Prashanth

[Kallis]

Thanks a lot Prashanth,

Looks like that may be the issue. I will try it out and update you.

Thanks again and have a wonderful day.

Kallis

[Kallis]

Hi,

Even after I changed the dll to the RT-dll, the executable is still not running.  Now when I try to connect to the remote application (using the 'debug aplication or shared library' utility), I get a 'failed to connect to remote appliction' message. So not able to realy know what's happening there inside RT. After this I tried to build an application which has only one vi which calls the 'OAT convert to even Angle Signal (1 channel) as a subVI. With this, the remote debugging works, but again the VI will show a broken arrow. The error is with the same old VI (OAT single stage Interpolation with IC.vi). Now I'm really running short of ideas....

Bye

Kallis

[Prashanth]

Hi Kallis,

When you replaced the RT-dll did you replace it with version 8.0 RT-dll? If you create a regular RT executable and not a debug exe does the result change? Also, would you be able to create a debug executable for Windows O.S and see if you can get that to work. This will tell us if we should concentrate our debugging effort on RT OS or more towards the OAT vis. Thanks and have a great day!

Regards,
Prashanth

[Kallis]

Hi Prashanth,

There was only one RT-dll in the installer CD ( inside 'RT Dll' Folder) which I copied to C:\WINDOWS\system32. I was not able to find any seperate 8.0 RT Dll. The regular RT exe (w/o debugging) also doesn't works. But in Windows, exe with or without debugging works perfectly. Thanks,

Kallis

[Prashanth]

Hi Kallis,

It may be that the dependencies of your executable are not being FTPed over to the RT controller correctly. One thing to try would be to manually ftp these dependencies over to the RT controller. You can find out about the dependencies of your vi by taking a look at 'Dependencies' section of your project explorer window. Please let me know if this doesnt work. Have a great day!

Regards,
Prashanth

[Kallis]

Hi Prashanth,

What we found out is that in the dependencies for the RT code, LV identifies order.dll as a mising dependency (see the attached picture). Also how can we manually FTP a dependency. To which folder do we have to keep this file?

Kallis

[Prashanth]

Hi Kallis,

Have you tried to ftp the order.dll to 'root//NI-RT/SYSTEM/' folder? Just open up an Internet Explorer window and use a url similar to this 'ftp:// YourControllerIP//NI-RT/SYSTEM'. Have a great day!

Regards,
Prashanth.

[Kallis]

Hi Prashanth,

I tried this, but the problem remains.

Kallis