> 未分类 > [FluidNC Issue#1476] Problem: Configuration issue

[FluidNC Issue#1476] Problem: Configuration issue

未分类 bolang 4个月前 (10-14) 37次浏览

Issue #1476 | 状态: 已关闭 | 作者: Starejpes | 创建时间: 2025-04-11

Wiki Search Terms

Hi,
I am using FluidNC with BTT Rodent and CoreXY kinematics.
I set homing section following FluidNC Wiki as follows (for X and Y axis):
homing:
cycle: 2
positive_direction: false
mpos_mm: 50.000
feedmmper_min: 200.000
seekmmper_min: 2000.000
settle_ms: 500
seek_scaler: 1.1
feed_scaler: 1.1
The issue was that motors was rumbling on X and Y axis when moving to left side of sketch. I solved the issue by changing mpos_mm: -50.000. If there is more clever solution please let me know.
Kind regards

Controller Board

BTT Rodent V1.1

Machine Description

CoreXY Laser cutter

Input Circuits

Configuration file

board: BTT Rodent V1.0
name: BTT CNC
meta: (04.12.2024) by BTT
kinematics:
  Corexy:
stepping:
  engine: I2S_STREAM
  idle_ms: 255
  pulse_us: 4
  dirdelayus: 1
  disabledelayus: 0
axes:
  sharedstepperdisablepin: NOPIN
  x:
    stepspermm: 160.000
    maxratemmpermin: 5000.000
    accelerationmmper_sec2: 100.000
    maxtravelmm: 500.000
    soft_limits: false
    homing:
      cycle: 2
      positive_direction: false
      mpos_mm: -10.000
      feedmmper_min: 200.000
      seekmmper_min: 2000.000
      settle_ms: 500
      seek_scaler: 1.1
      feed_scaler: 1.1
    motor0:
      limitnegpin: gpio.35
      limitpospin: NO_PIN
      limitallpin: NO_PIN
      hard_limits: false
      pulloff_mm: 5
      tmc_5160:
        step_pin: I2SO.2
        direction_pin: I2SO.1:low
        disable_pin: I2SO.0
        cs_pin: gpio.5
        spi_index: 1
        rsenseohms: 0.022
        run_amps: 1.5
        hold_amps: 0.5
        microsteps: 32
        toff_disable: 0
        toff_stealthchop: 5
        use_enable: false
        run_mode: CoolStep
        homing_mode: CoolStep
        stallguard: 16
        stallguard_debug: false
        toff_coolstep: 3
        tpfd: 4
  y:
    stepspermm: 160.000
    maxratemmpermin: 5000.000
    accelerationmmper_sec2: 100.000
    maxtravelmm: 300.000
    soft_limits: false
    homing:
      cycle: 1
      positive_direction: false
      mpos_mm: -10.000
      feedmmper_min: 200.000
      seekmmper_min: 2000.000
      settle_ms: 500
      seek_scaler: 1.1
      feed_scaler: 1.1
    motor0:
      limitnegpin: gpio.34
      limitpospin: NO_PIN
      limitallpin: NO_PIN
      hard_limits: false
      pulloff_mm: 5
      tmc_5160:
        step_pin: I2SO.5
        direction_pin: I2SO.4
        disable_pin: I2SO.7
        cspin: NOPIN
        spi_index: 2
        rsenseohms: 0.022
        run_amps: 1.5
        hold_amps: 0.5
        microsteps: 32
        toff_disable: 0
        toff_stealthchop: 5
        use_enable: false
        run_mode: CoolStep
        homing_mode: CoolStep
        stallguard: 16
        stallguard_debug: false
        toff_coolstep: 3
        tpfd: 4
  z:
    stepspermm: 800
    maxratemmpermin: 5000
    accelerationmmper_sec2: 100
    maxtravelmm: 300
    soft_limits: false

   homing:


     cycle: 3


     positive_direction: true


     mpos_mm: 150


     feedmmper_min: 100


     seekmmper_min: 800


     settle_ms: 500


     seek_scaler: 1.1


     feed_scaler: 1.1

    motor0:
      limitnegpin: NO_PIN
      limitpospin: NO_PIN
      limitallpin: NO_PIN
      hard_limits: false
      pulloff_mm: 1
      tmc_5160:
        step_pin: I2SO.10
        direction_pin: I2SO.9
        disable_pin: I2SO.8
        cspin: NOPIN
        spi_index: 3
        rsenseohms: 0.022
        run_amps: 0.5
        hold_amps: 0.5
        microsteps: 8
        toff_disable: 0
        toff_stealthchop: 5
        use_enable: false
        run_mode: CoolStep
        homing_mode: CoolStep
        stallguard: 16
        stallguard_debug: false
        toff_coolstep: 3
        tpfd: 4
  a:
    stepspermm: 157.75
    maxratemmpermin: 18000
    accelerationmmper_sec2: 1500
    maxtravelmm: 325
    soft_limits: true

   homing:


     cycle: 4


     positive_direction: true


     mpos_mm: 150


     feedmmper_min: 100


     seekmmper_min: 800


     settle_ms: 500


     seek_scaler: 1.1


     feed_scaler: 1.1

    motor0:
      limitnegpin: NO_PIN
      limitpospin: NO_PIN
      limitallpin: NO_PIN
      hard_limits: false
      pulloff_mm: 1
      tmc_5160:
        step_pin: I2SO.13
        direction_pin: I2SO.12
        disable_pin: I2SO.15
        cspin: NOPIN
        spi_index: 4
        rsenseohms: 0.022
        run_amps: 0.5
        hold_amps: 0.5
        microsteps: 16
        toff_disable: 0
        toff_stealthchop: 5
        use_enable: false
        run_mode: CoolStep
        homing_mode: CoolStep
        stallguard: 16
        stallguard_debug: false
        toff_coolstep: 3
        tpfd: 4
  homing_runs: 2
i2so:
  bck_pin: gpio.22
  data_pin: gpio.21
  ws_pin: gpio.17
spi:
  miso_pin: gpio.19
  mosi_pin: gpio.23
  sck_pin: gpio.18
sdcard:
  cs_pin: gpio.0
  carddetectpin: NO_PIN
  frequency_hz: 8000000
#uart1:

 txd_pin: gpio.15


 rxd_pin: gpio.16


 rts_pin: gpio.14


 baud: 9600


 mode: 8N1

#Huanyang:

 uart_num: 1


 modbus_id: 1


 tool_num: 0


 speed_map: 0=0% 0=25% 6000=25% 24000=100%


 offonalarm: false

i2c0:
  sda_pin: gpio.27
  scl_pin: gpio.26
status_outputs:
  reportintervalms: 500
  idle_pin: I2SO.11:low
  run_pin: I2SO.14:low
  alarm_pin: I2SO.3:low
Laser:
  pwm_hz: 2000
  output_pin: gpio.15:high
  enable_pin: gpio.14:high
  disablewithS0: false
  s0withdisable: true
  tool_num: 0
  speed_map: 0=0.000% 1000=100.000%
  offonalarm: true
start:
  must_home: false

Startup Messages

OK

User Interface Software

WebUI, GRBL, LightBurn

What happened?

Homing was OK.
Motors was rumbling on X and Y axis when trying to cut far left and down.

GCode File

Any

Other Information

No response

评论 (3)

#1 – MitchBradley 于 2025-04-11

Lightburn’s zero position can be very confusing, so it is hard to answer your question without knowing exactly how you set the origin in Lightburn and where the sketch is located in that coordinate system.

#2 – Starejpes 于 2025-04-12

Hi Mitch,
You are right, LightBurn is sometime confusing. But my comment on situation was observed using GRBL actually.
When I set mposmm: to positive value having homing to negative on X and Y GRBL shows this value as current location. Gcode Instruction to go to position X=0, Z=0 or value less than that value mposmm: resulted in overrun physical structure.
My intention of the comment was to add into documentation something like:
“Having end-switches on negative X, Y axes will induce to set mpos_mm: value to negative as well”.
Maybe it will save other users couple of hours investigating what is wrong with their project.
Cheers Starejpes
From: Mitch Bradley @.*>
Sent: 11 April 2025 15:25
To: bdring/FluidNC @.*>
Cc: Starejpes @.>; Author @.>
Subject: Re: [bdring/FluidNC] Problem: Configuration issue (Issue #1476)

Lightburn’s zero position can be very confusing, so it is hard to answer your question without knowing exactly how you set the origin in Lightburn and where the sketch is located in that coordinate system.

–
Reply to this email directly, view it on GitHub<https://github.com/bdring/FluidNC/issues/1476#issuecomment-2796073681>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJRAFDDYQ622AMCG37BWQVT2Y5U5LAVCNFSM6AAAAAB25LDCXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJWGA3TGNRYGE>.
You are receiving this because you authored the thread.Message ID: @.*>
[Image removed by sender.]MitchBradley left a comment (bdring/FluidNC#1476)<https://github.com/bdring/FluidNC/issues/1476#issuecomment-2796073681>

Lightburn’s zero position can be very confusing, so it is hard to answer your question without knowing exactly how you set the origin in Lightburn and where the sketch is located in that coordinate system.

–
Reply to this email directly, view it on GitHub<https://github.com/bdring/FluidNC/issues/1476#issuecomment-2796073681>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJRAFDDYQ622AMCG37BWQVT2Y5U5LAVCNFSM6AAAAAB25LDCXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJWGA3TGNRYGE>.
You are receiving this because you authored the thread.Message ID: @.*>

#3 – MitchBradley 于 2025-04-12

> When I set mpos_mm: to positive value having homing to negative on X and Y GRBL shows this value as current location

What exact interaction with GRBL “showed the value as current location”? Was it a response to the “?” status report inquiry? Was $10 AKA $Report/Status set to report WPos or MPos?

The reason that this is important is because GCode always operates in work coordinates, except for the rare case when there is a G53 on the line. If the status report says that the MPos coordinate is 50, and you do not know the work coordinate offset for the currently-selected coordinate system (G54 .. G59), then when you say ‘G0 X0 Y0`, it might go anywhere, because 50 in machine coordinates could be anything at all in work coordinates, depending on where you were the last time that you zeroed the work coordinate system.

The typical workflow is to home the machine, thus establishing the machine coordinates for the purpose of soft limits, then jog (incremental moves) to an appropriate position relative to the stock, and then zero the work coordinates. The work coordinate offset (per work coordinate system) is persistent across reboots, so the next time that you home the machine, the work zero will be in the same position as before.

原始Issue: https://github.com/bdring/FluidNC/issues/1476

喜欢 (0)