View Single Post
  #25   Spotlight this post!  
Unread 05-04-2016, 10:39
plnyyanks's Avatar
plnyyanks plnyyanks is offline
Data wins arguments.
AKA: Phil Lopreiato
FRC #1124 (The ÜberBots), FRC #2900 (The Mighty Penguins)
Team Role: College Student
 
Join Date: Apr 2010
Rookie Year: 2010
Location: NYC/Washington, DC
Posts: 1,113
plnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond repute
Re: Human Vision Camera compatiable with FMS & Java ?

As an FTAA and CSA myself, like Greg said,
Quote:
Originally Posted by Greg McKaskle View Post
The FMS has no involvement with the DS/DB/camera comms. The field network is involved. It blocks some ports and affects connection timings, just as almost any ethernet or wifi network will. But it has no idea what is on your encrypted TCP/UDP stream between your devices.
After another quick skim through this thread, I also haven't seen you clarify exactly what "doesn't work" on the field. Does the stream not appear at all on the Dashboard? Is it choppy or frozen on an image? Do you see any logs? What kind of things did you try and troubleshoot with the FTA/CSA at your event? All of those things can help us understand the problems you're facing and give better ideas on what to try next.

That being said, I'll spitball a few ideas
  • Not all network ports are open on the field, see R60 this year
    Quote:
    Originally Posted by R60
    Communication between the ROBOT and the OPERATOR CONSOLE is restricted as follows:
    A. Network Ports:
    i. TCP 1180: Camera data from the roboRIO to the Driver Station (DS) when the camera is connected the roboRIO via USB, bi-directional.
    ii. TCP 1735: SmartDashboard, bi-directional
    iii. UDP 1130: Dashboard-to-ROBOT control data, uni-directional
    iv. UDP 1140: ROBOT-to-Dashboard status data, uni-directional
    v. HTTP 80: Camera connected via switch on the ROBOT, bi-directional
    vi. HTTP 443: Camera connected via switch on the ROBOT, bi-directional
    vii. UDP/TCP 554: Real-Time Streaming Protocol for h.264 camera streaming, bi-directional
    viii. UDP/TCP 5800-5810: Team Use, bi-directional

    Teams may use these ports as they wish if they do not employ them as outlined above (i.e. TCP 1180 can be used to pass data back and forth between the ROBOT and the DS if the Team chooses not to use the camera on USB).
  • QoS limitations. The radio will limit your connection to 7Mbit/sec (see R60B). If you have the camera configured to stream super high quality video at 60fps, you may run into trouble. This document explains how you can test your bandwidth usage at home. Additionally, the 7Mbit limit is a theoretical ceiling, wireless conditions at your specific event may preclude such speeds. In any case, robot control packets are prioritized over video streaming, so packets from your camera may get dropped, causing issues with your stream.
  • This one is a real long shot, but I vaguely remember a discussion on a CSA call about a Java WPILib bug with the CameraServer code, I believe it's this on the tracker. I don't know enough about this to recommend further troubleshooting to see if this is what you're experiencing though, I'd have to defer to someone else on the subject.
__________________
Phil Lopreiato - "It's a hardware problem"
Team 1124 (2010 - 2013), Team 1418 (2014), Team 2900 (2016)
FRC Notebook The Blue Alliance for Android
Reply With Quote