Posts made by KeesL 0

Problem solved under warranty, it works fine now.

Thanks Kees

@KeesL-0
Because the problem with the DC42IR probe has not yet been solved, I did the following.

1. Formatted the SD card and installed the latest software. Printer works properly except for the IR probe.

2. Measured the wiring of the probe, it is okay.

3. Measured the voltage on the Duet3D mini 5+, which is 3.28V on the slots.

As soon as the voltage is applied, D3 flashes weakly once.
After 1 second, D3 flashes brightly once.
After 5 seconds, D3 flashes 2 times.

See also the config file.
; Z-Probe
M558 P1 C"io3.in" H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X20:180 Y20:180 S20 ; define mesh grid

If I connect the probe to an external voltage, it flashes 4 times!

If the probe is triggered at a distance of 2mm from the bed, it will indicate 997 with a red background on the screen.

At a distance of 6mm between bed and probe, this indicates 66 without a red background.

When moving the bed I don't see any values ​​change, so it is 997 or 66.

Does anyone have any suggestions on how to solve this?

Regards

Kees

@droftarts
Today I changed the cables.
I checked the voltage on the IR board, it is 3.28V. Seems okay to me. This is also 3.28 V on all slots on the motherboard. Wiring tested for bad contacts, all are fine.
As soon as I apply power to the printer, D3 flashes once and again after approximately 5 seconds only 2 times. So not 4 times as expected.
I have tried other slots with no success.
I then connected 3.3V to the IR board via an external power supply. Now D3 flashes once and 4 times after 5 seconds. D3 also reacts to the black surface.

As soon as I disconnect the signal wire, the IR board responds well, flashing 1x and 4 times respectively.
So in my opinion there is something wrong with the signal line.

Do you have any further suggestions to implement?

Greetings Kees

@Phaedrux
Yes,
I changed it. No succes
M558 P8 C"io3.in" H5 F120 T1200

@droftarts

Hi Ian,

Thank you for your response. The LED does indeed burn softer than normal. I checked the wiring again and I don't see anything wrong with it. See also the attached photo.

Would you like to take a look, maybe I'm overlooking something.

regards Kees

Hello,

I recently purchased a Duet3D IR board, which I connected to IO_3 of my DUET3D mini 5+ board according to the manual. VCC to 3.3V GND to GND and Out to In.

Config file looks like this.

; Z-Probe
M558 P1 C"!io3.in" H5 F120 T1200 ; set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X20:180 Y20:180 S20 ; define mesh grid.

As soon as I turn on the XY core printer, the red LED D3 on the IR board lights up continuously. So no 4 flashes, I have a reading of 478 on my screen, but this does not change when I move the bed.

Do you have a solution for this problem?

Yours sincerely
Kees

Hi,

I did M588 S"*"
M588 => with the wifi name and password, now it's working. I hope for a long time!
But I still don't know what the cause of the malfuction was.

I did not set an IP aress manualy in the config, just followed the instructions on the Duet3D website. Getting connected to your Duet.

Best regards.

Kees

My read out M122

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.4 (2022-10-20 16:18:28) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: UAP8L-B196U-D65J0-40KMW-KM03Z-HUZ51
Used output buffers: 1 of 40 (17 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 110684 of which 64 recycled
Never used RAM 27208, free system stack 134 words
Tasks: NETWORK(ready,13.9%,365) HEAT(notifyWait,0.0%,358) Move(notifyWait,0.0%,261) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,341) TMC(notifyWait,0.0%,124) MAIN(running,85.2%,408) IDLE(ready,0.1%,30) AIN(delaying,0.9%,272), total 100.0%
Owned mutexes: WiFi(NETWORK) USB(MAIN)
=== Platform ===
Last reset 00:01:47 ago, cause: power up
Last software reset at 2023-01-24 12:17, reason: User, GCodes spinning, available RAM 27208, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 107898, completed 107896, timed out 0, errs 0
Step timer max interval 737
MCU temperature: min 12.0, current 12.4, max 12.7
Supply voltage: min 0.6, current 0.6, max 0.6, 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 209632694
Slowest loop: 10.92ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.1ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 4, completed 4, 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, 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 155, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 86/0/0
Tx timeouts 0,0,86,0,0,69 last cancelled message type 4514 dest 127
=== Network ===
Slowest loop: 100.95ms; fastest: 0.06ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 2
WiFi firmware version 1.27
WiFi MAC address f0:08:d1:03:77:14
WiFi Vcc 3.39, reset reason Power up
WiFi flash size 2097152, free heap 26232
WiFi IP address 255.255.255.255
WiFi signal strength 31dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok

Best regards

Kees

Sorry for the mistake,

M552 S1
ok<LF>
M122
=== Diagnostics ===<LF>RepRapFirmware for Duet 3 Mini 5+ version 3.4.4 (2022-10-20 16:18:28) running on Duet 3 Mini5plus WiFi (standalone mode)<LF>Board ID: UAP8L-B196U-D65J0-40KMW-KM03Z-HUZ51<LF>Used output buffers: 1 of 40 (17 max)<LF>=== RTOS ===<LF>Static ram: 103684<LF>Dynamic ram: 110684 of which 64 recycled<LF>Never used RAM 27208, free system stack 134 words<LF>Tasks: NETWORK(ready,14.0%,367) HEAT(notifyWait,0.0%,358) Move(notifyWait,0.0%,290) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,341) TMC(notifyWait,0.0%,124) MAIN(running,85.0%,411) IDLE(ready,0.0%,30) AIN(delaying,0.9%,272), total 100.0%<LF>Owned mutexes: USB(MAIN)<LF>=== Platform ===<LF>Last reset 00:04:31 ago, cause: power up<LF>Last software reset at 2023-01-24 12:17, reason: User, GCodes spinning, available RAM 27208, slot 0<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a<LF>Error status: 0x00<LF>MCU revision 3, ADC conversions started 271280, completed 271280, timed out 0, errs 0<LF>Step timer max interval 738<LF>MCU temperature: min 14.6, current 16.8, max 17.1<LF>Supply voltage: min 0.6, current 0.6, max 0.6, under voltage events: 0, over voltage events: 0, power good: no<LF>Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0<LF>Events: 0 queued, 0 completed<LF>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<LF>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<LF>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<LF>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<LF>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<LF>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<LF>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<LF>Date/time: 1970-01-01 00:00:00<LF>Cache data hit count 516045762<LF>Slowest loop: 11.04ms; fastest: 0.13ms<LF>=== Storage ===<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 22.5MBytes/sec<LF>SD card longest read time 3.1ms, write time 0.0ms, max retries 0<LF>=== Move ===<LF>DMs created 83, segments created 3, maxWait 0ms, bed compensation in use: none, comp offset 0.000<LF>=== MainDDARing ===<LF>Scheduled moves 4, completed 4, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF>=== AuxDDARing ===<LF>Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF>=== Heat ===<LF>Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0<LF>=== GCodes ===<LF>Segments left: 0<LF>Movement lock held by null<LF>HTTP is idle in state(s) 0<LF>Telnet is idle in state(s) 0<LF>File is idle in state(s) 0<LF>USB is ready with "M122" in state(s) 0<LF>Aux is idle in state(s) 0<LF>Trigger is idle in state(s) 0<LF>Queue is idle in state(s) 0<LF>LCD is idle in state(s) 0<LF>SBC is idle in state(s) 0<LF>Daemon is idle in state(s) 0<LF>Aux2 is idle in state(s) 0<LF>Autopause is idle in state(s) 0<LF>Code queue is empty<LF>=== CAN ===<LF>Messages queued 1669, received 0, lost 0, boc 0<LF>Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 927/0/0<LF>Tx timeouts 0,0,927,0,0,742 last cancelled message type 30 dest 127<LF>=== Network ===<LF>Slowest loop: 101.53ms; fastest: 0.06ms<LF>Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)<LF>HTTP sessions: 0 of 8<LF>= WiFi =<LF>Network state is active<LF>WiFi module is connected to access point <LF>Failed messages: pending 0, notready 0, noresp 2<LF>WiFi firmware version 1.27<LF>WiFi MAC address f0:08:d1:03:77:14<LF>WiFi Vcc 3.39, reset reason Power up<LF>WiFi flash size 2097152, free heap 26232<LF>WiFi IP address 255.255.255.2[Warning: Maximal number of characters per line exceeded! Check the line break settings in Terminal > Settings > Text or increase the limit in Terminal > Settings > Advanced.]

M552 S1
ok<LF>
M112
Emergency Stop! Reset the controller to continue.<LF>ok<LF>

The commands you asked for.

Best regards

Kees