rehome.g not found

Marco Bona

@droftarts, I think they are correct, I usually use those parameters without problems, do they seem excessive to you?
Sorry, but start.g comes before those lines, always takes the first values it finds in gcode file?

@Phaedrux, exactly, start.g is automatically called up at the start of printing.

I explain the problem (setting M915 S3):

if I start a print during the execution of start.g, X and Y motors stall continuously (then I suspend print because it does not probe bed correctly)
-if I start "start.g" from the DWC console with M98 "start.g", machine works perfectly.
I think isn't related to the sensitivity of the stall detection otherwise I think I should have same problem in both cases.

Phaedrux

@Marco-Bona said in rehome.g not found:

if I start a print during the execution of start.g,

Again, this doesn't make sense. When you start a print, start.g will be executed. Why would you start a print while start.g is executing?

Marco Bona

@Phaedrux , They are 2 separate operations. I'm saying that if I start printing the machine behaves in one way while if I start only start.g with the print canceled the printer behaves in another way. I don't repeat start.g while the machine is paused. Clear?
I think it takes some value when starting the program which creates some errors.

droftarts

@Marco-Bona This is the start.g you posted earlier in the thread.

G4 S1 
M117 Preparing            ;write Preparing
G4 S1                     ;delay 1 seconds
M280 P0 S160                  ; Send PWM channel 0 the s160 (angle) command
M84 V;
; If the printer hasn't been homed, home it
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
  G28

M42 P6 S40
G21                       ;metric values
G90                       ;absolute positioning
M107                      ;start with the fan off
G1 X0 Y0 F10000            ;
G1 Z20 F1000               ;
M98 P"probe.g"            ;
T2 P0                     ;
G1 R2 X0 Y0 Z0 F5000      ; 
G32                       ;
G1 Z10 F800               ;
G1 X0 Y0 F8000            ;go to the center of bed
G30 X0 Y0 S-2             ;probe current position and ajust Z offset
G1 Z40 F1000              ;go to Z40
M584 P5
M98 P"homev.g"
M584 P3
G1 X-137 Y120 F8000      ;go to X-137 Y160
;M42 P6 S50
G4 S1

As you have a start.g, it runs first when a print is run. If you run start.g yourself (with M98 P"start.g") then start a print, it will run start.g again. So possibly running start.g once causes an issue, but twice fixes it. I can't see anything obvious, though start.g seems largely related to homing the V axis, and you haven't linked homev.g. Please post that too.

Ian

droftarts

@Marco-Bona Also, in config.g I noticed:

M350 X16 Y16 Z16 W16 16 V16 E32:32 I1 ; configure microstepping with interpolation

There needs to be a 'U' before the '16', eg:

M350 X16 Y16 Z16 W16 U16 V16 E32:32 I1                             ; configure microstepping with interpolation

Ian

Phaedrux

What happens if you step through the start.g manually command by command?

You say after a print is canceled. What do you have in pause.g cancel.g and stop.g?

What else do you have in your slicer start gcode?

Marco Bona

@droftarts said in rehome.g not found:

@Marco-Bona Also, in config.g I noticed:

M350 X16 Y16 Z16 W16 16 V16 E32:32 I1 ; configure microstepping with interpolation

There needs to be a 'U' before the '16', eg:
M350 X16 Y16 Z16 W16 U16 V16 E32:32 I1                             ; configure microstepping with interpolation
Ian

fantastic, correct immediately.

@Phaedrux , @droftarts, sorry but I can't be clear, I'm saying that stall warning occurs only and exclusively when a print is started, if I turn on the printer and execute M98 P "start.g", machine executes the command correctly, I can repeat command at infinity that will always work.
Instead, if I start any printout, stall warning continues to appear.
Again, I assume it is something that conflicts with Cura, but I don't understand what it could be.
If necessary I can post a video.
I am attaching the files you asked me, i am realizing that cancel.g is missing, is that a problem?
homev.g pause.g stop.g

Phaedrux

@Phaedrux said in rehome.g not found:

What else do you have in your slicer start gcode?

Can you post a sample gcode?

Marco Bona

@Phaedrux ,
White_minnow_rev1.gcode

Phaedrux

@droftarts said in rehome.g not found:

M84 V;

I think it has something to do with homing V and the high steps per mm.

M92 U37.67 V5245.9

What is the V axis?

The start.g turns off the V motor and then homes all axis if an axis isn't homed, so it runs G28. Then you call the probe. and then below again it calls homev with a M98 instead of a G28 V and then rehides the axis.

Then in your slicer end gcode you have M98 P"end.g". What is in end.g?

You don't have a cancel.g so when you cancel a print it's calling stop.g, or it should anyway.

Marco Bona

@Phaedrux, V axis is a small motor that raises the second tool when not in use.
It turns off the V motor because if it stays on it causes me disturbances during probing.
M98 P "homev.g" and G28 V should do the same thing.

end.g

Phaedrux

Minor point, but you could move the contents of stop.g into cancel.g, then move end.g into stop.g, and then change the slicer end gcode to M0 instead of M98 PEnd.g. Then all files would be fulfilling their original intentions.

In start.g you have G1 R2 X0 Y0 Z0 F5000 What does this do?

Can you send M98 P"Config.g" and post the results?
Can you send M584, M350, and M92 and M906 to see if the resulting settings are what you expect them to be?

Marco Bona

@Phaedrux, i try to move the files as you said.
G1 R2 X0 Y0 Z0 is used to translate the position of the probe.
Tomorrow I try to run M98 P "config.g" and let you have the results.

Phaedrux

I suspect that part of the problem may be in stall detection not working for motors on the expansion boards.

Marco Bona

@Phaedrux , you are right for the confusion of the files. If I remember correctly I had done end.g because I hadn't noticed that cancel.g was missing.
I'll arrange to fix

Marco Bona

@Phaedrux, even if the X and Y motors are on the main board?

Phaedrux

@Marco-Bona That's why I suspected a stall being detected on V or something and maybe related to the high steps per mm, but I'm not sure.

Marco Bona

@Phaedrux, here are results:

M98 P"config.g"
Warning: M307: Heater 3 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C

M584
Driver assignments: X0.0 Y0.1 Z0.2:0.3 U1.0 V1.1 W0.3 E0.4:0.5, 3 axes visible

M350
Microstepping - X:16(on), Y:16(on), Z:16(on), U:16(on), V:16(on), W:16(on), E:32(on):32(on)

M92
Steps/mm: X: 80.000, Y: 80.000, Z: 802.005, U: 37.670, V: 5245.900, W: 802.005, E: 806.000:806.000

M906
Motor current (mA) - X:2240, Y:2240, Z:2100, U:1800, V:1500, W:2100, E:560:560, idle factor 30%

would seem all correct

Phaedrux

With 3.2 beta now released you may want to try that out to see if the behaviour remains.

Marco Bona

@Phaedrux said in rehome.g not found:

With 3.2 beta now released you may want to try that out to see if the behaviour remains.

I tried to make a print. The strange behavior of stall remains, however, after fixing name of rehome.g the error occurs less frequently. Part of problem I think was caused by the lack of file. I tried to insert M204 P500 T1000 and M566 X600 Y600 in start.g and I fixed files you told me but nothing changed, motors stalled anyway during start.g execution.