Windriver wont communicate with cRIO

[emusteve]

WOOT!! The motors are moving!

Okay, it never occurred to us that the module positions would be different from the past few years. Combing through the Documentation, I Finally spotted the new module placement table! Moved the parallel module, re-imaged, and now the code is running. Still no printf output, but that's for another thread I think.

BTW, the "Getting Started" guide shows the 8-slot as cRIO-FRCII, and "Gettting Started with C++" says Wind River wants us to use the cRIOFRC_vxworks image for the 8-slot (NOT the cRIOFRCII_vxWorks image). Talk about confusing.

Thanks to everyone for all your suggestions. It's really appreciated!

Now we start on NetConsole and trying out CAN. Wish us luck.

Thanks,
Steve

[aeniug2]

I'm not sure if this will help at all, and its kind of redundant, but here is a video I made showing exactly what I do to load code to the robot.
(It excludes any of the connection setup, it's just the deploying part)

http://www.youtube.com/watch?v=9myCh...8fi7PHS94d4996

Hope this provides some insight, but I think you probably understand all of this already... Just throwing it out here in case you accidentally missed something obvious (happens to me all the time, derp)

EDIT:
NVM! My internet is being stupid and I didn't see that you had already solved it! Congtrats man!
BTW, that's what I was talking about when I asked if the imaging tool said they were all OK, it should tell you where they are supposed to go, and whether you got em right or not.

[emusteve]

The imaging tool correctly identified our cRIO as an 8 slot unit, and identified which modules were sitting in which slots. Since what it showed was consistent with the hardware, it never occurred to me it might not actually like what it was seeing.

Thanks again for all the help

Steve

[Alan Anderson]

Originally Posted by emusteve

The imaging tool correctly identified our cRIO as an 8 slot unit, and identified which modules were sitting in which slots. Since what it showed was consistent with the hardware, it never occurred to me it might not actually like what it was seeing.

The imaging tool colors its display of the modules as either green or red, based on whether they are the right module for the slot or not.

Are you red/green color blind?

[emusteve]

No, but when all the modules are shown in red, you don't always realize there might be another color used.

[Alan Anderson]

The analog module in the first slot should have shown as green. The 2011 and 2012 rules both require one there.