07-21-2012 06:44 AM
Hi , guys. has any of you nice people ever seen something like that ... in deployment progress?
Thanks in advance.
07-25-2012 03:15 AM
Thanks for your post. I'm sorry to hear you're having an issue with your deployment.
My first suggestion (which you may have already tried) would be to format and reinstall the software on your sbRIO. The error sometimes gets caused by corrupt files, so we need to rule that out first.
Make sure that you install all the necessary software components on your RIO - namely IMAQ in this case.
Let me know how you get on.
07-30-2012 01:54 PM
thanks for your help. I re-installed the IMAQ software, it seems working.
but i have some similar errors now, and i dont know which module i should re-install, could you tell me where the problem is, please.
the name of which module would be great.
thanks a lot.
07-31-2012 03:19 AM
Glad to hear the first errors are sorted now.
All three of those errors are because the niFPGA library appears to not be installed (or is corrupt) on the RIO. The FPGA library is a module for LabVIEW that you can download from our website. The latest version on our website is 2011 SP1. I suggest you download the module, reinstall this on your PC and then reinstall the RIO.
08-01-2012 04:03 PM
Thanks for your last reply.
I tried to format the disk and reinstall all the software on the RIO, the same software as my classmates. The same problem happened again.
When I used other RIOs ,all my labview software worked on them, Now I have no idea why mine is not working.
Here is the list of software I installed, did I miss anything?
08-06-2012 05:39 AM
I can't see anything obviously missing from the list of software.
You mentioned that other RIOs run your code correctly. That could be down to the versions of software that you have installed on your RIO and PC. Can you look at the software on one of the working RIOs and check to make sure it matches the software on your RIO exactly (with the same version numbers for all programs).
Some of the software in that list is a few versions old now, so perhaps the other RIOs you are using have more up to date software installed on them.
08-06-2012 06:15 PM
it seems the problem is I cant install the IMAQdx and NIvision, the RIO works well without this 2 SW, once I tried to install them, the RIO went crazy.
This happened to one of my classmates, too. We have no idea now.
Is there any information about which version of IMAQdx might cause corrupts with other SW? My project deadline is the end of this month, and I have
been stucked with this problem for like 3 weeks.
08-07-2012 05:02 AM
I'm not aware of any specific issues that have been found with IMAQdx and corruption of software on cRIOs.
I would suggest that you upgrade to the latest version of all of your software and try formatting and reinstalling the RIO. That way we can try to rule out any software issues that might have been caused by a corrupt host machine install.
Looking at the list of software you posted, it looks like you need to update Vision Acquisition Software (includes IMAQdx and Vision), NI-Serial, and NI-RIO to the latest versions. You are using LabVIEW 2010 by the looks of things, so there won't be any compatibility issues from upgrading. Hopefully that will fix the issues you are seeing.
I would advise that you uninstall the old drivers first, although this is not strictly necessary. You can also download the NI Device Drivers Disc if you want to update all of your NI drivers at once (but this doesn't include Vision Acquisition Software).
08-07-2012 03:49 PM
Hi. I was thinking about how to solve this problem these days. I just got part of my project worked by using TCP/IP function, run vision VIs on my laptop and transmit the results to the RIO.
I may have to keep working in this way, dont have much time to try to update SW now.
I just want to say thank you so much for your help, I really appreciate it.
If I finish this soon, I will try to reinstall all the SW you just mentioned to see if its going to work, and post the result here.
08-08-2012 02:55 AM
I'm glad you have a workaround that will allow you to finish your project and understand that making software changes towards the end of a project isn't usually a very wise idea. Probably a good decision not to - just in case something were to go wrong.
Hope the project goes well!