Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
zprobe [2018/05/10 09:59]
146.90.249.51 [Configuration]
zprobe [2018/08/05 01:08] (current)
134.41.43.103 [Hardware requirements]
Line 47: Line 47:
 <callout type="​warning"​ icon="​true"​ title="​ Homing">​ <callout type="​warning"​ icon="​true"​ title="​ Homing">​
 A probe is **not** an endstop and therefore cannot be used to Home the Z axis. You need a Z endstop to use G28 to home the Z axis. Below are some instructions on how you can set the bed Z height using a probe (G30). A probe is **not** an endstop and therefore cannot be used to Home the Z axis. You need a Z endstop to use G28 to home the Z axis. Below are some instructions on how you can set the bed Z height using a probe (G30).
-**NOTE** that gamma_max in the endstop configuration **IS** used to set the maximum default travel for a probe command (G30) **ONLY IF** zprobe.max_z is not defined+**NOTE** that gamma_max in the endstop configuration **IS** used to set the maximum default travel for a probe command (G30) **ONLY IF** zprobe.max_z is not defined
 + 
 +A bit more : You have two choices :  
 + 
 +* Configure your probe as an endstop ( in the endstop module ), in which case you can use G28 to use it to seek the bed, but you can't use it in the zprobe module 
 +* Configure your probe as a probe ( in the probe module ), in which case you can't use it with G28 ( the endstop module ) to seek the bed, **but** you can use it with G30 to seek the bed, and you can use it with G31/G32 etc to level/​calibrate ( this is likely what you want to do ). 
 + 
 +The point is you configure your sensor as *either* a probe or an endstop, **not both**. You can still use it for both levelling/​calibration *and* bed seeking, it's just that if it's a probe ( and not an endstop ), you use a different Gcode ( G30 ) than if it were an endstop ( G28 ).
 </​callout>​ </​callout>​
  
Line 431: Line 438:
 This is different to other Firmware and is deliberate. ​ This is different to other Firmware and is deliberate. ​
 This allows people to use temporary Z probes and not have a permanent z probe or know the exact Z offset of the probe in relation to the nozzle. **In addition the z component of the .probe_offsets should always be zero.** This allows people to use temporary Z probes and not have a permanent z probe or know the exact Z offset of the probe in relation to the nozzle. **In addition the z component of the .probe_offsets should always be zero.**
 +</​callout>​
 +
 +<callout type="​success"​ icon="​true"​ title="​ Note">​
 +The three probe points **MUST** be the three corners of a triangle, they **MUST NOT** be on a straight line or the math and coordinate system will get corrupt and you will need to reset.
 </​callout>​ </​callout>​
  
Line 769: Line 780:
 </​div>​ </​div>​
 </​html>​ </​html>​
 +
 +Or in a copy/​paste-friendly format : 
 +
 +<​code>​
 +# Switch module for Bltouch control
 +switch.servo.enable ​                       true          # Activate this new module
 +switch.servo.input_on_command ​             M280          # Command to set PWM value
 +switch.servo.input_off_command ​            ​M281 ​         # Command to turn off switch
 +switch.servo.output_pin ​                   1.23          # This must be a PWM pin, see smoothieware.org/​pinout ​  
 +switch.servo.output_type ​                  ​hwpwm ​        # Hardware PWM, as software PWM is not adequate for servo/​bltouch
 +switch.servo.pwm_period_ms ​                ​20 ​           # 20ms period, or 50Hz
 +</​code>​
  
 Note that this wiring is also valid for a servo and a switch probe, as this is what the bltouch emulates. Note that this wiring is also valid for a servo and a switch probe, as this is what the bltouch emulates.
 When connecting the bltouch the yellow wire on the 3pin connector needs to be connected to a HWPWM pin on the smoothieboard,​ valid pins are 1.23, 2.4, 3.25 or 3.26 as seen on the wirediagram on antlabs webge: https://​www.antclabs.com/​wiring32 When connecting the bltouch the yellow wire on the 3pin connector needs to be connected to a HWPWM pin on the smoothieboard,​ valid pins are 1.23, 2.4, 3.25 or 3.26 as seen on the wirediagram on antlabs webge: https://​www.antclabs.com/​wiring32
- 
  
  
Line 811: Line 833:
  
 <​html>​ <​html>​
-<iframe width="​100%" height="​720" src="​https://​www.youtube.com/​embed/​wJI7OGchE08"​ frameborder="​0"​ allowfullscreen></​iframe>​+<​center>​ 
 +<iframe width="​640" height="​480" src="​https://​www.youtube.com/​embed/​wJI7OGchE08"​ frameborder="​0"​ allowfullscreen></​iframe
 +</center>
 </​html>​ </​html>​
 +
 +Bltouch official Smoothieboard video : 
 +
 +<​html>​
 +<​center>​
 +<iframe width="​640"​ height="​480"​ src="​https://​www.youtube.com/​embed/​zn_qLmcB_b0"​ frameborder="​0"​ allow="​autoplay;​ encrypted-media"​ allowfullscreen></​iframe>​
 +</​center>​
 +</​html>​
 +
 +<callout type="​warning"​ icon="​true"​ title="​If you have a 5XC">​
 +Note that on a Smoothieboard 5XC, the pin 1.23 is used by the third big mosfet, so you can not use it for a bltouch, you need to use another pin. That other pin must also be PWM-capable,​ see [[pinout]] to find another pin that will work.
 +</​callout>​
  
 == Inductive proximity probes == Inductive proximity probes
Line 819: Line 855:
  
 <​html>​ <​html>​
-<iframe width="​100%" height="​720" src="​https://​www.youtube.com/​embed/​F7BjZElStfQ"​ frameborder="​0"​ allowfullscreen></​iframe+<​center>​ 
-</html>+<iframe width="​640" height="​480" src="​https://​www.youtube.com/​embed/​F7BjZElStfQ"​ frameborder="​0"​ allowfullscreen></​iframe>​
  
-<​html>​ +<iframe width="​640" height="​480" src="​https://​www.youtube.com/​embed/​EcGFLwj0pnA"​ frameborder="​0"​ allowfullscreen></​iframe
-<iframe width="​100%" height="​720" src="​https://​www.youtube.com/​embed/​EcGFLwj0pnA"​ frameborder="​0"​ allowfullscreen></​iframe>​+</center>
 </​html>​ </​html>​