After enabling, the code takes 9 seconds before it starts running

[Greg McKaskle]

If you aren't making progress, attach code for people to look at. In your case, attach the whole thing.

Greg Mckaskle

[Pirate King]

I had the same problem. All i did is start a new robot project and copied the code part by part to see what was causing the problem. I could not find anything. but the start up lag i had disappeared. Maybe i had deleted something necessary to the code by accident in the first code. Try it if you have the time.

[propionate]

I discovered that it is about 10 second from when the robot gets communication with the DS, and we just happened to be hitting "enable" right when we got communication. This made it look like the actual code was lagging, but if I wait 10 seconds after getting comm, there is no problem when I enable.

I am still having some problems with the robot "spazzing" on enable. About 1/4 of the times I enable, a solenoid will fire or the turret will turn, then become still. I have set values for these in Begin so they should do nothing. Thoughts?

[Greg McKaskle]

Thanks for the update. The delay before and during Begin makes more sense and is actually expected.

To help with the spazzing, you may want to add a set to disable as well. If you swap from tele to disabled to auto, the old value will still be in effect until auto sets it. You may also want to search for the name of the refnum to help find everywhere it is being set, such as periodic tasks.

Greg McKaskle