Creality CR-10 upgrade

Agniusm

[[language]]
M122
=== Diagnostics ===
Used output buffers: 3 of 32 (8 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19 running on Duet WiFi 1.0
Board ID: 08DDM-9FAM2-LW4S4-6JKF0-3SD6J-T2SVX
Static ram used: 21176
Dynamic ram used: 95928
Recycled dynamic ram: 1680
Stack ram used: 1304 current, 4840 maximum
Never used ram: 7448
Last reset 00:01:19 ago, cause: power up
Last software reset reason: User, spinning module GCodes, available RAM 7448 bytes (slot 3)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 21.0, current 26.2, max 28.4
Supply voltage: min 12.1, current 12.1, max 12.3, under voltage events: 0, over voltage events: 0
Driver 0: standstill
Driver 1: standstill
Driver 2: standstill
Driver 3: standstill
Driver 4: standstill
Date/time: 2017-11-11 23:25:16
Slowest main loop (seconds): 0.008141; fastest: 0.000034
=== Move ===
MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heater = 0, chamber heater = -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
Network state is running
WiFi module is connected to access point 
WiFi firmware version 1.19
WiFi MAC address 5c:cf:7f:ef:4d:9b
WiFi Vcc 3.12, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39848
WiFi IP address 192.168.2.144
WiFi signal strength -62dBm
HTTP sessions: 1 of 8
Socket states: 2 0 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)

Agniusm

Updated firmware and interface, i don't know why some modules show as 1.19 when it should be 1.20:

Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.19 (2017-08-14)
WiFi Server Version: 1.19.2
Web Interface Version: 1.19.3

Dougal1957

beecause it hasn't taken the firmware try again make sure you are doing the right one?

Agniusm

OK. Tried this one more time and it updated. Now disconnects are rarer and reconnects faster. Still get them though

Agniusm

Stuck with mesh bed probing. I follow this:
Make sure there is no filament stuck to the nozzle (you may want to do this test with the nozzle hot)
Cancel any existing bed compensation by sending M561
Send M208 S1 Z-3 to temporarily allow Z moves down to Z=-3mm. This is to ensure that you can lower the nozzle all the way to the bed in step 5.
Command the print head to the XY coordinates you want to probe
Command the print head down in small steps until the nozzle just touches the bed or just grips a sheet of paper. You may need to send M564 S0 to allow movement lower than where the firmware thinks Z=0 is. You may also wish to create a macro to lower the head by e.g. 0.02mm to get greater accuracy (G91 followed by G1 Z-0.02).
Send G92 Z0 to define that height as Z=0
Command the nozzle up 5mm (G1 Z5)
Send G30 S-1 to probe the bed without resetting the Z=0 position
Read off the Z height from the web interface. That is the trigger height.

And get trigger height at 2.320
I put that value in config.g
G31 P500 X5 Y14.5 Z2.32
I don't know if i set the offsets correct. My probe is 5mm to the left of the nozzle and 14.5mm in front of the nozzle.
When i home, Z is at 2.32
The i do Mesh grid and send G29 but the bloody thing drives into the bed.
I am totally lost here

dc42

Check that you don't also have a config-override.g file with a G31 command in it.

The WiFi disconnects may be even rarer if you upgrade to 1.20RC1, but you may wish to defer that until you have everything working.

Agniusm

OK Everything works fine now. Trying to extrude. Doing extruder calibration. E3D states that their extruder is 400 steps but i only get half of the requested 100mm of filament. Will double the steps but why twice from stated 400? Could be voltage, that they state rate at 24V? Will see

P.S. BTW, any pointers where i can get sample start end end gcode scripts with mesh compensation?

dc42

@Agniusm:

OK Everything works fine now. Trying to extrude. Doing extruder calibration. E3D states that their extruder is 400 steps but i only get half of the requested 100mm of filament. Will double the steps but why twice from stated 400? Could be voltage, that they state rate at 24V? Will see

The (approx.) 400 steps is for a 1.8deg extruder motor. You are probably using a 0.9 deg motor. If you bought it from E3D, it will be 0.9deg.

Agniusm

Ah, yes, you are correct, i completely forgot i've read somewhere about it.
I thank you David for your support and answering those noob questions. I can state that my build is alive and printing. Still some road to cover with fine tuning but i am so happy that i have completed this machine. Here is my 6th test cube:

P.S. I have noticed that each time i control printer through Panel Due i get ajax error on web interface.

dc42

Please report the text of the "Error reason" in the Ajax error message Z if there is one.

Agniusm

One general question. Trying printing quicker and i get some uneven perimeter lines. What could be happening? Does Extrusion Factor on web interface got anything to do with it?
My pressure advance is set to .7 on direct drive

; 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
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X79.9 Y80.69 Z396 E800 ; Set steps per mm
M566 X900 Y900 Z12 E200 ; Set maximum instantaneous speed changes (mm/min) (buvo e120)
M203 X40000 Y40000 Z1000 E1200 ; Set maximum speeds (mm/min)
M201 X3000 Y1500 Z20 E250 ; Set accelerations (mm/s^2)

M906 X1000 Y1500 Z1000 E1200 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

dc42

If your extruder is direct drive (i.e. no significant length of Bowden tube between the extruder drive and the nozzle), then pressure advance of 0.7 is much too high. Try 0.05.

Agniusm

Tried 0.5 and 0.7 made it better. I found my problem. Skipping gear on e3d.
Don't know why its happening so will contact their support

Agniusm

What should i put in starting Gcode for mech bed compensation?
is it only the M28 command or should i erase previous probing?
Here is what i have at the moment (mainly modified from prusa mk2
M83 ; extruder relative mode
M104 S[first_layer_temperature] ; set extruder temp
M140 S[first_layer_bed_temperature] ; set bed temp
M190 S[first_layer_bed_temperature] ; wait for bed temp
M109 S[first_layer_temperature] ; wait for extruder temp
G28 ; home all without mesh bed level
G32 ; mesh bed leveling
G1 Y20 X10 Z0.30 F7000.0 ; go outside printing area
G1 E10 F100
G1 X100.0 E9.0 F1000 ; intro line
G1 X180.0 E12.5 F1000 ; intro line

So instead of 5 point probing G32 i have, should i change to:
G29 S0 (or S1 if i want to use previous data from last measurement)?

Agniusm

So my titan aero is clicking and e3d sent a new motor only larger which does not fit my design. Are you David use titan aero and if so any issues ? I found this motor and i dont know if the data is correct and if it would work: https://www.omc-stepperonline.com/hybrid-stepper-motor/nema-17-bipolar-18deg-18ncm-255ozin-07a-29v-42x42x25mm-4-wires-17hs10-0704s.html

dc42

I don't use a Titan Aero, I use a regular Titan. The motor I use is this https://www.omc-stepperonline.com/hybrid-stepper-motor/nema-17-bipolar-18deg-22ncm-31ozin-133a-28v-42x42x34mm-4-wires-17hs13-1334s.html.

Agniusm

Changed my bed for precision plate now battling IR probe as endstop. I cant seem to grasp the concept here. I lover the nozzle to where it touches the piece of paper then G92 Z0 and when i home it does not go back to that height. Tried G31 P500 X5 Y14.5 Z-5.5 ; with no success.
Whats the proper procedure setting Z probe height?
I am looking at these :
https://duet3d.com/wiki/Setting_up_automatic_probing_of_the_print_bed
https://duet3d.com/wiki/Using_mesh_bed_compensation

dc42

The G31 Z parameter should be positive for sensors that trigger before the nozzle touches the bed. For the IR sensor is should be no higher than about 3mm.

If you are restarting the Duet between attempts, also check that you don't also have a G31 command in config-override.g.

Agniusm

I dont have that file. So G31 is the offset of the Z probe depending how its mounted?
So then i would go:
M208 S1 Z-3
Lower the nozzle to where it touches say piece of paper.
G92 Z0 to store that
But where is that offset, do i need to read it from web interface and then enter it to config.g's G31? Is there a step by step somewhere?

dc42

I suggest you read the commissioning instructions in the fitting instructions page, at https://miscsolutions.wordpress.com/mini-height-sensor-board/.