Posts made by keyz182

undefined

@dc42 fantastic, thanks!

undefined

@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?

undefined

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?

undefined

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.

undefined

@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.

undefined

@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

undefined

@t3p3tony There's continuity on all three.

undefined

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

undefined

@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.

undefined

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

Front
Back
Closeup

undefined

@nurgelrot Check the table here - https://duet3d.dozuki.com/Wiki/Duet_3_Mini_5plus_Wiring#Section_Description_of_Connectors_and_indication_LEDs

Specifically 1x2 Jumper: Int_5V_Disable and Note 2 at the bottom. The diagram on the top of the page shows where it is.

undefined

@dc42 So power the pi from 5V directly, drop the ext_5v connection, and just use SBC 5V?

Seems the more sensible approach now that I actually think about it. I'm only running a set of 7 neopixels off the 5v, so could probably just use internal 5v. I guess I was thinking future proofing, but I think I'll just address that in the future

undefined

@nurgelrot Just reassembled the panels so can't take pics.

All I did though was jumper the internal 5V disable pins, and jumper all 3 pins on the 5V_SELECT pins together.

Then I have a 5v supply connected to the EXT 5V pins.

undefined

Well, I tried it, and nothings gone pop yet

undefined

I currently have both the Pi and 5V_EXT_INPUT powered from external 5v. In an efforts to clean up wiring, (and potentially reduce noise to combat BAD CRC32) I'm wondering if it's possible to short 5V_EXT_INPUT, 5V_SBC, and 5V_SELECT on the 5V selection jumpers so that the pi gets powered from the 5V_EXT supply over the ribbon cable?

Looking at the schematics, the 5V_EXT_INPUT and 5VSBC rails only have inputs and jumpers attached to them, so it seems like it'd be OK, but want to make sure.

undefined

@paulhew https://www.omc-stepperonline.com/round-nema-14-bipolar-1-8deg-9-ncm-12-75-oz-in-1-0a-f36x17-5mm-4-wires.html

That's the one. Yeah, it's a bit high, as I said, still tuning. Put probably a roll of filament through at that amperage though and so far it looks fine (had the extruder disassembled yesterday).

undefined

This is what I have on my V0.1 + Duet 3 Mini 5+, with OMC steppers. No guarantees it's correct, still tuning in and adjusting, but it's printing things reasonably so should be a good starting point at least. Also, critique welcome

; Configuration file for Duet 3 Mini 5+ (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Fri Jun 04 2021 16:03:31 GMT+0100 (British Summer Time)

; General preferences
G90                                                   ; send absolute coordinates...
M83                                                   ; ...but relative extruder moves
M550 P"voronzero"                                        ; set printer name
M669 K1                                               ; select CoreXY mode

; Drives
M569 P0.1 S0                                          ; physical drive 0.1 goes backwards
M569 P0.2 S0                                          ; physical drive 0.2 goes backwards
M569 P0.4 S0                                          ; physical drive 0.4 goes backwards
M569 P0.3 S1                                          ; physical drive 0.3 goes forwards
M584 X0.1 Y0.2 Z0.4 E0.3                              ; set drive mapping
M350 X16 Y16 Z16 E16 I1                               ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E1370.00                    ; set steps per mm
M566 X1080.00 Y1080.00 Z90.00 E150.00                   ; set maximum instantaneous speed changes (mm/min)
M203 X30000.00 Y30000.00 Z1200.00 E9000.00            ; set maximum speeds (mm/min)
M201 X4000.00 Y4000.00 Z450.00 E6000.00               ; set accelerations (mm/s^2)
M906 X1250 Y1250 Z400 E800 I25                        ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                               ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                                      ; set axis minima
M208 X120 Y120 Z120 S0                                ; set axis maxima

; Endstops
M574 X2 S1 P"io3.in"                                  ; configure active-high endstop for high end on X via pin io3.in
M574 Y2 S1 P"io5.in"                                  ; configure active-high endstop for high end on Y via pin io5.in
M574 Z1 S1 P"io6.in"                                  ; configure active-high endstop for low end on Z via pin io6.in

; Z-Probe
M558 P0 H5 F120 T3000                                 ; disable Z probe but set dive height, probe speed and travel speed

; 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 B1 S1.00                                      ; enable 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"temp1" Y"pt1000" R2200                      ; configure sensor 1 as PT1000 on pin temp1
M950 H1 C"out1" T1                                    ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00                                      ; 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"out6" Q75                                  ; create fan 0 on pin out6 and set its frequency
M106 P0 C"Cooling" H1 T45 B0.5                     ; set fan 0 name and value. Thermostatic control is turned on
M950 F1 C"out5" Q75                                  ; create fan 1 on pin out5 and set its frequency
M106 P1 C"Part" H-1 B0.5                          ; set fan 1 name and value. Thermostatic control is turned off

; Tools
M563 P0 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
; DHT22 Temperature Sensor
M308 S10 P"io4.out+io4.in" Y"dht22" A"Chamber Temp"
M308 S11 P"S10.1" Y"dhthumidity" A"Chamber Hum[%]"  

; Set bed screw positions for true bed leveling
M671 X60:5:115 Y5:115:115 P0.5

;  Laser filament monitor with over the top R values 
M591 D0 P6 C"io1.in" R0:200 E3.0 S1   

; ST7567 12864 display
M918 P2 E2                                           ; enable ST7567-based 12864 display
M150 X2 R32 U255 B32 S3                              ; set all 3 LEDs to white

; M955 P0 C"io0.out+io0.in"

; Miscellaneous
M501                                                  ; load saved parameters from non-volatile memory
T0                                                    ; select first tool

undefined

@smoothquark If that module has +12, PWM, and GND, then yes. PWM (and GND) from CN1 to the module, then 12v from wherever (GND too - make sure GND from the supply and duet are linked, otherwise PWM would have no reference).

You can also plug in the 12v power to CN2, that just means you module only needs to be wired to one place - CN1, rather than PWM + GND going there, 12v going elsewhere, and splitting GND to bridge duet + PSU. V_IN goes from CN2 to CN1 but isn't connected to Duet, just a passthrough.

Electrically, there's no difference, just a matter of convenience.

undefined

@smoothquark V_IN on CN1 is just a direct connection to V_IN on CN2. My laser had 3 inputs, +V, PWM, GND. I added the V_IN passthrough so that I could just plug the three connections into one header, then pull in the 12v I need from elsewhere and just wire it to V_IN on CN2.

This shows what's going on - https://duet3d.dozuki.com/Wiki/Laser_PWM_control#Section_Preparation

Note - I haven't touched this since 2018, so I'm a little rusty

undefined

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