G1 H1 in stop.g cause strange behavior

dc42

My guess is that your slicer start GCode contains a M18 or M84 command to turn off the motors.

danzaywer

No, I tryed a custom gcode to test a multimaterial module I'm developing:

T-1
G1 U250 F3600
G1 U0 F3600
G1 U250 F3600
G1 U0 F3600
G1 U250 F3600
G1 U0 F3600
G1 U250 F3600
G1 U0 F3600
G1 U250 F3600
G1 U0 F3600
[...]
G1 U250 F3600
G1 U0 F3600

just go from 0 to 250, no other instruction and no start gcode from slicer
and tfreeX.g

G1 X-10.7 F6000 
M291 P"tfree TOOL X" T3

danzaywer

@dc42
I changed stop .g as follow:

T-1
M400
G28 X Y 
G91            ; relative positioning
G1 H2 Z0.1 F360     ; lift Z by 10mm
G90            ; absolute positioning
G1 Y210  F1000 ;
G91            ; relative positioning

and put

G1 H1 X-200 F1000

in console and have no issue to start a new print-file.
Changed in:

T-1
M400
G28 X Y 
G91            ; relative positioning
G1 H2 Z0.1 F360     ; lift Z by 10mm
G90            ; absolute positioning
G1 Y210  F1000 ;
G91            ; relative positioning
G1 H1 X-200 F1000 ;

and again no able to start new gcode file.
Everything I put in the file after

G1 H1 X-200 F1000

is not processed, i tried with

M291 P"HELLO WORLD" T15

it will newer be displayed

dc42

Firmware version?

danzaywer

@dc42 Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.0 (2020-01-03b3),
I don't remember if I'm on beta1 or later

danzaywer

I think I have solved but I would like a technical explanation:
an

M400

must be placed just before

G1 H1 X-200 F1000

dc42

@danzaywer said in G1 H1 in stop.g cause strange behavior:

I think I have solved but I would like a technical explanation:
an
M400
must be placed just before
G1 H1 X-200 F1000 

The firmware already does the equivalent of M400 before a G1 H1 move anyway. However, I recall a problem in this area in firmware 3.0 that was fixed in the 3.01 beta series. So please can you try 3.01-RC2 and see if that works without that M400 command.

danzaywer

@dc42
Gladly but I got the error "M997 S0 operation has been cancelled"! I uploaded Duet2CombinedFirmware.bin
from DWC 2.0.7 and answered yes to the update question, what am I missing?

and M122 give me:

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.01-RC2 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-917DA-G4MSD-6JKD0-3S46K-KTVZB
Used output buffers: 3 of 24 (20 max)

Am I on 3.01 -RC2 or not?

however in the current situation if I remove the M400 I still have the problem

dc42

Yes, you appear to be running 3.01-RC2. Send M115 to confirm that.

danzaywer

@dc42

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.01-RC2 ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2020-02-18b1

The problem persist.