-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Where do you see that the stock fw uses UART with individual addresses? Right now I only found one part in the Configuration_adv.h of the stock fw which is about this, but it's for 2209 which we don't have: /** * Four TMC2209 drivers can use the same HW/SW serial port with hardware configured addresses. * Set the address using jumpers on pins MS1 and MS2. * Address | MS1 | MS2 * 0 | LOW | LOW * 1 | HIGH | LOW * 2 | LOW | HIGH * 3 | HIGH | HIGH * * Set *_SERIAL_TX_PIN and *_SERIAL_RX_PIN to match for all drivers * on the same serial port, either here or in your board's pins file. */ #define X_SLAVE_ADDRESS 0 #define Y_SLAVE_ADDRESS 1 #define Z_SLAVE_ADDRESS 2 #define E0_SLAVE_ADDRESS 3
I'm getting a bit confused about your cfg - could you somewhere somehow share it, so that I can have a look at it? Cuz neither in the example cfg for the Go (which was made by xpeng) nor in my own cfg at my Neo (https://github.com/1coderookie/Klipper4KobraGoNeo/blob/main/cfg/NEO_1coderookie_printer.cfg) is anything about a certain tmc config. So I'm wondering right now if it was necessary and/or good for you to add the uart_pin and the run_current; the way I understood it earlier was that you maybe only would have needed to add the stealthcop_threshold line for enabling that other mode. But I might be wrong, especially cuz I was still a bit in zombie mode this morning and in a hurry as well.. ;)