Just wondering if anyone had issues with their drivetrain being slower in Bluetooth mode vs vex net? My teams about to compete in the 6th NorCal signature event, and they noticed their robot is not as quick in Bluetooth as it is in Vex Net. I am unfortunately not with them, my other coaches are.
Anyone else got ideas?
What exactly do you mean ? More latency between controller input and motor actions ?
My kids FaceTimed me while they were in their pits and showed me the performance of their bot Bluetooth vs VexNet, Bluetooth they didn’t have as much power in their motors, all around. Vexnet they were able to make their robot jump.
We tried to reset all settings on the brain, but did not try to reset the brain fully as to wipe the programs off.
Not sure what else to do, I told them talk to the refs of NorCal and let them know, but like I said I’m not with them.
More latency, or is it the actual motors being slower?
Well, that makes no sense to me.
The code sending the motor commands has no idea if the radio is configured as VEXnet or BLE. The only difference between the two is the communications method that controller joystick and button data is sent to the brain. I will check, but I find it hard to believe that if there is a difference (or bug) that no one else has noticed in the last 6 years.
I got a hold of Richard Craig, he’s gonna check in on my kids tomorrow, honestly my kids are probably freaking out on a new thing we never taught them, this is their first year in robotics, and they have come so far just within the first year.
Sorry for making it sound like an emergency, they called me frantic.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.