Potential firmware issue - bltouch

Alex.cr

My Bltouch does not deploy when G30 is called.

Current setup: Pi4+6HC+3HC both confirmed running 3.3b2 through M115. (also tried to downgrade to 3.2.2 and had same results) This is a genuine V3.1 Bltouch that worked without issues in a previous setup with the 6HC and a toolboard. The pi and 3HC are new.

The Bltouch will respond 100% reliably with M401 and M402 is sent through console. All self tests and alarm resets while using the M280 command work properly. When power is applied it performs the self test without issue.

I have tried calling G30 in the console and it is obviously called during homez.g

Here is the fun part, if I home X and Y using their individual commands, M401 no longer responds. If I fire M401 before I home X and Y, then use G30 (obviously the probe is deployed at this point) the machine moves down in Z andresponds correctly (rapids up) after I trigger the probe.

I included a debug echo command in deploy.g and it does not write to the console during G30.

Any thoughts? I out of ideas for what the issue could be.

When running M98P"config.g" it returns two errors that are unrelated to this problem, they are because my PT100 daughterboard appears to be fried.

config.g

; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
;Voron 2.4 config 350x350x350mm
;Hardware: Duet3 6HC+3HC, mosquito hotend, bltouch

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

M80										           ; turn off ATX supply for safety (and trigger button on DWC)
G4 S5                                              ; wait for Canbus to stabilize 
; --- drive map ---
;    _______
;   | 3 | 4 |
;   | ----- |
;   | 2 | 5 |
;    -------
;     front

; Drives
M569 P0.0 S0                                       ; physical drive 0.0 goes forwards (A Stepper)
M569 P0.1 S0                                       ; physical drive 0.1 goes forwards (B Stepper)
M569 P0.2 S0                                       ; physical drive 0.2 goes forwards
M569 P0.3 S1                                       ; physical drive 0.3 goes backwards
M569 P0.4 S0                                       ; physical drive 0.4 goes forwards
M569 P0.5 S1                                       ; physical drive 0.5 goes backwards
M569 P1.0 S0                                       ; physical drive 1.0 goes forwards (E Stepper)

M584 X0.1 Y0.0 Z0.2:0.3:0.4:0.5 E1.0               ; set drive mapping
M350 X16 Y16 Z16 E16 I1                            ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.0 E415.00                   ; set steps per mm 
M906 X1200 Y1200 Z1200 E800 I50                    ; set motor currents (mA) and motor idle factor in per cent
M84 S120                                           ; Set idle timeout

; Accelerations and speed
M98 P"/macros/print_scripts/speed_normal.g"


; Axis Limits
M208 X0 Y0 Z0 S1                                    ; set axis minima
M208 X350.0 Y350.0 Z350.0 S0                        ; set axis maxima

; Endstops
M574 X2 S1 P"0.io2.in"                               ; configure active-high endstop for high end on X via pin io0.in
M574 Y2 S1 P"0.io1.in"                               ; configure active-high endstop for high end on Y via pin io3.in
M574 Z0                                			     ; No Z endstop

; BLTouch
M950 S0 C"0.io7.out"                                 ; create servo pin 0 for BLTouch
M558 P9 C"0.io7.in" H5 A3 S0.005 F120 T9000 K0       ; set Z probe type to bltouch and the dive height + speeds (probe 3 times and average)
G31 K0 P25 X0.0 Y23.23 z3.5					     ; set Z probe trigger value, offset and trigger height, 
M557 X25:325 Y25:325 S50                          	 ; define mesh grid

; Nozzle Height sensor
;M558 P8 C"0.io3.in" H5 A1 F120 T6000 K1             ; set Z probe type to unfiltered digital and the dive height + speeds 
;G31 K1 P500 Z-4.0						  		    ; set Z probe trigger value, offset and trigger height (3.35 was old value)

; Bed leveling
M671 X-65:-65:415:415 Y-10:450:450:-10 S20         ; Define Z belts locations (Front_Left, Back_Left, Back_Right, Front_Right)

; Heaters
;bed heater - dual sensor config 
;hex stud thermistor: https://www.amazon.com/gp/product/B07Q5MKSLS/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
M308 S0 P"0.temp0" Y"thermistor" T100000 B3950 C0.0 A"Build Plate Temp" ; configure sensor 0 as thermistor on pin temp0 
;Built in Keenovo sensor
M308 S1 P"0.temp1" Y"thermistor" T100000 B4725 C7.06e-8 A"Bed Heater Temp" ; configure sensor 0 as thermistor on pin temp1
M950 H0 C"0.out0" T0 Q60                                ; create bed heater output on out0 and map it to sensor 0
M307 H0 B0 S1.0                                   ; disable bang-bang mode for the bed heater and set PWM limit
M307 H0 R0.450 C420.1 D1.06 S1.00 
M140 H0                                            ; map heated bed to heater 0
M143 H0 S120                                       ; set temperature limit for build plate to 120C
M143 H0 T1 P1 S125 A2                             ; Monitor heater thermistor, if temp goes above 125C temporarily turn off
M143 H0 T1 P2 S132 A3                             ; Monitor heater thermistor, if temp goes above 132C cut "atx" supply


;Extruder T0 heater
;Slice Engineering 50W heater+ E3d PT100
M308 S2 P"1.spi.cs0 Y"rtd-max31865" A"T0" 	; configure sensor 2 as PT100 on SPI
M950 H1 C"1.out0" T2                                 ; create nozzle heater output on out1 and map it to sensor 2
M307 H1 B0 S1.00                                   ; disable bang-bang mode for the nozzle heater and set PWM limit
M307 H1 R3.009 C152.2:145.8 D3.17 S1.00 V24.0
M143 H1 S300                                       ; set temperature limit for heater 1 to 300C

;Chamber Monitors
;Thermisors below: https://www.amazon.com/gp/product/B07D9LSKWK/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1
M308 S3 P"0.temp3" Y"thermistor" T100000 B4725 C7.06e-8 A"Chamber Upper Temp"
M308 S4 P"0.temp2" Y"thermistor" T100000 B4725 C7.06e-8 A"Chamber Gantry Temp"  ; configure sensor 2 as thermistor on pin temp2			
M308 S10 P"0.spi.cs1" Y"dht22"       A"Chamber Lower Temp"    ; define DHT22 temperature sensor
M308 S11 P"S10.1"     Y"dhthumidity" A"Chamber Hum[%]"  ; Attach DHT22 humidity sensor to secondary output of temperature sensor


;mcu calibration
M308 S7 Y"mcu-temp" A"MCU"                               ; configure MCU as sensor 3
M912 P0 S-13.6                                     ; set CPU temp correction


; Fans/LEDs
;part cooling fan
M950 F0 C"1.out7" Q500                             ; create fan 0 on pin out1 and set its frequency
M106 P0 S0 H-1 L2 C"Part fan"                                   ; set fan 0 value. Thermostatic control is turned off
;main extruder cooling fan
M950 F1 C"1.out6" Q500                               ; create fan 1 on pin 20.out1 and set its frequency
M106 P1 S255 H1 T45 C"Extruder fan"                                 ; set fan 1 value. Thermostatic control is turned on
;Electronic cooling fan
M950 F2 C"0.out7" Q100                              ; create fan 2 on pin out7 and set its frequency
M106 P2 S.25 H-1
;M106 P2 L0.5 X1 H7 T26:32 C"MCU fans"                                   ; set fan 2 value. Thermostatic control is turned on
;Main LEDs
M950 F3 C"0.out4" Q500                               ; create fan 3 on pin out4 and set its frequency
M106 P3 S0 H-1 C"Lights"                                    ; set fan 3 value. Thermostatic control is turned off
;Filter fan
M950 F4 C"0.out8" Q500                               ; create fan 4 on pin out8 and set its frequency
M106 P4 S0 H-1 C"Filter Fan"                                   ; set fan 4 value. Thermostatic control is turned off


; Tools
M563 P0 S"Tool 0" 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
;M591 D0 P7 C"io6.in" S0 E51 L2.1 R50:150          ; create filament monitor for Tool 0
M572 D0 S0.00                                      ; default pressure advance for Tool 0
M592 D0 A0.0 B0.00 L0.2                            ; Nonlinear extrusion Tool 0
;M593 F34.48                                        ; Cancel ringing

Work Offsets:
G10L2P1 X0.0Y0.0Z0.0  ;Set G54 offset to be machine coordinates
G10L2P7 X0.0Y0.0Z0.0  ;use G59.1 for tool height probing Z zero is top of the setter when not pressed
G10L2P8 X0.0Y0.0Z0.0  ;use G59.2 for nozzle cleaning, center of brush, top of brush

; Motor Stall Detect
M915 X S0 F1 H200 R1
M915 Y S0 F1 H200 R1
M915 Z S0 F1 H200 R1

; Miscellaneous
M115
M115 B1										   ;Check status of Can-FD exansion board
M911 S19 R22 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
M207 S0.4 R0.0 F3600 T3600 Z1.0                    ; set default retraction settings

G54
T0                                                 ; select first tool
;G31 K0 												;select Bltouch by default
M106 P3 S255 									   ; turn on lights

;M564 H0 S0; Allow movement outside of max/min and allow movment without homing

;Random Notes---------------------------------------------------------------------------------------------------------------------
;wget -q https://pkg.duet3d.com/duet3d.gpg
;wget -q https://pkg.duet3d.com/duet3d-unstable.list
;sudo mv duet3d.gpg /etc/apt/trusted.gpg.d/
;sudo mv duet3d-unstable.list /etc/apt/sources.list.d/duet3d-unstable.list
;sudo chown root:root /etc/apt/trusted.gpg.d/duet3d.gpg
;sudo chown root:root /etc/apt/sources.list.d/duet3d-unstable.list
;sudo rm /etc/apt/sources.list.d/duet3d.list
;sudo apt-get update
;sudo apt-get upgrade
;(may need: sudo apt-get dist-upgrade) 

;Webcam
;full interface http://voron.local:8080/
;minimal interface http://voron.local:8080/html/min.php

deployprobe.g

; deployprobe.g
; called to deploy a physical Z probe

; generated by RepRapFirmware Configuration Tool v2.1.4 on Mon Dec 23 2019 11:14:30 GMT-0500 (Eastern Standard Time)
M280 P0 S10 ; deploy BLTouch
echo sensors.probes[0].deployedByUser ; what is happening

retractprobe.g

; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v2.1.4 on Mon Dec 23 2019 11:14:30 GMT-0500 (Eastern Standard Time)
M280 P0 S90 ; retract BLTouch

homeall.g

; homeall.g
; called to home all axes
;

G91                   ; relative positioning
;G31 K0 													  ; select Bltouch
M561                                                      ; Clear any bed transform
G1 H2 Z10 F2000
M98 P"/macros/print_scripts/speed_homing.g"   			  ; Setup low speed & accel

G1 X600 Y600 F2400 H1   ; Coarse home X or Y
G1 X600 H1 			 ; Coarse home X
G1 Y600 H1   		 ; Coarse home Y
G1 X-5 Y-5 F9000     ; Move away from the endstops
G1 X600 F360 H1  	 ; Fine home X
G1 Y600 H1  		 ; Fine home Y

G90;
M98 P"homez.g"  ; home Z using the home Z file
M98 P"/macros/print_scripts/speed_normal.g"   			  ; Setup normal speed & accel

G1 Z20.0
M98 P"/macros/print_scripts/goto_bucket.g"   			  ; Go to park position
G29 S1 ; load bed map

homez.g

; homez.g
; called to home the Z axis
;
G90
G54
;G31 K0 													  ; select Bltouch
M98 P"/macros/print_scripts/speed_homing.g"   			  ; Setup low speed & accel
G0 X175.0 Y175.0 F9000
;M401
G30 K0
;M402
M98 P"/macros/print_scripts/speed_normal.g"   			  ; Setup normal speed & accel
G01 Z20.0 F20000

homex.g

; homex.g
; called to home the X axis
;
G91              ; relative positioning
M98 P"/macros/print_scripts/speed_homing.g"   			  ; Setup low speed & accel
G1 H1 X600 F2200 ; move quickly to X axis endstop and stop there (first pass)
G1 H0 X-5 F6000  ; go back a few mm
G1 H1 X600 F360  ; move slowly to X axis endstop once more (second pass)
G90              ; absolute positioning
M98 P"/macros/print_scripts/speed_normal.g"   			  ; Setup normal speed & accel

homey.g

; homey.g
; called to home the Y axis
;
G91              ; relative positioning
M98 P"/macros/print_scripts/speed_homing.g"   			  ; Setup low speed & accel
G1 H1 Y600 F2200 ; move quickly to Y axis endstop and stop there (first pass)
G1 H0 Y-5 F6000  ; go back a few mm
G1 H1 Y600 F360  ; move slowly to Y axis endstop once more (second pass)
G90              ; absolute positioning
M98 P"/macros/print_scripts/speed_normal.g"   			  ; Setup normal speed & accel

;speed_normal.g

M913 X100 Y100 Z100                ;set motor currents normal
M566 X900 Y900 Z60 E8000 P1       ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z3000 E15000 ; Set maximum speeds (mm/min)
M201 X2000 Y2000 Z250 E1800     ; Set maximum accelerations (mm/s^2) 
M204 P1500 T2000                ; Set printing acceleration and travel accelerations

;speed_homing.g

M913 X60 Y60 Z40                ;set motor currents low
M566 X900 Y900 Z20 E3600        ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z3000 E5000  ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z100 E800      ; Set maximum accelerations (mm/s^2)

M122 response:

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3beta2 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
Board ID: 08DJM-956L2-G43S4-6J1FD-3SJ6T-TB6QH
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 148476
Dynamic ram: 62248 of which 0 recycled
Never used RAM 143468, free system stack 184 words
Tasks: SENSORS(delaying,51) Linux(resourceWait,147) HEAT(delaying,324) CanReceiv(notifyWait,798) CanSender(notifyWait,374) CanClock(delaying,343) TMC(notifyWait,92) MAIN(running,943) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:13:39 ago, cause: software
Last software reset at 2021-04-14 22:26, reason: User, none spinning, available RAM 144076, slot 2
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 20.7, current 20.9, max 35.6
Supply voltage: min 3.5, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 0.5, current 12.2, max 12.2, under voltage events: 1
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, reads 19622, writes 28 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 19622, writes 28 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 19622, writes 28 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 19622, writes 28 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 19623, writes 28 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 19623, writes 28 timeouts 0, SG min/max 0/0
Date/time: 2021-04-14 22:40:09
Slowest loop: 0.47ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, 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 doing "M122" 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.
=== CAN ===
Messages queued 7350, send timeouts 12, received 6490, lost 0, longest wait 1ms for reply type 6018, peak Tx sync delay 50220, free buffers 49 (min 48)
Last cancelled message type 30 dest 127
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 1ms ago
RX/TX seq numbers: 31105/31105
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2d52c
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.3-b2
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 38.05
Codes per second: 0.11
Maximum length of RX/TX data transfers: 3028/712

Phaedrux

If it deploys and retracts fine before moving, but not after moving, that makes me think it's the moving that is causing a loose wire or something.

Instead of homing X and Y can you turn the motors off and then gently position the print head by hand and then send G30/M401/M402 to test if it's a positional problem?

If you need to force it to be homed first send G92 X100 Y100 Z100 to trick it into being homed.

dc42

@alex-cr, it's also worth running M558 without parameters, to check that the BLTouch is properly configured on the correct input pin as probe type 9.

Alex.cr

@dc42 said in Potential firmware issue - bltouch:

@alex-cr, it's also worth running M558 without parameters, to check that the BLTouch is properly configured on the correct input pin as probe type 9.

It looks like it has taken most information correctly. Should it return "output pin nil" ? I can't find any info for this.

Alex.cr

@phaedrux said in Potential firmware issue - bltouch:

If it deploys and retracts fine before moving, but not after moving, that makes me think it's the moving that is causing a loose wire or something.

I was thinking wiring as well at first but no matter how I move my probe, as long as I don't use my homex/homey or homeall programs I can get the probe to deploy using M401. I even faked the endstop locations so the homez G30 move was not in the center of the bed and no dice.

Instead of homing X and Y can you turn the motors off and then gently position the print head by hand and then send G30/M401/M402 to test if it's a positional problem?

If you need to force it to be homed first send G92 X100 Y100 Z100 to trick it into being homed.

The probe will deploy after the G92 line to home it. No matter where the head is, no matter how far it has moved.
I ran a run-in program to exercise the wiring. I homed XY using the home commands and no luck with G30. In the same exact X and Y position I fire G92 X100 Y100 and it will deploy the probe after that.

Alex.cr

@dc42 @Phaedrux

So I got out an oscilloscope to measure the and watch the signal coming from the duet to the Bltouch. The Duet is doing what it is supposed to do, when its supposed to do it. Now I have to figure out why the Bltouch chooses not to respond only during homing commands. I rewired the whole device, temporarily removing as many plugs from the setup as I could and still have the same issue.

Thanks for the help. Disregard my initial concerns.

jay_s_uk

@alex-cr

if it works when the motors aren't energised but fails when they are then one of the motors is generating some electrical interference thats interfering with the signals from the duet.
I would suggest as a first step, changing the wiring on the bltouch so the cables running to it don't run by anything else. if that works then look at changing the routing of your cabling or shielding your motor cables

o_lampe

@alex-cr said in Potential firmware issue - bltouch:

Now I have to figure out why the Bltouch chooses not to respond only during homing commands.

Did you check the 5V rail after homing XY? Maybe it is pulled low because of some endstop issues?

Alex.cr

@jay_s_uk said in Potential firmware issue - bltouch:

@alex-cr

if it works when the motors aren't energised but fails when they are then one of the motors is generating some electrical interference thats interfering with the signals from the duet.
I would suggest as a first step, changing the wiring on the bltouch so the cables running to it don't run by anything else. if that works then look at changing the routing of your cabling or shielding your motor cables

It works while the motors are running/energized. If I fire G92 X0 Y0 and then fire G30 it works great, regardless of where it is located in the travel. It only does not work after running any of the home.g files. This is why I thought it was a firmware issues to start. Thanks for the suggestion though. See my O-scope results below.

I also ran cables outside of the cable chains to test and have the same result.

@o_lampe said in Potential firmware issue - bltouch:

@alex-cr said in Potential firmware issue - bltouch:

Now I have to figure out why the Bltouch chooses not to respond only during homing commands.

Did you check the 5V rail after homing XY? Maybe it is pulled low because of some endstop issues?

Good thought. Here's my analysis for that.

I did check the 5V rail after running homing commands. It shows 4.8xx volts using my Fluke 117 meter. So I decided to break out my oscilloscope and see what I could find. With the exception of the ground, the scope is hooked up as close to the Bltouch as I can manage.

This first image shows what the M401 command looks like without any motors on, probe did deploy successfully. Yellow is the signal to the Bltouch and blue is the 5v rail.

Notice the difference in vertical channel heights in the upper left hand corner. The yellow peak to peak voltage is about 2.93 volts. The blue peak to peak voltages at this state are about 10-20mV.

The next image shows the oscilloscope while performing a homeall.g command at the point when the G30 has fired to home the machine in Z. The probe did not deployed here. Same voltage peak to peak for the Bltouch signal line. The Bltouch was getting the correct command. In fact the parameters at the bottom of the screen for channel 1 show very little change.

The 5v rail only shows about 200mV peak to peak now. So a bit of noise but nothing I would consider major. In fact both rails show the same about of "noise" in them. It just looks way worse for the 5V rail because of the vertical resolution I had everything set to.

Does 200mV of noise in the 5V line really something to shake a stick at? I guess its time to see what my other printers are running into.

Phaedrux

Only thing that sticks out to me is that you define the probe as K0 but only have a single probe. Can you try removing the instances of K0?

You're also using G54 in your homez. Why is that?

Alex.cr

@phaedrux

I will have two other coordinate systems defined. G59.1 and G59.2 for nozzle cleaning and a nozzle height probe. My hope is to get another stationary probe running on K1(hence the bltouch being defined as K0). If you see I have my nozzle height sensor commented out at this time in my config, right below the bltouch setup. So every time a sub is called where the program needs to move to a specific point i want to make sure the proper coordinate system is called, this is why G54 is called as it will be the standard work coordinate system. This is very similar to how I have my work CNCs setup. I was hoping to follow "similar" systems.

I have removed all instances of K0 and K1 in my config and still have the same issue. I will try commenting out G54 and see if that helps. I am really hoping to be able to use the coordinate systems though so lets hope that doesn't fix it...

I have purchased another bltouch and it it on its way. I also have a shielded wire bundle on its way as well.
I am at a loss at this point. I don't think the Duet is doing anything wrong as it is very clearly sending the proper commands.

o_lampe

@alex-cr
There is a missing semicolon, might cause some irritations?

M592 D0 A0.0 B0.00 L0.2                            ; Nonlinear extrusion Tool 0
;M593 F34.48                                        ; Cancel ringing

 

Work Offsets:      <= HERE
G10L2P1 X0.0Y0.0Z0.0  ;Set G54 offset to be machine coordinates
G10L2P7 X0.0Y0.0Z0.0  ;use G59.1 for tool height probing Z zero is top of the setter when not pressed
G10L2P8 X0.0Y0.0Z0.0  ;use G59.2 for nozzle cleaning, center of brush, top of brush

Wouldn't it make more sense to check CAN-bus right after 'M80' in config.g?

 

; Miscellaneous  <= very late in config.g?

M115
M115 B1										   ;Check status of Can-FD exansion board

Alex.cr

@o_lampe said in Potential firmware issue - bltouch:

@alex-cr
There is a missing semicolon, might cause some irritations?

Nice catch! unfortunately it did not make a difference. It also never triggered an error when running an m98P"config.g" so that's interesting.

Wouldn't it make more sense to check CAN-bus right after 'M80' in config.g?

This is mainly for me to be able to easily see which firmware is running on the boards so I can double check that they match. But not a bad idea.

Alex.cr

I have singled down the issue to stepper noise. I have never had this problem before even on similar machines with similar wire runs. Now to figure out how to solve this...

Phaedrux

Do you have your steppers grounded?

Alex.cr

@phaedrux said in Potential firmware issue - bltouch:

Do you have your steppers grounded?

They are not currently but I did install jumpers and grounded them and it had no effect.

I swapped the bltouch into another machine that is working and it worked great. A spare bltouch just showed up today but it is behaving just like all of the others.

Next step I am going to run a completely new harness for the bltouch that does not pass any of the stepper motors and see if I can get that to work. I also have shielded cable coming but I really hope I don't have to use that.

Nuramori

@alex-cr said in Potential firmware issue - bltouch:

M558 P9 C"0.io7.in" H5 A3 S0.005 F120 T9000 K0

This should have the pull up resistor enabled. It’s a commonly overlooked issue with bltouch installations.

Try this instead. Note the caret.

M558 P9 C"^0.io7.in" H5 A3 S0.005 F120 T9000 K0