Creality CR-10 upgrade
-
So my upgraded printer is working 24/7 great. Had a fan failure but that was to be expected with cheap chinese stuff. Got a small issue i was putting off for some time. i have mesh compensation in place and it works great but i have my front off the bed not completely working with this.
Here is 2 same run parts, one from the middle of the bed(rest are same good) and one from the front (on the right). The nozzle is a tad off when printing on the front of the bed:
I was wandering where i should look for the issue? I know my grid is set wrong as it misses some points(skips them). Would that cause an issue?
Otherwise i am very happy with Duet hardware and the way i can edit my configs on the fly, i can really appreciate that now since i am working on Marlin firmware for my budget cluster.
P.S. perhaps the tool to calculate mesh grid appeared for square build plates? That would be handy. or is there any plans on automatic calculation of the mesh? Say you enter how many grid points on x and y and it sets spacing? Would be even better. i think Marlin does that
-
@agniusm said in Creality CR-10 upgrade:
I know my grid is set wrong as it misses some points(skips them). Would that cause an issue?Any probe points that cannot be reached by the probe (taking into account the machine limits set by M208 and the Z probe offsets set by the G31 X and Y parameters) will be skipped.
P.S. perhaps the tool to calculate mesh grid appeared for square build plates? That would be handy. or is there any plans on automatic calculation of the mesh? Say you enter how many grid points on x and y and it sets spacing? Would be even better.
Good idea, I'll add it to the work list.
-
David, we were brainstorming a method for e3d toolchange and how we can automate tool offsets for different tools. Perhaps you have a solution but i got an idea i would like to test as it is relevant to me too.
I want to mount precision piezo disc on my frame where my extruder can reach and probe it to set the height of the nozzle then use inductive probe for mesh mapping. This way, each time i swap the nozzle, i dont have to readjust z offset as even quarter turn of the nozzle throws calibration away.
How can i implement this in duet settings? -
Have you looked at https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M585_Probe_Tool ?
-
Actually just yesterday was going through gcode wiki and saw this one. I will investigate.
-
@agniusm said in Creality CR-10 upgrade:
David, we were brainstorming a method for e3d toolchange and how we can automate tool offsets for different tools. Perhaps you have a solution but i got an idea i would like to test as it is relevant to me too.
I want to mount precision piezo disc on my frame where my extruder can reach and probe it to set the height of the nozzle then use inductive probe for mesh mapping. This way, each time i swap the nozzle, i dont have to readjust z offset as even quarter turn of the nozzle throws calibration away.
How can i implement this in duet settings?Are you using E3D hotends? The nozzle should tighten against the heat break so provided the nozzles are all the same length from end to tip, they should all tighten to the same distance.
-
@tjb1 Yes. Using e3d. Even if so printing different materials can have impact(thermal expansion) PLA vs PC can be 100C difference. This idea came thinking about e3d toolchanger. I was not specifically wanting to do this on my machine, but I had precision piezo kit and thought I will test the idea. Actually it will be handy if it works the way I think. Sometimes I need to change a fan and it is mounted with induction probe. Even if I do not touch induction probe out of the clamp it still needs recalibration.
@dc42 I want to place my probe slightly below my bed so it is out of the way. So my macro should look something like this:G28 ; home
G10 P0 Z0 ; clear Z offset
T0 ; select a tool
G1 X430 Y0 Z10 F3000 ; move above probe
M585 Z F400 E2(cant remember which is asignet to z stop(2?) and which to z probe) ; drive into probe
M500 ; save new offset
G1 Z20 ; lift the tool not to drive into bed edge
G28
M98 Pmeshbed.g
One thing I'm not sure about how to add extra distance if my probe is say 10mm below my bed. -
@agniusm said in Creality CR-10 upgrade:
One thing I'm not sure about how to add extra distance if my probe is say 10mm below my bed.
You could use G1 to move the nozzle to be above the switch at Z=5. Then send G92 Z15 to pretend it is at Z=15. Use the M585 command to probe the switch. Then do G1 Z15 followed by G92 Z5 to remove the 10mm Z offset.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 thanks. A work around then
How should i set my probe in M585 E if i connect my probe to Z probe 4 pin connector near paneldue connector? My stop endstops are all pupulated. -
@agniusm said in Creality CR-10 upgrade:
@dc42 thanks. A work around then
How should i set my probe in M585 E if i connect my probe to Z probe 4 pin connector near paneldue connector? My stop endstops are all pupulated.I suggest you use one of the endstop inputs on the CONN_LCD connector.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@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?
