Brian Schmalz

Yes, correct. I was thinking the limp delay would be the amount of time before killing power to the motors. So you're looking for two separate input actions - one...

@oskay That looks like a good plan to me. That's what we'll go with. My only concern is that if you're streaming SM commands to the EBB, at step (4)...

Yes, that's perfect. OK, so would it be better to change the QG command to return additional information, or keep it the same (for backward compatibility sake) and make a...

Very nice. Instead of QueryLevel being simply a number of bytes, I'd rather have it be considered like a verbosity command. The reason is because I'd like to not limit...

Agreed. How about default bootup behavior is to use a FIFO depth of 1, and then there would be a new command that would allow the PC to ask "how...

How about: CU,3,0 will return fifo_depth,max_depth CU,3, will set the fifo depth (to a value that is non-zero) CU,X where X is 4 through 13, will return the input type...

Good point. We'll make a new command, as discussed above ("EE") for all estop/pause/resume functionality. FIFO control seems appropriate as a CU type command.

Progress is being made! Currently code to handle the larger FIFO is going in and being tested.

Good news, the larger FIFO code is working (finally). Next steps: add in the above commands. Slowly, slowly, it will get done.

A partial solution to this issue has now been committed on the EBB_EStop branch. It only addresses the first part of the work to resolve this issue - the larger...