Release 3.01-RC10

Leblond

the cases are two at the origin to the problem of the blocking of the extrusures "correct me if I'm wrong !!", 1: when the trigger is wrong, that is too attached to the plate and does not extrude, by force of give and give yes the filament is compact and freezes, 2: filament dirty or low temperature, but the problem encountered by me is strange perhaps it has something to do with it
the motor voltage? it is set to 800 but, and in any case it should jump, make the usual "tac tac ..." noise which has not happened to me and which has caused a waste of time for me and for you, I was wondering if there was a way via SW to check if an engine actually runs or not, type ammeter?

chrishamm

@Leblond Yes, there is a way to detect motor stalls. See https://duet3d.dozuki.com/Wiki/Stall_detection_and_sensorless_homing#main

Leblond

@chrishamm ok thanks, I print it and I care about it

Leblond

Good morning and good May 1st
Well I have a problem that repeats itself every time I homing, then I thought the last problem had been the fault of the nozzle blocked by the filament, in part yes, it blocked because the extruder motor stops, now I understood the reason, the tests I did are all without filament in order not to damage the nozzle, I describe what I did:
1: I set the temperature to 180 in order to have the extrusion and retraction buttons active the drive buttons work very well and the motor responds
2: if I homing all the axes and retry the procedure n.1 the extruder no longer works
3: I did the single homing of the axes
4: homing x axis and retrying the extruder and it works
5: homing y axis and retrying the extruder and it works
6: z axis homing and try again the extruder does not work
I tried to load the fw one by one starting from 3.0 until the last beta and the problem persists,
7: I removed the sd and reformatted and loaded the fw but nothing happens
Any suggestions on this?
for @ dc42
m92
Steps / mm: X: 80.000, Y: 80.000, Z: 400.000, E: 424.000
M906
Motor current (mA) - X: 800, Y: 800, Z: 800, E: 800, idle factor 30%
M913
Motor current% of normal - X: 100, Y: 100, Z: 100, E: 0
m563 p0
Tool 0 - drives: 0; heaters (active / standby temps): 1 (180.0 / 0.0); xmap: X; ymap: Y; fans: 0; status: selected

Leblond

to restart the engine I have to reset with the command M999

dc42

@Leblond said in Release 3.01-RC10:

6: z axis homing and try again the extruder does not work

Please post your homez.g file.

Leblond

@dc42
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu Apr 23 2020 22:39:29 GMT+0200 (Ora legale dell’Europa centrale)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G90 ; absolute positioning
G1 X60 Y50 F6000 ; go to first probe point
G30 ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z10 F100 ; lift Z relative to current position
;G90 ; absolute positioning

Leblond

now I have mounted the fw 2.05 to see if even with this it does the same problem

dc42

Is the tool still selected when you have this problem? Send T by itself to report the current tool number.

Leblond

@dc42 ok I reassemble the FW and then I tell you

Leblond

@dc42 made reloaded FW 3.01-RC10
yes the tool is always active
1/5/2020, 14:51:33 T
Tool 0 is selected

Leblond

@dc42 I compress all the sd and send it to you?

Leblond

it still does not work

Leblond

the engine practically vibrates as if it were stalled

Leblond

@dc42 I confirm that with version 3 of the fw I have this problem, but with the version of FW 2.05 everything works great, so I will continue to use FW 2.05, until you can understand where the problem lies

Leblond

Hi everyone, have you discovered anything about my problem?

Leblond

good morning guys
I have found that by sending the axes home manually one at a time starting with x, y and z, the extruder works

Leblond

but as soon as a g28 is made it no longer works and the extruder stalls

Leblond

I also installed Release 3.01-RC12 ma niet

Leblond

for @dc42 no idea?