@casainho - have a couple of questions about the osf motor controller and how the control works.
This is in relation to me trying to incorporate mspider65's changes - I'm trying to get pwm control to work properly so I can code a calibration process.
The way the ebike_control_motor loop in ebike_app.c seems to work - if you set a target current then the pwm value is forced to 255... if you have a current target of 0 - then pwm is forced to zero..
How should I do variable pwm control? If I don't set a target current I get no motor action... so seems to me I can't have pwm levels between 0 or 255..
i'm sure I'm missing something in the code
This is the part that seems to be problematic:
Code:
// apply the target current if motor is enable and if not, reset the duty_cycle controller
if(ui8_m_motor_enabled)
{
ebike_app_set_target_adc_motor_max_current(ui16_m_adc_target_current);
ebike_app_set_target_adc_battery_max_current(ui16_adc_battery_current_max);
}
else
{
ebike_app_set_target_adc_motor_max_current(0);
ebike_app_set_target_adc_battery_max_current(0);
ui8_g_duty_cycle = 0;
}
// set motor PWM target
if (m_config_vars.ui8_walk_assist && ui8_g_brake_is_set == 0 && ui8_m_motor_enabled)
{
if (ui16_wheel_speed_x10 < WALK_ASSIST_CRUISE_THRESHOLD_SPEED_X10)
{
motor_set_pwm_duty_cycle_target(ui8_m_walk_assist_target_duty_cycle);
}
else
{
motor_set_pwm_duty_cycle_target(ui8_cruise_target_PWM);
}
}
// else if (ui16_m_adc_target_current)
// {
// motor_set_pwm_duty_cycle_target(255);
// }
// else
// {
// motor_set_pwm_duty_cycle_target(0);
// }
// let's reset this counter, meaning this code is called from main loop
ui16_main_loop_wdt_cnt_1 = 0;
}
The bit at the end i've commented out - is the part that seems to totally override any pwm setting I set...
How do I do pure pwm control - where the current used is just whatever the pwm cycle needs to run with whatever load applied?
edit: and do you by any chance have any notes or other docs that describe what the motor control variables do - the things that confuse me most are things that are similarly named but are ui8_g_yada or ui_m_yada - what's the m/g mean?
e.g.
Code:
(ui8_m_duty_cycle_target < ui8_g_duty_cycle)
