Posts made by airscapes

Replaced the stop switch and have not been able to reproduce the problem on demand as of yet.. Finished the current project without issues. Started the printer today and homed Y .. slowed half way to the switch but after that, could not reproduce it again. Will see what happens. I do not believe I have found root cause but will be a while until I use it again, so If you want to close this, that is fine, will just post any updates if the issue returns.
Thanks

@airscapes Spoke too soon,, still doing it.. stopping halfway to the switch as if it were tripped.. about out of ideas.. already ordered oem switches so change to NC not in the card and is not a problem on the other M2 with DUET2 board.. so must be something else going on..

I believe I have found root cause of this issue am and maybe another with pause not working correctly form the M226 usage. One of the Y stepper motor wires was pushed up out of the connector and not making good contact. Whit Y homed and motor locked, wiggling the wire caused the motor to stop and start. Once pushed into the connector shell and locked the issues seems to be corrected... hopefully!

@jay_s_uk I thought there were pull down resistors on the inputs to prevent this? I have no such issue with the Duet2 board, same printer. I will try moving the wiring around to see if I can get anything to change.

Makergear M2, duet3 mini was 3.5.1 updated to 3.5.2 no change
Homing of Y works so this is not a Macro issue.
Y like the rest of the axis are Mechanical NO end stop switches. If I move the bed near the end of travel like to Y240 or greater,max travel is Y254, then when I Home Y, the bed will run at the normal fast speed for about 75mm or so then sort of stop and drop to the low speed for the rest of the travel, if it makes to the switch. Sometimes it stop and the GUI read -2 which is what it would read once the switch is triggered, but the bed is still no where near the switch. If I click home again, it will proceed at fast speed, hit switch, back up and little and go slow like it should.
The failure come when a print finishes fine and parks the bed at Y254 for part removal and then I click print again.. Y does not always make it home proper and the job starts. Work around is to home manually and make sure Y ends up at the switch. I have ordered a new switch but being it is NO and nothing is touching it, not sure how the board it getting a signal.. I have reset the connection but have not redone the connector.. again NO so I do not understand how a bad connection would do this
The Duet2 has LEDs to tell you when the switch is close, but not the Duet3 mini. I thought I read about a plugin for the gui that would tell you the status of the end stops? If there is such a thing can you point me to it and how to install it? This might shed some light on what is happening if it works in real time.. Any ideas as to what to look for next would be most appreciated. The wiring for Y end stop is wired tied to the frame so nothing is moving or flexing
Thanks! Doug

Axis and end stop cold

;##########################################################################################
; Axis Limits
M208 X0 Y0 Z0 S1                            ; set axis minimum
M208 X210 Y255 Z215.00 S0 	                ; set axis maximum

;##########################################################################################
; Endstops
M574 X1 S1 P"!io0.in"                        ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io0.in
M574 Y1 S1 P"!io1.in"                        ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io1.in
M574 Z2 S1 P"!io2.in"                        ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io2.in

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Sun Nov 28 2021 16:12:33 GMT-0500 (Eastern Standard Time)
G91               ; relative positioning
;G1 H2 Z5 F6000    ; lift Z relative to current position
G1 H1 Y-250 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y5 F6000    ; go back a few mm
G1 H1 Y-250 F360  ; move slowly to Y axis endstop once more (second pass)
;G1 H2 Z-5 F6000   ; lower Z again
G90               ; absolute positioning

G91 				; relative positioning
G1 H1 Z215 F3600	; move quickly to z axis endstop and stop there (first pass)
G1 H2 Z-5 F3600  	;go back a few mm
G1 H1 Z215 F360 	; move slowly to X axis endstop once more (second pass)
G90					; absolute positioning

;Y
G91               ; relative positioning
G1 H1 Y-250 F3600	;move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y5 F3600 		; go back a few mm
G1 H1 Y-250 F360  	; move slowly to Y axis endstop once more (second pass)
G90               	; absolute positioning

;X
G91               ; relative positioning
G1 H1 X-215 F3600 ;move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F3600 	  ; go back a few mm
G1 H1 X-215 F360  ; move slowly to X axis endstop once more (second pass)
G90               ; absolute positioning

;G29 S2 ; unload any map
;G28    Home all  
;G1 F1000 X100 Y125 Z10 ; Center 10mm away 
;G30                    ; probe bed

@droftarts Thanks! There is also some weirdness with Y homing when loading a Hight map, so maybe the upgrade will take care of that as well.
Here are the 2 macros.. The pause and resume using the GUI works as expected and if I add the M226 at the start of the layer is is also working correctly for the most part.

; pause.g
; called when a print from SD card is paused
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Sun Nov 28 2021 16:12:33 GMT-0500 (Eastern Standard Time)
M83            ; relative extruder moves
G1 E-10 F3600  ; retract 10mm of filament
G91            ; relative positioning
G1 Z5 F360     ; lift Z by 5mm
G90            ; absolute positioning
G1 X0 Y250 F6000 ; go to X=0 Y=250

Resume

; resume.g
; called before a print from SD card is resumed
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Sun Nov 28 2021 16:12:33 GMT-0500 (Eastern Standard Time)
G1 R1 X0 Y0 Z5 F6000 ; go to 5mm above position of the last print move
G1 R1 X0 Y0 Z0       ; go back to the last print move
M83                  ; relative extruder moves
G1 E10 F3600         ; extrude 10mm of filament

Hi, trying to put an M226 within my Gcode to stop a print to insert a washer. This works hit or miss. If I place it at the start of a layer, it will work. If I take too long to put the washer in, once resume is hit, it will move back, sit there and present an error that it took too long. When I tried to add this in a different area (before infill) it will return to the stopping spot
and home z and just be unresponsive. I did a search and have seen post about similar behavior in older FW versions but nothing resent.

I would like this pause in the infilll rather than the perimeter if it will work that way but I have a feeling you are going to tell me that is why it is not working
; infill
G1 X104.847 Y60.348 F18000
;CUSTOM_GCODE
;PAUSE
M117 Insert washer
M226
;END PAUSE
G92 E0
G1 X105.014 Y60.515 E0.0193 F840

@EasyTarget That is what I have been doing and yes it works fine but one needs to baby sit the layer to stop. I will revisit this at a later time when I have more time to experiment. I did try the M226 but the other code must have messed things up as it did not work as expected.. think I probably need to use M226 with some way to wait x number of second before doing the code to resume.. Clicking the button to resume after M226 does not work as it did in Octoprint years ago. If I remember from what I had read and tired to understand.. M25 and M226 do the same thing but one is for data coming from the SD card gcode and the other the Gui?? Anyway, thanks everyone for the ideas and insight into your own experiences!
Also I found that coating the top of the washer with glue stick and heating it as was suggested worked best. I was using TPU so probably the easiest to get to stick...

Sorry if this is not the proper place to put this. I am still using antient S3D (the devil I know). I have the need to stop a print at layer 11 to insert a fender washer and goggle is not helping me. I have found the code to insert from years ago which worked with antique Marlin but I can not find what I need for the current Duet firmware.
I am fine inserting it directly into the gcode at the start of the layer just need the proper code of a link to the "How To" document I have yet to find. Yes most of the current slicers have this option .. not looking to move to a new slicer yet.
Gee.. just had a novel idea.. just paste in the code from the pause button script.. testing now.. NOPE..

@chrishamm Yes, as I said in previous post, the current 64bit OS was dog slow on this old pi, so reinstalled an older 32bit version and all works as it does on windows.

@droftarts I get the same message as with windows browser.. unfortunately this 64bit version of the OS is unusable for browsing. trying to reload with 32bit to see if that make it usable. May need to just install current octoprint since that is typically stripped down.

Update: legacy 32bit pi OS is functional enough for my purpose and both Duet 2 and Duet 3 work. Sorry for waste of time Should know better to update all things involved before looking for bugs in any one thing.

@droftarts The new Pi OS install works. So must be something new or removed from the Http server that makes it incompatible with that old OS. With the full blown OS on the old Pi3b+ it is annoyingly slow but once booted and connected it works.

@droftarts said in DWC 3.5.1 Does NOT Connect with Pi3b+ chromium:

@airscapes said in DWC 3.5.1 Does NOT Connect with Pi3b+ chromium:

@droftarts OK thanks! It shows the correct version 3.5.1.

Okay, that’s odd. It feels like something has got stuck on the Raspberry pi, whether cookie or downloaded content, and is trying to load an old version of DWC. I think @chrishamm may need to help you on this one.

Does everything work correctly on Windows 11?

Ian

Don't have win 11.. well wife does so I can check.
I just reloaded the zip file, no change..
I went into the developers console on the pi browser and this is what it shows for the blank page it loads

Win 11 works but console shows this error

@droftarts OK thanks! It shows the correct version 3.5.1.
I will get back to this later today.

@droftarts I assume that since that is the DWC directory I have to remove the sd card from the board and mount it on a windows machine to remove the content of the WWW dir and replace it ??

@droftarts Ok cool. I will grab that file and see what happens!

@droftarts I have done that a dozen times. I will use a different sd card and reload a current pi OS without octoprint to see if that corrects the issue. However, when the duet 2 has worked perfectly at 3.4.6 you have to ask yourself how it the browser..
So just now booted both machines and connected to both from windows 10 using chrome.
I went to developer tools (no idea what any of this stuff means but error are bad in my book)
So in console I refreshed each page
This is 3.4.6

If I do the same on 3.51 duet 3 mini I get this

Now if I refresh again just the single error.. Yes cable is good, been replaced and verified with cable tester.Have also used different ports on the swithch. should have gone with 3.4.6.. one month old firmware is always a crap shoot no matter who the manufacture is..

It is not the Pi it is the Firmware or board. I just booted up the Duet 3 and could not connect with pi or windows. Power cycled again and this time windows would connect but still no pi.
Can I install 3.4.6 without wiping out my config? Do not feel like trouble shooting this as 3.4.6 works fine on the Duet 2.

I just finished all the updates to my M2 with Duet 3 mini and attempted to use it by connecting from Chromium on my old Pi3b+. I have updated chromium to 72.0.3626.121-0+rpt4 ... thinking that was the issue but no change. I get a blank screen when it connects. It looks as if it is connected but displays nothing. I can connect fine from a windows 10 with chrome or Opera. I also have an M2 with a Duet 2 and DWC 3.4.6 that works just fine on the Pi3b+. The os is old on the pi, it is an old Octoprint image that has not been updated. I am guessing there is something not installed on the pi that the new version of DWC needs to function? Both boards are Ethernet. I would like this to work since the pi is local to the machines and what I use to load/unload and prep the printers.

Output or m122, have a job running so not sure if that impacts this output.
5/25/2024, 1:01:43 PM M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.1 (2024-04-19 14:41:25) running on Duet 3 Mini5plus Ethernet (standalone mode)
Board ID: JLUSU-MT8LU-F65J0-409NU-M503Z-ZMRV2
Used output buffers: 3 of 40 (32 max)
=== RTOS ===
Static ram: 103232
Dynamic ram: 116020 of which 12 recycled
Never used RAM 19104, free system stack 138 words
Tasks: NETWORK(1,ready,23.8%,165) ETHERNET(5,nWait 7,0.2%,563) HEAT(3,nWait 1,0.0%,326) Move(4,nWait 6,0.1%,268) CanReceiv(6,nWait 1,0.0%,940) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,334) TMC(4,nWait 6,0.8%,68) MAIN(1,running,74.2%,665) IDLE(0,ready,0.0%,30) AIN(4,delaying,0.8%,260), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:38:09 ago, cause: reset button
Last software reset at 2024-05-16 16:41, reason: User, Gcodes spinning, available RAM 19352, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 2289538, completed 2289538, timed out 0, errs 0
MCU temperature: min 27.1, current 37.6, max 39.6
Supply voltage: min 23.8, current 23.9, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/108/84, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min 0, read errors 0, write errors 1, ifcnt 31, reads 54917, writes 17, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 31, reads 54916, writes 17, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 33, reads 54914, writes 19, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min 0, read errors 0, write errors 1, ifcnt 33, reads 54918, writes 15, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 21, reads 54923, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2024-05-25 13:01:42
Cache data hit count 3930349869
Slowest loop: 64.30ms; fastest: 0.14ms
=== Storage ===
Free file entries: 19
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 4.9ms, write time 1.9ms, max retries 0
=== Move ===
DMs created 83, segments created 8, maxWait 908579ms, bed compensation in use: mesh, height map offset -0.043, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 1.00
next step interrupt due in 209 ticks, enabled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 86, completed 79, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 27], CDDA state 3
=== DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.3
=== GCodes ===
Movement locks held by null, null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 3
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 3, axes/extruders owned 0x0000807
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 20603, received 0, lost 0, errs 10854939, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 26 (min 26), ts 11447/0/0
Tx timeouts 0,0,11446,0,0,9155 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 50.82ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
= Ethernet =
Interface state: active
Error counts: 0 0 0 0 0 0
Socket states: 5 2 2 2 2 2 0 0

Thanks in advance

@deckingman Thanks so much for the highly detailed explanations! Yes, I assumed making the loop/slack just right so the X carriage can move from end to end without the filament binding or getting caught on something may be the tricky part. Will come back to this thread once I get to this portion of the project! This really does not look as difficult as I had thought.
Thanks again!