vision builder invalid inspection

[aucci]

Hello,

I am using NI Vision Builder to test software with 2 cameras on a product developed by our company.  I recently changed the ports of both cameras on my firewire card that has 3 ports to gain added accessibility to the other port.  This caused major problems on my setup and every inspection that I opened, modified and saved since I made the change gets corrupted, and then can no longer be opened.  When I go to select those inspections I get a pop up that says 'Invalid Inspection File".  I have the need to be able to port this over to different PCs and if the files get corrupted whenever the cameras change, it is going to cause a lot of problems for our system.  Is there anyway to fix these sequences and prevent this from happening on my PC and any further ones that we may need to run these inspections from?  I have added an attachment of one of the corrupted inspections if this helps.

Thanks

April Ucci

[seVEMes]

April,

After you changed the ports did you reconfigure your cameras in Measurement and Automation Explorer (MAX)? If so, did you reconfigure them in Vision Builder (VBAI) after MAX?

Is there any other information on the "Invalid Inspection File" error? If so could you attach a screenshot of that error?

[aucci]

I did get the cameras configured again (I put them back into the original ports and checked that they worked in MAX), but I don't know what you mean about configuring the cameras in VBAI.  Are you talking about the sequences?  Because after I got the cameras working again, I could open the sequences one more time, but after saving it, I can't open them.  So I can no longer configure the sequences.  I've attached a screen shot of the error, but there isn't really any information on it.

Thanks,

April

[aucci]

Hi,

Well I figured out that the issue was that I was attempting to open a vision builder sequence that was saved in 3.5, in version 3.0.  I know in other NI programs the error is more descriptive and tells you what the problem is, where "Invalid Inspection File Selected" is rather vague.  Perhaps this could be changed to be more descriptive?

Thanks for your help.

April