Creality CR-10 upgrade
-
You can initiate a pause using an endstop input a a trigger. See the M580 command in the GCode wiki.
-
The M580 is something "select Roland". I don't even know what that is. Was it a typo and should i just look up pause M25 (M24 to resume) in combination with M581 for external trigger?
-
I am sorry, I misremembered - I meant M581. You can use the T1 trigger number to make the printer pause, without having to set up a trigger macro.
-
So if i put: M581 E1 T1 S1 C1 in config.g, it should suffice to execute <pause>and when power is restored, i would execute <resume>macro or it should still be available on print menu on LCD?
Probably i would want to have T2 to execute macro file as i will need to shutdown all the heaters to prevent UPS drain</resume></pause> -
That all sounds good to me, except that you will also need to restore the heater temperatures in your resume macro.
-
Regarding build plate. I cant seem to find the difference between Mesh grid compensation (G29) and Auto bed compensation (G32)
When i run G29 and add G29 S1 to my starting gcode, nothing happens but when i run G32 just before a print, i can see Z lead screws move tiny bit when printing a model.
On the wiki it says G32 is obsolete, and better to use G29. But what i am missing here. My bed is quiet level at about ~0.09mm (on G32, probing 5 points).EDIT. probably it does the job. Since G29 grid is multiple points adjustments are not that noticeable.
-
BTW is there a tuning procedure for pt100 sensor? I have done tuning for the bed and now its dead on target but hotend is fluctuating up and down 2.5 degrees
-
exactly the same as you would do the bed I did mine last week when I changed my Heater block and Nozzle to the Copper ones.
-
BTW is there a tuning procedure for pt100 sensor? I have done tuning for the bed and now its dead on target but hotend is fluctuating up and down 2.5 degrees
Is it a regular oscillation of 2.5 degrees, or a random fluctuation?
-
If it is a regular oscillation, try increasing the D parameter in the M307 command for the hot end by about 20% (bearing in mind that if you are using a config-override.g file, it's the one in config-override.g that counts).
-
If it is a random fluctuation, you probably have a poor connection in the PT100 wiring.
-
-
Regarding build plate. I cant seem to find the difference between Mesh grid compensation (G29) and Auto bed compensation (G32)
When i run G29 and add G29 S1 to my starting gcode, nothing happens but when i run G32 just before a print, i can see Z lead screws move tiny bit when printing a model.
On the wiki it says G32 is obsolete, and better to use G29. But what i am missing here. My bed is quiet level at about ~0.09mm (on G32, probing 5 points).EDIT. probably it does the job. Since G29 grid is multiple points adjustments are not that noticeable.
You can run M122 and look at "Bed compensation in use" to check whether mesh compensation is active.
-
Thank you. Will check it out
-
I am having problems with IR probe. Last night set the probe and all was good, today morning started a print and it was 0.55mm off. I ran mesh bed compensation (G29). I have gcode so use saved bed map in my gcode starting script. I noticed this throughout the build that it is not consistent. I do mesh bed compensation probing with heated bed and nozzle.
One thing i have noticed that my IR probe LED sometimes goes very dim and sometimes goes out. Don't know if that has to do with anything.
Just ran test 3 times and i get a lot of play. Here is single point measured:
1. -1.102
2. -1.080
3. -0.595
That is no good at all -
I'm thinking now, perhaps i should run the test before each print?
-
One thing i have noticed that my IR probe LED sometimes goes very dim and sometimes goes out.
You probably have a bad crimp connecting in the +3.3V feed to it.
-
Done some testing as per mesh bed compensation wiki description. Set the Z=0 where paper just touches the nozzle.
save Z G92 Z0. then command nozzle up 5 to 100mm and then G30 S-1. I get these on the same spot with heated bed and heated nozzle at my print temps:
2.475
2.477
2.482
2.480
2.517
2.505
2.500
2.507
2.515
So the variation is 42uM. Is that within tolerances? I never print at 0.05 layer hight -
That's a higher variation than normal. Also it seems to be creeping up. What type of Z axis do you have, what is your Z steps/mm, and what probing speed are you using (F parameter in M558)?
-
I have 2 lead screw trapezoidal system, standard prusa style @ Z402.43 steps. My speed is at F800 at the moment but i have bumped it up cause running mesh compensation each time before print. I think it was 600 when tested.
BTW, i checked my IR probe connections and they are good. LED on the probe is out completely. I did not put kapton tape on the back side of IR and my offsets are X5 Y14.5 from the heater block -
Be careful, if you don't have Kapton take on the back of the IR sensor, it could contact the heater block, and if your heater cartridge develops a short too then that will wreck your Duet.
Try a lower probing speed. You may be able to reduce the dive height to speed up probing.
-
Its about 10mm away from heater. Will put some just in case. I have lowered my probing speed to 400. Will test later if it make any difference.
I have a bit of issue trying to set up my starting G code for heater sequence.
I want printer to home, heat up the bed and nozzle at the same time, then home and perform mesh bed compensation.
Something is wrong with my gcode and i ran out of ideas. It heats the bed, then does homing, mesh bed and then heats the nozzle.
Here is my starting gcode:
M83 ; extruder relative mode
M106 P2 S1 ; LED on
G10 ;
M116 H0 ;
M116 H1
G28 W ; home all without mesh bed level
G29 S0 ; mesh bed leveling
G1 Y3 X-7 Z0 F7000.0 ; go outside printing area
M572 D0 S0.07 ; Pressure advance
G1 X100.0 E9 F1000 ; intro line
G1 X204 E12.5 F1000 ; intro lineI tried with M109 and M190
-
Most slicers insert there own heat-and-wait commands before your start GCode. Look at the start of the GCode file to see what your slicer has actually generated.
