Auto-Leveling in Firmware Not Active - Mini IR Height Sensor
I have auto leveling enabled in firmware to use my mini ir height sensor board from David Crocker. I've followed directions from his blog https://miscsolutions.wordpress.com/mini-height-sensor-board/ to the point I've set my configuration to the offset i obtained. However, when i load the firmware and boot it, auto-leveling is off. I turn it on from the LCD menu, but i don't see an option to have it run the auto-level. Do i need to send it Gcode to run the auto level from the menu? Or is it suppose to run before a print? It seems like i should be able to run auto level if i enable it in the lcd menu. Can it enable automatically?
Comments
So i know that i verified i could read when the sensor was activated like on the David Crocker blog instructions. It boots in digital mode and with M119 z probe would go to H when triggered. I had ALWAYS_CHECK_ENDSTOPS checked, so i need to uncheck that box to make it 0 correct? I don't recall seeing Zmin toggling with the probe before, but i wanted to re-verify my config before re-running.
Since my probe is using z min, do i need ENDSTOP_PULLUP_Z_MIN/ENDSTOP_Z_MIN_INVERTING to be a Electronic, Normally Open switch?
And if temp doesnt matter then why do i need to Home X Y Preheat then Z?
> 4:51:46 PM: N77 M119 *58
< 4:51:46 PM: endstops hit: x_min:L y_min:L z_min:L Z-probe state:H
> 4:52:58 PM: N145 M119 *10
< 4:52:58 PM: endstops hit: x_min:L y_min:L z_min:L Z-probe state:L
First M119 was with the IR sensor not activated its LED off
Second M119 was with the IS sensor activated its LED on
Was my ENDSTOP_PULLUP_Z_MIN/ENDSTOP_Z_MIN_INVERTING = Electronic, Normally Open switch the wrong selection?
Just tried toggling Z_PROBE_ON_HIGH to true and it still gives me a H on an not activated probe and a L on an active probe, with no zmin changes..
Update: adding in a Zmax button, the printer will still try to continue upward even if zmax is H, i checked with M119 and it's not acting like an endstop....
link to my configuration.h file:
https://drive.google.com/open?id=0B7lZgNIb_aruZmtNSjlwcWFsZkU
#define MULTI_ZENDSTOP_HOMING 0 Does this have anything to do with anything?
#define ENDSTOP_PULLUP_X_MIN true
#define ENDSTOP_X_MIN_INVERTING true
#define MIN_HARDWARE_ENDSTOP_X true
#define ENDSTOP_PULLUP_Y_MIN true
#define ENDSTOP_Y_MIN_INVERTING true
#define MIN_HARDWARE_ENDSTOP_Y true
#define ENDSTOP_PULLUP_Z_MIN true
#define ENDSTOP_Z_MIN_INVERTING true Just like you noted above
#define MIN_HARDWARE_ENDSTOP_Z true
#define ENDSTOP_PULLUP_Z2_MINMAX true
#define ENDSTOP_Z2_MINMAX_INVERTING false
#define MINMAX_HARDWARE_ENDSTOP_Z2 false
#define ENDSTOP_PULLUP_X_MAX true
#define ENDSTOP_X_MAX_INVERTING false
#define MAX_HARDWARE_ENDSTOP_X false
#define ENDSTOP_PULLUP_Y_MAX true
#define ENDSTOP_Y_MAX_INVERTING false
#define MAX_HARDWARE_ENDSTOP_Y false
#define ENDSTOP_PULLUP_Z_MAX true
#define ENDSTOP_Z_MAX_INVERTING true Is this the correct way to setup z_max endstop? It isn't stopping motion
#define MAX_HARDWARE_ENDSTOP_Z true when the z_max switch is High... it tried to crash right through it.
#define max_software_endstop_r true
Z Probe:
#define Z_PROBE_Z_OFFSET 0
#define Z_PROBE_Z_OFFSET_MODE 0
#define UI_BED_COATING 1
#define FEATURE_Z_PROBE 1
#define EXTRUDER_IS_Z_PROBE 0
#define Z_PROBE_BED_DISTANCE 10
#define Z_PROBE_PIN ORIG_Z_MIN_PIN Again, just like you noted above.
#define Z_PROBE_PULLUP 1
#define Z_PROBE_ON_HIGH 1
Update: So i found how to tell X and Y to move to 110mm bed center for z homing. But what's weird is that when i Z home, the probe just wants to move up and and never back down to trigger the probe. It's like it raises the 30 cm for cleareance but won't go towards the bed to trigger the probe... Something i'm missing?
Updated link to my configuration.h file:
https://drive.google.com/open?id=0B7lZgNIb_aruZmtNSjlwcWFsZkU
< 4:51:46 PM: endstops hit: x_min:L y_min:L z_min:L Z-probe state:H
> 4:52:58 PM: N145 M119 *10
< 4:52:58 PM: endstops hit: x_min:L y_min:L z_min:L Z-probe state:L
Second M119 was with the IS sensor activated its LED on
Arduino: 1.8.1 (Mac OS X), Board: "Arduino/Genuino Mega or Mega 2560, ATmega2560 (Mega 2560)"
HAL.cpp:784: error: operator '<' has no left operand
#if COOLER_PWM_SPEED < 0
^
HAL.cpp:787: error: operator '>' has no left operand
#if COOLER_PWM_SPEED > 4
^
HAL.cpp:791: error: operator '==' has no left operand
#if COOLER_PWM_SPEED == 0
^
HAL.cpp:794: error: operator '==' has no left operand
#elif COOLER_PWM_SPEED == 1
^
HAL.cpp:797: error: operator '==' has no left operand
#elif COOLER_PWM_SPEED == 2
^
HAL.cpp:800: error: operator '==' has no left operand
#elif COOLER_PWM_SPEED == 3
^
HAL.cpp:803: error: operator '==' has no left operand
#elif COOLER_PWM_SPEED == 2
^
sketch/HAL.cpp: In function 'void __vector_22()':
HAL.cpp:879: error: 'COOLER_PWM_MASK' was not declared in this scope
if((pwm_pos_set[PWM_FAN1] = (pwm_pos[PWM_FAN1] & COOLER_PWM_MASK)) > 0) WRITE(FAN_PIN,1);
^
HAL.cpp:985: error: 'COOLER_PWM_MASK' was not declared in this scope
if(pwm_pos_set[PWM_FAN1] == pwm_count_cooler && pwm_pos_set[PWM_FAN1] != COOLER_PWM_MASK) WRITE(FAN_PIN,0);
^
HAL.cpp:1062: error: 'COOLER_PWM_STEP' was not declared in this scope
pwm_count_cooler += COOLER_PWM_STEP;
^
exit status 1
operator '<' has no left operand
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
????