Closed cray12399 closed 4 weeks ago
I am running into a bug where I am getting the following error after some time:
!! Toolhead stopped below model range
Nothing in my code throws that error. Where are you getting it from?
Hi, Thank you for the response. I am using a Cartographer Eddy Probe. I am not exactly sure where the error is coming from. However, someone on the cartographer discord told me it is a klipper error.
That line does not appear anywhere in the Klipper code base either. It seems like it may be an issue in the probe software?
Sorry, I was mistaken. They did not say the error was klipper. They just said that the error was not related to an issue with the cartographer probe. I did find the code with the error right here though:
https://github.com/Cartographer3D/cartographer-klipper/blob/master/idm.py
Not sure how much it will help with diagnosing this issue. But line 1310-1311 is where the error originates from.
Edit:
It appears the same line appears in the beacon probe code too. So it appears to not be cartographer-specific as far as I can tell. Which indicates to me that this might be some sort of issue with how eddy probes work with the measure_thermal_behavior script.
https://github.com/beacon3d/beacon_klipper/blob/master/beacon.py
The measurement script simply sends the MEASURE_GCODE
that you configure in the script, so if what you're using there is throwing errors then I would start be investigating that gcode.
Someone using a Beacon probe was using this gcode there:
G28 Z METHOD=CONTACT CALIBRATE=0
The measurement script simply sends the
MEASURE_GCODE
that you configure in the script, so if what you're using there is throwing errors then I would start be investigating that gcode.Someone using a Beacon probe was using this gcode there:
G28 Z METHOD=CONTACT CALIBRATE=0
Hmm, interesting. I will try using that as my measure g-code and report back here with the results.
Alright, so I got the same error again despite changing the measure_gcode. I attached my klippy.log in case that might help in figuring out what is going on here. klippy(1).zip
I checked out the log and unfortunately I can't give you any new insight. As I said, the measurement script does not hook into Klipper at all, but just sends gcode via the conventional interface and reads positions - so the issue is not on my end.
I'd recommend opening up the issue with the Cartographer team, pointing them at the relevant lines from your log:
Post-homing adjustment measured samples [{'clock': 167675247094, 'data': 33180002, 'temp': 66.28499918592377, '#name': 'cartographer_data', '#sent_time': 22431.599132926, '#receive_time': 22431.949836148, 'time': 3491.9803665701425, 'data_smooth': 33179999.776770175, 'freq': 2966523.15051289, 'dist': inf, 'pos': (175.0, 175.0, 2.0), 'vel': 0.0}, {'clock': 167675297914, 'data': 33180002, 'temp': 66.23614597241243, '#name': 'cartographer_data', '#sent_time': 22431.599132926, '#receive_time': 22431.950870703, 'time': 3491.981425352849, 'data_smooth': 33180000.887909062, 'freq': 2966523.249856448, 'dist': inf, 'pos': (175.0, 175.0, 2.0), 'vel': 0.0}, {'clock': 167675348734, 'data': 33180433, 'temp': 66.13152172397258, '#name': 'cartographer_data', '#sent_time': 22431.599132926, '#receive_time': 22431.951928684997, 'time': 3491.9824841355558, 'data_smooth': 33180216.94347962, 'freq': 2966542.56672975, 'dist': inf, 'pos': (175.0, 175.0, 2.0), 'vel': 0.0}, {'clock': 167675399554, 'data': 33179959, 'temp': 66.18207972189583, '#name': 'cartographer_data', '#sent_time': 22431.599132926, '#receive_time': 22431.952991406997, 'time': 3491.983542918262, 'data_smooth': 33180087.97148096, 'freq': 2966531.0357345007, 'dist': inf, 'pos': (175.0, 175.0, 2.0), 'vel': 0.0}, {'clock': 167675450374, 'data': 33179959, 'temp': 66.1977740825173, '#name': 'cartographer_data', '#sent_time': 22431.599132926, '#receive_time': 22431.954651887998, 'time': 3491.9846017009686, 'data_smooth': 33180023.485352654, 'freq': 2966525.270225345, 'dist': inf, 'pos': (175.0, 175.0, 2.0), 'vel': 0.0}, {'clock': 167675501194, 'data': 33180002, 'temp': 66.20300595249739, '#name': 'cartographer_data', '#sent_time': 22431.599132926, '#receive_time': 22431.955127055, 'time': 3491.985660483675, 'data_smooth': 33180012.742224015, 'freq': 2966524.3097147956, 'dist': inf, 'pos': (175.0, 175.0, 2.0), 'vel': 0.0}, {'clock': 167675552014, 'data': 33180002, 'temp': 66.19428628491846, '#name': 'cartographer_data', '#sent_time': 22431.599132926, '#receive_time': 22431.956229018, 'time': 3491.9867192663814, 'data_smooth': 33180007.370648954, 'freq': 2966523.8294585603, 'dist': inf, 'pos': (175.0, 175.0, 2.0), 'vel': 0.0}, {'clock': 167675602834, 'data': 33180002, 'temp': 66.13675096308145, '#name': 'cartographer_data', '#sent_time': 22431.599132926, '#receive_time': 22431.957215314, 'time': 3491.987778049088, 'data_smooth': 33180004.684856053, 'freq': 2966523.5893299626, 'dist': inf, 'pos': (175.0, 175.0, 2.0), 'vel': 0.0}, {'clock': 167675653654, 'data': 33180002, 'temp': 66.23963488284261, '#name': 'cartographer_data', '#sent_time': 22431.599132926, '#receive_time': 22431.958312610997, 'time': 3491.9888368317943, 'data_smooth': 33180003.34195692, 'freq': 2966523.469265424, 'dist': inf, 'pos': (175.0, 175.0, 2.0), 'vel': 0.0}, {'clock': 167675704474, 'data': 33180433, 'temp': 66.25359145416104, '#name': 'cartographer_data', '#sent_time': 22431.599132926, '#receive_time': 22431.959345222, 'time': 3491.9898956145007, 'data_smooth': 33180218.170506008, 'freq': 2966542.6764344582, 'dist': inf, 'pos': (175.0, 175.0, 2.0), 'vel': 0.0}, {'clock': 167675755294, 'data': 33179959, 'temp': 66.21172619893031, '#name': 'cartographer_data', '#sent_time': 22431.599132926, '#receive_time': 22431.960449796, 'time': 3491.990954397207, 'data_smooth': 33180088.58499538, 'freq': 2966531.0905869645, 'dist': inf, 'pos': (175.0, 175.0, 2.0), 'vel': 0.0}, {'clock': 167675806114, 'data': 33179959, 'temp': 66.180336019646, '#name': 'cartographer_data', '#sent_time': 22431.599132926, '#receive_time': 22431.961592517997, 'time': 3491.9920131799136, 'data_smooth': 33180023.792110484, 'freq': 2966525.297651632, 'dist': inf, 'pos': (175.0, 175.0, 2.0), 'vel': 0.0}, {'clock': 167675856934, 'data': 33180002, 'temp': 66.1977740825173, '#name': 'cartographer_data', '#sent_time': 22431.599132926, '#receive_time': 22431.96251324, 'time': 3491.99307196262, 'data_smooth': 33180012.895603243, 'freq': 2966524.3234279673, 'dist': inf, 'pos': (175.0, 175.0, 2.0), 'vel': 0.0}, {'clock': 167675907754, 'data': 33180002, 'temp': 66.16464373870792, '#name': 'cartographer_data', '#sent_time': 22431.599132926, '#receive_time': 22431.963584998997, 'time': 3491.9941307453264, 'data_smooth': 33180007.44733873, 'freq': 2966523.8363151606, 'dist': inf, 'pos': (175.0, 175.0, 2.0), 'vel': 0.0}, {'clock': 167675958574, 'data': 33180476, 'temp': 66.14372360408834, '#name': 'cartographer_data', '#sent_time': 22431.599132926, '#receive_time': 22431.965064887998, 'time': 3491.995189528033, 'data_smooth': 33180241.72320102, 'freq': 2966544.7822094876, 'dist': inf, 'pos': (175.0, 175.0, 2.0), 'vel': 0.0}, {'clock': 167676009394, 'data': 33180476, 'temp': 66.14023723754462, '#name': 'cartographer_data', '#sent_time': 22431.599132926, '#receive_time': 22431.965711091998, 'time': 3491.9962483107397, 'data_smooth': 33180358.861366447, 'freq': 2966555.2551775975, 'dist': inf, 'pos': (175.0, 175.0, 2.0), 'vel': 0.0}]
Toolhead stopped below model range
The only unusual thing I can see is the discrepancy between your kinematic and toolhead/gcode Z positions:
mcu: stepper_x:16 stepper_y:14 stepper_z:-5848 stepper_z1:-6041 stepper_z2:-5754 stepper_z3:-8216
stepper: stepper_x:350.000000 stepper_y:0.000000 stepper_z:1.921194 stepper_z1:1.921194 stepper_z2:1.921194 stepper_z3:1.921194
kinematic: X:175.000000 Y:175.000000 Z:1.921194
toolhead: X:175.000000 Y:175.000000 Z:10.000000 E:0.000000
gcode: X:175.000000 Y:175.000000 Z:10.021028 E:0.000000
gcode base: X:0.000000 Y:0.000000 Z:0.000000 E:0.000000
gcode homing: X:0.000000 Y:0.000000 Z:0.000000
I am running into a bug where I am getting the following error after some time:
!! Toolhead stopped below model range
I suspect that it is due to the AB motors timing out. However, I set my idle timeout to 999999 in my config and its still timing out after around 30 minutes. Is there any way to work around this?