Quote from osmogr on 01/30/08 at 8:51pm:
I am ready for the firmware, could you set the default start points at 1.5. High side at 2 and low side at 1. That should work great..
Bear with me for a bit - the original plan was to use #IFDEF statements in the code, and recompile depending on whether there the drive is an PWM H-bridge or PPM servo. After looking at the specific code, I now think it would be better to select the device type at the command (SRV_protocol) level, so that a single version of firmware supports PWM or PPM.
At the control loop level, just as we currently have the 'M' command to set PWM power levels, we could add new commands to set PPM timing for each servo pair. The user could redefine the The code would detect whether the user is requesting PWM or PPM functions, and initialize the timer channels accordingly. The trick is deciding what to do about the keypad commands ('8' forward, '5' stop, '2' back, etc).
Anyhow, let me think this through a bit further - I definitely prefer the idea of supporting a single version of firmware rather than branching versions for different hardware configurations.