@phaedrux

My config file is a text file attachment on my original post.

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.1 (2022-06-01 21:09:01) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-9P63L-DJ3T0-6JKD0-3S46K-TU1R8
Used output buffers: 6 of 40 (22 max)
=== RTOS ===
Static ram: 151000
Dynamic ram: 96564 of which 288 recycled
Never used RAM 102820, free system stack 188 words
Tasks: NETWORK(ready,26.8%,209) ETHERNET(notifyWait,0.0%,168) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.8%,92) MAIN(running,65.3%,925) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:08:46 ago, cause: power up
Last software reset at 2022-08-30 16:15, reason: HardFault undefInstr, GCodes spinning, available RAM 102860, slot 1
Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00010000 ICSR 0x00400803 BFAR 0x00000000 SP 0x2041b508 Task MAIN Freestk 1672 ok
Stack: 00000000 2042c2f8 00000000 00000000 000001cd 00457c9b 0045c898 610f0000 20419a8c 2042bf54 00000000 00000001 00000000 00484687 2042bf54 00000000 00000000 004849cf fffbfff0 00484ba7 2042c2f8 20429f48 00000000 2041b5a4 a5a5a5a5 0045c897 ffffffff
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 151
MCU temperature: min 19.7, current 36.7, max 36.9
Supply voltage: min 24.2, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, 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 62152, writes 17 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 62152, writes 17 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 62152, writes 17 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 62159, writes 11 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 62159, writes 11 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 62159, writes 11 timeouts 0
Date/time: 2022-08-31 08:17:24
Slowest loop: 10.47ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 5.7ms, 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
=== 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 4794, received 18972, lost 0, boc 0
Longest wait 3ms for reply type 6026, peak Tx sync delay 6, free buffers 50 (min 49), ts 2633/2632/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 13.24ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0

M122 B21
Diagnostics for board 21:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.1 (2022-06-01 21:16:39)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2800, free system stack 88 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,113) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,3.0%,57) MAIN(running,91.9%,341) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:08:53 ago, cause: power up
Last software reset data not available
Driver 0: pos 0, 415.0 steps/mm,standstill, SG min 0, read errors 0, write errors 0, ifcnt 15, reads 4516, writes 15, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x72, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 0/6, peak Rx sync delay 211, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.7, current 24.7, max 24.7
MCU temperature: min 21.9C, current 39.1C, max 39.1C
Last sensors broadcast 0x00000002 found 1 148 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 8561, send timeouts 0, received 6947, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, other errors 0

M122 B22
Diagnostics for board 22:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.1 (2022-06-01 21:16:39)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2624, free system stack 88 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,101) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(delaying,3.0%,57) MAIN(running,91.9%,341) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:08:55 ago, cause: power up
Last software reset data not available
Driver 0: pos 0, 415.0 steps/mm,standstill, SG min 0, read errors 0, write errors 0, ifcnt 15, reads 5341, writes 15, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 1/6, peak Rx sync delay 210, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.0, current 24.1, max 24.1
MCU temperature: min 22.5C, current 37.7C, max 37.7C
Last sensors broadcast 0x00000004 found 1 38 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 10734, send timeouts 0, received 6983, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, other errors 0

@chrishamm can confirm this works.

sudo apt update
sudo apt full-upgrade
sudo rm /opt/dsf/conf/config.json
sudo systemctl reboot

@chrishamm new image with no updates works. M997 S2 F"unstable", M997 S2

@jay_s_uk Oops, I forgot to mention that. I edited my original post, but it's these in the 300C version:
https://www.sliceengineering.com/products/thermistor-high-temperature

I reorganized my macros into a couple folders have encountered some issues.

• In the web interface, I can no longer select all and download as zip. I really liked this feature because it was a quick way to make a local backup before I started messing around with code. I wish it worked with folders.

• On the Panel Due when I first boot up the machine I can see my folders represented with asterisks, which is great, but when I exit a folder, the macros persist on the initial screen. Closing and reopening the macro menu does not fix it, and navigating in and out of macros can cause illegible text artifacts to appear on the buttons.

I should note that I'm using a panel due 7i, with a duet 3 in SBC mode with a raspberry pi, running the 3.5 release candidate.

@dc42 Thanks! This version of the code works:

var fanSpeed = fans[1].requestedValue

while var.fanSpeed < 1 ; while less than full speed
	set var.fanSpeed = var.fanSpeed + 0.01 ; update variables
	if var.fanSpeed > 1 ; make sure variable never exceeds 1
		set var.fanSpeed = 1
	M106 P1 S{var.fanSpeed} ; set fan speed
	G4 S0.01 ; dc42 said to add this

echo "fan at full speed"

@jay_s_uk I tried commenting that out and still got this error:

Heater 1 fault: exceeded allowed temperature excursion: target 240.0°C actual 257.5°C

@jay_s_uk It shouldn't have changed, it was working great on 3.5.0 RC3. During the ordeal, I did attempt switching to stable and doing a downgrade according the documentation, which worked and DWC was connecting, but then when switched back to unstable, it started getting stuck at connecting... again. I want to also mention, that I have the printer beep at the end of the config.g file, and I hear it, so that means the code is at least running. It makes me think the issue is more on the web-interface side. I will try BOSSA and get back to you soon.

@dc42 @gloomyandy Thanks for your suggestions, that fixed the issue!

M950 F1 C"5.io1.out"                      ; create chamber fan 1
M106 P1 S0 H-1 C"Chamber Fan"             ; set fan 1 value, thermostatic control off

@deckingman OMG that's got to be it! I feel so stupid... I totally forgot that I changed from a 12V to 24V PSU... Thanks so much!

@dc42 Interesting. Any idea on an estimated completion date on the feature request? Or maybe a workaround I could do instead? I want the user to be able to have a way out of a very long while loop.

Thanks.

@droftarts I updated to 3.5.3 and tested the code but no change, I then added a M400 like this below, and it still did not run the last few lines of code, line 11 & 12.

M98 P"soundNotifyShort.g"   ; beep
M42 P17 S1  ; set closing direction
G4 S1   ; wait
while sensors.gpIn[15].value == 1   ; while not fully closed yet
    M42 P16 S1  ; turn on motor
    M98 P"promptUser.g" ; give user opportunity to cancel
    if global.userPrompt == 1
        break
    G4 S1
M400
M42 P16 S0  ; turn off motor
M98 P"soundAlert.g" ; beep
M291 "Top cover is at max closed" S2

This code runs every line

M98 P"soundNotifyShort.g"   ; beep
G4 S1   ; wait
var myCounter1 = 5
while iterations <= 5
    M98 P"promptUser.g" ; give user opportunity to cancel
    if global.userPrompt == 1
        break
    G4 S1
M98 P"soundAlert.g"    ; beep
M291 P"end of code" S2

This code skips the lines after the while loop

M98 P"soundNotifyShort.g"   ; beep
M42 P17 S1  ; set closing direction
G4 S1   ; wait
while sensors.gpIn[15].value == 1   ; while not fully closed yet
    M42 P16 S1  ; turn on motor
    M98 P"promptUser.g" ; give user opportunity to cancel
    if global.userPrompt == 1
        break
    G4 S1
M42 P16 S0  ; turn off motor
M98 P"soundAlert.g" ; beep
M291 "Top cover is at max closed" S2

@jay_s_uk SBC mode, 3.5.3-rc.1. I'm afraid to update because that was an ordeal last time that bricked some of my expansion boards updating in sbc mode.

I have a bunch of code to automatically open/close a retractable cover on my printer and I have subsets of code that run different beeps to indicate motion and M291's to prompt the user. What I'm noticing is that it's not always running all of my code. I can't tell if line 10 isn't running b/c the motor is stopped with relay logic, lines 11 and 12 are definitely not running.

Problematic code

M98 P"soundNotifyShort.g"	; beep
M42 P17 S1	; set motor direction to closing
G4 S0.25	; short wait to let relay flip
while sensors.gpIn[15].value == 1	; while not fully closed yet
	M42 P16 S1	; turn on motor
	G4 S4		; wait
	M98 P"promptUser.g"	; give user opportunity to cancel
	if global.userPrompt == 1
		break ; user canceled
M42 P16 S0 	; turn off motor
M98 P"soundAlert.g"	; beep - note this is apparently not running b/c I don't hear it beep
M291 P"Top cover is at max closed" S2 ; this doesn't run either b/c I don't see the message box in DWC

soundNotifyShort.g

M42 P20 S1
G4 S.37
M42 P20 S0

promptUser.g

; Working within the limitation of the firmware, for there to be a non-exiting default option you must have a Cancel button (J1) and a message box
; of S4 or above, so the options are redundant if you only want a yes or no value, which I do. So the logic is reversed, no response sets input = 0
; creating a new global variable, and setting it to a non-zero value. So IF the user responds, the variable will change to 0

set global.userPrompt = 3
M291 P"Continue?" S4 T3 J1 K{"Yes", "No"} F0
set global.userPrompt = input

; global.userPrompt legend
; 0 is Yes
; 1 is No
; 3 is No response

soundAlert.g

M42 P19 S1
G4 S2.2
M42 P19 S0

@T3P3Tony Yep, that's what I ended up doing. I spoke with Teknic support and expressed interested in the HLFB wire potentially signaling errors rather than enabled status and they filed my feature request. For now this is my solution: https://forum.duet3d.com/post/346434

@droftarts I don't think I want to enable the servos on startup because then if the servos were ever disabled with a M18 for instance, that would trigger a driver-error because the HLFB wire would switch.

Question about the M957 being used for testing, would it cause the printer to pause if sent during a print?

Thanks

@p8blr From what I've discovered, the duet firmware assumes the state of the error pin on startup is "not an error", but the best you can configure the teknic motors to do is treat the HLFB wire as "enabled & not in shutdown" or "disabled or maybe in shutdown", and because the servos aren't enabled on startup, the duet's assumption will always be wrong. Until this is configurable by Duet or Teknic, this can't work.

Here's my workaround: I added another expansion board!!! I wired the servos with the "sinking" output as Teknic recommends.

in config.g

M950 J16 C"^121.io0.in"                   ; assign input for X HLFB+
M950 J17 C"^6.io0.in"                     ; assign input for Y1 HLFB+
M950 J18 C"^6.io1.in"                     ; assign input for Y2 HLFB+
M950 J19 C"^6.io2.in"                     ; assign input for Z1 HLFB+
M950 J20 C"^6.io3.in"                     ; assign input for Z2 HLFB+
M950 J21 C"^6.io4.in"                     ; assign input for Z3 HLFB+
M950 J22 C"^6.io5.in"                     ; assign input for Z4 HLFB+
M581 P16:17:18:19:20:21:22 T2 S0 R1       ; configure external trigger 2, active to inactive, when printing

trigger2.g

if sensors.gpIn[16].value == 0  ; if x servo is disabled or in shutdown
    M957 E"driver-error" D0 B121    ; raise driver error event, driver 0, CAN 121, P???

if sensors.gpIn[17].value == 0  ; if Y1 servo is disabled or in shutdown
    M957 E"driver-error" D0 B0    ; raise driver error event, driver 0, CAN 0, P???

if sensors.gpIn[18].value == 0  ; if Y2 servo is disabled or in shutdown
    M957 E"driver-error" D1 B0    ; raise driver error event, driver 1, CAN 0, P???

if sensors.gpIn[19].value == 0  ; if Z1 servo is disabled or in shutdown
    M957 E"driver-error" D2 B0    ; raise driver error event, driver 2, CAN 0, P???

if sensors.gpIn[20].value == 0  ; if Z2 servo is disabled or in shutdown
    M957 E"driver-error" D3 B0    ; raise driver error event, driver 3, CAN 0, P???

if sensors.gpIn[21].value == 0  ; if Z3 servo is disabled or in shutdown
    M957 E"driver-error" D4 B0    ; raise driver error event, driver 4, CAN 0, P???

if sensors.gpIn[22].value == 0  ; if Z4 servo is disabled or in shutdown
    M957 E"driver-error" D5 B0    ; raise driver error event, driver 5, CAN 0, P???

Any suggestions on improving the functionality? I've not created driver-error.g so the printer should just send a popup message in DWC and pause the print - which is essentially what I want when a servo goes into shutdown.

Also what does the P parameter do in M957? I was reading through the Events documentation and all it says is "Lower 16 bits of driver status word" and I have no idea what that means.

Thanks!

@T3P3Tony Because of this limitation, I don't think the HLFB (high level feedback) signal from Teknic servo motors can be used as an error signal to the duet. The way Teknic handles it, the HLFB pin will conduct (Active-High) when the servo is enabled and not in a shutdown state, but the servo will not be enabled on startup. Because of this, the current firmware will assume Active-Low on startup, and when the servo is enabled, it will trigger a driver-error event.

For Teknic servos (very popularly paired with Duet hardware) the error pin should only be observed when the printer is sending an enable signal and attempting to send move commands.

Are there any solutions in the meantime? I need a way to protect a large printer from potentially damaging itself.

I have some Teknic CPM-SDHP-3446P-ELN motors and a combination of Duet 6XDs and 1XDs and I'm trying to make the HLFB wire from the servo signal the duet to pause a print if the motors over-torque or lose steps.

How exactly would I set this up? It appears that the servo can be wired multiple ways.

Also, what is the name of the event trigger and how would that work? The HLFB conducts when the motor is enabled and not in a shutdown state, which may not necessarily mean that the motor is in an error state, it might just not be enabled yet so maybe I would code something like this?

config.g

; driver 0-5 error inputs are not configured in config.g
M950 J4 C"!^40.io0.in" ; create input pin number 4 on 1XD board at CAN address 40 for servo error
M581 P4 S0 T3 R1 ; invoke trigger 3 when an active-to-inactive edge is detected on input 4 and a file is being printed from SD card

driver0-error.g

if driver0 == "enabled"  ; not sure what variable to use here to see if axis was commanded to be enabled
   M25  ; pause print
   echo "Cannot move servo 0. Servo may be in a fault state"

trigger3.g

if driver6 == "enabled"  ; not sure what variable to use here to see if axis was commanded to be enabled
   M25  ; pause print
   echo "Cannot move servo 6. Servo may be in a fault state"

From the manual: