Creality CR-10 upgrade
-
@dc42 Good note. Had no clue there were extra inputs. So i can take +3.3V, gnd and say stop 11(ENC_A) and in M585 E11? This is for precision piezo
-
Do i need to define precision piezo in config.g? At the moment i have my induction probe:
M558 P4 I0 F300 X0 Y0 Z1 T7000 ;
should i need to add:
M558 P1 I0 R0.4 F300 X0 Y0 Z0 ; Set precision piezo probe -
I getting an error of missing command, M501 in config.g.
"Set the active parameters to those stored in sys/config-override.g on the SD card. This command should be included near the end of the config.g file so that the stored parameters will be loaded at startup. It can also be used to revert parameters to the values stored in config-override.g after experimenting with them."
I am not really grasping on what it does. -
The purpose of config-override.g is to replicate some of the behaviour of EEPROM in 8-bit firmwares. You don't really need that facility in RRF because it's so easy to edit config.g to save settings that you want restored every time you power up the printer; but that doesn't stop users asking for the feature, and In a few situations it is genuinely useful. But if it confuses you, just remove or comment out the M501 command at or near the end of config.g, then don't expect M500 to save any settings.
-
But i cant cancel it out as it is required by M585.
So the question then is, does M585 write offset to override file and then load that offset from there?
Also its unclear how that endstop needs to be set up. Does it needs to be set in config.g
I am afraid it will not stop with M585 at trigger.
Its advanced electronics with duet and i am probably too fresh to sort it out on my own so sorry for keep asking. -
If you want to run M585 and then M500 so that the resulting offset is restored after you power the machine down and up again, then you do need to use config-override.g.
-
So i have it set up like this:
; Probe piezo and set new tool offset
G28
M574 Z0 S0
G10 P0 Z0 ; clear Z offset
T0 ; select a tool
G90
G1 X436 Y0 Z205 F3000 ; move above probe
G92 Z215 ; Pretend that tool is offset at Z=15
M585 Z100 L0 E11 F400 S1 ; Znnn - Probe tool in Z direction where nnn specifies the expected distance between the trigger point of your endstop switch and the starting point
M500 ; save new offset
G1 Z215 ; lift the tool to Z=15
G92 Z205 ; Cancle tool offset
G28I am probing high not to crash into the bed. When i hit piezo it does not stop. I dont knkw what i am doing wrong here. It got to do with my endstop on stop 11 i think.
-
Which firmware version are you using?
-
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.02RC2(RTOS) (2018-09-07b2)
WiFi Server Version: 1.21
Web Interface Version: 1.22.3Also M98 does not work for me. I have a macro file: gantry_leveling.g
When i put: M98 Pgantry_leveling.g in my slicer starting gcode script it would not execute that script.
P.S. or perhaps i have to include subdir: M98 P/sys/gantry_leveling.g ? -
I just read on another chaps rant that you dont support RC releases so perhaps i have upgraded too far up and some issues i am having are to do with that.
I noticed my bed would not switch off after print.
Anyway, what would be most recent stable combo to have non of compatibility issues between FW, wifiFW and DWC? -
@agniusm said in Creality CR-10 upgrade:
I just read on another chaps rant that you dont support RC releases so perhaps i have upgraded too far up and some issues i am having are to do with that.
I noticed my bed would not switch off after print.
Anyway, what would be most recent stable combo to have non of compatibility issues between FW, wifiFW and DWC?Did you send the required code to shut the bed off in the ending g-code?
-
Version 2.01 is the last stable release if you'd like to try.
Do you have more info about the bed switching off? Was there a heater fault?
-
@agniusm said in Creality CR-10 upgrade:
I just read on another chaps rant that you dont support RC releases so perhaps i have upgraded too far up and some issues i am having are to do with that.
That applies to beta and RC releases that have been superseded by a stable release. I do support users running the latest beta or RC release, and your feedback on them is very valuable.
-
@tjb1 it was working fine untill upgrade of the firmware. Maybe there is something new like with homing gcodes and s2's
P.S. all is good regarding bed heater. When updating i uncommented so i dont have to way for the bed while doing test prints.
Discard this -
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 MarlinM584 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) Z200M906 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
-
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.
-
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?
-
@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.
-
@phaedrux I use G29 alone so it probes before each print.
I will get the map posted as my printer is away -
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.
