View Single Post
  #27   Spotlight this post!  
Unread 30-10-2013, 22:52
ekapalka's Avatar
ekapalka ekapalka is offline
Registered User
FRC #3216
 
Join Date: Dec 2012
Location: Bermuda
Posts: 277
ekapalka has a spectacular aura aboutekapalka has a spectacular aura about
Re: Using a Kinect as a primary camera for drivers

[Sigh]
We finally got to try out my program with the robot today, and I can't say I'm happy with the results. A few other programmers and I got to spend about an hour with the robot, and all we managed to do was eliminate a few potential problems. Still no connection, though. By the end we were just plugging in random IPv4 address suffixes and seeing what type of errors we'd receive. From what I've been lead to believe, the entire computer on board the robot has to replace the functionality of the Axis Camera in order to properly send MJPEG data to the DriverStation. The actual "sending it out through the router" part was probably the biggest issue to wrap our heads around. We disabled all of the adapters except the Ethernet (on the on-board computer), disabled any and all firewalls, and checked to make sure that the java Server library (java.net.Server) was available. Then we configured the DriverStation IPv4 address and Subnet mask the way we always have (10.[te].[am].9 and 255.255.255.0). That's about all of the variables we could rule out. We tried all sorts of IP address and port combinations for the socket running on the on-board computer, and multiple variations of IPv4 and Subnet settings on it's Ethernet network adapter. The errors we received were either timeouts or refused connections (when creating the socket). Is there something obvious we're missing? Should the Socket IP address and the on-board computer's IPv4 be set to the same address or something? Thanks!