eStop help

[jpearman]

All it means is that your approach to using eStop is perfectly valid. The eStop task will stop the main task and all motors when you detect whatever analog sensor you are using going below the threshold you have set. Using a check for that sensor in the main loop would be ok, but as soon as the program becomes more complex and you possibly have other tests and while loops, it will not work so well, that’s why putting it in another task is really the correct approach. You can read about ROBOTC tasks in detail here (it gets complicated)

Discussion on using tasks in ROBOTC

It’s time for another one of my long posts, this time discussing ROBOTC tasks and some of the do’s and don’ts. I realize this information is going to be way beyond the comprehension of many of the new students reading it, however, don’t worry, this is complicated stuff and most of you don’t really need to know all of these details, it’s aimed at mentors and those obsessive programmers that want to extract the maximum from ROBOTC. ROBOTC Tasks There were a couple of threads last week that comme…

and you can see an old implementation of eStop in this project

Open source robot

OSR_1/OpenSourceBot_simple.c at master · jpearman/OSR_1 · GitHub

that one was a bit verbose, the eStop task did not want to stop itself and there is no easy way to do that in ROBOTC except for testing each know task as I did there.