Closed mattydboom closed 3 weeks ago
Try it with debugging on. like this.
$message/level=debug
ok
$hy
[MSG:DBG: Homing Cycle Y]
[MSG:DBG: Y Axis StealthChop]
[MSG:DBG: Y2 Axis StealthChop]
[MSG:DBG: Homing nextPhase FastApproach]
[MSG:DBG: Starting from 0.000,0.000,0.000]
[MSG:DBG: Planned move to 0.000,-1100.000,0.000 @ 2000.000]
[MSG:DBG: Y Neg Limit 1]
[MSG:DBG: Homing limited Y]
[MSG:DBG: Y2 Pos Limit 1]
[MSG:DBG: Homing limited Y Y2]
[MSG:DBG: Homing nextPhase Pulloff0]
[MSG:DBG: Starting from 0.000,-4.080,0.000]
[MSG:DBG: Planned move to 0.000,-0.080,0.000 @ 2000.000]
[MSG:DBG: Y Neg Limit 0]
[MSG:DBG: Y2 Pos Limit 0]
[MSG:DBG: CycleStop Pulloff0]
[MSG:DBG: Homing nextPhase SlowApproach]
[MSG:DBG: Starting from 0.000,-0.080,0.000]
[MSG:DBG: Planned move to 0.000,-4.480,0.000 @ 2000.000]
[MSG:DBG: Y2 Pos Limit 1]
[MSG:DBG: Homing limited Y2]
[MSG:DBG: Y Neg Limit 1]
[MSG:DBG: Homing limited Y Y2]
[MSG:DBG: Homing nextPhase Pulloff1]
[MSG:DBG: Starting from 0.000,-4.040,0.000]
[MSG:DBG: Planned move to 0.000,-0.040,0.000 @ 2000.000]
[MSG:DBG: Y Neg Limit 0]
[MSG:DBG: Y2 Pos Limit 0]
[MSG:DBG: CycleStop Pulloff1]
[MSG:DBG: Homing nextPhase Pulloff2]
[MSG:DBG: mpos was 0.000,-0.040,0.000]
[MSG:Homed:Y]
[MSG:DBG: mpos becomes 0.000,0.000,0.000]
[MSG:DBG: mpos transformed 0.000,0.000,0.000]
[MSG:DBG: Y Axis StealthChop]
[MSG:DBG: Y2 Axis StealthChop]
[MSG:DBG: Homing done]
ok
OK see below running on v3.9.0, doesn't seem to differentiate the two Y axis from one another. (The Alarms are me hitting the estop before it tears the axis apart!)
$message/level=debug
ok
$hy
[MSG:DBG: Homing Cycle Y]
[MSG:DBG: Homing nextPhase FastApproach]
[MSG:DBG: Starting from 0.000,0.000,0.000]
[MSG:DBG: Planned move to 0.000,-1386.000,0.000 @ 3000.000]
[MSG:DBG: Y Neg Limit 1]
[MSG:DBG: Homing limited Y]
[MSG:DBG: Y Neg Limit 0]
[MSG:DBG: Y Neg Limit 1]
[MSG:DBG: Homing limited Y]
[MSG:DBG: Y Neg Limit 0]
[MSG:DBG: estop_pin 1]
[MSG:INFO: Stopped by estop_pin]
[MSG:INFO: ALARM: Hard Stop]
ALARM:13
ALARM:13
[MSG:ERR: Reset to continue]
ok
Here is the same but running on v3.8.4-pre9 where it homes just fine:
$message/level=debug
ok
$hy
[MSG:DBG: Homing Cycle Y]
[MSG:DBG: Homing nextPhase FastApproach]
[MSG:DBG: Starting from 0.000,0.000,0.000]
[MSG:DBG: Planned move to 0.000,-1386.000,0.000 @ 3000.000]
[MSG:DBG: Y Neg Limit 1]
[MSG:DBG: Homing limited Y]
[MSG:DBG: Y2 Neg Limit 1]
[MSG:DBG: Homing limited Y Y2]
[MSG:DBG: Homing nextPhase Pulloff0]
[MSG:DBG: Starting from 0.000,-632.056,0.000]
[MSG:DBG: Planned move to 0.000,-631.056,0.000 @ 100.000]
[MSG:DBG: Y Neg Limit 0]
[MSG:DBG: Y2 Neg Limit 0]
[MSG:DBG: CycleStop Pulloff0]
[MSG:DBG: Homing nextPhase SlowApproach]
[MSG:DBG: Starting from 0.000,-631.056,0.000]
[MSG:DBG: Planned move to 0.000,-632.156,0.000 @ 100.000]
[MSG:DBG: Y2 Neg Limit 1]
[MSG:DBG: Homing limited Y2]
[MSG:DBG: Y Neg Limit 1]
[MSG:DBG: Homing limited Y Y2]
[MSG:DBG: Homing nextPhase Pulloff1]
[MSG:DBG: Starting from 0.000,-631.681,0.000]
[MSG:DBG: Planned move to 0.000,-630.681,0.000 @ 100.000]
[MSG:DBG: Y2 Neg Limit 0]
[MSG:DBG: Y Neg Limit 0]
[MSG:DBG: CycleStop Pulloff1]
[MSG:DBG: Homing nextPhase Pulloff2]
[MSG:DBG: mpos was 0.000,-630.681,0.000]
[MSG:Homed:Y]
[MSG:DBG: mpos becomes 0.000,0.000,0.000]
[MSG:DBG: mpos transformed 0.000,0.000,0.000]
[MSG:DBG: Homing done]
ok
Your startup messages are from pre9. Can you show the messages from 3.9?
I see no evidence of second switch in the debug. Try manually triggering each switch when you are in debug mode. it should look something like this.
[MSG:DBG: Y Neg Limit 1]
[MSG:DBG: Limit switch tripped for Y motor 0]
[MSG:DBG: Y Neg Limit 0]
[MSG:DBG: Y2 Neg Limit 1]
[MSG:DBG: Limit switch tripped for Y motor 1]
[MSG:DBG: Y2 Neg Limit 0]
Start-up messages with v3.9.0 reinstalled:
$G
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
ok
$SS
<Alarm|MPos:0.000,0.000,0.000|FS:0,0|Ov:100,100,100>
[MSG:INFO: FluidNC v3.9.0 https://github.com/bdring/FluidNC]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: Configuration file:DatumCAD_UltimateBee.yaml]
[MSG:INFO: Machine DatumCAD UltimateBee]
[MSG:INFO: Board Root Controller ISO]
[MSG:INFO: UART1 Tx:gpio.17 Rx:gpio.16 RTS:gpio.4 Baud:9600]
[MSG:INFO: I2SO BCK:gpio.22 WS:gpio.21 DATA:gpio.12]
[MSG:INFO: SPI SCK:gpio.18 MOSI:gpio.23 MISO:gpio.19]
[MSG:INFO: SD Card cs_pin:gpio.5 detect:NO_PIN freq:8000000]
[MSG:INFO: Stepping:I2S_STREAM Pulse:4us Dsbl Delay:3us Dir Delay:1us Idle Delay:255ms]
[MSG:INFO: User Digital Output: 0 on Pin:I2SO.20]
[MSG:INFO: User Digital Output: 1 on Pin:I2SO.21]
[MSG:INFO: User Digital Output: 2 on Pin:I2SO.22]
[MSG:INFO: User Digital Output: 3 on Pin:gpio.13]
[MSG:INFO: Axis count 3]
[MSG:INFO: Axis X (0.000,740.000)]
[MSG:INFO: Motor0]
[MSG:INFO: standard_stepper Step:I2SO.7:low Dir:I2SO.5 Disable:I2SO.3]
[MSG:INFO: X Neg Limit gpio.34]
[MSG:INFO: Axis Y (0.000,1260.000)]
[MSG:INFO: Motor0]
[MSG:INFO: standard_stepper Step:I2SO.12:low Dir:I2SO.10:low Disable:I2SO.8]
[MSG:INFO: Y Neg Limit gpio.32]
[MSG:INFO: Motor1]
[MSG:INFO: standard_stepper Step:I2SO.13:low Dir:I2SO.11:low Disable:I2SO.9]
[MSG:INFO: Y2 Neg Limit gpio.35]
[MSG:INFO: Axis Z (-150.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: standard_stepper Step:I2SO.18:low Dir:I2SO.16 Disable:I2SO.14]
[MSG:INFO: Z Pos Limit gpio.27]
[MSG:INFO: estop_pin gpio.15:low]
[MSG:INFO: Kinematic system: Cartesian]
[MSG:INFO: Connecting to STA SSID:GematMesh]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connecting...]
[MSG:INFO: Connected - IP is 10.35.1.31]
[MSG:INFO: WiFi on]
[MSG:INFO: Start mDNS with hostname:http://fluidnc-UltimateBee.local/]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
[MSG:INFO: Huanyang Spindle Tx:gpio.17 Rx:gpio.16 RTS:gpio.4 Baud:9600]
[MSG:INFO: Probe gpio.2:low]
ok
<Alarm|MPos:0.000,0.000,0.000|FS:0,0>
Axis limit switches all triggered in turn as suggested, and they all seem to function as expected:
$message/level=debug
ok
[MSG:DBG: Z Pos Limit 1]
[MSG:DBG: Limit switch tripped for Z motor 0]
[MSG:DBG: Z Pos Limit 0]
[MSG:DBG: X Neg Limit 1]
[MSG:DBG: Limit switch tripped for X motor 0]
[MSG:DBG: X Neg Limit 0]
[MSG:DBG: Y Neg Limit 1]
[MSG:DBG: Limit switch tripped for Y motor 0]
[MSG:DBG: Y Neg Limit 0]
[MSG:DBG: Y2 Neg Limit 1]
[MSG:DBG: Limit switch tripped for Y motor 1]
[MSG:DBG: Y2 Neg Limit 0]
When you have time to test again, contact me on Discord via DM. I want to work interactively with you to debug this.
Closing out as homing issues are resolved in v3.9.1
Wiki Search Terms
homing
Controller Board
RootCNC ISO v3
Machine Description
UlitmateBee Gantry Router with external DM542T v4.0 stepper drivers, dual Y motors, inductive proximity switches on all axes. Spindle is a 240v Huanyang 2.2kw
Input Circuits
No response
Configuration file
Startup Messages
User Interface Software
WebUI, gSender
What happened?
As per recent discord discussion with Bart:
There seems to be a serious homing issue with v3.9 that isn’t present on the pre-releases that I have since rolled back and tested (that is to say 3.8.4-pre7, pre8, pre9 all work fine) but 3.9 sends my Y2 axis off (at pace) in the wrong direction after initially homing in the right direction?!
Only effects the Y2 motor and as far as timing, it seems to be either; just after it first hits its own limit switch OR just after Y1 hits its one… it all happens rather fast and I was always jumping for the estop at the same moment.
GCode File
No response
Other Information
No response