[not yet solved] Tevo Little Monster DuetWifi errors
-
It's just odd that the motors will move properly when commanded manually but not when printing. Can you verify the motor current while printing? Send M906 and then M913 without parameters in the console and it will report what the current is set to along with any percentage scaling. Maybe there is a rogue current reduction command happening somewhere.
-
M906
Motor current (mA) - X:1800, Y:1800, Z:1800, E:1800:1800:1800:1800:1800:1800:1800:1800:1800, idle factor 30%
M913
Motor current % of normal - X:100, Y:100, Z:100, E
100100100100:100I tried different voltages for the 4 motors. Are all identical and the default should be 1.8.
I tried also 1200 and 1000. Nothing change.
I tried also the firmware 2.0 but didnt work either. Exactly same attitude as the 2.01.
The probe is settled well ,it perform a good calibration without errors reporting the graph of the surface. Of course not rising the z axis during the print generate a mess of plastic under the extruder.Im starting to feel a little sad...
There is something that can inhibit the Z axis rising during the printing?
-
@giostark can you post the code file you are trying to print
-
0_1537811866488_stab.gcode
0_1537812126970_Tevo_LM_Duet_Adapter_v1.gcode
Maybe those files and setting are not perfect but the first (stab) with the original motherboard was printed several time.
Im able to perform a "good" calibration without errors. For this reason I dont think is something related to the hardware. I settled the zprobe and the first layer is printed well. the second one come printed on the 1st and so on generating a mess of plastic.
-
This post is deleted! -
Well I notice 2 things from your gcode file. First, you don't have a G28 in there to home the printer, so if it isnt already homed when you start the print it may cause problems. Second, your Z moves are all negative.
-
My actual config.g:
Config.g
; Configuration file for Duet WiFi (firmware version 1.20 or newer)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Sat Jul 07 2018 15:37:48 GMT-0700 (Pacific Daylight Time); General preferences
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
;M555 P2 ; Set firmware compatibility to look like Marlin;*** The homed height is deliberately set too high in the following - you will adjust it during calibration.
M665 R157 L397.1073 B175 H523 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; Put your endstop adjustments here, or let auto calibration find them; Network
M550 PTEVO Little Monster ; Set machine name
M552 S1
G4 P1000
M587 S"----------" P"-----------"
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet; Drives original ones with 1.8 degree
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z80 E425 ; Set steps per mm
M566 X1200 Y1200 Z1200 E1200 ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z18000 E1200 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z1000 E1000 ; Set accelerations (mm/s^2)
M906 X1800 Y1800 Z1800 E1800 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 Z0 S1 ; Set minimum Z; Endstops
M574 X2 Y2 Z2 S1 ; Set active high endstops
M557 R130 S20 ; Define mesh grid; Z-Probe
M307 H3 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 H5 F100 T2000 A5 R0.1 ; P9 for BLTouch, dive height 5mm, probe at 100mm/min, travel 6000mm/min, up to 5 probes, pause 0.1s
G31 X0 Y20 Z0 P25 ; Set Z probe trigger value, offset and trigger height
M557 R150 S45 ; Define mesh grid; Heaters
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C; Fans
M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P2 S1 I0 F500 H0 T50 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on; 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; Automatic power saving
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss; Custom settings
M591 D0 C3 P2 E6.0; Filament Sensor - Add the following to config file anywhere before the M501 command
M591 D0 P1 C4 R20 ; configure extruder drive 0 to use E1 endstop (C4) with 20% tolerance
M591 D0 ; display filament sensor parameters for extruder drive 0; Miscellaneous
M501 ; Load saved parameters from non-volatile memory; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool on Sat Jul 07 2018 15:37:48 GMT-0700 (Pacific Daylight Time)
;M280 P3 S160 I1
M280 P3 S10 I1; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool on Sat Jul 07 2018 15:37:48 GMT-0700 (Pacific Daylight Time)
M280 P3 S90 I1 -
Now every time I start a print I put the head in home by hand. Ill fix it.
Sorry , what you mean negative? and where? How should I set them properly ? -
@phaedrux the file I have checked have no Z Moves at all in fact the only Z character is at the start to zero the extruder no wonder everything is printed on top of each other it is as if the layer height has been set to 0
-
I was looking at the stab.gcode.
-
@phaedrux said in [help] Tevo Little Monster + DuetWiFi + DuetTouch7" errors:
I was looking at the stab.gcode.
Ah...ok
So what do you would insert as start script? -
@dougal1957 said in [help] Tevo Little Monster + DuetWiFi + DuetTouch7" errors:
@phaedrux the file I have checked have no Z Moves at all in fact the only Z character is at the start to zero the extruder no wonder everything is printed on top of each other it is as if the layer height has been set to 0
Ok im facing with all my ignorance...so do you mean the same as Phaedrux?
-
@giostark at the minimum just g28
Can you post some screen shots of your slicer configuration?
-
I'll look at that next mine was the tevo_lm one
-
the first one I looked at was cura the stab was S3d
-
@phaedrux said in [help] Tevo Little Monster + DuetWiFi + DuetTouch7" errors:
@giostark at the minimum just g28
Can you post some screen shots of your slicer configuration?
Sure...
Those files come from the web...are not mine.The tab not reported are not configured (all unchecked)
About the start and end script:
Start: empty...i dont know is appropriate for the duetwifi
end:
M104 S0 ;extruder heater off
M140 S0 ;heated bed heater off (if you have it)
G91 ;relative positioning
M83 ; RELATIVE EXTRUSION
G1 E-1 F300 ;retract the filament a bit before lifting the nozzle, to release some of the pressure
G1 Z+0.5 E-5 X-20 Y-20 F{travel_speed} ;move Z up a bit and retract filament even more
G28 ;move to endstops
M84 ;steppers off
G90 ;absolute positioning
M82 ; RESTORE ABSOLUTE EXTRUSION
-
OK if you downloaded the Code files from the web then I would discount them totally and work with raw STL files and slice them and see what you get
-
Maybe start with a simple cube printed in vase mode or such you will soon see whats happening without wasting to much filament/time
-
0_1537814313478_stab.stl
0_1537814322221_Tevo_LM_Duet_Adapter_v1.stlThanks really ,
What I should insert as "start script" ?
The Z negative make sense if it stay always on the same layer...(the 1st lower) -
From what I have studied the code whoever did it has a large negative offset which could account for it looking that way but it does seem to increment by 0.2 each layer but if you start at - 0.5 wish then it is doomed to failure if you need to start at 0.1 say I think you need to forget downloading other peoples gcode and start from your own
