[SOLVED] Updated fw, now z-probe is inverted?

Hi,

Upgraded my Ormerod 2 today from 1.09 to DC's 1.10+4 with the 1.11 web interface. Everything seemed to have worked out fine, but trying to print now I get 2 problems;

1. According to the RepRap wiki, when calibrating the z-probe, the values are supposed to be lower when closer to the bed, but my machine suddenly works the other way around. This in turn means that the bed compensation instead of slightly rising the z-axis to compensate instead drops the head down onto the bed.
I have the standard z-probe.

2. The printer does not wait until the the heater is up to temp before it starts printing (but it waits for the bed as before), do I need to change something in my default ormerod slicer profile? I can get around this by manually heating the head as the bed warms up.

I've searched the forum but I can't find anything about the specific issues...

Ormerod config:

; Ormerod 2 config file for dc42 Duet firmware
M111 S0								; Debug off
M550 PMy Ormerod 2					; Machine name (can be anything you like)
M551 Preprap							; Machine password (currently not used)
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED	; MAC Address

;*** Adjust the IP address and gateway in the following 2 lines to suit your network
M552 P10.83.10.215					; IP address (0 = use DHCP)
M554 P10.83.10.1						; Gateway
M553 P255.255.255.0					; Netmask
M555 P2								; Set output to look like Marlin
M575 P1 B57600 S1					; Comms parameters for PanelDue

G21									; Work in millimetres
G90									; Send absolute coordinates...
M83									; ...but relative extruder moves
M574 X0 Y1 Z0 S1						; set endstop configuration (Y endstop only, at low end, active high)
M92 X87.4890 Y87.4890 Z4000			; Set axis steps/mm
M906 X800 Y1000 Z1000 E800			; Set motor currents (mA)
M563 P0 D0 H1						; Define tool 0
G10 P0 S0 R0							; Set tool 0 operating and standby temperatures
M92 E424							; Set extruder steps per mm (single nozzle)

;*** If you have a dual-nozzle build, remove or comment out the previous line, and un-comment the following 3 lines
;M563 P1 D1 H2						; Define tool 1
;G10 P1 S0 R0						; Set tool 1 operating and standby temperatures
;M92 E420:420						; Set extruder steps/mm (dual nozzle)

;*** If you have a modulated IR probe with on-board microcontroller, change P2 to P1 in the following
M558 P2								; Use a simple modulated Z probe (change to P1 for an intelligent Z probe)
G31 Z2.0 P595						; Set the probe height and threshold (put your own values here)

;*** If you have a Duet board with 1K thermistor series resistors, change R4700 to R1000 to the following M305 commands
M305 P0 R4700 H0 L0					; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P1 R4700 H0 L0					; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
M305 P2 R4700 H0 L0					; Put your own H and/or L values here to set the second nozzle thermistor ADC correction

;*** Adjust the XY coordinates in the following M557 commands to suit your build and the position of the IR sensor
M557 P0 X60 Y0						; Four...
M557 P1 X60 Y165						; ...probe points...
M557 P2 X222 Y165					; ...for bed...
M557 P3 X222 Y0						; ...levelling
;M557 P4 X141 Y82.5					; 5th probe point for levelling (un-comment this if you are using a dc42 differential IR probe)

;*** if you are using axis compensation, put the figures in the following command
M556 S80 X0 Y0 Z-0.5					; Axis compensation here
M201 X800 Y800 Z15 E1000				; Accelerations (mm/s^2)
M203 X15000 Y15000 Z100 E3600		; Maximum speeds (mm/min)
M566 X600 Y600 Z30 E20				; Minimum speeds mm/minute
M208 X214 Y210 Z200					; set axis maxima (adjust to suit your machine)
M208 X-8 Y0 Z-1 S1					; set axis minimum (adjust to make X=0 the edge of the bed)
;
T0									; select first hot end

Diagnostics

M122
Diagnostics
Used output buffers: 4 of 16 (15 max)
Platform Diagnostics:
Memory usage:
Program static ram used: 42104
Dynamic ram used: 39688
Recycled dynamic ram: 128
Current stack ram used: 2712
Maximum stack ram used: 5396
Never used ram: 10988
Last reset 00:40:06 ago, cause: software
Last software reset code & available RAM: 0x0003, 10484
Spinning module during software reset: GCodes
Error status: 0
Bed probe heights: 0.616 -0.245 -1.074 0.703 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
Free file entries: 9
Longest block write time: 462.5ms
Slowest main loop (seconds): 0.463837; fastest: 0.000000
Move Diagnostics:
MaxReps: 4, StepErrors: 0
Heat Diagnostics:
GCodes Diagnostics:
Move available? no
Stack pointer: 0 of 5
Network Diagnostics:
Free connections: 15 of 16
Free transactions: 23 of 24
Webserver Diagnostics:
HTTP sessions: 1 of 8
FTP connections: 0, state 0
Telnet connections: 0

Console log

G32
Bed equation fits points [60.0, 0.0, 0.616] [60.0, 165.0, -0.245] [222.0, 165.0, -1.074] [222.0, 0.0, 0.703]
M32 Cable_Spool-_low_A_100%.gcode
File Cable_Spool-_low_A_100%.gcode selected for printing
Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault
M0 H1
Printing paused
Print cancelled

Edited 1 time(s). Last edit at 04/15/2016 05:38AM by telefunken.

Hi, and thanks for trying my fork.

1. The Z probe reading always has got higher the closer to the bed it is - except when it is very close to the bed, when it may start going down again.

2. Whether the machine waits for the hot end to heat up or not at the start of a print depends on what you have in your slicer start gcode. So we need to see the start of the gcode file you are trying to print to diagnose the problem.

---

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].

Quote
dc42
Hi, and thanks for trying my fork.

1. The Z probe reading always has got higher the closer to the bed it is - except when it is very close to the bed, when it may start going down again.

2. Whether the machine waits for the hot end to heat up or not at the start of a print depends on what you have in your slicer start gcode. So we need to see the start of the gcode file you are trying to print to diagnose the problem.

Thank you for taking the time to answer my questions, and for improving my printer ;-)

1. Great, I guess might have misunderstood the calibration documentation, "Move the Z axis up 2mm. Send G31. The response will most likely be less than 600. Move the Z axis up 0.1mm. Send G31. Repeat the above until G31 reports a value of around 600, +/-20". My number was indeed lower then 600, but I had to move the Z axis down to get a higher reading, not up...
There is something fishy with the leveling though, since the print looks ok in the front part of the bed, and then the head hits the bed as it goes back towards the z-axis. Will look some more into it this afternoon.

2. I use Slic3r and downloaded the "profiles" for ormerod 2 as per the reprap documentation. The custom printer settings looks like this:

Start Gcode:

G28 ; home all axes
M83;
G10 P0 S195 R160                       ; Set tool 0 operating and standby temperatures
T0

End Gcode:

G1 X2 Y190 F9000
G4 S0
G10 P0 S-273 R-273                       ; Set tool 0 operating and standby temperatures
M140 S40

And here is the top of a generated gcode-file (I've btw tried several with the same results):

; generated by Slic3r 1.2.9 on 2016-04-13 at 14:19:05

; external perimeters extrusion width = 0.50mm
; perimeters extrusion width = 0.50mm
; infill extrusion width = 0.50mm
; solid infill extrusion width = 0.50mm
; top infill extrusion width = 0.50mm

M107
M190 S57 ; set bed temperature
G28 ; home all axes
M83;
G10 P0 S195 R160                       ; Set tool 0 operating and standby temperatures
T0

G21 ; set units to millimeters
G90 ; use absolute coordinates
M83 ; use relative distances for extrusion
G1 E-3.50000 F2400.00000
G1 Z0.300 F9000.000
G1 X65.465 Y65.908 F9000.000
G1 E3.50000 F2400.00000
G1 X67.813 Y63.684 E0.29682 F1200.000
G1 X70.519 Y61.456 E0.32155
G1 X73.604 Y59.282 E0.34628
...

Edited 1 time(s). Last edit at 04/14/2016 03:56AM by telefunken.

1. There must be a mistake in those instructions. They should tell you to move the head down 0.1mm at a time, not up.

2. You are setting the head temperature with a G10 command, but after the T0 line you need a M116 command to tell it to wait for all temperatures, unless you have a tpost.g file that does that.

---

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].

And we're back to printing! Thank you for your help!

I added M116 to the custom g-code, and that solved the problem of letting the head heat up properly before starting the print.
The problem with the bed leveling seemed to have been the spots where the auto compensation height was measured. They didn't quite line up with my white tape anymore, meaning inconsistent values. So I adjusted that, and then some small adjustments to the z-axis calibration to get the first layer height back on track.

I'm glad you fixed the problem. Btw I sell a better IR sensor that doesn't need white tapes and works anywhere on the bed.

---

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].