Creality CR-10 upgrade
-
Motor directions: set them all to forwards, then reverse any that are wrong
IR probe: select smart IR probe. Set trigger height to 1mm initially, and adjust it by editing the G31 command in config.g when you have measured it.
Microstepping: start with x16 and interpolation on.
See https://duet3d.com/wiki/Bed_levelling_using_multiple_independent_Z_motors and https://duet3d.com/wiki/Using_mesh_bed_compensation for bed levelling and mesh bed compensation. You can use bed levelling followed by mesh bed compensation if you want.HTH David
-
How did it work out. I'm going to put a WiFi in my CR-10
-
Still in progress. Have taken upon task changing motion system to linear guide rails. Basically little of creality will be present
-
@MontyFlange - I am currently filming a video about converting a CR-10, and will also do a live stream installation. If you need any help just let me know.
-
With prusa i3 mk3 anounced i wander if duet wifi hardware is capable of detecting skipped steps and could work without end stops by detecting current increase on hard stop?
-
It would possible to do that, but it would need to be tuned to the particular motors and mechanics you made using. It's not especially accurate, because the stall detection is only updated every full step of the motor. You couldn't rely on it it to detect the stall on exactly the same full step each time. IMO it's a bit of a gimmick - like the automatic XY skew calibration in the i3 Mk2, which solves a problem that doesn't exist except in badly-made cheap 3D printer kits.
-
When i was ordering my mk2 i was made thinking about XY skew correction to be a top notch tech but when i got thinking about it as you say just a gimmick, but that's what they have to do to get printer made of threaded rods(
) aligned. It was my first machine so i was not really familiar with cnc or 3D printers.
So basically all that stuff is just eye candy, except perhaps the bed. There is no need for layer shift detection cause if the machine is setup right it should not happen anyway unless you left part removal mallet on the rails.
What would you suggest to use for endsops? I have CR-10 mechanical switches and those geeetech optical endstops. Salvaged some resistors to replace and make them compatible with 3V as per guide. -
I have found mechanical switches to be entirely adequate. The optical ones should work well too. So use either.
-
I would like to reduce some wiring going to the extruder assembly and was wandering if everyting on duet has common ground and if it is OK to tie up ground?
I would like to route common groung for extruder heater, pt100, 2 fans, stepper and ir sensor.
Thanks -
You can use a common +12V or +24V line for the extruder heater and both fans (assuming they are all the same voltage), because the Duet switches the ground side ot the supply to all those devices. That's all. Take the common positive supply from the extruder heater output, because the fan output connectors shouldn't carry more than 2A.
-
OK. Got another weird question out of the blue, dont laugh. So i habe that IR probe with signal, ground and +3.3. What would happen if i will have a switch paralleled to IR ground and signal shorted? The probe is used before print and keepimg wiring to the minimum, what if simple filament runout sensor switch was hooked there? I am no electronics guy but would that might work?
-
Btw, here is my extruder and all:
-
OK. Got another weird question out of the blue, dont laugh. So i habe that IR probe with signal, ground and +3.3. What would happen if i will have a switch paralleled to IR ground and signal shorted? The probe is used before print and keepimg wiring to the minimum, what if simple filament runout sensor switch was hooked there? I am no electronics guy but would that might work?
I don't see why you would want to connect a filament runout sensor to the Z probe input. Filament monitors are normally connected to spare endstop inputs.
-
Started wiring. Got the X and Z working fine. Still need to wire in some end stops.
Do i need mechanical endstop on Z if i have IR bed probe?
The thing that buggers me though is the constant disconnect with message:
An AJAX error has been reported, so the current session has been terminated.
Please check if your printer is still on and try to connect again.
Error reason: timeout
Then i get:
Could not establish a connection to the Duet firmware! Please check your settings and try again.
After some refreshes it connects but it repeats.
I have read about signal strength but have no clue why, i think i have good connection, probably 6m away. -
See https://duet3d.com/wiki/WiFi_disconnections_and_AJAX_timeout_errors to start with.
-
[[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) -
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 -
beecause it hasn't taken the firmware try again make sure you are doing the right one?
-
OK. Tried this one more time and it updated. Now disconnects are rarer and reconnects faster. Still get them though
-
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
