No Code Error

[jhersh]

Originally Posted by bcieslak

we cant check error messages via the serial port because the crio is not talking back to the laptop for some reason.

Have you tried the new NetConsole interface? It allows you to see the console without a serial port (which is especially handy if you are using the serial port to run your Black Jaguars!)

Originally Posted by bcieslak

Here's the catch..we also tried using a laptop with last years tools on it and we were able down load and run the default program

If last year's code runs on the robot, then you haven't updated the image to v19 successfully.

Originally Posted by jhersh

Have you tried the new NetConsole interface? It allows you to see the console without a serial port (which is especially handy if you are using the serial port to run your Black Jaguars!)



If last year's code runs on the robot, then you haven't updated the image to v19 successfully.

Hi Joe, I was starting to suspect that...I had another mentor reimage the Crio and he asssured me it was complete but I am starting to have my doubts...Is there an easy way to check the version that is running in the Crio?

I am also not sure that he installed the labview update. Since we are running wind river he may have thought we didn't need it...What would be the effect of not updating that?


thanks again...
Brian

[Alan Anderson]

Originally Posted by bcieslak

I am also not sure that he installed the labview update. Since we are running wind river he may have thought we didn't need it...What would be the effect of not updating that?

If you didn't update LabVIEW, you didn't get the v19 image that comes with the updated imaging tool.

[Mark McLeod]

Originally Posted by bcieslak

Is there an easy way to check the version that is running in the Crio?

The cRIO image version is displayed on the Driver Station at the bottom of the Diagnostics tab.
So it's easy to double check.

[jhersh]

Originally Posted by bcieslak

Hi Joe, I was starting to suspect that...I had another mentor reimage the Crio and he asssured me it was complete but I am starting to have my doubts...Is there an easy way to check the version that is running in the Crio?

I am also not sure that he installed the labview update. Since we are running wind river he may have thought we didn't need it...What would be the effect of not updating that?

Like Mark said... Driver Station Diagnostics tab.

You can tell if the update worked by looking at the version of the image that the imaging tool is trying to send to the cRIO when you enable formatting the controller.

[zombiezen]

I ended up figuring out the issue on mine, hopefully this helps others:

My target install machine is running Windows 7. According to a Windows guy I know, Microsoft changed the security API for a few different things going from Vista to 7, especially concerning a feature called UAC. UAC does not allow programs to write directly to the C: drive, so certain programs will not function properly.

One of these programs that fails (silently) is the WindRiver installer.

The solution? Log into an adminstrator account, go to Control Panel -> User Accounts and Family Safety -> User Account. Choose "User Account Control" settings (the infamous UAC). Slide the bar to the bottom, and restart your computer. You have now disabled UAC; you can enable it later (probably after build season).

Now for the fun part. Remove WindRiver entirely (i.e. blow away the C:\WindRiver directory). Pop in the WindRiver install DVD and run the setup program. It should install significantly faster. After that, run the update program on the same disk, then install the latest WPI updates. Once you've done that, everything should work properly.

Hope that helps!

Yippeee!! everything is finally working....We re-imaged the Crio, made sure 'ALL' the updates were applied to the driver station and the development laptop, compiled then downloaded the BuiltinDefaultCode.out file. Then we added Joe's accelerometer code and fixed the I2C.cpp file. and all still worked.

We had some problems with the IterativeDemo but I we'll revisit that later. The BuiltinDefaultcode is what we will base our robot code on.

Thanks to all especially Joe Hersch for all the info and his patience..They don't pay you enough...Every one should send Joe a Starbucks gift card so he can buy enough coffee to keep him awake when he sending those responses at 3 AM..

Brian C

[slavik262]

Originally Posted by zombiezen

UAC does not allow programs to write directly to the C: drive, so certain programs will not function properly.

I love Windows 7 and Vista (call me a Micro$oft fanboy; I don't care), but UAC was the one thing I couldn't stand on both Vista and 7. It's the first thing I shut off when I get a new computer with either OS on it. It fixes so many problems instantly...