-
-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update to latest Klipper3d/klipper (f7567a0d) #70
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Donna Whisnant <[email protected]>
Signed-off-by: Donna Whisnant <[email protected]>
Signed-off-by: Thijs Triemstra <[email protected]>
Signed-off-by: Konstantin Vogel <[email protected]>
Verified with an Monoprice Mini Select v2 using katapult. Signed-off-by: Chris Lombardi <[email protected]>
Added a more detailed explanation for pwm-2chan. Signed-off-by: Alfie Batthullt <[email protected]>
Created a base config for the Creality CR10s Pro v2 as described here: https://www.creality.com/products/cr-10s-pro-v2-3d-printer This will allow users with this printer to more easily setup Klipper firmware. Signed-off-by: Peter Kydas <[email protected]>
Required for the Anycubic Kobra 2. Signed-off-by: Falk Höppner <[email protected]>
Signed-off-by: Luke Vuksta <[email protected]>
Added alias for Octopus pro h723 v1.1 for sdcard update script. Signed-off-by: David Bucek <[email protected]>
Commit 594c024 updated the workflows from actions/stale@v3 to actions/stale@v8, but did not make the corresponding updates to the config parameters. This resulted in the closing of some PRs. Update the config parameters to avoid this regression. Signed-off-by: Kevin O'Connor <[email protected]>
lis2dw12 is an accelerometer from STMicroelectronics(https://www.st.com/resource/en/datasheet/lis2dw12.pdf) With better performance than the ADXL345 according to the datasheet. Signed-off-by: XM.Zhou from BigTreeTech [email protected] Signed-off-by: Alan.Ma from BigTreeTech [email protected]
Signed-off-by: Alan.Ma from BigTreeTech [email protected]
Signed-off-by: Alan.Ma from BigTreeTech [email protected]
PR to add the newer version of the Ender 2 Pro with the CR-FDM-v2.5.54.170 motherboard with the HC3232F460 chip. Confirmed as working with discord member NyftHeart and using configs from Steve Gotthardt, with his permission to use and submit. Signed-off-by: James Hartley <[email protected]>
Signed-off-by: Allen Cox <[email protected]>
Signed-off-by: Christoph Frei <[email protected]>
…melting point of platinum (#6320) Limit the maximum temperature in MAX31865.calc_adc() to the melting point of platinum. Above this temperature the Callendar-Van Dusem formula does not make sense. The default value for max_temp is 99999999.9 and at this temperature the result of this formula is negative. This sets max_sample_value to 0 which causes the mcu to shutdown. Set max adc value to (1<<15)-1 . This is needed because the max value of the adc register of the MAX31865 is 0b1111 1111 1111 1110 which represents 32767 and not 32768. Signed-off-by: David van 't Wout <[email protected]>
The RetryAsyncCommand code needs to ensure that any response messages are not from a previous (unrelated) query. To do that it compares the '#sent_time' from potential responses to ensure they are not from a previous session. However, if there are any low-level serial retransmits then the low-level code sets the '#sent_time' to zero (to indicate that the query send time is not strictly known). That could result in a valid response not being accepted by RetryAsyncCommand. If a low-level connection is experiencing a small amount of periodic retransmits it could result in multiple high-level retry attempts failing to the point that there is a user-facing error. This could result in "Timeout on wait for 'tmcuart_response' response" errors. Fix by accepting responses even if there is a low-level retransmit once the code can confirm that there can be no previous query still in progress. Signed-off-by: Kevin O'Connor <[email protected]>
Signed-off-by: Kevin O'Connor <[email protected]>
…(#6310) Previous version of the code assumed that dual carriages home away from each other, which is not true on some machines, which have the second dual carriage homing on the first carriage. The new code correctly identifies the relative order of the carriages now. This fixes discrepancies between the documentation and the actual implementation of the carriages kinematic ranges calculation. Notes about dual_carriage homing and proximity checks changes Fixed clearing of homing state after homing in certain modes In case of multi-MCU homing it is possible that the carriage position will end up outside of the allowed motion range due to latencies in data transmission between MCUs. Selecting certain modes after homing could result in home state clearing instead of blocking the motion of the active carriage. This commit fixes this undesired behavior. Signed-off-by: Dmitry Butyugin <[email protected]>
additionaly -> additionally Signed-off-by: Ikko Eltociear Ashimine <[email protected]>
Add support for can2040_stop() Add data_state_go_error() helper Add new can2040_get_statistics() API function Call report_note_discarding() after setting MS_DISCARD state Convert report_is_rx_eof_pending() to report_is_not_in_tx() Signed-off-by: Kevin O'Connor <[email protected]>
Replace the set_stat_x_bits() functions with a single calc_epr_bits() function. This new function supports setting bits other than the stat field in the epr register. Signed-off-by: Kevin O'Connor <[email protected]>
The usbfs device supports two buffers for each endpoint - typically one for rx and one for tx. Add support for explicit handling of both buffers. This is in preparation for improved "double buffering" support. Signed-off-by: Kevin O'Connor <[email protected]>
Implement the usbfs fast buffer switching mechanism on the "bulk out" endpoint. This can improve the overall USB throughput and bus utilization. Signed-off-by: Kevin O'Connor <[email protected]>
Implement the usbfs fast buffer switching mechanism on the "bulk in" endpoint. This can improve the overall USB throughput and bus utilization. Signed-off-by: Kevin O'Connor <[email protected]>
Add helper functions for manipulating the buffer memory and packet control registers. This is in preparation for double buffer support. Signed-off-by: Kevin O'Connor <[email protected]>
Copy the code for these two functions to their respective callers. This is in preparation for double buffer support. Signed-off-by: Kevin O'Connor <[email protected]>
Signed-off-by: Kevin O'Connor <[email protected]>
Signed-off-by: Kevin O'Connor <[email protected]>
Rename the internal variable names. This is in preparation for support of a USB message queue. Signed-off-by: Kevin O'Connor <[email protected]>
Read USB messages arriving from the host into a queue. This makes it less likely that USB "bulk out" packets will be NAK'ed on the USB bus, which improves USB bus utilization. Signed-off-by: Kevin O'Connor <[email protected]>
Prioritize sending responses back to the host over transmitting new messages from the host. Otherwise, the gs_usb host usb acknowledgments could saturate the usb bandwidth for extended periods. Signed-off-by: Kevin O'Connor <[email protected]>
The bulk out endpoint should not be enabled in tx mode, and the bulk in endpoint should not be enabled in rx mode. Signed-off-by: Kevin O'Connor <[email protected]>
Commit cd8d57c added USB double buffering mode on transmits. However, when enabling double buffering mode, the hardware seems to always send at least two packets. Spurious transmissions could cause the Linux gs_usb driver to get confused, which could lead to the can0 device becoming unavailable on restarts. Fix by waiting for two USB packets to be available before enabling the endpoint. Signed-off-by: Kevin O'Connor <[email protected]>
Klipper logs an error on a failed CANbus write. Unfortunately, if the bus becomes permanently disabled (eg, due to a user removing power to devices on the CANbus) then it can result in the logs filling with error messages. Permanently disable the low-level processing of messages if CANbus writes continually fail for at least 10 seconds. This avoids filling the log with redundant messages. Signed-off-by: Kevin O'Connor <[email protected]>
Wait for two tx packets before startup, and make sure one of those packets is acked before sending a third tx packet. Signed-off-by: Kevin O'Connor <[email protected]>
…or silent boards (#6326) Recently tested on my ender 5 pro that came from creality with a v1.1.5 board. Works. Tested all endstops, motors, and heaters. Signed-off-by: Jake Aronleigh <[email protected]>
Signed-off-by: Kevin O'Connor <[email protected]>
Signed-off-by: Aaron B. Haun <[email protected]>
The atsam USB hardware only requires that the ACM endpoint be endpoint 3. As of commit 1182838 the atsam chips can therefore use the default USB endpoints. This will allow CAN bridge support for the SAME70 to function (upstream host driver has hardcoded endpoints). Signed-off-by: Alex Maclean <[email protected]>
Signed-off-by: Luke Vuksta <[email protected]>
Signed-off-by: Aaron B. Haun <[email protected]>
In the "Verify endstops" section there is an example of adding an exclamation point to the pin definition to invert its logic. I believe the intention in the example is to keep the hardware pull-up ^ and follow it with ! to invert the pin logic, but the ! is missing. Signed-off-by: Tom Dunn <[email protected]>
Makes the API to extruder and input shaper more robust, avoiding the need to track the old delay. Signed-off-by: Viesturs Zariņš <[email protected]>
rogerlz
previously approved these changes
Oct 19, 2023
This reverts commit 6749985. A defect was found in the above commit (the input shaper code calls note_step_generateion_scan_time() for many steppers, so the input_shaper class can't be used as the index). Signed-off-by: Kevin O'Connor <[email protected]>
rogerlz
changed the title
Upstream changes
update to latest Klipper3d/klipper (b1f597c5)
Oct 24, 2023
Piezoid
changed the title
update to latest Klipper3d/klipper (b1f597c5)
update to latest Klipper3d/klipper (f7567a0d)
Oct 24, 2023
rogerlz
approved these changes
Oct 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update to latest Klipper3d/klipper (b1f597c) (Oct 13)
Do not merge from Github, fast-forward locally once the PR is approved.
10-24: Updated to f7567a0