BLTouch V3 config file
-
@Phaedrux said in BLTouch V3 config file:
You shouldn't need to do anything at all to get the V3 working. Just connect it and configure it.
I had version 2 before working then the pin broke so I primed a new one.
I thought it would just be plug and play, but i read this post and was unsure
https://forum.duet3d.com/topic/10023/bltouch-v3-0-information-setup-and-o-scope-pictures
-
Yeah it's a little confusing, but most of the issues surrounding the V3 were with Marlin. No changes or special actions were required with RRF and Duet hardware.
No more resistors, or traces to cut, or anything like that.
-
beautiful! Thank you for the clarification @Phaedrux !
-
@fcwilt do you have to step config.g to look for configprobe.g?
-
@jaurand said in BLTouch V3 config file:
@fcwilt do you have to step config.g to look for configprobe.g?
Sorry but I don't understand the question.
I have a reference to configprobe.g where it is needed, such as when homing the Z axis, but no reference appears in config.g as it is not needed.
Frederick
-
@fcwilt Sorry I fat fingered. What goes in the config.g so that configprobe.g works? I assume I cannot just make a configprobe.g with all the probe values and have config.g with no probe info
-
@jaurand you can actually. Config.g doesn't need anything for the probe, so long as configprobe.g has all the needed commands and it gets called before the probe is activated for probing.
The only thing special about config.g is that it called called at startup. It's a macro like any other. Just a list of commands.
-
Hello there
dont want to be a ain but i am having a problem with a v3.1 bltouch as in everything works up to the point where I put in the g30 command then the thing just sits there with a error saying already deployed 
-
@jobesynoob1234
please open your own thread. otherwise it becomes confusing.
your problem is most likely with wrong or faulty wiring. -
@Veti ok sorry
and thanks