First we put the sensor in detect mode and had it report whenever it heard sound in the ultrasonic range. Back when NXT was introduced there was a lot of concern about using the US sensor in a noisy environment so we ran a bunch of experiments to determine if the concerns were founded or not. Music, loudspeakers, lights, crowd noise, etc.
We were always afraid the noise at competitions would interfere with that sensor, so we avoided it. During practice we have seen failing sensors, but it has not been possible to pinpoint reason.Īnyone else with similar experiences and have any contributing ideas? I suspect that sensor may become idle while robot it being idle and not "wake" up properly afterwards. At the semi final they could enter the table well in time for the round and they loaded the robot maybe 8-10 minutes before start. In all earlier rounds they started up the robot just two three minutes before start. There is one thing I am thinking of could be a contributing factor. Is this the only resolution some times in these cases? After the competition the EV3 was shut down and powered up again and the sensor was working well. The kids said there were light in the sensor, and they even tried to disconnect cable and reconnect, but it did not make any difference. We have had failing gyro and they learned really well how to handle this, but this failure came as a surprise. I just want to learn what may have happened here.
This was a very good result for us in any respect, but during the day expectations rised of course so the kids were really disappointed by this failure in the most critical part of the competition.
However, in the semi-final our ultrasonic sensor failed ruining most of the missions and they had to take a third place. It all seemed to be decided between our team and one another team as those two teams stood out. We had our competition yesterday and our team performed really well.
0 kommentar(er)
