Welcome to the SeeMeCNC Community

DerStig wrote:I have no idea what you just wrote but I want it.

so what you are saying is that I can use that with the Accel board and a E3D hotend on my MetalMax with a Duet WiFi board. Could you dumb down the post so I can do it?

M558 P5 X0 Y0 Z1 H10 F1100 T6000   ; Z probe is an digital output probe and is not used for homing any axes

M558 P3                  ; drive mod pin on Probe Z connector LOW
G28                        ; home the printer
M558 P1                  ; drive mod pin on Probe Z connector HIGH
M558 P5                  ; release mod pin connector and set the type to 5

Jimustanguitar wrote:Is this similar to what MHackney has done? Also for the Duet, interestingly.

mhackney wrote:Yes, its a nice job. The primary differences are:

1) I attach mine AT the HE280 so there is no long I2C run
2) I'm using an ATTiny85 (cheap)
3) I'm testing the wazoo out of mine and
4) I'm having a little board made with 3 pin connectors at each end that just plug into the HE280 and an endstop harness at opposite ends

I added an LED for status messages and to signal probing too. But this one works and can be programmed without a special programmer like the Sparkfun Tiny Programmer.

Nice job!

mhackney wrote:Indeterminate since The boards were delayed in manufacturing

geneb wrote: I'm probably going to hell for this....I take it you got an email from Some Ting Wong?

g.

trash80 wrote:I wrote a simple program that converts the HE280 Probe i2c accelerometer for use with the Duet Wifi using a Teensy 3. The Pro Mini 3v version would also work as well. The key is it has to be 5v tolerant because of the level shifting on the HE280 PCB to 5v and it has to output 3v for the Duet, So either a 3v micro that is 5v tolerant or a level shifter is required.

The Duet E0 probe connection is used for 3v power, gnd and the trigger signal and configured as using the auto probe type #4.
I used one of the homing limit switch signals as a "reset" signal to make sure that the accelerometer is initialized with the correct values before probing. IE: a pin is wired in parallel to one of the switches.

The code is up on github here, not much for documentation but it's very very simple. The pins are described in the .ino file.
https://github.com/trash80/HE280AccelerometerInterface

Here's the little guy wired up and ready to be installed. You can see the limit switch line at the top, the E0 3 pin connection, i2c mating input, and the "int" 2 pin connector.
[img]http://trash80.com/junkfood/teensyhe280.jpg[/img]

Here's a video of one of my test runs:
https://www.youtube.com/watch?v=QkDeiUMv68M

I've since slowed down the speed in config.g via: (it doesn't bash as hard on the glass bed and give me a 0.01 to 0.02 deviation)

Code: Select all

M558 P4 X0 Y0 Z1 H10 F1000 T5000	; Z probe is an IR probe and is not used for homing any axes

Note: I have had a few failed attempts at calibration now with the hotend hot, keep it under 40C for successful results with this approach.

dc42 wrote: Have you considered connecting the Teensy to the 4 pin Z probe connector instead of to the E0 endstop connector? You could use the Mod pin on the Z probe connector to do the reset. Selecting probe type 3 in the M558 command will drive that signal low, then select type 5 before you probe to drive it high.

dc42 wrote: Have you considered connecting the Teensy to the 4 pin Z probe connector instead of to the E0 endstop connector? You could use the Mod pin on the Z probe connector to do the reset. Selecting probe type 3 in the M558 command will drive that signal low, then select type 5 before you probe to drive it high.

M558 P5 X0 Y0 Z1 H10 F1000 T6000	; Z probe is an digital output probe and is not used for homing any axes

; Auto calibration routine for delta printers
; Before running this, you should have set up your zprobe Z offset to suit your build, in the G31 command in config.g.

M561						; clear any bed transform, otherwise homing may be at the wrong height
G31 X0 Y0					; don't want any probe offset for this
M558 P3						; drive mod pin on Probe Z connector LOW
G28						; home the printer
M558 P1						; drive mod pin on Probe Z connector HIGH
M558 P5						; release mod pin connector and set the type to 5

mhackney wrote:@trash80 (great name by the way, I wonder how many people get it!) - in your photo it looks like you have 3 wires going to the 4 pin I2C male connector. Is that just as shadow? There are only 2 wires on the connector from the whip.

trash80 wrote:

dc42 wrote: Have you considered connecting the Teensy to the 4 pin Z probe connector instead of to the E0 endstop connector? You could use the Mod pin on the Z probe connector to do the reset. Selecting probe type 3 in the M558 command will drive that signal low, then select type 5 before you probe to drive it high.

Update: I got it to work. Though it appears flipping between type 3 and 5 leaves the mod pin state LOW, so it only triggers once, I got it working by going to type 3, than type 1 to drive it HIGH, then finally to type 5 to probe on.

In config.g:

Code: Select all

M558 P5 X0 Y0 Z1 H10 F1000 T6000	; Z probe is an digital output probe and is not used for homing any axes

And at the top of bed.g

Code: Select all

; Auto calibration routine for delta printers
; Before running this, you should have set up your zprobe Z offset to suit your build, in the G31 command in config.g.

M561						; clear any bed transform, otherwise homing may be at the wrong height
G31 X0 Y0					; don't want any probe offset for this
M558 P3						; drive mod pin on Probe Z connector LOW
G28						; home the printer
M558 P1						; drive mod pin on Probe Z connector HIGH
M558 P5						; release mod pin connector and set the type to 5

I'll be updating the first post and pics and codebase to reflect the changes shortly.

dc42 wrote: I'm glad you got it working. Looks like the firmware doesn't set the control pin state when switching to probe type 5. I'll fix that in the 1.17 release to drive it high.