Open fll-pigeons opened 4 years ago
timdavid says: Would using a master program solve the delay issue? The master program could start up and then wait for various signals to launch the appropriate code for a specific outing from the launch area. ... When using a master program, you need to reset all the motor rotation sensors before each time you tell the robot to leave the launch area.. Between missions in the master program, most teams also release the motors, so the wheels move easily.
Dean Hystad says: This is a known problem and there is a solution. Resetting the rotation sensor is heading in the right direction, but using the wrong block. Look for posts about "master program" or "mission sequencer", they will all talk about this and other similar issues that pop up when your program takes on the cleanup activities that automatically happen when you start a program.
Would using a master program solve the delay issue? The master program could start up and then wait for various signals to launch the appropriate code for a specific outing from the launch area.
In the EV3 extension in Visual Studio Code, you can click on "Explore Example Projects". There's a mission button menu example that lets you quickly start various actions/missions using the buttons.
Thanks for the pointer!
from Any recommendations for alternative programming languages?:
ethanreece says:
When exploring solutions, I looked at RobotC, EV3-G, ev3dev (Python, MicroPython, C++), and LeJOS: ... ev3dev with Python is an interesting solution, as it uses VS Code as its IDE. However, ev3dev has a delay of at least three seconds when a program is selected on the brick, which is unacceptable during a match.
MicroPython, which uses ev3dev, has the same issue as regular Python. ...
Action: confirm that this is still an issue and look for solutions