The potential use case of this is for remote start indicaion to the robot code, and additionally maybe exposing the game state to robots (ie a human presses a button when a point is scored, then this info is transmitted to the robot via bluetooth beacon)
We think this should be good to do in Bluetooth, however we were also considering using IR sensors to do this.
We would need to produce a reliable Bluetooth transmitter (preferably with a class 1 bluetooth device as the transmitter), which then should be received by the Raspberry Pi 3s, and passed over robotd to the robot API.
I suggest this runs as a part of a thread in robotd. I suggest we expose this to the students as a robot.game.get_state() function that returns a dictionary of the game state, ie {'time':120,'limit':300, 'team0':{'points':2}....}, obviously the actual information will vary on the game.
The potential use case of this is for remote start indicaion to the robot code, and additionally maybe exposing the game state to robots (ie a human presses a button when a point is scored, then this info is transmitted to the robot via bluetooth beacon)
We think this should be good to do in Bluetooth, however we were also considering using IR sensors to do this.
We would need to produce a reliable Bluetooth transmitter (preferably with a class 1 bluetooth device as the transmitter), which then should be received by the Raspberry Pi 3s, and passed over robotd to the robot API.
I suggest this runs as a part of a thread in robotd. I suggest we expose this to the students as a
robot.game.get_state()function that returns a dictionary of the game state, ie{'time':120,'limit':300, 'team0':{'points':2}....}, obviously the actual information will vary on the game.