2021-05-24, 05:40 PM
(2021-05-23, 04:22 PM)seandepagnier Wrote: it is another servo setting you can adjust, so far at least from the lcd interface and pypilot clients.
The downside is existing motor controllers use a lower frequency which may make an annoying tone, however it can be filtered out with external components.
How exciting is this! I have just updated openplotter on my raspberry and now looking to upload the new sketch to another arduino nano to find out how it works paired with the Neco autopilot.
There are 2 new servo settings: clutch_pwm and clutch_start_time, right? Clutch_pwm is the pwm value of the clutch and clutch_start_time is the time it takes for the clutch to throttle back?
There is also a new pin used, the clutch_sense_pwm_pin or A5. It is then pulled up, so I guess there should be a normally off switch connected to the clutch solenoid, and this switch is supposed to pull the A5 pin down when the clutch has successfully engaged? This is turn will throttle down the PWM signal of clutch_pin 11, is this right?
Is the clutch sensor needed? Should I just comment out the line where you define the clutch sense pin, and then the clutch will be driven at the lower pwm value after the clutch_start_time has passed?