Log in

View Full Version : Camera software Update 2/3/10 C/C++


jault
05-02-2010, 17:52
There is a new update on the usfirst.org website. This update came out on February 3rd, 2010. Fixes a lot of camera issues and the lag time on the dashboard image from the camera. heres the link : http://first.wpi.edu/FRC/frccupdates.html

hope this helps.

bronxbomber92
05-02-2010, 19:47
After installing the update is anyone having problems deploying code? Its fine on the PC side in WindRiver but when I go to boot the robot the dashboard says that there is no robot code.

Spacetech
05-02-2010, 20:13
After installing the update is anyone having problems deploying code? Its fine on the PC side in WindRiver but when I go to boot the robot the dashboard says that there is no robot code.

Same thing happened to me. It was related to one of the DriverStationLCD class enum's. Just comment out your code that uses the class and you should be fine.

bronxbomber92
05-02-2010, 20:48
The problem was that part of the project wasn't recompiling (duh). Clean and rebuild solved my problems :-)

ideasrule
05-02-2010, 21:02
I'm supposing that there's a corresponding Java update? I'm looking at the list of updates in the updates.xml file and don't see anything...

sunit
06-02-2010, 12:09
Clean and Build did not fix the problem.

Commenting out the DriverStationLCD code did not fix the issue.

MattD
06-02-2010, 12:20
I'm supposing that there's a corresponding Java update? I'm looking at the list of updates in the updates.xml file and don't see anything...

I had an update available for the FRCSquawkSDK plugin, but after installing it I did not see any of the API changes that were present in the C++ version of the library. Am I missing something, or is a Java update to match the C++ version still pending?

Kingofl337
07-02-2010, 00:36
I'm also looking forward to said update for Java.

kevin51292
09-02-2010, 20:10
Hey guys!

I installed the update a couple of days ago and it seems to have created a problem that I'm wondering if anyone on here has been able to figure out. When I declare the Axis camera instance, I tried setting the resolution of the image, but when I do that it says that my resolution (kResolution_640x480) is undeclared. I am including the updated AxisCamera.h and AxisCameraParams.h header files. Do any of you have any ideas on what I'm doing wrong? Here is what my source code looks like:

AxisCamera &camera = AxisCamera::GetInstance();
camera.WriteResolution(kResolution_640x480);

byteit101
09-02-2010, 20:17
Hey guys!

I installed the update a couple of days ago and it seems to have created a problem that I'm wondering if anyone on here has been able to figure out. When I declare the Axis camera instance, I tried setting the resolution of the image, but when I do that it says that my resolution (kResolution_640x480) is undeclared. I am including the updated AxisCamera.h and AxisCameraParams.h header files. Do any of you have any ideas on what I'm doing wrong? Here is what my source code looks like:

AxisCamera &camera = AxisCamera::GetInstance();
camera.WriteResolution(kResolution_640x480);

you aren't doing anything wrong, this is a WPILib bug. See post 3 above

kevin51292
09-02-2010, 20:35
Hmm...I'm actually not using the DriverStationLCD class. I've been using the DashboardDataSender class. Is that another problem? So if I'm not using the DriverStationLCD class is there something else that could be causing the problem?

-Kevin

MattD
09-02-2010, 20:46
you aren't doing anything wrong, this is a WPILib bug. See post 3 above

I disagree.

Try this:

AxisCamera &camera = AxisCamera::GetInstance();
camera.WriteResolution(AxisCameraParams::kResoluti on_640x480);

kevin51292
09-02-2010, 21:05
Ah thank you very much!! I tried it and it worked wonderfully.

byteit101
11-02-2010, 15:30
Hmm...I'm actually not using the DriverStationLCD class. I've been using the DashboardDataSender class. Is that another problem? So if I'm not using the DriverStationLCD class is there something else that could be causing the problem?

-Kevin

Oops! I didn't read the question all the way :yikes: