Need help, willing to pay, I'm completely stuck.

Phaedrux

G31 X30.44 Y-9.48 Z-0.25 P25

Your z trigger height should be positive. I think the firmware will automatically convert it to a positive value in this case, but it also seems really small. This should be a measured value as it sets the distance between your nozzle tip and the bed.

Use this procedure to measure the trigger height.

https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe?revisionid=HEAD#Section_Calibrate_the_Z_probe_trigger_height

Then verify that when you move the head to Z0 it is just touching the bed.

In your homing files you can remove the M98 Pretractprobe.g and M98 Pdeployprobe.g commands since G30 will handle that on it's own.

What firmware version are you using by the way?

jameswstubbs

I've made the suggested changes and I've calibrated the z offset, but when I go to print the nozzle just crashes into the bed until I hit emergency stop. Is it an issue with the starting script?

Phaedrux

Can you post the first 50 lines or so of a sliced gcode file to show what it's all trying to do? Just in case S3D is inserting some other gcode into the start.

Also, I just noticed that you run G28 to home the printer, then G32 to run bed.g. And in bed.g you clear any bed compensation, so I think you end up running the print without compensation active. Add G29 S1 to the end of your bed.g to reload your heightmap and re-enable compensation.

jameswstubbs

The G28 command no longer works either, it just crashes the nozzle into the bed! Can't catch a break!

Phaedrux

What firmware version are you using? And can you repost your current config?

jameswstubbs

I've added the G29 S1 to the bed.g file.

My firmware version is 1.21 (2018-03-21).

My S3D starting script for gcode is:

T0
M104 S[extruder0_temperature]
M140 S[bed0_temperature]
M116 H0
;M104 S[extruder0_temperature]
G28
;G32
G1 X0 Y20 Z0.2 F3000 ; get ready to prime
G92 E0 ; reset extrusion distance
G1 X100 E20 F600 ; prime nozzle

My current config with the suggested alterations.

https://1drv.ms/u/s!AvB1JFYrIu_kgv94SEodTxkfG9fvBA

Phaedrux

Ok, you've added G29 S1 to the bed.g file, but you've commented out the G32 command in your start script, so bed.g isn't being called.

Phaedrux

Curious why you have your Z axis minimum set to -0.25mm below the bed.
M208 X-25 Y0 Z-0.25 S1 ; Set axis minima

Phaedrux

If you send M401 and M402 does the BLtouch deploy and retract?
If you raise the nozzle above the bed a good ways and send g30 does the probe deploy and head move toward the bed? If you trigger the probe by hand does it stop? Be ready to power down if it doesn't stop.

jameswstubbs

I can confirm that M401 deploys the prove and M402 retracts it.

I'm not sure why it's set to -0.25 I think this was me in the early stages of trying to figure this out using it like the M851 command in marlin.

I've set it to 0.

I used the g30 command the deploys the probe and when I stop it with my finger it does stop.

The Home all command still doesn't work though, back to crashing into the bed.

jameswstubbs

After a reboot Home all is now working.

Phaedrux

I see one problem with your homeall.g

; homeall.g
; called to home all axes
; generated by RepRapFirmware Configuration Tool on Mon Jul 02 2018 18:40:51 GMT+0100 (GMT Summer Time)
G90                     ; relative positioning
G1 Z5 F6000 S2          ; lift Z relative to current position
G1 S1 X-225 Y-225 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 X5 Y5 F6000          ; go back a few mm
G1 S1 X-225 Y-225 F360  ; move slowly to X and Y axis endstops once more (second pass)
G90                     ; absolute positioning
G1 X110 Y110 F6000      ; go to first bed probe point and home Z
G30                     ; home Z by probing the bed

The very first line is G90 ; relative positioning except that G90 is absolute positioning. Change that to G91 to properly raise the head.

; homeall.g
; called to home all axes
; generated by RepRapFirmware Configuration Tool on Mon Jul 02 2018 18:40:51 GMT+0100 (GMT Summer Time)
G91                     ; relative positioning
G1 Z5 F6000 S2          ; lift Z relative to current position
G1 S1 X-225 Y-225 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 X5 Y5 F6000          ; go back a few mm
G1 S1 X-225 Y-225 F360  ; move slowly to X and Y axis endstops once more (second pass)
G90                     ; absolute positioning
G1 X110 Y110 F6000      ; go to first bed probe point and home Z
G30                     ; home Z by probing the bed

jameswstubbs

That's done, should I go ahead and try and print?

jameswstubbs

Now when I try to print, it home all fine the first time, then goes to home all again and just crashes into the bed.

Phaedrux

You have another G28 in bed.g. remove that one.

jameswstubbs

Done, still getting a nozzle crash when trying to print the calibration cube unfortunately.

I just want to say how grateful I am for your help.

Phaedrux

Can you upload the gcode file you're trying to print? Or copy and paste the first 50 lines or so of it? I need to see what it's trying to do.

Can you post a picture of your heightmap being displayed? I'd like to see what it thinks the bed surface is like.

And just to recap. Homing now works correctly if you tell it to home x, homey, home z, and home all?

Can you post a video of what it looks like from when you start a print?

Is it going just a little too far down into the bed and stopping, or is it just trying to continuously push into the bed?

Can you measure each side of your x axis from the bed to see if your lead screws are misaligned and tilting the x axis.

wilriker

@jameswstubbs said in Need help, willing to pay, I'm completely stuck.:

The Z travel is also way to fast and makes a stupidly loud noise.

Is this solved by now? I am on my phone so I cannot check your steps/mm for Z but if you still use the stock Anet A8 lead screws this should be set to 400 (at x16 microstepping).

This is the one value that I got wrong when converting my A8 and it did what your described. It moved way to fast and also very choppy.

Another consequence of having your steps/mm for Z too high would be that it would move longer than it should what could explain the nozzle crashing into the bed.

Phaedrux

@wilriker Yeah z steps is currently set to 400 according to the config.

SLKittie

Also the speed of the z axis ,might be to fast. i had this and my z axis moved clunky but to fast.
here is a snippet from my g code
; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes backwards
M569 P3 S1 ; Drive 3 goes forwards
M569 P4 S1 ; Drive 4 goes forwards
M350 X16 Y16 Z16 E16:16 I1 ; Configure microstepping with interpolation
M92 X80.14 Y79.89 Z401.04 E95.83:95.83 ; Set steps per mm
M566 X900 Y900 Z12 E120:120 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z180 E1200:1200 ; Set maximum speeds (mm/min)
M201 X500 Y20 Z250 E250:250 ; Set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800:800 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30