Use WANT_ADXL345 and WANT_MPU9250 instead of WANT_SENSOR_ADXL345 and
WANT_SENSOR_MPU9250. This makes these definitions similar to the
other accelerometer defintions.
Order menu so accelerometers are close to each other in the menu.
Simplify Makefile as Kconfig already assures a symbol will only be
defined if its dependencies are met.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This adds a new resonance test method that can help if a user has some mechanical problems with the printer.
Signed-off-by: Dmitry Butyugin <dmbutyugin@google.com>
The M23 command has similar requirements for extracting the full
parameter string that M117/M118 have. Use the same code for those
fixups.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
Alter gcmd._command in cmd_default if the special M117/M118 handling
is detected. This avoids having to recheck for this condition in
get_raw_command_parameters().
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
The g-code command parser did not allow three characters to be passed
as parameters to commands (asterisk, semicolon, pound sign). Rework
the parsing code to better leverage the python shlex package so that
these characters can be supported.
In particular, this should allow better support for printing g-code
files that have unusual characters in the filename.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
Don't silently drop leading numbers and unusual characters at the
start of a command - for example, don't interpret '99M88' as 'M88'.
Don't silently drop spaces in a command - for example, don't interpret
"M 101" as the command "M101". Doing so will cause other parts of the
code (such as get_raw_command_parameters() ) to not work properly.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
Extended g-code command names may only contain A-Z, 0-9, and
underscore, and the first two characters may not be digits.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
When calculating the junction speed between two moves the code checked
for angles greater than 0.999999 or less than -0.999999 to avoid math
issues (sqrt of a negative number and/or divide by zero). However,
these arbitrary constants could unnecessarily pessimize junction
speeds when angles are close to 180 or 0 degrees.
Change the code to explicitly check for negative numbers during sqrt
and to explicilty check for zero values prior to division. This
simplifies the code and avoids unnecessarily reducing some junction
speeds.
Signed-off-by: Dmitry Butyugin <dmbutyugin@google.com>
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
As a minor math optimization, it's possible to calculate:
.5 * self.move_d * self.accel * tan_theta_d2
using:
self.delta_v2 * .25 * tan_theta_d2
because self.delta_v2 is "2. * self.move_d * self.accel".
Signed-off-by: Dmitry Butyugin <dmbutyugin@google.com>
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
The Fysetc PITB V2 board uses a spi bus config that is supported by the
RP2040 chip, but not klipper, so this adds the relevant config to the file
to allow you to run the tmc5160's on the board via hardware SPI. This
resolves the issue of software spi not working on this board, which I
was unable to fully understand.
I have also seen other users encounter similar bus config issues with
the rp2040 setting up things like accelerometers and such with this
pin layout.
As requested, this also uses the new convention for spi bus naming, while
maintaining the old bus names for compatibility.
Signed-off-by: Jessica Hunt <hunt.jessica@proton.me>
Rewrite chipid.c so that it contains just the USB and canbus id
manipulation code. Move the low-level chipid reading to bootrom.c.
Also, introduce a new bootrom_reboot_usb_bootloader() function in
bootrom.c so that the main.c code does not need to know the specifics
of rebooting into the bootrom.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
