Posts made by foesi

@Herve_Smith these files look exactly the same on my sd card and the config.g M950 and M558 are the same as yours.
Remember that the BL-Touch had been working for a few months.

@Phaedrux I tried to position the screw in a position where the test at power on just gets the pin back up in retracted position.
I can´t get the screw in the position as mentioned in the antclabs documentation - because then the pin would not get back up.
And I also used magnets to get the pin magnetised.

Hello,

I have a Duet Wifi 1.04 with RRF 3.2.2 and use a BL-Touch as a z-probe.
The BL-Touch has been working for a few month until a few weeks ago I needed to replace the pin because some warped ppsu just got into the way of the pin...
I tried to replace the pin... no difference
Then I tried another BL-Touch that I had for just that case and it didn´t work too.
I adjusted the screw in the BL-Touch so that the pin gets retracted at the self test when power is on.

The BL-Touch started blinking red after self test... I tested all the wires - everything fine.
Then I put the M280 P0 S160 at the end of config.g - after that the blinking is gone.
When I try the M401 the pin gets deployed and then it starts blinking red - same is for M280 P0 S10.
After that I used the M402 command to retract the pin... and it didn´t work - exactly the same happens with the M280 P0 S90.

The M280 P0 S160 retracts the pin and gets the red LED to flash steadily.

So i it can push the pin up and down by itself - but why not with M402?
Why does it blink when using M401?

Any suggestions are appreciated!

@jay_s_uk thanks for the reminder to try this - and it was indeed the problem.
But why did my wiring work the day before for at least homing 10 times? It doesn´t really matter now but I am just curious...

@jay_s_uk I have connected one wire with the 5V of the IO port and the other wire with the ioX_in. Same on both X- and Y endstops. Only Z is wired to 12V in the middle of the board and only the signal wire is connected to the io3_in. I need this because the z-probe needs 6V+.

Hallo,

I have now set up my Duet 3 mini 5+ and after trying everything I wanted to make a test print.
The next day I heated up the bed and wanted to home the axis for z-probe offset...
The X- and Y-stop then did not work or to be precise they did trigger right away.
Then I tried to use the IO_2 and the IO_4 port instead of the IO_0 and the IO_1 - same problem.
After that I converted the pinname with a "!" like P"!io.0in". That made the endstopps to not trigger regardless of what I tried.
It made no difference if the endstopps were connected or not.
The thing is... they worked the day before so there should not be a wiring or configuration problem!?
I also checked the voltage of the IO pins and the 5V to GND and 3.3V to GND were both fine on all IOs.

To update the firmware did also not change anything.

Here is some more information:

Board: Duet 3 Mini 5+ (Mini5plus)
Firmware: RepRapFirmware for Duet 3 Mini 5+ 3.4.1 (2022-06-01)
Duet WiFi Server Version: 1.26

config.g definition:

M574 X1 S1 P"io0.in"
M574 Y1 S1 P"io1.in"
M574 Z1 S2

The z-probe works - for some reason.

Thanks in advance!

@cosmowave the sensor is configured like this:

; Z-Probe
M558 P1 C"!io3.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds
G31 P999 X-41 Y5 Z5 ; set Z probe trigger value, offset and trigger height
M557 X50:550 Y50:550 S50 ; define mesh grid

I have connected the signal to the io3.in of the IO_3 port. The + and - are connected to the 12V port in the center of the board.

@cosmowave I use the orignal Tronxy TR leveling sensor.

https://www.tronxyonline.com/Tronxy-Black-TR-Auto-Leveling-Sensor-p1486299.html

I run it with 12V because I have not connected it to the 5V or the 3.3V of the IO port.

Another thing which is not a problem but could be done better is the value of the Z-Probe.
I got it to work whith a trigger value of 1000 and the usual value is 964.
Is there a way to get the normal value down to 0?

@norder The change to T100000 made the difference - but I have put 84000 there wich is the resistance I measured at around 18°C and that made no difference.
And no I did NOT just copy someone else's config.g . I just saw the line in the config.g and gave it a try . I will definetly do a PID tuning for both - because I need to do this twice a year due to the fact that the temperatures of winter and summer are quite different in Austria.

Thank you for your effort!

@jumpedwithbothfeet config.g-25082022.txt config.g.bak.txt
The thermistors and heaters are stock parts - I have only changed the controller board to the duet 3 mini 5+ because the tronxy board was not reliable and made strange things during printing - after I had it for 4 months. Then I bought the duet because the tronxy support could not figure out what the problem was and I have another duet 2 wifi for 2 1/2 years now which works reliable on my own built printer.

@norder I saw this in another config.g and gave it a try

@jumpedwithbothfeet No, I haven't. I put the M563 P0 D0 H1 just now into config.g and it worked!

The other strange thing is that the extruder and bed temperatures are at -21°C. What could be the cause of that?

Hallo, I want to use a Duet 3 mini 5+ as controller for a Tronxy X5SA-600 and therfore I want to have one bed heater and one hotend heater.

I have them configured in config.g like this:

; Heaters
M308 S0 P"temp0" Y"thermistor" T10000 B4100 ; 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 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S105 ; set temperature limit for heater 0 to 105C
M308 S1 P"temp1" Y"thermistor" T10000 B4100 ; configure sensor 1 as thermistor 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
M140 H1 ; map EXTRUDER HEATER to heater 1
M143 H1 S310 ; set temperature limit for heater 1 to 310C

But in DWC there is just the bed heater displayed (picture).

I tried to type in M98 p"config.g" which gives me this output:

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

Did I miss something obvious or can someone tell me what to try?

I recently got the new duet board and - it works fine now! Thanks for your help!
It must have been the SD-card socket. Now I can get on with my project - which is to make the Duet 3 mini 5+ my controller for a Tronxy X5SA-600.
Thanks again and all in all it was surprisingly convenient to get the new board.

@phaedrux here are the results of M122 and the contents of the SD-card.

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.1 (2022-06-01 21:06:56) running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: KS8ZD-NT8LU-F65J0-409NL-1513Z-7LQYL
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 96528 of which 0 recycled
Never used RAM 41500, free system stack 170 words
Tasks: SBC(notifyWait,0.0%,972) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,372) CanClock(delaying,0.0%,339) TMC(notifyWait,0.0%,123) MAIN(running,98.4%,583) IDLE(ready,0.8%,29) AIN(delaying,0.8%,274), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:00:12 ago, cause: power up
Last software reset details not available
Error status: 0x00
MCU revision 3, ADC conversions started 12868, completed 12868, timed out 0, errs 0
Step timer max interval 1490
MCU temperature: min 10.4, current 13.5, max 13.5
Supply voltage: min 0.4, current 0.9, max 0.9, 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
Events: 0 queued, 0 completed
Driver 0: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 6: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 31761453
Slowest loop: 0.23ms; fastest: 0.00ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, 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 -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 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
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 64, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 64/0/0
Tx timeouts 0,0,63,0,0,0 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 0, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 0/1
SPI underruns 0, overruns 0
State: 0, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x0f1ec
Buffer RX/TX: 0/0-0, open files: 0
ok

@jay_s_uk yes sure I can send you the details per Mail.
A few weeks ago means I purchased it at 03.07.2022

@jay_s_uk that is correct.
The SD-card is FAT32 and I have no SBC connected.

I purchased a new Duet 3 mini 5+ from 'cr3d.de' a few weeks ago.
Now I wanted to setup the duet with YAT but somehow this error occurs when I type in M552

-> Error: M552: Network-related commands are not supported when using an attached Single Board Computer

When I type in M115 it tells me this

->FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.4.1 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2022-06-01 21:07:06

I also have tried to reformat the SD-card like explained but there is still no difference. By searching for a dead SD-card reader I found out to check the M122 which tells me this

->=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0

Is the problem with the M552 connected with a dead SD-card reader? Or is there another problem?
Any guesses appreciated!