Posts made by Chris 0

undefined

Hi y'all and sorry for not responding this long I was very busy the last week.

But in the last days I decided to switch on a capacitive sensor because nothing seemed to work with my BL-Touch-scenario. So this matter is closed.

But still, I wanna thank you very much for being so kind as to wanna help me with my problem!

Greetings from Austria

undefined

@phaedrux

Hi phaedrux, thank you very much for your time

my m122 sends me:
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2.2 running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-9P63L-DJMSS-6JTD6-3SD6L-KUDZ9
Used output buffers: 1 of 40 (11 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 92940 of which 16 recycled
Never used RAM 116088, free system stack 200 words
Tasks: NETWORK(ready,210) ETHERNET(blocked,110) HEAT(blocked,300) CanReceiv(blocked,927) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,53) MAIN(running,1105) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 00:00:41 ago, cause: power up
Last software reset at 2021-05-26 17:21, reason: User, GCodes spinning, available RAM 116136, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 40.5, current 45.2, max 45.4
Supply voltage: min 23.7, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.7, under voltage events: 0
Driver 0: position 0, standstill, reads 38227, writes 14 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 38227, writes 14 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 38227, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 38227, writes 14 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 38230, writes 11 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 38231, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-05-27 10:51:18
Slowest loop: 13.91ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, 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 = 0 -1 -1 -1 -1 -1 -1 -1 -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 idle 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.
=== Network ===
Slowest loop: 2.28ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8

Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
=== CAN ===
Messages queued 166, send timeouts 373, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48

I am using duet web control and the RRF-configtool and when i send M98 P"config.g" over the web control, it sends <M98 P"config.g" HTTP request timed out> and then the overlay says that the connection is lost and tries to reconnect. After that, a restart of the machine is needed and its back to normal.
retractprobe:
; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Wed May 26 2021 12:43:50 GMT+0200 (Mitteleuropäische Sommerzeit)
M280 P0 S90 ; retract BLTouch
deployprobe:
; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Wed May 26 2021 12:43:50 GMT+0200 (Mitteleuropäische Sommerzeit)
M280 P0 S10 ; deploy BLTouch
i am sending everything through the duet web control overlay
also, I am using the latest BL-Touch (V3.1)
Here is a picture of my (temporary) wiring of the BL (connected to Duet 3 MB6HC, IO-Port 7). Is this wrong? I may be dumb.
Another important thing: if I first manually deploy the probe with M280 P0 S10 and then home, it works andthe z-axis goes up as soon as the bl touch touches the surface (but the pin does not retract here). So, when I command a G29 AFTER that, it will say: "error: zprobe not triggered during probing" or something like that. So in conclusion, the first homing works after deploying the pin with M280 P0 S10 and after that, it doesnt work at all.

Greetings

undefined

Hi.
I am currently configuring a custom 3D printer and so far have overcome all of the other problems and am now at my wits end regarding my BL-Touch...

->Problem description:
When turning on my machine, the Probe does its automatical restract-and-deploy test 2 times, like it should. Afterwards, it turns red (constant, not blinking). M401 and M402 do what the should do. But when I call G30 OR G29 to home, the Pin won't deploy on its own, so if I wouldnt hit the Emergency-Stop, the hotend would crash down into the bed (since Z-axis is moving).
my M115 says Reprap 3.2.2
my config, my homeall and homez
homez.g homeall.g config.g

I would be extremely grateful for your help as I am under time pressure; and since this is the last thing to adjust before a first testprint, I am quite unnerved.

Looking forward to your answers

EDIT:
I forgot to mention quite a few things:
I am using Duet 3 MB6HC and the reprapfirmware-online-configtool

Also I did the wiring according to this guide on duet dozuki:
connect bltouch.png
so my black (endstopground) and brown (powerground) cable are connected immediatly after the bl touch (not quite sure if this could give me a problem, thats why im mentioning it here)

EDIT END