DUEX 5 V0.8 TO DUEX 5 V0.11
-
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
M308 S3 P"duex.e2temp" Y"thermistor" T100000 B4138 R2200
Good morning the correct TEMPERATURE I had to put R 2150
M308 S3 P"duex.e2temp" Y"thermistor" T100000 B4138 R2150
-
@droftarts
E2 +E3+E4+E5+E6 Filament Sensing it works very well
E2 +E3+E4+E5+E6 it does not work when microswitch is configured There is no way to make it work if I close the led the same collector lights up I connect it in duet and it works is very strange -
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
Good morning the correct TEMPERATURE I had to put R 2150
Use R2200, that's the value of the sense resistor. Don't worry about temperature variation of a couple of degrees at room temperature - thermistors are not very accurate at low temperature. If you use a different R value, they will be inaccurate where it is important, around 200C.
Also, the M308 B value is wrong. I have asked you before, what thermistors or hot ends are you using?
Ian
-
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
E2 +E3+E4+E5+E6 it does not work when microswitch is configured
Please show how you are testing this.
Ian
-
@droftarts NTC 100K ohm B3950
220v 1400W 500*500 NTC 100K 3950
-
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
E2 +E3+E4+E5+E6 it does not work when microswitch is configured
Please show how you are testing this.
Ian
M119
-
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@droftarts NTC 100K ohm B3950
220v 1400W 500*500 NTC 100K 3950That is the bed. What about the hot ends?
For bed, change config.g to:
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp
Ian
-
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
M119
M119 does not show filament sensor status, only endstop status for axes (X, Y, Z).
Send
M591 D#
where # is the extruder drive number, 0 to 3.Ian
-
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
M119
M119 does not show filament sensor status, only endstop status for axes (X, Y, Z).
Send
M591 D#
where # is the extruder drive number, 0 to 3.Ian
Yes exactly so I made the limit switch m119 and for the end of the line m 591 d is the distributor number
and the film works perfectly instead of the switch does not work now I have replaced it and put it on two WiFi switch Z2config (22).g -
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
M119
M119 does not show filament sensor status, only endstop status for axes (X, Y, Z).
Send
M591 D#
where # is the extruder drive number, 0 to 3.Ian
Yes exactly so I made the limit switch m119 and for the end of the line m 591 d is the distributor number
and the film works perfectly instead of the switch does not work now I have replaced it and put it on two WiFi switch Z2config (22).g -
@droftarts if it is possible for you we can see the problem of the loss of pace because the rest everything works
for other small problems I look at myself I do not want to take advantage of your kindness we see the biggest problem of the loss of the Step of X and Y -
; Endstops M574 X0 S1 P"!xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y1 S1 P"!ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z2 S1 P"!zstop+!e1stop" ;Filament Sensing M591 P2 C"e0stop" S0 D0 M591 P2 C"duex.e2stop" S1 D2 M591 P2 C"duex.e3stop" S1 D3 M591 P2 C"duex.e4stop" S1 D4
With this configuration, homez.g works? And the filament sensing works?
Ian
-
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
; Endstops M574 X0 S1 P"!xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y1 S1 P"!ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z2 S1 P"!zstop+!e1stop" ;Filament Sensing M591 P2 C"e0stop" S0 D0 M591 P2 C"duex.e2stop" S1 D2 M591 P2 C"duex.e3stop" S1 D3 M591 P2 C"duex.e4stop" S1 D4
With this configuration, homez.g works? And the filament sensing works? YES
Ian
-
M566 X1000.00 Y1000.00
M201 X2000.00 Y2000.00
I tried to make a print with this configuration without extruding the pitch I don't lose it but if I increase it I lose it
DM860H V3.3 act英文 (1).pdf 17HS19-2004S1.pdfI made the print at 100 mm and the displacement 130 mm
-
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@droftarts if it is possible for you we can see the problem of the loss of pace because the rest everything works
Okay, back to the original problem. DM860H driver is made by Leadshine. I expect you have a Chinese clone version. All documentation I have found, except for the one you posted, has a different timing specification for the DM860H drivers. eg:
http://www.jdsmotion.com/products1/dma860h.pdf
https://manuals.plus/microrostep/leadshine-microstep-dm860-user-s-manualI suggest trying the following timing:
M569 P7 S0 R1 T3:3:6:6 ; E4 X physical drive 7 goes forwards M569 P8 S1 R1 T3:3:6:6 ; E5 Y physical drive 8 goes forwards
Stated timing is minimum length. Timings can be longer than stated in documentation, but not shorter. This will not affect the speed you can achieve with the axis.
But note that even the pdf you linked says that signal level must be >3.5V.
Ian
-
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@droftarts if it is possible for you we can see the problem of the loss of pace because the rest everything works
Okay, back to the original problem. DM860H driver is made by Leadshine. I expect you have a Chinese clone version. All documentation I have found, except for the one you posted, has a different timing specification for the DM860H drivers. eg:
http://www.jdsmotion.com/products1/dma860h.pdf
https://manuals.plus/microrostep/leadshine-microstep-dm860-user-s-manualI suggest trying the following timing:
M569 P7 S0 R1 T3:3:6:6 ; E4 X physical drive 7 goes forwards M569 P8 S1 R1 T3:3:6:6 ; E5 Y physical drive 8 goes forwards
Stated timing is minimum length. Timings can be longer than stated in documentation, but not shorter. This will not affect the speed you can achieve with the axis.
But note that even the pdf you linked says that signal level must be >3.5V.
Ian
Ok so I apply this configuration and do a test test without instructions
-
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
3:3:6:6
EN+ EN- they are not connected because if I reconnect the motors remain disabled In fact I tried to see if the voltage changes but there is no change in voltage when it prints and when it stops
-
@droftarts
M566 X1000.00 Y1000.00
M201 X2000.00 Y2000.00
Listen I don't know how the accelerations are calculated because with this configuration indicated above I have no problem printing at 100 mm -
@droftarts test without extrusion is 100mm print and 130mm shift
M569 P7 S0 R1 T3:3:6:6
M569 P8 S1 R1 T3:3:6:6
M566 X1000.00 Y1000.00 No loss of pace
M201 X2000.00 Y2000.00 No loss of paceM569 P7 S0 R1 T3:3:6:6
M569 P8 S1 R1 T3:3:6:6
M566 X1200.00 Y1200.00 No loss of pace
M201 X2000.00 Y2000.00 No loss of paceM569 P7 S0 R1 T3:3:6:6
M569 P8 S1 R1 T3:3:6:6
M566 X1500.00 Y1500.00 so i have step loss
M201 X2000.00 Y2000.00 so i have step loss
What do you advise me to do? -
M566 is 'instantaneous speed change'. See gcode dictionary M566. If the axis is not moving, then you command movement, it will try to start moving at this speed. All machines will skip steps if you set this too high. Because you try to move the axis at high speed immediately. Usual setting for M566 is between 300 and 900. if you set it too high, it can limit acceleration, and will cause a lot of shake in your machine from violent starts. If your axis is heavy, it will have to be lower. Generally, it is better to set M566 low (eg 300) and set acceleration (M201) higher. This should reduce violent movement of the machine, but still give good speed.
M201 is acceleration. See gcode dictionary M201. Increase this for the axis to achieve high speed quicker. 2000 is quite low. Some machines can reach 20000.
M203 is maximum speed. See gcode dictionary M203. Even if you send a GCode command with a feed rate faster than this, the firmware will limit the speed to this setting.
For these three, it is dependent on the machine what can be set, and you will need to experiment to find the best values, for each axis (X, Y and Z). The usual procedure to tune these settings is to:
- Find a value for each that works, eg M566 X300, M201 X2000, M203 X5000
- Change one value, find where there is step loss, eg M201 X10000
- Halve the difference between the values, eg M201 X6000, then test
- If it works, halve the difference with the higher number, and test again, eg M201 X8000
- If it doesn't work, halve the difference with the lower number and test, eg M201 X4000
- Repeat using the highest value that works, and lowest value that does not work.
- When you find the highest value that works, eg M201 X5000, set to 80% of this value, eg M201 X4000. This gives you some flexibility.
This technique is called a 'binary search'. You can use it to tune all the settings, for each axis.
Ian