When I recall correctly the initial bug was related to DWC, that is why am reporting this here again. On some occastions when pressing a button on the PanelDue the message related to this is displayed only, whereas the PanelDue shows only "busy"
This is pretty annoying when you sit in front of the printer and don't what the printer is waiting for. Especially when the computer is in the next room...
This is the ressurection of an older bug that was fixed.
When writing to a file the leading blanks and tabs are not written.
; =========================================================================================================
;
M28 "/sys/AutoloadStatus" ; open file for output
M950 J1 C"nil" ; free input 1 e0 filament sensor
if sensors.filamentMonitors[0].enabled = true ; if filament sensor is active
M591 D0 P2 C"e0stop" S1 ; filament runout sensor;
M29 ; close file
;
; =========================================================================================================
The output looks like this
M950 J1 C"nil"
if sensors.filamentMonitors[0].enabled = true
M591 D0 P2 C"e0stop" S1
The if statement is not executed properly. Any ideas?
Thanks, Wolfgang
With M470, M471 and now since fw 3.5 we have M472 for file operations. It would be nice to have something like
M473 P"test"
set var.file_status = {output}
which checks if the file "test" exists and assigns the variable file_status to the output (integer 0/1 or boolean true/false)
@chrishamm This error shows up more frequently with 3.60-b2
I noticed a strange thing. After a pause the extruders are not returning to the correct z-height. With T0 there seems to be a deviation of 0-0.2mm. With T1 the extruder is moving down after a each pause. Sometimes it then gets back to a gigher position.
Here is the logged user position when pausing and resuming
Time 2024-11-19T18:11:14 Job 0:/gcodes/CFFFP_TestPrint-both.gcode
Pause: x= 122.426 y= 97.718 u= 286.800 z= 0.200
Resume: x= 122.426 y= 97.718 u= 286.800 z= 0.200
Pause: x= 126.492 y= 118.153 u= 286.800 z= 0.560
Resume: x= 126.492 y= 118.153 u= 286.800 z= 0.560
Pause: x= 122.804 y= 98.097 u= 122.804 z= 1.160
Resume: x= 122.804 y= 98.097 u= 122.804 z= 1.160
Pause: x= 123.204 y= 117.709 u= 123.204 z= 1.160
Resume: x= 123.204 y= 117.709 u= 123.204 z= 1.160
Pause: x= 135.949 y= 117.709 u= 135.949 z= 1.160
Resume: x= 135.949 y= 117.709 u= 135.949 z= 1.160
Pause: x= 123.203 y= 99.036 u= 123.203 z= 0.882
Resume: x= 123.203 y= 99.036 u= 123.203 z= 0.882
Pause: x= 126.975 y= 98.497 u= 126.975 z= 0.586
Resume: x= 126.975 y= 98.497 u= 126.975 z= 0.586
Pause: x= 131.101 y= 98.496 u= 131.101 z= 1.280
During a print move.axes[2].machinePosition (which is z in my case) is permanently jumping, whereas the move.axes[2].userPosition stays constant during a print. Unlike in 3.4.6 the user[2]Position is not equal to the machine[2]Position. For the other axis both values are the same, ignoring round-offs.
For the purpose of this post I changed my pause.g to
set global.pausex=move.axes[0].userPosition
set global.pausey=move.axes[1].userPosition
set global.pausez=move.axes[2].userPosition
set global.pauseu=move.axes[3].userPosition
echo >>"0:/sys/0-printlog" "Pause: x= " ^{global.pausex}^ " y= " ^{global.pausey}^ " u= " ^{global.pauseu}^ " z= " ^{global.pausez}
G1 X200
M99
So just moves the x-axis out off the way of a test print.
And resume.g to
M98 P"00-Functions/CurrentSenseNormal" ; ensure the drivers current and sensitivity is set for normal routines
M17
G4 P100
;
;************************************
echo >>"0:/sys/0-printlog" "Resume: x= " ^{global.pausex}^ " y= " ^{global.pausey}^ " u= " ^{global.pauseu}^ " z= " ^{global.pausez}
G1 R1
@chrishamm Thanks Christian. Thursday I'll be at formnext, maybe we see each other.
@droftarts indent comments is working
@gloomyandy standalone, see screenshots below
@droftarts running in standalone mode
Today I updated one printer to RRF 3.6.0-beta2. In the object model browser the documentation cannot be found. I had that with beta 1 as. There exists a DuetAPI.xml.gz. Unpacking this file helped in an earlier version, but not here.
@dc42 Today I tried 3.6.0-beta1-2 on a Dual extruder where the extruders have a can board. So far, this works as well.
@dc42 Here is some feedback from my side. For about a week I tried 3.6.0-beta1-2 on a Duet3Mini5 where everything was connected directly to the board. Good news: WiFi and printer ran without error. Observations:
YAP connects, but no data is displayed in YAP. M115 does not return anything.
The old home sequence doesn't work without change
; =========================================================================================================
; home y axis
; =========================================================================================================
;
M400 ; wait for current moves to finish
G1 H2 Y0.5 F1000 ; energise motors to ensure they are not stalled
M400 ; wait for current moves to finish
G1 H1 Y5 F1000 ; move slowly away
G1 H1 Y-260 F1800 ; move quickly to x axis endstop and stop there (first pass)
G1 H2 Y5 F1000 ; go back a few mm
G1 H1 Y-10 F1800 ; move slowly to x axis endstop once more (second pass)
G28
Error: G1: Homing move abandoned because driver 3 is moving too slowly for stall detection
It had to be changed to
; =========================================================================================================
; home y axis
; =========================================================================================================
;
M400 ; wait for current moves to finish
G1 H2 Y0.5 F2000 ; energise motors to ensure they are not stalled
M400 ; wait for current moves to finish
G1 H1 Y5 F2000 ; move slowly away
G1 H1 Y-260 F1800 ; move quickly to x axis endstop and stop there (first pass)
G1 H2 Y5 F2000 ; go back a few mm
G1 H1 Y-10 F1800 ; move slowly to x axis endstop once more (second pass)
;