View Single Post
  #5   Spotlight this post!  
Unread 17-12-2008, 23:45
Woodie Flowers Award
JDNovak JDNovak is offline
Mentor
AKA: John Novak
FRC #0016 (Bomb Squad)
Team Role: Engineer
 
Join Date: Jan 2005
Rookie Year: 1996
Location: Mountain Home, AR
Posts: 52
JDNovak has a reputation beyond reputeJDNovak has a reputation beyond reputeJDNovak has a reputation beyond reputeJDNovak has a reputation beyond reputeJDNovak has a reputation beyond reputeJDNovak has a reputation beyond reputeJDNovak has a reputation beyond reputeJDNovak has a reputation beyond reputeJDNovak has a reputation beyond reputeJDNovak has a reputation beyond reputeJDNovak has a reputation beyond repute
Re: Who is Programming the cRIO with C++ and what success are you having?

Windriver setup is a little tedious. I can't remember how long it took to understand it but here is what I can remember.

Hopefully you installed Windriver into the default location using the default workspace. Assuming that, go to C:\Windriver\docs\extensions\FRC and look at the C Programming Guide for FRC. It is definitely not finished but it gets updated when updates to C++ are released.

Starting at page 85 is the setup to connect to the cRIO and use debug etc. You should be able to open a program from the File/New/Example/VxWorks Downloadable Kernel module Sample Project like Iterative Robot Demo Main Program and then compile it with project/Build All.

i can't remember where the documentation is to set up the FIRST Downloader but go to Windrivers toolbar and go to Window/Preferences. In the list on the left select FIRST Downloader Preferences. Enter your team number and check the path to the file to download to the cRIO. My path is:

C:\Windriver\workspace\Iterativedemo\PPC603gnu\Ite rativeDemo\Debug\IterativeDemo.out

This is the compiler output file targeted for the PowerPC in the cRIO. If this path is right, when you go to the FIRST tab on the toolbar and select Download the file will be transferred to the cRIO solid state drive. You have to make sure the cRIO is configured for C++ with the Imaging tool and then reboot and the cRIO should load and run the program. If you reconfigure for Labview and back to C++ this file will load and run again. It is not written over by Labview output. You can remone it with Undeploy in the FIRST pulldown.

Hope this helps some.