@AndreS Care to release the firmware and board files under FOSHW?

Hello,

First off, let me apologize for the crap PCB design; I am nowhere close to @T3P3Tony or others on this forum when it comes to PCB design / routing.

Some background: I have my printers on a UPS; however, if and when there is a power cut, depending on how many printers are running, the UPS may get overloaded. Before the UPS circuit breaker trips, I switch off the bed heating to make the power draw a little less.

I wanted to 'automate' the process and here is what I have come up with: a mish-mash between the Prusa Power Panic and a Duet capacitor bank.

The goal for this is to enable the bed to be switched off automatically; while allowing printing to continue / duet power recovery to kick in.

Please note, the Panic_In signal comes in from a non-UPS outlet.

Please review the attached schematic and board files and let me know if you see an opportunity to make this better.

Duet_Power_Panic.pdf

https://drive.google.com/file/d/1wGrmC7JF2DsiOV9DeAoTHiJEPFfpRMTZ/view?usp=sharing

Hello,

First off, let me apologize for the crap PCB design; I am nowhere close to @T3P3Tony or others on this forum when it comes to PCB design / routing.

Some background: I have my printers on a UPS; however, if and when there is a power cut, depending on how many printers are running, the UPS may get overloaded. Before the UPS circuit breaker trips, I switch off the bed heating to make the power draw a little less.

I wanted to 'automate' the process and here is what I have come up with: a mish-mash between the Prusa Power Panic and a Duet capacitor bank.

The goal for this is to enable the bed to be switched off automatically; while allowing printing to continue / duet power recovery to kick in.

Please note, the Panic_In signal comes in from a non-UPS outlet.

Please review the attached schematic and board files and let me know if you see an opportunity to make this better.

Duet_Power_Panic.pdf

https://drive.google.com/file/d/1wGrmC7JF2DsiOV9DeAoTHiJEPFfpRMTZ/view?usp=sharing

I would be interested in trying this out. Let me know how I can help.

@dc42 ,

any thing else I need to do?
I can confirm that this issue exists with DuetWiFIServer 1.22 and Duet FW 2.02 as well.

THanks,
Madhu.

okay; heres a change in the situation:

• When I lost the connection to DWC, I sent M552 S1 to check if the board would connect to WiFi. It just replied OK and did not do anything
• I then sent M552 S0; it gave me an error that the wireless mode could not be changed
• Sending M552 S1 again switched the WiFi on and the board was able to connect to the network.

And, I have carefully noticed; the DWC connection drops the moment the pre-heat is done and the printer starts to move.

~Madhu.

@dc42 ,
Here is the fresh M122 outout:
RepRapFirmware for Duet 2 WiFi/Ethernet Version 2.03 dated 2019-06-13b2

Executing config.g...HTTP is enabled on port 80
FTP is enabled on port 21
TELNET is enabled on port 23
Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset.

Done!
RepRapFirmw
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
Used output buffers: 1 of 24 (8 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93696 of which 0 recycled
Exception stack ram used: 440
Never used ram: 11256
Tasks: NETWORK(ready,524) HEAT(blocked,1236) MAIN(running,3756) IDLE(ready,160)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:06:39 ago, cause: software
Last software reset at 2019-08-11 14:36, reason: User, spinning module GCodes, available RAM 11376 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 7
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 7.7ms, max retries 0
MCU temperature: min 26.9, current 28.5, max 28.8
Supply voltage: min 23.2, current 23.9, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, SG min/max 0/100
Driver 1: ok, SG min/max 0/48
Driver 2: ok, SG min/max 0/1023
Driver 3: standstill, SG min/max not available
Driver 4: ok, SG min/max 0/3
Date/time: 2019-08-11 14:43:31
Cache data hit count 1587842547
Slowest loop: 105.25ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 166, MinFreeDm: 163, MaxWait: 297857ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 8, completed moves: 7, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.6
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 2 in use
Movement lock held by file
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 43 8 0
serial is ready with "M122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 200.97ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8

• WiFi -
  Network state is running
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 75
  Failed to get WiFi status
  Socket states: 0 0 0 0 0 0 0 0
  ok

Thanks,
Madhu.

Hi @dc42 ,

Here is the M122 output:

=== Diagnostics ===<LF>Used output buffers: 1 of 24 (11 max)<LF>=== RTOS ===<LF>Static ram: 25680<LF>Dynamic ram: 93696 of which 0 recycled<LF>Exception stack ram used: 452<LF>Never used ram: 11244<LF>Tasks: NETWORK(ready,524) HEAT(blocked,1236) MAIN(running,1668) IDLE(ready,160)<LF>Owned mutexes: WiFi(NETWORK)<LF>=== Platform ===<LF>Last reset 00:07:02 ago, cause: software<LF>Last software reset at 2019-08-11 00:00, reason: User, spinning module GCodes, available RAM 11372 bytes (slot 3)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d<LF>Error status: 0<LF>Free file entries: 9<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 0.0ms, max retries 0<LF>MCU temperature: min 25.0, current 25.5, max 25.7<LF>Supply voltage: min 23.2, current 23.4, max 24.2, under voltage events: 0, over voltage ev<Warning: Maximal number of bytes per line exceeded! Check the end-of-line settings or increase the limit in the advanced terminal settings.>

I am sorry about the formatting; but, I just copied and pasted the output on YAT directly.

Please let me know in case you need more info.

Thanks,
Madhu.

Hello all,

I Have a Duet 2 1.03 with FW 2.03, DuetWiFIServer 1.23 and DuetWebControl 1.22.6

The issue I am describing was not present in Duet FW 2.02 with DuetWiFIServer 1.23 and DuetWebControl 1.22.3

What happens is this:

• If I am not printing, the Duet stays connected to the WiFi indefinitely; no issues.
• The Duet stays connected while preheating, mesh bed level and probably for the first couple of lines of printing
• I havent determined the exact location in the Gcode for the disconnect; but, after about 5 minutes into the print, the Duet disconnects from the Wifi. The blue LED on the ESP turns off

This happens on ALL prints, regardless of which slicer I use. I have tried S3D, Prusa Slicer 2.0

I dont know whats happening. Any help would be highly appreciated.

Thanks,
Madhu.

@AndreS Care to release the firmware and board files under FOSHW?

What about somehting like this: https://www.thingiverse.com/thing:3091625
the part in that thing is just an interposer... but, the skelestruder project has the other parts.
sensing off of a rotating bearing kinda sorta makes sense to me.

Hi Florian,
Other than the filament sensor, you should be able to use everything else.
Duet3d has their own spin on the filament sensor; it is not compatible with the PR one.

Rgds.

P.S. Nice job on the robot arm.