Anyone successful with camera in RobotPy?

[BotnEyedJoe]

Glad to hear it helped!

Can I ask, which model of camera are you using: the 206 or M1011?

[BotnEyedJoe]

Originally Posted by jhersh

Have you also tested it with the Axis 206 camera that many teams have? We would prefer not to break the other camera to make the new one work.

Thanks,
-Joe

For anyone interested in the Axis 206, I have run a quick test using the modified WPILib routines mentioned above, with a borrowed 206 model camera, and the live video stream to the FRC Dashboard works, and changing the camera params also works.

Please let me know if you encounter any problems.

[tux]

2 Questions.

1) My team just wants video feed from the camera back to the driver station.

Can I do this without the default RobotPy or do I have to apply all of the fixes discussed in this thread and build from source?


2) I'm not sure which camera we have. I recognize it from the picture in the KoP list, but the description says:

"Camera, Axis M1011
206 color camera..."

So, is it the M1011 or the 206?

[BotnEyedJoe]

Originally Posted by tux

2 Questions.

1) My team just wants video feed from the camera back to the driver station.

Can I do this without the default RobotPy or do I have to apply all of the fixes discussed in this thread and build from source?


2) I'm not sure which camera we have. I recognize it from the picture in the KoP list, but the description says:

"Camera, Axis M1011
206 color camera..."

So, is it the M1011 or the 206?

2) The picture in the KOP list is of the M1011.

1) If you just want video back to the driver station, there is a new option this year of plugging the camera directly into the network bridge on the robot (bypassing the cRIO). I understand this requires Dashboard changes, and the camera config is a little different. There are threads here on CD about that, though I can't help more than that, since we are not pursuing that solution.

If you follow the 'traditional' solution, plugging the camera in the cRIO, and doing the vision.AxisCamera.GetInstance() to start the video feed to the Dashboard, I will tell you that we had problems doing even that much with the M1011 in either C++ or any version of RobotPy. Quite a few times the feed would work, many times it would not, and we could never change the camera parameters through the software. But the patch fixed all that.

You can apply the proposed patch mentioned in this thread to either RobotPy 2011.2 or the latest RobotPy from the git repository, and though you will have to 'build it yourself', I believe the result will be a more reliable and configurable video feed.

[team 3311]

If you follow the 'traditional' solution, plugging the camera in the cRIO, and doing the vision.AxisCamera.GetInstance() to start the video feed to the Dashboard, I will tell you that we had problems doing even that much with the M1011 in either C++ or any version of RobotPy. Quite a few times the feed would work, many times it would not, and we could never change the camera parameters through the software. But the patch fixed all that.

You can apply the proposed patch mentioned in this thread to either RobotPy 2011.2 or the latest RobotPy from the git repository, and though you will have to 'build it yourself', I believe the result will be a more reliable and configurable video feed.

Hmmm I read the whole thread and tried a bit with our robot but I can't get it done. I did exactly what you are saying up here.

Can maybe anybody briefly explain the steps that we have to do to get our camera running? Its an Axis 206 camera.

[Robototes2412]

two methods:

one:

import vision
camera_obj = vision.PCVideoServer()

two:

import vision
camera_obj = vision.AxisCamera.GetInstance()

[krudeboy51]

When ever I plug the Camera into the c-rio An error and enable the robot, we would get a live feed from the camera for like 4 seconds and then for some reason the robot would disconnect from the Driverstation and an error would show up on Windriver saying:

Target Exception:

VxWorks6x_10.3.69.2: Exception in Kernal Task FRC_paramTask:0x231b5b0
at pc=0x198F84

Vector 0x300 : Data Access addr=0x6D5FE50E status=0x3E8

The System has been stopped. Do you want to attach the debugger now?

do any one know how to fix this?

[taichichuan]

Originally Posted by krudeboy51

When ever I plug the Camera into the c-rio An error and enable the robot, we would get a live feed from the camera for like 4 seconds and then for some reason the robot would disconnect from the Driverstation and an error would show up on Windriver saying:

Target Exception:

VxWorks6x_10.3.69.2: Exception in Kernal Task FRC_paramTask:0x231b5b0
at pc=0x198F84

Vector 0x300 : Data Access addr=0x6D5FE50E status=0x3E8

The System has been stopped. Do you want to attach the debugger now?

do any one know how to fix this?

The error you're seeing is a bus error on the cRIO. The 0x6D... is the address that's being accessed caused the buss error. The problem happened in the FRC_paramtask application. So, this is a pointer related problem. Recheck your camera configuration in the cRIO code and make suer that you've updated to the latest WPILib release. There are a couple of threads that talk about a problem with WPILib that was fixed.

[krudeboy51]

Originally Posted by taichichuan

The error you're seeing is a bus error on the cRIO. The 0x6D... is the address that's being accessed caused the buss error. The problem happened in the FRC_paramtask application. So, this is a pointer related problem. Recheck your camera configuration in the cRIO code and make suer that you've updated to the latest WPILib release. There are a couple of threads that talk about a problem with WPILib that was fixed.

I have updated to the latest WPIlib. over three times now, and still the same problem. and also in the description in the lateset update, it doesnt state anyhing on fixing this error
this is the code that I have for it right now:

                              Class
                              AxisCamera *camera;

                              Operator control(void)
		    HSLImage image;     //Creates an image
		    AxisCamera &camera = AxisCamera::GetInstance();
		    camera.WriteResolution(AxisCamera::kResolution_640x480);
		    camera.WriteCompression(20);
		    camera.WriteBrightness(0);

would I have to add something in Public in order to fix it other than ds = driverstation::GetInstance();?

[jhersh]

Have you attached the WindRiver Workbench debugger when running your code so that you can trap the exception and potentially get a call stack to give us a better idea where to look?

[krudeboy51]

Originally Posted by jhersh

Have you attached the WindRiver Workbench debugger when running your code so that you can trap the exception and potentially get a call stack to give us a better idea where to look?

Yes I have over three times now but it wont connect back to the driverstation at all only when I restart and when I restart the same error pop up and I attach the debugger over and over but still the same problem

[jhersh]

Originally Posted by krudeboy51

Yes I have over three times now but it wont connect back to the driverstation at all only when I restart and when I restart the same error pop up and I attach the debugger over and over but still the same problem

Great!

Please post the call stack here.

[krudeboy51]

Originally Posted by jhersh

Great!

Please post the call stack here.

wats that? when I click the attach debbugger it shows a loading page then closes out when complete

[jhersh]

Originally Posted by krudeboy51

wats that? when I click the attach debbugger it shows a loading page then closes out when complete

So you don't ever get the debugger to stop when the exception occurs? It sounds like you are attaching the debugger in response to a crash. Try attaching the debugger to the running python interpreter before you do whatever instigates the crash or start the python interpreter using the debugger. When the exception occurs, you should be able to open the stack view. That would be the first helpful piece of information in tracking down the issue.

[krudeboy51]

Originally Posted by jhersh

So you don't ever get the debugger to stop when the exception occurs? It sounds like you are attaching the debugger in response to a crash. Try attaching the debugger to the running python interpreter before you do whatever instigates the crash or start the python interpreter using the debugger. When the exception occurs, you should be able to open the stack view. That would be the first helpful piece of information in tracking down the issue.

this is the stack view I got:

java.io.FileNotFoundException
at org.eclipse.help.internal.context.ContextFileProvi der.loadContexts(ContextFileProvider.java:235)
at org.eclipse.help.internal.context.ContextFileProvi der.getContexts(ContextFileProvider.java:181)
at org.eclipse.help.internal.context.ContextFileProvi der.getPluginContexts(ContextFileProvider.java:158 )
at org.eclipse.help.internal.context.ContextFileProvi der.getContext(ContextFileProvider.java:83)
at org.eclipse.help.internal.context.ContextManager.g etContext(ContextManager.java:79)
at org.eclipse.help.HelpSystem.getContext(HelpSystem. java:49)
at com.windriver.ide.internal.apidoc.WRAPIHelpProvide r.getFunctionInfo(WRAPIHelpProvider.java:110)
at org.eclipse.cdt.internal.ui.text.CHelpSettings.get FunctionInfo(CHelpSettings.java:121)
at org.eclipse.cdt.internal.ui.CHelpProviderManager.g etFunctionInfo(CHelpProviderManager.java:163)
at org.eclipse.cdt.internal.ui.text.c.hover.CDocHover .getHoverInfo(CDocHover.java:73)
at org.eclipse.cdt.internal.ui.text.c.hover.BestMatch Hover.getHoverInfo(BestMatchHover.java:100)
at org.eclipse.cdt.internal.ui.text.c.hover.CEditorTe xtHoverProxy.getHoverInfo(CEditorTextHoverProxy.ja va:64)
at org.eclipse.jface.text.TextViewerHoverManager$4.ru n(TextViewerHoverManager.java:165)

and the error messege was:

Error reading context-sensitive help file /"com.windriver.ide.doc.wr_vx_simulator_6.3/wr_workbench_diagnostics_programmers_guide_1.1/html/contexts.xml" (skipping file)