nsaspook - i dont agree with your 99%. Some use an RTOS for the sake of the structure/order it brings even to a small application. My applications are mostly controlling things where timing is important. The following is a general example of tasks and services required.
- Read keyboard and drive led's and lcd display
- Logic to edit and save setpoint to eeprom
- Logic to edit and save alarm values
- Talk to rtc via i2c
- Logic to handle alarm indications
- Read temperature and filter it
- PID management logic
- PID controller
- PWM driver for thyristor
- uart handler for monitor and control via pc (38400 Baud)
Bill - seems like we are on the same wavelength. The following are a few details about my task scheduler system which you can see is at basic similar to yours:
- PIC clock speed 32Mhz (using PLL)
- 8 round robin tasks (task switch takes 2.25uSec)
- 7 Time activated tasks (select from 10,20,40,50,100,200mSec)
- A scheduler routine (2.25uSec) runs every 10mSec to control time tasks
- The program memory required is less than 100 bytes and up to 30 bytes ram