-
-
Notifications
You must be signed in to change notification settings - Fork 19.3k
Commit
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||
---|---|---|---|---|
|
@@ -23,6 +23,7 @@ | |||
|
||||
/** | ||||
* Common pin assignments for all RUMBA32 boards | ||||
* | ||||
*/ | ||||
|
||||
#ifndef STM32F4 | ||||
|
@@ -31,11 +32,21 @@ | |||
#error "RUMBA32 boards support up to 3 hotends / E-steppers." | ||||
#endif | ||||
|
||||
#define RUMBA32_V1_0 | ||||
#define DEFAULT_MACHINE_NAME BOARD_INFO_NAME | ||||
|
||||
//#define I2C_EEPROM | ||||
#define MARLIN_EEPROM_SIZE 0x1000 // 4KB | ||||
// Use soft PWM for fans - PWM is not working properly when paired with STM32 Arduino Core v1.7.0 | ||||
// This can be removed when Core version is updated and PWM behaviour is fixed. | ||||
#define FAN_SOFT_PWM | ||||
|
||||
// | ||||
// Configure Timers | ||||
// TIM6 is used for TONE | ||||
// TIM7 is used for SERVO | ||||
// TIMER_SERIAL defaults to TIM7 so we'll override it here | ||||
// | ||||
#define STEP_TIMER 10 | ||||
#define TEMP_TIMER 14 | ||||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
chrissbarr
Author
Contributor
|
#define HAL_TIMER_RATE (F_CPU / 2) // frequency of timer peripherals |
I'm unsure how to improve the initialisation to distinguish which timers use which clock source.
One solution is to change to a timer that uses the same timebase as the original. Changing STEP_TIMER
in the pins file from 10
to 12
is working for me - can you give that a go and see if that gets things running at correct speeds for you?
This comment has been minimized.
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
This comment has been minimized.
Sorry, something went wrong.
chrissbarr
Jun 21, 2020
Author
Contributor
That's good, thanks for confirming @dankatanka. It looks like the above assumption in the HAL_TIMER_RATE is the issue, and I've opened a PR (#18374) with a fix.
Are you still experiencing the PID autotune issue? I have not attempted to reproduce this yet. I notice there is a PR (#18352) merged yesterday that fixes a problem with the PID autotune - perhaps that is the cause of the problem you're seeing?
@chrissbarr — Looks like this change is causing some major problems. What did you test with?