LV 7 upgrade - VXI word serial problems

[enzomatic]

We are trying to upgrade some software that was written with LV 5.0.1 on WIN NT, using Labview 7 on a PC running WIN 2K pro. After re-compiling, the Corelis CVXI-JTM VXI module(message based) drivers delivered the error in a one button dialogue " VI Corelis Setup.vi was stopped at node 0x6D4 of subVI 'WScmd.vi'." We've tried substituting the 'OLD' WS commander vis with the same results. Using VISA VXI cmd or query to substitute in the VI, I received the error "Could not perform operation because of IO error".
Any suggestions why this might be occurring, or possible solutions you could give would be helpful.
Thanks,
Enzo

[JustinBritten]

Hello Enzo,

When you upgraded from LabVIEW 5.0.1 to LabVIEW 7 did you also perform a driver update? If so, then you may have installed drivers, such as VISA, for example, which are not compatible with the Corelis driver you are using. Our drivers have changed significantly since LabVIEW 5.0.1 and they may simply not work with your Corelis VIs. If you did perform a driver upgrade, you may want to contact Corelis and check that the new NI driver versions are compatible with the version of their driver which you are using.

You may find the current versions of all NI software installed on your computer by launching the Measurement & Automation Explorer program and viewing the Software tab. You can also view software versions from the Windows Add/Remove Progr
ams icon in your Windows Control Panel.

Best Regards,
Justin Britten

Applications Engineer
National Instruments

[enzomatic]

Thanks Justin for the quick reply,
We did have the same problem when using the older versions of the drivers also. Corelis support was helpful, but the driver vis were not developed by them.
We currently have sidestepped the problem by replacing all of the vxi word serial vis with visa vis in all of the driver vis and it appears to be working correctly with the exception of the Corelis module self-test command which only works when the timeout property is increased for that command from 2 to 13 seconds. This has no impact on our application.
Thanks again for your help.
Enzo