|
Re: Windriver wont communicate with cRIO
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
|