[FluidNC Issue#1531] Problem:Bluetooth Name Cannot Be Changed via $ Command

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

Issue #1531 | 状态: 已关闭 | 作者: arlimbad222 | 创建时间: 2025-07-25


Wiki Search Terms

Steps to Reproduce

Connect to FluidNC via serial/terminal
Execute command: $Bluetooth/name=INB
System responds: ok
System restarts (either automatically or manually)
Check boot log for Bluetooth initialization

Controller Board

CUSTOM BOARD

Machine Description

SIMPLE 3 AXIS MILLING MACHINE

Input Circuits


Configuration file

NONE

Startup Messages

$SS
[MSG:INFO: FluidNC v3.9.7 https://github.com/bdring/FluidNC]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is spiffs]
[MSG:ERR: Cannot open configuration file:config.yaml]
[MSG:INFO: Using default configuration]
[MSG:INFO: Axes: using defaults]
[MSG:INFO: Machine Default (Test Drive)]
[MSG:INFO: Board None]
[MSG:INFO: Stepping:RMT Pulse:4us Dsbl Delay:0us Dir Delay:0us Idle Delay:255ms]
[MSG:INFO: Axis count 3]
[MSG:INFO: Axis X (-1000.000,0.000)]
[MSG:INFO:   Motor0]
[MSG:INFO: Axis Y (-1000.000,0.000)]
[MSG:INFO:   Motor0]
[MSG:INFO: Axis Z (-1000.000,0.000)]
[MSG:INFO:   Motor0]
[MSG:INFO: Kinematic system: Cartesian]
[MSG:INFO: BT Started with FluidNC]
ok

User Interface Software

FLUIDTERM

What happened?

The $Bluetooth/Name= command is not working properly. When I execute $Bluetooth/Name=INB followed by a system reset, FluidNC continues to show the default Bluetooth name in the boot sequence. The expected behavior would be to see [MSG:INFO: BT Started with INB] in the log, but instead it still displays [MSG:INFO: BT Started with FluidNC]. The command is accepted without returning any error message, suggesting the setting change appears successful, but it doesn’t persist after restart. Log files demonstrating this behavior are included below.

FluidTerm v1.2.1 (ca9a451-dirty) using COM23
Exit: Ctrl-C, Ctrl-Q or Ctrl-], Clear screen: CTRL-W
Upload: Ctrl-U, Reset ESP32: Ctrl-R, Send Override: Ctrl-O, STM32 Loader: Ctrl-S
$Bluetooth/Name=INB
ok
Resetting MCU
[MSG:INFO: uart_channel0 created]

[MSG:RST]
[MSG:INFO: FluidNC v3.9.7 https://github.com/bdring/FluidNC%5D
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is spiffs]
[MSG:ERR: Cannot open configuration file:config.yaml]
[MSG:INFO: Using default configuration]
[MSG:INFO: Axes: using defaults]
[MSG:INFO: Machine Default (Test Drive)]
[MSG:INFO: Board None]
[MSG:INFO: Stepping:RMT Pulse:4us Dsbl Delay:0us Dir Delay:0us Idle Delay:255ms]
[MSG:INFO: Axis count 3]
[MSG:INFO: Axis X (-1000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis Y (-1000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis Z (-1000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Kinematic system: Cartesian]
[MSG:INFO: BT Started with FluidNC]

Grbl 3.9 [FluidNC v3.9.7 (bt) ‘$’ for help]
[MSG:ERR: Configuration is invalid. Check boot messages for ERR’s.]
$S
$Grbl/SoftLimitsEnable=0
$Grbl/HardLimitsEnable=0
$Grbl/HomingCycleEnable=0
$Grbl/HomingDirections=0
$Grbl/MaxSpindleSpeed=0
$Grbl/LaserMode=0
$Grbl/Resolution/X=80.000
$Grbl/Resolution/Y=80.000
$Grbl/Resolution/Z=80.000
$Grbl/MaxRate/X=1000.000
$Grbl/MaxRate/Y=1000.000
$Grbl/MaxRate/Z=1000.000
$Grbl/Acceleration/X=25.000
$Grbl/Acceleration/Y=25.000
$Grbl/Acceleration/Z=25.000
$Grbl/MaxTravel/X=1000.000
$Grbl/MaxTravel/Y=1000.000
$Grbl/MaxTravel/Z=1000.000
$GCode/Echo=OFF
$Start/Message=Grbl \V [FluidNC \B (\R) \H]
$Firmware/Build=
$SD/FallbackCS=-1
$Report/Status=1
$Config/Filename=config.yaml
$Message/Level=Info
$Bluetooth/Name=FluidNC
$Bluetooth/Enable=ON
ok
$Bluetooth/Name=INB
ok
$S
$Grbl/SoftLimitsEnable=0
$Grbl/HardLimitsEnable=0
$Grbl/HomingCycleEnable=0
$Grbl/HomingDirections=0
$Grbl/MaxSpindleSpeed=0
$Grbl/LaserMode=0
$Grbl/Resolution/X=80.000
$Grbl/Resolution/Y=80.000
$Grbl/Resolution/Z=80.000
$Grbl/MaxRate/X=1000.000
$Grbl/MaxRate/Y=1000.000
$Grbl/MaxRate/Z=1000.000
$Grbl/Acceleration/X=25.000
$Grbl/Acceleration/Y=25.000
$Grbl/Acceleration/Z=25.000
$Grbl/MaxTravel/X=1000.000
$Grbl/MaxTravel/Y=1000.000
$Grbl/MaxTravel/Z=1000.000
$GCode/Echo=OFF
$Start/Message=Grbl \V [FluidNC \B (\R) \H]
$Firmware/Build=
$SD/FallbackCS=-1
$Report/Status=1
$Config/Filename=config.yaml
$Message/Level=Info
$Bluetooth/Name=INB
$Bluetooth/Enable=ON
ok
Resetting MCU
[MSG:INFO: uart_channel0 created]

[MSG:RST]
[MSG:INFO: FluidNC v3.9.7 https://github.com/bdring/FluidNC%5D
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is spiffs]
[MSG:ERR: Cannot open configuration file:config.yaml]
[MSG:INFO: Using default configuration]
[MSG:INFO: Axes: using defaults]
[MSG:INFO: Machine Default (Test Drive)]
[MSG:INFO: Board None]
[MSG:INFO: Stepping:RMT Pulse:4us Dsbl Delay:0us Dir Delay:0us Idle Delay:255ms]
[MSG:INFO: Axis count 3]
[MSG:INFO: Axis X (-1000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis Y (-1000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis Z (-1000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Kinematic system: Cartesian]
[MSG:INFO: BT Started with FluidNC]

Grbl 3.9 [FluidNC v3.9.7 (bt) ‘$’ for help]
[MSG:ERR: Configuration is invalid. Check boot messages for ERR’s.]

GCode File

No response

Other Information

Other Information

– Installation: FluidNC-v3.9.7-Windows via install-bt.bat
– Commands tested: $ESP140=INB and $Bluetooth/Name=INB
– Setting requirements met: “INB” is valid (3 chars, letters only)
– Bluetooth remains functional for connections
– Possible YAML override: DEFAULT.YAML may be overriding NVRAM settings
– Consistent reproduction: Fails to persist on every restart


评论 (1)

#1 – MitchBradley 于 2025-07-25

Thanks for the clear bug report. The fix will appear in the next release. Meanwhile, you can pick up a test binary from the continuous integration build at https://github.com/bdring/FluidNC/actions/runs/16526830956/artifacts/3616977224


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

喜欢 (0)