@jay_s_uk

Thank you.

I've also just noticed something in my config.g that I thick, with looking in the dictionary ,is causing conflict. In M950 shouldn't my bed heater be H0 (H zero), rather than T0 (T zero), and my nozzle be T0 (T zero) instead of T1?

; Configuration file for Duet 3 MB 6HC (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Mon Sep 19 2022 16:04:20 GMT+0100 (British Summer Time)

; General preferences
M575 P1 S1 B57600                                  ; enable support for PanelDue
G90                                                ; send absolute coordinates...
M83                                                ; ...but relative extruder moves
M550 P"Duet 3"                                     ; set printer name
M669 K1                                            ; select CoreXY mode

; Network
M552 P

; Bed Leadscrew Positions
M671 X5:278 Y146:146 P2.0						; middle left, middle right

G4 S1												;wait for expansion boards to start

; Drives
M569 P0.0 S0                                       ; physical drive 0.0 goes backwards
M569 P0.1 S0                                       ; physical drive 0.1 goes backwards
M569 P0.2 S1                                       ; physical drive 0.2 goes forwards
M569 P0.3 S1
M569 P121.0 S0                                       ; physical drive 0.3 goes forwards
M584 X0.0 Y0.1 Z0.2:0.3 E121.0                           ; set drive mapping
M350 X16 Y16 Z16 E16 I1                            ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E333.40                  ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00                ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00            ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00                ; set accelerations (mm/s^2)
M906 X900 Y900 Z900 E800 I30                       ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                            ; Set idle timeout

; Axis Limits
M208 X-2 Y-8 Z0 S1                                 ; set axis minima
M208 X330 Y330 Z400 S0                             ; set axis maxima

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


; Z-Probe
M574 Z1 Z1 S2									   ; set endstops controlled be probe
M558 P8 C"^!121.io0.in" H5 F120 T6000                 ; set Z probe type to switch and the dive height + speeds
G31 P500 X-46 Y-19 Z2.45                            ; set Z probe trigger value, offset and trigger height
M557 X19:244 Y-2:304 P9                           ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138       ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                                 ; create bed heater output on out0 and map it to sensor 0
M307 H0 R0.187 K0.192:0.000 D1.89 E1.35 S1.00 B0   ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                            ; map heated bed to heater 0
M143 H0 S120                                       ; set temperature limit for heater 0 to 120C
M308 S1 P"121.temp0" Y"thermistor" T100000 B4138       ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"121.out0" T1                                 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 R2.498 K0.275:0.349 D6.79 E1.35 S1.00 B0 V24.0  ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280                                       ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"121.out1" Q500                               ; create fan 0 on pin out4 and set its frequency
M106 P0 C"Print Cooler" S0 H-1                     ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"121.out2" Q500                               ; create fan 1 on pin out5 and set its frequency
M106 P1 C"Extruder Cooling" S1 H1 T45              ; set fan 1 name and value. Thermostatic control is turned on

; Tools
M563 P0 S"Hemera" D0 H1 F0                         ; define tool 0
G10 P0 X0 Y0 Z0                                    ; set tool 0 axis offsets
G10 P0 R0 S0                                       ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined
; Emergency Stop
M950 J1 C"io4.in"
M851 P1 T0 S0 R0


; Miscellaneous
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

T0

M501

So far so good with using the ethernet, and without fully commissioning I ran a G32 once with no problems, no running a second scan for unknown reasons and no network error.
Without further testing I can't say if this was linked to the previous board, found to have an sd card issue or not.

Sorry "I thick" , * I think.

@norder

Thank you for your detailed guidance. I've tinkered with your example code, but not had a good chance to test it (I've got a lot on at the minuet).
I have had to omit the G92 Z0 in the homez as this resets the the settings previously entered for the trigger height in config.g.
I appreciate you have different z probes, and what you've sent above is an example. Thank you, It does help a lot.

I'll try and get time to test/tinker/play tomorrow, but it may be at the weekend until I get good chance to do so.

Dizzwold.

@Dizzwold

Yep, a clone Toolboard and clone Hemera.

I'm disabled, and on UK benefits due to health, so after purchasing the original and authentic Duet3 6HC, I couldn't afford the authentic Toolboard or Hemera, so please don't hold that against me. I will over time manage to afford these as original products.

@mandragora @Norder @jay_s_uk @deckingman ,

Thank you guy's, these are all very informative and valued information. This give me a lot to consider, and decide upon which way to go with this.

I've added a photo below. Sorry, I should have done this in first post so you all had a better understanding.

@Norder I already have a second floor/partition, but this directly above the "built-in" soundproof chamber. I was planning on using this as my filament storage. When I say built-in, it's breeze blocks and plaster. I've already had to strap one side with an addition joist in the loft to take the extra weight of the TecSound soundproofing and soundproof plasterboard as this was unsupported and above a stair case (it did have small notched joist, but not enough for the addition weight).

I'll have to take some temperature reading in the partition above. I suppose I could have it in an enclosure (in the above partition), and have a fan and duct in the timber above the door if needed. Then run cables to the paneldue, that will hopefully sit to the right of the door on the cable trunking.

Thank you again guy's for your time and advice.

@droftarts

Hi Ian,

Thank you again for your help and input.

I figured the above out in the end (or I hope I have).

Here is my example from the terminal. Maybe this will help others.

Mrxxxx's-imac:~ $ bossac -e -w -v -b -R -p /dev/tty.usbmodemFD131 /Users/Mrxxxx/Downloads/PanelDueFirmware-logo-3.4.1-v3-7.0.bin 
Erase flash

Done in 1.302 seconds
Write 218036 bytes to flash (426 pages)
[==============================] 100% (426/426 pages)
Done in 7.088 seconds
Verify 218036 bytes of flash
[==============================] 100% (426/426 pages)
Verify successful
Done in 5.581 seconds
Set boot flash true
Mrxxxx-imac:~ $ 

Thank you for your help.

One happy smily bunny.

@norder

Thank you again for your help, I'm very grateful.

I'll have a look at the home all and homez files.

@norder said in NPN Inductive Z Probe:

This is not necessary because the G29 command that does the MeshBedLeveling has already calculated this offset.

I'd been advised in a previous thread that this wasn't calculated and had to allow for this myself, but was also told that the probe would just report "Unreachable", and continue.

I'll go and look at the files and see what I can do.

@jay_s_uk

Seriously, a big Thank you for your help @jay_s_uk .

I'm really grateful for your time and guidance.

Hi All,

So it looks like I'm swaying toward the Duet 3 Mini 5 as few have commented on. This way I can also upgrade ‘if and when’ needed.

It looks like I'll have to wait a few weeks before any more Duet 3 Mini 5's are ready, No Pressure David. LOL

I am most grateful for everyone's input and advice.

No doubt I'll be back again with yet more questions, but for now I think I have a bit of reading to do, to familiarise myself better with the Duet system.

Also any more comments and / or suggestions are very welcome.

Thank you,

Dizzwold.

@jay_s_uk @Phaedrux

Hi Guys,

I had just written a reply stating that I still hadn't quite figured it out, but I think I've kind-of grasp both your ideas, although they need tidying up they both work;

Bed.g

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Mon Sep 19 2022 16:04:20 GMT+0100 (British Summer Time)
;M561 ; clear any bed transform
;G29  ; probe the bed and enable compensation
M671  X5:278 Y146:146 P2.0
G28			; home
G30 P0 X5 Y146 Z-9999				; probe front left
G30 P1 X278 Y146 Z-9999	S2		; probe front right
G1  X0 Y0 F12000
;G28
M671 X5:278:278:5 Y5:5:302:302 P0.5
G28
G30 P0 X5 Y5 Z-9999				; probe front left
G30 P1 X278 Y5 Z-9999			; probe front right
G30 P2 X278 Y302 Z-9999			; probe rear right
G30 P3 X5 Y302 Z-9999 S4  		 ;probe rear left
G1  X0 Y0 F12000

Config.g

; Configuration file for Duet 3 MB 6HC (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Mon Sep 19 2022 16:04:20 GMT+0100 (British Summer Time)

; General preferences
M575 P1 S1 B57600                                  ; enable support for PanelDue
G90                                                ; send absolute coordinates...
M83                                                ; ...but relative extruder moves
M550 P"Duet 3"                                     ; set printer name
M669 K1                                            ; select CoreXY mode

; Network
M552 Pxxx.xxx.xxx.xxx

; Bed Leadscrew Positions
M671 X5:278 Y146:146 P2.0						; middle left, middle right
M671 X5:278:278:5 Y5:5:302:302 P0.5

G4 S1												;wait for expansion boards to start

; Drives
M569 P0.0 S0                                       ; physical drive 0.0 goes backwards
M569 P0.1 S0                                       ; physical drive 0.1 goes backwards
M569 P0.2 S1                                       ; physical drive 0.2 goes forwards
M569 P0.3 S1
M569 P121.0 S0                                       ; physical drive 0.3 goes forwards
M584 X0.0 Y0.1 Z0.2:0.3 E121.0                           ; set drive mapping
M350 X16 Y16 Z16 E16 I1                            ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E333.40                  ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00                ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00            ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00                ; set accelerations (mm/s^2)
M906 X900 Y900 Z900 E800 I30                       ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                            ; Set idle timeout

; Axis Limits
M208 X-2 Y-8 Z0 S1                                 ; set axis minima
M208 X330 Y330 Z400 S0                             ; set axis maxima

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


; Z-Probe
M574 Z1 Z1 S2									   ; set endstops controlled be probe
M558 P8 C"^!121.io0.in" H5 F120 T6000                 ; set Z probe type to switch and the dive height + speeds
G31 P500 X-46 Y-19 Z2.45                            ; set Z probe trigger value, offset and trigger height
M557 X19:244 Y-2:304 P9                           ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138       ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                                 ; create bed heater output on out0 and map it to sensor 0
M307 H0 R0.187 K0.192:0.000 D1.89 E1.35 S1.00 B0   ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                            ; map heated bed to heater 0
M143 H0 S120                                       ; set temperature limit for heater 0 to 120C
M308 S1 P"121.temp0" Y"thermistor" T100000 B4138       ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"121.out0" T1                                 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 R2.498 K0.275:0.349 D6.79 E1.35 S1.00 B0 V24.0  ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280                                       ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"121.out1" Q500                               ; create fan 0 on pin out4 and set its frequency
M106 P0 C"Print Cooler" S0 H-1                     ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"121.out2" Q500                               ; create fan 1 on pin out5 and set its frequency
M106 P1 C"Extruder Cooling" S1 H1 T45              ; set fan 1 name and value. Thermostatic control is turned on

; Tools
M563 P0 S"Hemera" D0 H1 F0                         ; define tool 0
G10 P0 X0 Y0 Z0                                    ; set tool 0 axis offsets
G10 P0 R0 S0                                       ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined
; Emergency Stop
M950 J1 C"io4.in"
M851 P1 T0 S0 R0


; Miscellaneous
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

T0

M501

*Nb, I've omited M98 P"Bed_Adjusting_Screws.g" from bed.g.

Bed Adjusting Screw Macro

G28
M671  X5:278:278:5 Y5:5:302:302 P0.5
G30  P0 X5 Y5 Z-9999				; probe front left
G30  P1 X278 Y5 Z-9999			; probe front right
G30  P2 X278 Y302 Z-9999			; probe rear right
G30  P3 X5 Y302 Z-9999 S4  		 ;probe rear left
G1   X0 Y0 F12000

So it looks like I've learnt more than I even expected today.

Now I'll try the bed pid again...

Thank you both again for your help, I'm really grateful. You have the patience of saint's.

@jay_s_uk

The thought I had was to use 6mm deep magnet and leave 2mm on top, but with your failure it maybe best just to go with the large PEI sheet.

As @deckingman has previously commented and written-up on, and currently uses, you can always use a glass plate on top.

@T3P3Tony @jay_s_uk

Hi Guys,

Thank you for that.

Ah, okay, so I'm taking the information for the sensor from the S2 part of the config.g rather than the actual board input connection "Temp1".
Edit.
Which I beleieve means changing;
M118 S{"Message to Show: " ^ sensors.analog[1].lastReading ^ " C"} L1
to
M118 S{"Temp 2: " ^ sensors.analog[2].lastReading ^ " C"} L1
Thank you again for your help and advice.

Dizzwold.

@jay_s_uk

Okay, thank you.

Hmm, It's working but seems to be reading the wrong sensor. Temp1, which is what it is reading and documenting, is this T1 in my config.g?
It's basically reading the nozzle temp in the log at around 203˚C. I have the sensor I want to read in-between the fan and the heatsink on my Matrix extruder, "(he chamber heater below). In the graph it shows as around 40 ish ˚C ?

I have the following in my config.g on my 6HC board;

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138       ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                                 ; create bed heater output on out0 and map it to sensor 0
M307 H0 R0.187 K0.192:0.000 D1.89 E1.35 S1.00 B0   ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                            ; map heated bed to heater 0
M143 H0 S120                                       ; set temperature limit for heater 0 to 120C
M308 S1 P"121.temp0" Y"thermistor" T100000 B4138       ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"121.out0" T1                                 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 R2.498 K0.275:0.349 D6.79 E1.35 S1.00 B0 V24.0  ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280                                       ; set temperature limit for heater 1 to 280C

; Sensors
M308 S2 P"temp1" Y"thermistor" A"Chamber Temp"T100000 B4138

The very bottom "sensor" temp1 chamber heater is what I'd like to read.

But hey, I'm printing again and with my cast toolplate with pei sheet and mains heater. Hip-Hip-Hooray
It is printing so sweet.
It's not fully trammed yet, as I can't afford the new framework yet to enable doing so, but it's the best I can do for now.

Dizzwold

@T3P3Tony @jay_s_uk

Hi Guys,

Thank you for your direction I'll give them a try.

I'd already promised previously to look into the BtnCMD, but I really just haven't had the time. This is actually going to be my first print with the Cast Toolplate I've been on about for the last 2 if not 3 years.

Daemon.g;
I know very little about this, but with a quick goggle I understand it's to do with running a clock from the MCU in the background.
So this has to be called "daemon.g in the /sys directory?
Can you have more than one daemon.g in the /sys directory as I've seen it mentioned before with something else I read, and would you just number them?
daemon1.g
daemon2.g
etc

I don't even know if your need more than one to be fair, just asking?

@stef @T3P3Tony @Adamfilip @engikeneer @jay_s_uk @whopping-pochard

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.6 (2023-07-21 14:11:38) running on Duet 3 MB6HC v1.01 (standalone mode)
Board ID: 0JD2M-999AL-D25SW-6J9D0-3SD6M-9PY70
Used output buffers: 1 of 40 (20 max)

Hi Guys,

I appreciate this is an old thread and I'd like to do something similar, but not sure I fully understand it.

What I would like to do is take temperature readings every 20 seconds (or so), from a thermistor on (temp1), for the duration of a print and save them to a log/file or something like the heightmap.csv to look over at a later date. I only really need the temperatures.

I've tried putting both the suggested lines above in Config.g but all that seamed to do when I clicked save was immediately creat the file in /sys then start then stop a log.

Can I ask for your advice of what should actually go where or if there's another method to use?

Dizzwold.

Hi Guys,

I'm relevantly new to the Duet 3 boards (a year or 2), and have a friend looking into purchasing a Laser Engraver mostly for etching images on wood.
He's had a bit of a bad experience with trying to purchase an American or Canadian unit, so it crossed my mind that between myself and my friend, we could build one use a duet board.

I've had a little look around on the forum regarding laser engraving with the Duet series of boards, but there doesn't seem to be a great deal of people on the forum regarding this.

Would a Duet be a good choice of board for controlling a laser engraver?

Hi Guys,

This is following on from the end of my thread "Cast Toolplate Bed Progress ?", the last 8 posts within.
https://forum.duet3d.com/topic/34461/cast-toolplate-bed-progress/34?_=1704187570604

I have a Duet 6HC with a NC Emergency Stop Mushroom type button switch. When I press the emergency stop button, it stops everything as is should, but when I disengage the switch I have to manually click the RESET MACHINE radio button on DWC on my computer screen.

I've tried various methods and combinations using the triggers, but nothing eliminates having to physically click the radio button on my computer screen.
The triggers and the switch have been tested and all function correctly.

I now believe it's something in the actual program in C++;
@Dizzwold said in Cast Toolplate Bed Progress ?:

https://github.com/Duet3D/RepRapFirmware/blob/3.4-dev/src/GCodes/GCodeInput.cpp
src/GCodes/GCodeInput.cpp
From line 144-219 is regarding the M112 command and how it is reset. I think?
Lines 188, 189, 205, 206 prevent a perpetual reset?

@Dizzwold said in Cast Toolplate Bed Progress ?:

RepRapFirmware/src/GCodes/GCodes.cpp

Lines 866-872

Dizzwold.

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.6 (2023-07-21 14:11:38) running on Duet 3 MB6HC v1.01 (standalone mode)
Board ID: 0JD2M-999AL-D25SW-6J9D0-3SD6M-9PY70
Used output buffers: 3 of 40 (13 max)
=== RTOS ===
Static ram: 153252
Dynamic ram: 97472 of which 44 recycled
Never used RAM 99904, free system stack 194 words
Tasks: NETWORK(ready,31.7%,165) ETHERNET(notifyWait,0.0%,567) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,798) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,349) TMC(notifyWait,7.5%,90) MAIN(running,60.5%,925) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:02:32 ago, cause: power up
Last software reset at 2024-01-11 12:27, reason: User, GCodes spinning, available RAM 99904, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 127
MCU temperature: min 23.6, current 35.7, max 35.9
Supply voltage: min 24.1, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 8, reads 2389, writes 14 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 2389, writes 14 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 2389, writes 14 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 2390, writes 14 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 2390, writes 14 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 2393, writes 11 timeouts 0
Date/time: 2024-01-14 09:58:45
Slowest loop: 6.57ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
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
Code queue is empty
=== CAN ===
Messages queued 1391, received 3058, lost 0, boc 0
Longest wait 3ms for reply type 6053, peak Tx sync delay 177, free buffers 50 (min 49), ts 765/764/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 6.55ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
State: active
Error counts: 0 0 0 0 0 0
Socket states: 2 2 2 2 2 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0```

Okay, posted as follows;
DWC on Computer Screen RESET MACHiNE from Emergency Stop
https://forum.duet3d.com/topic/34675/dwc-on-computer-screen-reset-machine-from-emergency-stop

@deckingman
Going back to the toolplate bed, I'm going to use the following connector mounted to the bed frame. The idea being that I can disconnect the cables so I can remove the bed (the printer will be in a cupboard, tight on space, so less weight with moving the frame in and out).

Being that this is now a Mains 240Vac bed heater, and I have spare pins on the connector, I'm thinking on the grounds of safety and running some kind of signal loop (5/12v on a relay), so when the connector is disconnected, the break in the (5/12v) signal loop will disconnect the mains with the relay (if I've not already done so), so there is no loose Live Mains cable floating around.
At the moment I have a1 SSR controlling the 240Vac mains bed switched directly by the 24v O/P from the Duet 6HC.
So I'm looking for ideas.
Should I use a mechanical relay in series with the mains from the SSR, or is there a good chance this will weld closed?
Use another SSR, again in series with the switched mains;

Dizzwold.

@Dizzwold

RepRapFirmware/src/GCodes/GCodes.cpp

Lines 866-872

@dc42 @deckingman @Phaedrux @chrishamm @fcwilt

Hi guys,

I think with looking around I might be needing to change something in the following which is C++. I know a little C++ (and I mean a little), but I'm certain this is part of of why I need to physically press a Reset Machine radio button ;
https://github.com/Duet3D/RepRapFirmware/blob/3.4-dev/src/GCodes/GCodeInput.cpp
src/GCodes/GCodeInput.cpp

From line 144-219 is regarding the M112 command and how it is reset. I think?
Lines 188, 189, 205, 206 prevent a perpetual reset?

I've more code (.cpp files), to read, but I think I'm on the right track. I've got some thing to do this afternoon, but will come back.

Dizzwold.

@deckingman @fcwilt

Hi Guys,

Again thank you for your support and input.

@fcwilt
Sorry you misunderstand me.
I'm not trying to send any line of code. I'm just stating what clicking the on screen "Reset Machine" Button possibly does (on my computer screen). I'm no programmer but I believe DWC is Javascript and it would probably be something like onclick to enable a function for M999.

@deckingman
I've tried your suggestion with the following, but refreshing the browser makes no difference. If anything it makes it longer to reset the machine as your also reconnecting before resetting.
Also during the time after pressing the Emergency Stop Button, while the computer screen states and requests Reset Machine, the paneldue is Halted. It's either press Stop on the paneldue or click Reset Machine on the computer screen.
I think it's a case of getting into the software code for the GUI, to be able to enable this as a use, unless this plugin might help as previously mentioned by @Phaedrux in another post;
https://github.com/MintyTrebor/BtnCmd

 ; Emergency Stop
M950 J2 C"io3.in"
M581 P2 T2 S1 R0
M581 P2 T3 S0 R0

;Trigger2.g Reset Emergency Stop Button
M112
M999

;Trigger3.g Z Axis Limt Switch
M98 P"config.g"

Then changed to;

 ; Emergency Stop
M950 J2 C"io3.in"
M581 P2 T0 S1 R0
M581 P2 T2 S0 R0

;Trigger2.g Reset Emergency Stop Button
M112
M999

Then changed to;

;Trigger2.g Reset Emergency Stop Button
M999

And then again with;

;Trigger2.g Reset Emergency Stop Button
M98 P"config.g"