Help - setting up endstops please.... FIXED

I'm going out of my mind trying to setup the X, Y endstop and the Z Probe (DC42 IR probe) on a Prusa I3 "look a like"

Set up the IR probe following the instructions, and I get a value of 0.065.
So I guess I should have this line:

G31 P500 X0 Y0 Z0.065

If I send the command M558 X0 Y0, then G28 Z, the z homes nicely.

I've managed to get the X and Y endstops to work individually.

After homing X & Y and then homing Z, it all goes wrong. The x carriage goes up 1cm, then as X is already homed it just jams against the endstop, y then goes the opposite way from home (jams at the far end) and z lowers - but as the sensor is now off the bed, the hot end just crashes into the bed (sensor is about 2cm behind the hot end).

So I've played around in the homez file - changing various X Y co-ordinates to get the head supposedly at a corner, centered on the bed, but each time it is the same. Please help me!


; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Sat Jan 28 2017 17:26:07 GMT+0000 (GMT Standard Time)

; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility
to look like Marlin
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X240 Y240 Z200 S0 ; Set axis maxima

; Endstops
M574 X2 Y2 S0 ; Define active low and unused microswitches
M574 S1 ; Define active high microswitches
M558 P1 X2 Y2 Z1 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
G31 P600 X0 Y0 Z0.01 ; Set Z probe trigger value, offset and trigger height

; Drives
M569 P0 S0 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X87.489 Y87.489 Z4000 E420 ; Set steps per mm
M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z180 E1200 ; Set maximum speeds (mm/min)
M201 X500 Y500 Z250 E250 ; Set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Heaters
M143 S260 ; Set maximum heater temperature to 260C
M305 P0 R4700 T100000 B3950; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1

; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

; Network
M550 PPhytone3D ; Set machine name
M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP

; Fans
M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Custom settings are not configured


Below is homez.g


; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool on Sat Jan 28 2017 17:26:07 GMT+0000 (GMT Standard Time)

; Lift Z relatively to current position
G91
G1 Z1 F6000

; Back to absolute positioning
G90

; Go to first bed probe point and home the Z axis
G1 X70 Y70 F6000
G30

; Uncomment the following lines to lift Z after probing
;G91
;G1 Z1 F100
;G90

Edited 1 time(s). Last edit at 02/05/2017 03:08PM by Phytone.

reloaded firmware, seems OK now.........

But seriously, I think DC needs to add a health warning to these boards....

They suck up way too much time in setting up, coming from a RAMPS board....

Quote
Phytone
But seriously, I think DC needs to add a health warning to these boards....

They suck up way too much time in setting up, coming from a RAMPS board....

If you can tell me what took a lot of time, I'll do my best to make it easier and quicker. But do you really think it took longer than setting up your first RAMPS board did?

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

I spent 4 hours trying to get the Endstops to work, as per the original issue. Reloading the firmware fixed it, should have done that sooner.

There is a lot more to read and understand for this board, the wiki is great, but its not really plug n play : and to be honest, I didn't think it would be.
Whilst it sucked up time, I had a whale of a time...

In terms of what could you do...

A really simple walk through, or some kind of configuration file that asks machine specific questions to help tailor the setup, the RepRapFirmware has some of this, but I think I fell into a newbie trap and couldn't dig my way out.

An explanation of the configuration file and the key codes, it took me a while to figure out where acceleration was, which motor is which, why the carriage z went up 5cm, then down 5cm on print etc.

I also had some errors in my gcode scripts from s3d that ramps ignored, but the duet found them and where a speed was not identified, it went to the slowest speed. I didn't know why, and it took me ages to figure out. I ended up using cura and s3d to troubleshoot.

The bed mapping is interesting, and I can't figure out why my supposedly milled 8mm plate looks like the Swiss alps...

Yes, RAMPS was a learning curve, but I had just figured out arduino programming for quadcopters so it made sense. This is a different bucket and you to need understand G and M codes in more detail.

The price is a premium, and I doubt it will attract novices - so it could be argued that people will know what's what. My ramps is two years old, and I felt lost untill I read, read and did some more reading.

Did you generate your configuration and homing files using [configurator.reprapfirmware.org] ? If so, can you say which selections you found unclear?

Edited 1 time(s). Last edit at 02/07/2017 03:44PM by dc42.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Hi David

Yes, I did - but to be honest I really didn't know what I was doing. I've gone back to the configurator and now armed with some understanding on the board, i must admit it makes more sense.

It is probably just me, trying to do things too quickly.

However, a simple guide showing the config.g and where the various codes match to the individual screens in the configurator would have helped me in the first instance. As i note now, that the axes show the motor labels - I really didn't see them the first/second/third time......

The z probe is still causing me a headache.

I have it tuned to single probe, then print - works fine.
I apply bed mapping and it probes, but then as it starts to print the nozzle is about 2mm low and bangs into the bed.
I tried G29 and it does the same. Is there a different offset that needs to be used when applying G32/G29?