It looks very comprehensive and well thought out. The only thing that comes to mind after looking at it is to make sure to cover the concept of "noise". The inside of a FIRST robot is not as noisy as under the hood of a car, but there are motors with chopper PWM drives, and relays and solenoids firing. All of these can corrupt the measurements. Make sure to cover when and where it is prudent or necessary to use shielded wiring on the sensors, and possibly some filtering.
The rest of these are things you have listed, but the things I see most often with new engineers and data acquisition are:
- The difference between precision and accuracy. Just because the display has 8 decimal places doesn't mean that they are all real.
- Sampling rate. Just because you can record data at 25 kHz doesn't mean that you should. Stress the importance of matching the sampling rate to the parameter being measured. One problem I run into now is that computers have made it so easy to capture huge amounts of data, that people are going ahead and doing it. Then you have to do something with it. Where years ago we would just right down one value from the instrument display, now we are saving hundreds of points of trace data.
- File management and data interpretation or visualization. Teach them to know before they capture the data what they are planning on doing with it, and then store it accordingly. I frequently have engineers come into my office who have stored little bits of data into hundreds of Excel files, because it was easy when they were programming it, who want to know if I can somehow magically get it all into one file so they can compare or plot it. There are ways, but it's much easier to get them to put a little effort into storing it properly to start with.
Best of luck with your teaching. I hope you will come back here later and let us know how it goes (and some of the class materials might make a good whitepaper).