After upgrading to LV7 I have so far seen the following "bugs";
- In a VI we had an array initialized incorrectly with a U8 constant (should be U16). The array was going into a shift-register, and in another case within the loop the same register would get some elements replaced with U16 values...This made LV6.x to set the shift-register to be U16. However when converting to LV7 the priorities seem to be a bit different so the array became U8 instead...causing overflow. It was a fault to have the array initialized using a U8, but it's a bit sceary that LV7 changed the type of the array.
- At one point we built an application in LV7 and ran it in a folder where the old 6.1 runtime engine files were...If this had been an 6.X app in a
folder with 5.x RTE you would get a message telling you that the runtime engine was of a different version...With an LV7 app and LV6.1 RTE however the only thing that happens is that a file dialogue pops up asking you to select which VI to open...It took some time before we found out that there was an old RTE in the same directory causing this behaviour (there's a lot of files).
Apart from those two episodes the lack of support for the old serpdrv files, forcing everyone to use VISA...is a bit annoying. We never use the LV app builder to make installation sets, so using the new Include serial support option there is not a solution (is there an updated description somewhere on how to install the necessary files etc. using a third-party install kit?), and in any case it would be nice to not see National Instruments mentioned on-screen during installation...as you do now if you enable the serial support part of the installer. So far we've just ported the old serpdrv based VIs to LV7 a
nd they still work fine...
