Log in

View Full Version : cRIO image 2012

Invictus3593
24-09-2013, 17:28
So, we imaged our 8-slot cRIO from 2011 to the v47 image. When we start run our robot, the robot doesn't want to realize there is a solenoid module there, even though it does see the module when imaging. We think that the image for the cRIO is the problem, since we had no problems with the 2012 image that used runtime 11, and in the new image it has runtime 12. So does anybody have a non-2013 version of the image for the 8-slot cRIO? Should just be a .zip pack, right?
Joe Ross
24-09-2013, 18:53
Did you move the solenoid module to the correct slot for the new image? The imaging tool shows you the correct slots.
Invictus3593
24-09-2013, 23:33
Did you move the solenoid module to the correct slot for the new image? The imaging tool shows you the correct slots.

Yeah, it's in the right one. We even tried putting it in the old slot just to be sure :confused:

We get all green cards in the imaging tool when that starts up
RufflesRidge
25-09-2013, 06:19
Has the code been updated to the new module numbering scheme? It should say module 1 or 2, not Slot 8.
Invictus3593
25-09-2013, 12:54
Has the code been updated to the new module numbering scheme? It should say module 1 or 2, not Slot 8.

Yeah, we tried using both "Solenoid Module 1" and "Solenoid Module 2". It may just be our cRio:/


We emailed NI to see if they have a previous version of the image with runtime 11 beacuse that's what worked before, then we would just have to use the program written in labview 2011.
Joe Ross
25-09-2013, 13:20
Can you post your code? Is there an error message about the solenoid module, or does it just not work?
Invictus3593
01-10-2013, 08:58
Can you post your code? Is there an error message about the solenoid module, or does it just not work?

It just doesn't work. We've programmed this bot a million times because it's just a compressor, two solenoids and drive. The only problem is when we re-imaged with the 2013 image.

Before we imaged, it said that it had runtime 11, now it has 12; would that have anything to do with it?

PS: this is not a competition bot, it's a t-shirt cannon for football games
MechEng83
01-10-2013, 09:36
We ran into this exact same issue -- for a t-shirt cannon robot too!

Once we reimaged the 8 slot cRIO with the 2013 tool, it required that we moved the modules to the same configuration as the 4 slot, and it worked for us.
Invictus3593
01-10-2013, 14:17
Once we reimaged the 8 slot cRIO with the 2013 tool, it required that we moved the modules to the same configuration as the 4 slot, and it worked for us.

We had only tried re-imaging with the modules in the old configuration, we'll try the whole process in the new one and see if that works!