Z-Probe dig into bed

Phaedrux

Electrical loop from the connector out of the board is fully closed when the nozzle toutches the bed. Got 0.5ohms

What port are you using on the board?

Can you post the results of M122 and M98 P"config.g" as well as the contents of your config.g and homing macros just for a sanity check?

It would seem to me to be a wiring/continuity issue.

b3nitro

@phaedrux thank you I will check that on monday

Just so you know I also tested the following, continuity at the connector when unplugged fron the board and probe toutching the bed: all good

With power on, probe in the air grnd to nozzle a have 3.3v

There are resistor in the connector on the board, they read 4.7 and 10k if I remember right

I'll get result of what you asked early next week, thank you for your help!

b3nitro

@Phaedrux

Here is the config.g and output commands as file

Thank you!

M98 P"config.g"
Macro file "config.g" not found.

config.g.txt
m122.cmd.txt

; Fusion3 F410 Firmware configuration file
; For FusionWare 1.18.1
; Revision 2018.08.22
; For Serial Number 5465

M111 S0                             	; Debug off
M550 PFusion3 F410		        		; Machine name MUST HAVE A "P" IN FRONT OF IT(can be anything you like)
M551 Pfusion3                       	; Machine password MUST HAVE A "P" IN FRONT OF IT
M540 P0xBE:0xEF:0xDE:0xAD:0x54:0x65 	; MAC Address (replace last 2 blocks with 4 digit s/n)
;=== Adjust the following 3 lines to suit your network ===
M552 P0.0.0.0 S1						; IP address (0 = use DHCP)
M554 P192.168.1.1                   	; Gateway
M553 P255.255.255.0                 	; Netmask
;=========================================================
M555 P2                             	; Set output to look like Marlin
M575 P1 B57600 S1						; comms params for paneldue

; Machine configuration
M569 P0 S1							; Drive 0 goes forwards
M569 P1 S0							; Drive 1 goes backwards
M569 P2 S0							; Drive 2 goes backwards
M569 P3 S0							; Drive 3 goes backwards
M569 P4 S0							; Drive 4 goes backwards
M574 X1 Y1 Z2 S1					; set endstop configuration
M667 S1								; set CoreXY mode
M92 X43.70 Y43.70 Z426.67 E190.0	; set axis steps/mm
M906 X1300 Y1300 Z1400 E1400 I100   ; Set motor currents (mA)
M201 X2000 Y2000 Z300 E4000	        ; Accelerations (mm/s^2)
M203 X33000 Y33000 Z2500 E10000     ; Maximum speeds (mm/min)
M566 X600 Y600 Z40 E950	     		; Maximum jerk speeds mm/minute
M208 X355 Y355 Z315					; set axis maxima
M208 X0 Y0 Z0 S1					; set axis minima 
G21									; work in mm
G90									; absolute coords
M83									; relative extruder movements

; Z probe
M558 P5 X0 Y0 Z0 H7 F100            ; Set probe type and if it's used for axis homing (no in our case)
G31 Z0.10 P600                      ; Set the probe height and threshold (smaller number = further away from bed)

; Thermistors and heaters
M305 P0 T100000 B4036 R4700 				
M305 P1 T100000 B4725 C7.06e-8 R4700 		
M305 P2 T100000 B4725 C7.06e-8 R4700 

M307 H0 A153.5 C534.2 D6.7 B0			; Configure H0 (bed) heater model
M307 H1 A483.4 C190.2 D6.6 B0			; Configure H1 (print head) heater model

M143 S320								; Set max print head temperature
M143 H0 S140							; Set max heat bed temperature
M570 H1 P10 T15							; Configure heater safety timeouts

; Tool definition
M563 P0 D0 H1                       ; Define tool 0
G10 P0 S0 R0		                ; Set tool 0 operating and standby temperatures
M563 P2 H0							; define heat bed tool
G10 P2 S0 R0						; define heat bed tool op and standby temps
;M572 D0 S0.20

; Configure filament monitor
M581 T2 E0 S0 C1

; Reset filament monitor when the board is rebooted
M42 P63 S0
G4 P50
G4 P50
M42 P63 S1

T0									; select first hot end

M122
=== Diagnostics ===
Used output buffers: 2 of 32 (22 max)
=== Platform ===
Static ram used: 24996
Dynamic ram used: 89780
Recycled dynamic ram: 4008
Stack ram used: 1104 current, 3876 maximum
Never used ram: 8412
Last reset 00:03:37 ago, cause: power up
Last software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Spinning module during software reset: GCodes, available RAM 8408 bytes (slot 2)
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 19.7, current 28.3, max 29.3
Supply voltage: min 23.4, current 23.4, max 23.5, under voltage events: 0, over voltage events: 0
Driver 0: standstill
Driver 1: standstill
Driver 2: standstill
Driver 3: standstill
Driver 4: standstill
Date/time: 2021-06-28 08:56:12
Slowest main loop (seconds): 0.607727; fastest: 0.000039
=== Move ===
MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
Code queue is empty.
=== Network ===
State: 4
=== Webserver ===
HTTP sessions: 1 of 8
FTP connections: 0, state 0
Telnet connections: 0, state 0

b3nitro

Forgot the homing scripts

homez.g homey.g homex.g

; ====================
; === Fusion3 F410 ===
; ====================
;
; X axis homing file
; Revision 3-22-16
;
G91
G1 Z0.5 F400
G1 X-500 F3000 S1
G1 X4 F600
G1 X-10 S1
G1 Z-0.5 F400
G90

; ====================
; === Fusion3 F410 ===
; ====================
;
; Y axis homing file
; Revision 3-22-16
;
G91
G1 Z0.5 F400
G1 Y-500 F3000 S1
G1 Y4 F600
G1 Y-10 S1
G1 Z-0.5 F400
G90

; ====================
; === Fusion3 F410 ===
; ====================
;
; Z axis homing file
; Revision 3-22-16
;
G91
G1 Z400 F500 S1
G1 Z-4 F200
G1 Z10 S1
G90

Phaedrux

Can you also send M115 to report the firmware version? It appears you're using a quite old version.

b3nitro

@phaedrux

Here it is

M115
FIRMWARE_NAME: RepRapFirmware for Duet Ethernet FIRMWARE_VERSION: Fusionware 1.18.1 RC2 ELECTRONICS: Duet Ethernet 1.0 FIRMWARE_DATE: 2017-05-15

Phaedrux

Yes that's quite ancient. However, I don't think that's the issue at hand.

There must be an electrical issue. Do you happen to have a normal endstop switch you could connect to the same port to test with?

As I'm not at all familiar with the Fusion printers am at a bit of a loss. Do they have support options as well?

b3nitro

@phaedrux

There is no normal endstop, the bed stop about 1cm before the nozzle, slow down until it toutches to calculate z-height

I'm on support with them, they say its the wiring harness or the pull up resistor BUT the wiring harness loop got conductivity and the pullup resistors are giving me 10k and 2.2k so I doubt its the issue.. I feel its the board

Phaedrux

Which connector on the board are you using?

b3nitro

@phaedrux

The one labelled "probe"

b3nitro

@Phaedrux

Got a little of success here, if I bypass the whole loop with a jumper wire while probing, the board get the connection and is going to the next step

That means the issue is in the wiring between 3.3v out of the board "probe" port after the pullup resistor AND before board probe input

Must be something with heat or vibration as the loop was "good" with ohmeter

Thanks for your help, I'll keep you posted

b3nitro

@Phaedrux

Looks like the thermistor is the culprit even while its still working

Noticed I had 3.003v at the board but 3.297 at nozzle to bed, figured out I must have voltage leakout somewhere, unplugged heater didnt change, unplugged thermistor triggered heater fault but voltage dropped to 3.003v as the board output

Ran a bed leveling without thermistor and its working!

Need to find out what type of sensor they use to change it!

b3nitro

Done deal, swapped the thermistor and everything works flawlessly now!