Quote:
Originally Posted by cbale2000
As a note to those of you considering Bluetooth, keep in mind that Bluetooth operates in the same 2.4GHz frequency range as traditional WiFi. While potentially harder for field staff to detect (as a WiFi scanner will not see it), if it is detected you will likely be told to stop using it.
I came across an interesting paper that describes, amongst other things, how WiFi and Bluetooth interact with each other: http://www.hp.com/rnd/library/pdf/Wi...oexistance.pdf |
The FRC field is not 2.4GHz it is 5GHz.
Of this I can be pretty sure as I have been a CSA/FTAA.
However feel free to take FIRST's word on it:
http://www.firstinspires.org/sites/d...-frc-qanda.pdf
See Q301.
Keep in mind the field security monitoring tools can still detect the 2.4GHz spectrum but usually we don't police it.
When there were issues in the past with the interference the source that caused the most public examples were all interacting with the 5GHz spectrum. Airport radar can also interfere with the top few channels of that 5GHz spectrum.
Also this 802.11n supports channel bonding which is usually turned on but occasionally has been turned off in the past.
So that means that your robots can use 2 channels of that spectrum to get extra radio bandwidth.
That still does not remove the 7Mb limit imposed between your robot and the field.
That bandwidth restriction is imposed not at the radio level but at the protocol level.