Creality CR-10 upgrade

Agniusm

Filament sensor did not work, was missing again S parameter. Is there a list of changes done to 1.21 as i just wasted a spool of filament.
Also, i looks like it does not apply mesh map when printing. Do i have something wrong?:

; Configuration file for Duet WiFi (firmware version 1.17 to 1.19)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Sat Nov 11 2017 18:50:00 GMT+0200 (FLE 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

M584 X0 Y1 Z2:4 E3 P3 ; two Z motors connected to driver outputs 0, 1, 2 and 4
M671 X-25:432 Y100:100 S5 ; leadscrews left and right

; Endstops
M574 X1 Y1 Z0 S1 ; Define active low and unused microswitches
M558 P4 I0 F300 X0 Y0 Z1 T7000 ;
G31 P100 X17.73 Y-19.32 Z0.195 ; Z probe offset from the nozzle
M557 X10:384 Y-20:370 S93.5 ; Define mesh grid 100
M208 X407 Y417 Z350 S0 ; Set axis maxima
M208 X-22 Y-12 Z0 S1 ; set axis minima and low homing switch positions (adjust to make X=0 and Y=0 the edges of the bed)
M591 D0 P2 C4 S1 ; Filament runout

;M556 S79.95 X-0.1 Y0.5 Z0.55 ; Axes compensation

; Drives
M569 P0 S0 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes forwards
M569 P4 S0 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80.03 Y80.22 Z402.43 E823.54 ; Set steps per mm X80.06 Y80.22
M566 X380 Y380 Z12 E120 ; Set maximum instantaneous speed changes Jerk (mm/min) Z100
M203 X12000 Y12000 Z1000 E1200 ; Set maximum speeds (mm/min) Z800
M201 X1000 Y1000 Z1000 E9000; Set accelerations (mm/s^2) Z200

M906 X1400 Y2800 Z1400 E1400 I20 ; Set motor currents (mA) and motor idle factor in per cent
M84 S10 ; Set idle timeout

; Heaters
M143 S380 ; Set maximum hotend temperature to 380C
M143 H0 S150 ; Set maximum bed temperature to 150C
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M307 H0 A202.7 C608.4 D3.0 B0 ; Use PID on bed heater
M305 P1 X201 ; (PT100 thermocouple on channel 2)

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

; Network
M550 PCreeX ; Set machine name
M551 P ; Set password
M552 S1 ; Enable network
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

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

; Custom settings are not configured

; M501 ; for tool offset

Agniusm

You can see here at the back that nozzle is too low and next to it it prints almost alright.
I have done gantry leveling and mesh compensation with 25 points and my plate is precision milled so it should not be that extreme.

alt text

Phaedrux

Do you use G29 S1 anywhere in your print start code to load the mesh grid compensation height map? You can add it to your config as well if you want it to be active always starting at power up.

Can you post the image of the height map results?

dc42

@agniusm said in Creality CR-10 upgrade:

Is there a list of changes done to 1.21 as i just wasted a spool of filament.

The GitHub page for every release refers to https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md. Always read the upgrade notes for the release you are upgrading to and for any releases you have skipped.

Agniusm

@phaedrux I use G29 alone so it probes before each print.
I will get the map posted as my printer is away

Agniusm

Can someone explane how to call macro file in start gcode? Asked this and still have no answer.
I am slicing with slic3r.
Putting:
M98 Pgantry_leveling.g
does not work.

Stephen6309

@agniusm You need to use the full path.
M98 P/macros/gantry_leveling.g

Agniusm

Thank you. And its not this path:
M98 P/sys/gantry_leveling.g ?

dc42

It depends on which folder you put the macro in. If you put it in /sys then you should not need to use the full path.

Agniusm

Had a chance to film my first layer.
Using Prusa 5V induction probe on precision aluminium plate.
Cant remember exact deviation on mesh map but its 0.07 max.
I am using gantry leveling as well.
I always get front right quarter of the bed too high. I am lost as dont know why it would not compensate. Those induction probes as per Tom's YT channel are ones of the most acurate ones.
If anyone could chime in and point my error?

https://youtu.be/ZjNbv5uATFE

dc42

Is there any other metalwork near the front right corner that might be affecting the inductive sensor?

Agniusm

There is none. Its uniform. It has y carriage on 4 rail blocks. Bed is 8mm thick on 10mm standoffs from y carriage. Those induction probes are less sensitive to aluminium and my z offset is at ~0.2mm.
I know it should be far better than this.
I have enders with those uneven chinese heated beds running pinda's and they do work very good. Layers are smooth like butter.

I have a script where it parks hotend 60mm abobe the bed, blows part cooling fan full whack and heats the bed to print temp, then goes for mesh mapping.

dc42

@agniusm said in Creality CR-10 upgrade:

Those induction probes are less sensitive to aluminium and my z offset is at ~0.2mm.

True; but they are much more sensitive to magnetic materials, such as non-stainless steel screws. They are also somewhat sensitive to temperature and supply voltage.

Agniusm

There is no fluctuation from psu, unless dwc readouts are inacurate. I have no protruding bolts and all of my fittings are stainless exept for the frame but they are far away.
I know that probes are sensitive to heat and thats why i have a script to move it out of the way while heating.
Here is my bed and whats underneath:

https://youtu.be/XLu0cw31nQE

Agniusm

So i have checked and rechecked and M98 does not work.
My macro file gantry_leveling.g is located in /Macros catalog and i place:
M98 P/macros/gantry_leveling.g
It reports that file is not found. Was this function tested and confirmed working?
Maybe there is syntax errors and rules that must be followed like space between P and path or CAP sensitive?

whosrdaddy

M98 is known to work but it is Case sensistive!

did you try M98 Pgantry_leveling.g ?

dc42

Do you have any other characters on that line after the final ".g" ?

Are you certain that when you created the file, you didn't add an extra space after or before the filename?

You can also try:

M98 P"/macros/gantry_leveling.g"

or:

M98 P"gantry_leveling.g"

whosrdaddy

@dc42 : maybe update the wiki to reflect the fact that quotes are allowed for M98?

Agniusm

OK, will try your suggestions. I guess my error will be with Case.
I am sure i have no space after .g

BTW, i think i have pinpointed my leveling issue.
I have printed holders for Z motors and my right motor was getting hotter than left one to the point it melted plastic. I have ordered longer motors and some 50x50x5 aluminium angle to fabricate some brackets.
I think it was just turning motor slightly so compensation was canceling out on melted saggy plastic.
Wow, that took me some time to notice.

Phaedrux

@whosrdaddy In addition to knowing quotes are allowed it would be nice to know when they are required.

Maybe I'm old school, but I always contain paths and strings in quotation marks. Especially if there is white space in it.