@CCS86

As requested, I'm starting a new thread. Not sure if this is the correct section. If not, feel free to move it.

@deckingman was specifically asked by the Duet engineers to post here

For anyone watching this thread, and for those who have contributed, I just want to say that the Duet team and I have opened up the communication medium that we used at the very start (when Gen 3 was still at the pre-production stage), in order to work together to resolve these issues. That's nothing personal - just that these forums are maybe not the best way to post messages rapidly back and forth between us.

They have now opened up more direct channels.

Just talk to the Duet engineers directly and spare everyone else from your dog and pony show.

No-one is forcing you to click on this thread, so consider yourself spared.

@t3p3tony said in Guide for posting requests for help:

Please only reply to this post with other constructive things forum users should do before asking for help.

• Be civil

Hey, I've just uploaded my changes to the 305 Engineering Laser Gcode generator for Inkscape, that takes advantage of the recent Duet changes to set laser power in the G1 commands. My testing has given much quicker, and cleaner outputs.

https://github.com/keyz182/inkscape-laser-gcode/tree/duet
Make sure to grab the duet branch. It should happily live alongside the original plugin, rather than replace it.

That'll be it. Now that you say that, I seem to remember reading it a while ago, evidently that snippet of information failed to stay in my brain

Would it be a good idea to make T commands output a message to the console along the lines of "free/pre/post scripts not executed as axes are not homed"?

Hey, just sharing a script I put together to notify me on print completion.

It runs on a Pi (though should run on any *nix connected to the Duet via USB), and uses Twilio to send SMS, and AWS S3 to store images. Also needs mjpeg_streamer to grab the images (or some service that can return a screenshot on a HTTP GET).

The script is available here.

There's some issues currently - Error handling needs a little work, as it's very verbose. Had the printer off overnight, with the Pi on, and the serial port not found errors spammed the logs and filled up the root partition. Added time.sleep(10) for now to take the edge off. Also, for now, added logrotate size 512k and set it to rotate every 5 minutes.

Use this link to ensure AWS is configured.

Once configured, add M118 P1 S"###END###" to your slicers end g-code.

At some point, I'd like to look at M408 or similar to include some extra detail in the SMS.

@arhi don't do that. Don't belittle people because they don't fit into your neat little boxes.

The paper isn't even trying to "do science", it's suggesting a legal framework for protection of privacy in regards to watermarks. I have issues with the intro to the paper, if this was a paper I was reviewing, I'd be sending it back as "needs work" referencing un-cited sentences such as "tracking
technologies that underlie 3D printing". But the body of the paper seems (I've only skim read), reasonably thought out. I think it applies more broadly than 3D printing, as watermarks or tracking IDs can be and are placed on non 3D printed products, but it's a start.

I wrote up a quick bit of code last night/this morning to control WS281x LEDs from a PI running the Duet Software Platform.

It uses the RPI_WS281X under the hood, so it's limitations apply to pin choices. I'm defaulting to GPIO12 in PWM mode, as DSF uses the SPI pin.

Right now it's using the duration and file time left to calculate progress, as I couldn't find a progress variable in the object model in DuetAPI (not saying it's not there, just couldn't find it).

I have considered being able to reserve LEDs at the start/end for indicators of other things, but not sure what - any suggestions? e.g. heater x on, fan x on, fan x speed (e.g. red to green or brightness of blue), etc.

To use, grab the zip from the releases tab, extract to /opt/LEDProgress, and install the systemd service as stated in the readme.

Modify the command line args as appropriate in the service file before installation. Defaults are my setup, so Pin 12, 56 LEDs, 255 max brightness.

@nuramori Never mind, just received a V1.1. Unexpected, but welcome

https://github.com/keyz182/DuetMQTT

A very basic service for DSF that'll publish the object model to MQTT. Can be consumed then by e.g. Home Assistant, NodeRED, etc.

@carcamerarig https://github.com/keyz182/DuetLEDProgress

I wrote this for my needs. It's limited in functionality, basically progress, and a couple of status LEDs at the end of the strip. That said, if you can at all code, it should be trivial to modify to your own needs. Its got the code for interacting with DSF on the SBC, and code for driving the LEDs, all you need to do is add the glue/logic.

If you can't code, feel free to make a request for a new feature, but I can't promise I'll have time to implement any time soon I'm afraid.

@dc42 fantastic, thanks!

@dc42 Would something like 10Ω, 100W work for the power resistor? Digging out the old ohms law (if I'm using it correctly, a bit rusty) says that would allow 2.4A, and hit 56 or so watts?

E.g. would these work?

• https://uk.farnell.com/on-semiconductor/sb530/rectifier-schottky-5a-30v-do-201ad/dp/2454184
• https://uk.farnell.com/arcol/hs100-10r-j/resistor-wirewound-10-ohm-5-axial/dp/2478154

As suggested here https://docs.duet3d.com/en/User_manual/Tuning/Resume I've been looking at adding a 10,000uF capacitor a cross the 24v line to make sure there's ample power left to do what's needed.

I've moved to a mains powered bed, and moved down to a 150W 24v power supply, as that's all I need. The issue is that it appears the supply can't handle the inrush current (I think that's the right term) of the big cap, and keeps restarting every second or so.

What's the best way to limit the inrush current? NTC seems to come up in searches, but not sure how to appropriately pick one for the job. Any other ways?

I needed to convert an image to work on a 12864 menu, so wrote a small python CLI tool to do it.

https://pypi.org/project/bmptoduet/
https://github.com/keyz182/bmptoduet

Install with pip3 install bmptoduet or similar.

Run with bmptoduet sourceimage.bmp outputimage.img.

The source image must be 255x255 or smaller, and in a monochrome 1bit per pixel bitmap format.

@jay_s_uk OK, that worked. Is that documented behavior that I've just misread? I swear I've always done M552 S1 before any M587 commands.

@t3p3tony Continuity (through 2.2KOhm) on both which seems to tally up with the schematic.

@dc42 It's consistent. Right after a flash, leaving it a while, rebooting, etc, all the same as soon as I try M587 or M122.

Connecting...
Printer is now online.
>>>M552 S1
SENDING:M552 S1
WiFi module started
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
>>>M587 S"IoT_2G" P"********"
SENDING:M587 S"IoT_2G" P"********"
Error: M587: Failed to add SSID to remembered list: SPI timeout
[ERROR] Error: M587: Failed to add SSID to remembered list: SPI timeout

Error retrieving WiFi status message: SPI timeout
[ERROR] Error retrieving WiFi status message: SPI timeout

WiFi module is idle
Failed to change WiFi mode: SPI timeout
>>>M552 S-1
SENDING:M552 S-1
>>>M552 S0
SENDING:M552 S0
WiFi module started
>>>M552 S1
SENDING:M552 S1
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
>>>M587 S"IoT_2G" P"********"
SENDING:M587 S"IoT_2G" P"********"
Error: M587: Failed to add SSID to remembered list: SPI timeout
[ERROR] Error: M587: Failed to add SSID to remembered list: SPI timeout

Error retrieving WiFi status message: SPI timeout
[ERROR] Error retrieving WiFi status message: SPI timeout

WiFi module is idle
Failed to change WiFi mode: SPI timeout

@t3p3tony There's continuity on all three.

@t3p3tony Continuity to the MCU for MOSI, MISO and SPCK, any other pins I should check?

@t3p3tony

Connecting...
Printer is now online.
>>>M997 S1
SENDING:M997 S1
Trying to connect at 230400 baud:
 success
Erasing 4096 bytes...
Erasing 196608 bytes...
Uploading file...
5% complete
10% complete
15% complete
20% complete
25% complete
30% complete
35% complete
40% complete
45% complete
50% complete
55% complete
60% complete
65% complete
70% complete
75% complete
80% complete
85% complete
90% complete
95% complete
Upload successful

And for good measure I did an M997 S0 too which correctly reports 3.3 after a restart and M122.

I have a pair of Duet Wifi 2 boards (1.02 and 1.03) that were modded with this SBC mod. I'm aware it's almost certainly voided the warranty (which would have run out anyway), so just looking for advice/pointers.

I've upgraded to Duet 3 Minis, so was going to sell these two boards. In preparation, I removed the mod board and got everything reset to factory. I reflashed the firmware with BOSSA, loaded up a new SD card, and ran M997 S1 to flash the Wifi firmware.

Unfortunately on both boards I just get SPI timeouts when trying to do anything with the WiFi. I thought I might have somehow borked the ESP boards so I replaced them (with ESP-07S, as Farnell sent out those instead of the 12S), reflashed with M997 S1 but still the same SPI timeout.

Can't see any solder bridges, or any other components that may have shifted/desoldered.

I've tried the latest 3.2 and 3.3 firmwares to no avail. Any ideas what to check, or what may be the cause?

RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3
Printer is now online.
>>>M122
SENDING:M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 08DGM-956GU-DJMSN-6J9FL-3SD6S-TTRHH
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 73544 of which 12 recycled
Never used RAM 16984, free system stack 193 words
Tasks: NETWORK(ready,1.9%,517) HEAT(delaying,0.0%,391) Move(notifyWait,0.1%,364) MAIN(running,66.1%,639) IDLE(ready,31.9%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:00:12 ago, cause: reset button or watchdog
Last software reset at 2021-09-09 14:06, reason: User, GCodes spinning, available RAM 15512, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
[ERROR] Error status: 0x00

Step timer max interval 0
MCU temperature: min 36.9, current 37.1, max 37.3
Supply voltage: min 1.7, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 716504001
Slowest loop: 0.22ms; fastest: 0.13ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 12.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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 ready with "M122" 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.18ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8
- WiFi -
Network state is disabled
WiFi module is disabled
Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
Socket states: 0 0 0 0 0 0 0 0
>>>M552 S1
SENDING:M552 S1
WiFi module started
WiFi reported error: no known networks found
WiFi module is idle
>>>M587 S"IoT_2G" P"********"
SENDING:M587 S"IoT_2G" P"********"
Error: M587: Failed to add SSID to remembered list: SPI timeout
[ERROR] Error: M587: Failed to add SSID to remembered list: SPI timeout

Error retrieving WiFi status message: SPI timeout
[ERROR] Error retrieving WiFi status message: SPI timeout

WiFi module is idle
Failed to change WiFi mode: SPI timeout

>>>M552 S1
SENDING:M552 S1
WiFi module started
>>>M122
SENDING:M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 08DGM-956GU-DJMSN-6J9FL-3SD6S-TTRHH
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 73544 of which 12 recycled
Never used RAM 16984, free system stack 193 words
Tasks: NETWORK(ready,3.9%,461) HEAT(delaying,0.0%,391) Move(notifyWait,0.1%,364) MAIN(running,73.4%,639) IDLE(ready,22.6%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:00:17 ago, cause: reset button or watchdog
Last software reset at 2021-09-09 14:06, reason: User, GCodes spinning, available RAM 15512, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
[ERROR] Error status: 0x00

Step timer max interval 0
MCU temperature: min 36.5, current 38.1, max 38.3
Supply voltage: min 1.7, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 920185181
Slowest loop: 99.74ms; fastest: 0.12ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 12.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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 ready with "M122" 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 1.28ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8
- WiFi -
Network state is changingMode
WiFi module is idle
Failed messages: pending 0, notready 0, noresp 0
Failed to get WiFi status
Socket states: 0 0 0 0 0 0 0 0
Error retrieving WiFi status message: SPI timeout
[ERROR] Error retrieving WiFi status message: SPI timeout

WiFi module is idle
Failed to change WiFi mode: SPI timeout