Re: Example of Vision Processing Avaliable Upon Request
 

Honestly something needs to change about this. We lost several matches because our fully charged battery has ran out of juice at the end of the match.

Re: Example of Vision Processing Avaliable Upon Request
 

We have never had a problem during a match. ALWAYS CHARGE YOUR BATTERIES BETWEEN MATCHES and NEVER put a bad battery in the rotation. We always buy new batteries each year and remove the bad ones for practice things.

Re: Example of Vision Processing Avaliable Upon Request
 

The cRIO power supply on the PDB will boost the battery voltage and operate down to 4.5 volts. At that point, the battery is very dead. Looking at the O-DROID U2 specs, it says it uses a 5v power supply. Do you know what kind of power circuitry the O-DROID U2 uses? It seems unlikely that it operates below 4.5 volts.


Rather then divert this thread, It would be good if you started a new thread and posted your driver station logs in it. The cRIO power supply operates down to 4.5 volts, as does the Radio. The Digital sidecar would be the first thing to turn off, but only momentarily until the battery voltage returns to normal. It seems likely that something else, like a loose wire or a bad battery caused the problems.

Re: Example of Vision Processing Avaliable Upon Request
 

With regards to image processing on a co-processor, one of the biggest obstacles my team had was getting the information from the co-processor to the cRIO. Network socket documentation for C++ on the cRIO is flaky at best. Does anyone have experience/example code for communicating between a C++ or Python co-processor and a cRIO running C++?

Re: Example of Vision Processing Avaliable Upon Request
 

Does Virtuald's link help? http://firstforge.wpi.edu/sf/projects/robotpy

I am interested to see where this thread goes. I do mechanical mentoring but python hobbyist.

Re: Example of Vision Processing Avaliable Upon Request
 

We ended up implementing our own network table class based on their documentation.Our Implementation. On line 63 of this we instantiate our network object and on line 265 to 367 we set a couple of values for the robot to read.

I believe the documentation came from.
Documentation

I recently started to mess with creating a custom dashboard from scratch and was able to get the network tables from here running with little hastle on linux from Here. I would recommend this because they are derived directly from the robot c++ implementation (from my understanding) and seem much more stable then the version we created and used on our robot.

Re: Example of Vision Processing Avaliable Upon Request
 

For powering the ODroid, we used this: http://www.pololu.com/catalog/product/2177 a 3A 5V Buck regulator. It's connected directly to the power distribution board, so we're not using the cRio regulator. It was made by using a multi-meter to determine plug polarity of the AC adapter, then splicing the barrel jack end onto the output of the regulator.

We also had some camera stability issues with them occasionally having driver issues, which we believed was caused by drawing too much power. This was solved with another 3A 5V Buck regulator and an external usb hub.

Re: Example of Vision Processing Avaliable Upon Request
 

AWESOME