Quote:
Originally Posted by Deetman
TCP/IP as designed and properly implemented is a reliable protocol. If a packet is not received properly it will be resent. Is it right for FIRST? Is the implementation throughout the system correct? I don't know.
|
Blaming TCP or IP should be completely out of the question. First of all, these are two of the most (really, THE most) used networking protocols in existence today. They are used by every single device (that's billions of devices) that connects to the internet.
Furthermore, one of TCP's advantages over other transport-layer protocols (such as UDP, commonly used for tasks such as video streaming) is it's reliability.
Which brings me to...
Quote:
Originally Posted by arizonafoxx
For what is worth. One thing I was told by the FTA at an off season event. The signal to start Autonomous or Teleop is only sent once at the beginning of that state.
|
Though I don't know for sure, I'm assuming that the FTA was telling you that the application only sends the signal once for auto/teleop, constantly for disabled. Even though the application layer only sends one message down to the lower layers (TCP, IP, etc), TCP will keep sending the packet over and over again until it receives an acknowledgement. If that packet is dropped, it will be resent.
Quote:
Originally Posted by akoscielski3
Is it possible that since Einstein was the back-up field that if there was an Update on the FMS for every-field, Einstein Never got that update, thus causing all these Robots to have a problem?
|
I very highly doubt that. I also doubt that never having used the Einstein field before would be to blame for any issues. The hardware and software are identical to that used on every other field.
Are there kinks that need to be worked out? Yes.
Do I think it is the FMS or field hardware's fault. Not really.
Do I think it is the robots' fault? Not really, though I have seen enough robots to believe that robots with various electrical or programming issues are just confuddling this problem more.