Quote:
Originally Posted by Greg McKaskle
The default dashboard will open a TCP connection on port 1180 to the roboRIO's IP address.
Greg McKaskle
|
This may be what we should have tried...
What I can tell you... same code worked flawlessly in 2013-2014 and worked using 1180... using 554 only worked in one match at Lubbock. The code is essentially ffmpeg... ffplay that has been modified to pass frames... so all connection code is deep within ffmpeg itself. My point is that its a well defined solution, worked flawlessly in the pit... can withstand cold cycles, and passes a simulated fms environment.
I'm replying here, because there may be a chance that someone may have similar issues, and someone may have some insight.
There is one other thing... our URL is
rtsp://FRC:FRC@10.34.81.11:554/axis-media/media.amp
Not sure if the login and password are an issue...
Code:
void FFPlay_Controller::FailSafe::operator() ( const void* )
{
bool EventResult=m_Heartbeat.wait(10000);
if (!EventResult)
{
FrameWork::DebugOutput("***No heartbeat... resetting\n");
m_pParent->SwitchFilename(m_FileName.c_str());
}
else
Sleep(2000); //This does not need to be so active
}
I've used this to mitigate the race condition of the connection and this has worked fine in outside FMS environment, and previous years (using 1180).
The thing I find most frustrating with this problem is that I cannot pursue it, and that makes it very frustrating. I'm hoping we can simulate FMS enough to reproduce it, or find some insight as to what it can be. We can only speculate, and wait until the last moment to test again.
