Description
Controller Board
Hello. I’m using the FluidNC Pen Laser Controller (SPI) with TMC2130 drivers. The board is V1.2, which I’m assuming has the same pinout as v1.0, running FluidNC v3.4.5
Help From Board Vendor
-
YesNoNot Applicable
Machine Description
The machine is a corexy sand table (ZENXYv2).
Configuration file
Config file pulled from memory via the $CD command in the web interface
board: FluidNC Pen/Laser 2130
name: TMC2130 ZenXY
meta:
stepping:
engine: RMT
idle_ms: 255
pulse_us: 2
dir_delay_us: 1
disable_delay_us: 0
segments: 6
axes:
shared_stepper_disable_pin: NO_PIN
shared_stepper_reset_pin: NO_PIN
x:
steps_per_mm: 80.000
max_rate_mm_per_min: 1000.000
acceleration_mm_per_sec2: 25.000
max_travel_mm: 450.000
soft_limits: true
homing:
cycle: 2
allow_single_axis: true
positive_direction: false
mpos_mm: 0.000
feed_mm_per_min: 100.000
seek_mm_per_min: 200.000
settle_ms: 500
seek_scaler: 1.100
feed_scaler: 1.100
motor0:
limit_neg_pin: gpio.39
limit_pos_pin: NO_PIN
limit_all_pin: NO_PIN
hard_limits: false
pulloff_mm: 1.000
tmc_2130:
step_pin: gpio.14
direction_pin: gpio.12
disable_pin: NO_PIN
r_sense_ohms: 0.110
run_amps: 0.250
hold_amps: 0.250
microsteps: 32
toff_disable: 0
toff_stealthchop: 5
use_enable: false
cs_pin: gpio.16
spi_index: -1
run_mode: StealthChop
homing_mode: StealthChop
stallguard: 0
stallguard_debug: false
toff_coolstep: 3
motor1:
limit_neg_pin: NO_PIN
limit_pos_pin: NO_PIN
limit_all_pin: NO_PIN
hard_limits: false
pulloff_mm: 1.000
null_motor:
y:
steps_per_mm: 80.000
max_rate_mm_per_min: 1000.000
acceleration_mm_per_sec2: 25.000
max_travel_mm: 885.000
soft_limits: true
homing:
cycle: 1
allow_single_axis: true
positive_direction: false
mpos_mm: 0.000
feed_mm_per_min: 100.000
seek_mm_per_min: 200.000
settle_ms: 500
seek_scaler: 1.100
feed_scaler: 1.100
motor0:
limit_neg_pin: gpio.36
limit_pos_pin: NO_PIN
limit_all_pin: NO_PIN
hard_limits: false
pulloff_mm: 1.000
tmc_2130:
step_pin: gpio.25
direction_pin: gpio.26
disable_pin: NO_PIN
r_sense_ohms: 0.110
run_amps: 0.250
hold_amps: 0.250
microsteps: 32
toff_disable: 0
toff_stealthchop: 5
use_enable: false
cs_pin: gpio.17
spi_index: -1
run_mode: StealthChop
homing_mode: StealthChop
stallguard: 0
stallguard_debug: false
toff_coolstep: 3
motor1:
limit_neg_pin: NO_PIN
limit_pos_pin: NO_PIN
limit_all_pin: NO_PIN
hard_limits: false
pulloff_mm: 1.000
null_motor:
z:
steps_per_mm: 80.000
max_rate_mm_per_min: 1000.000
acceleration_mm_per_sec2: 25.000
max_travel_mm: 1000.000
soft_limits: false
homing:
cycle: 0
allow_single_axis: true
positive_direction: true
mpos_mm: 0.000
feed_mm_per_min: 50.000
seek_mm_per_min: 200.000
settle_ms: 250
seek_scaler: 1.100
feed_scaler: 1.100
kinematics:
CoreXY:
spi:
miso_pin: gpio.19
mosi_pin: gpio.23
sck_pin: gpio.18
sdcard:
cs_pin: gpio.5
card_detect_pin: NO_PIN
control:
safety_door_pin: NO_PIN
reset_pin: NO_PIN
feed_hold_pin: NO_PIN
cycle_start_pin: NO_PIN
macro0_pin: NO_PIN
macro1_pin: NO_PIN
macro2_pin: NO_PIN
macro3_pin: NO_PIN
coolant:
flood_pin: NO_PIN
mist_pin: NO_PIN
delay_ms: 0
probe:
pin: NO_PIN
check_mode_start: true
macros:
startup_line0:
startup_line1:
macro0:
macro1:
macro2:
macro3:
start:
must_home: true
deactivate_parking: false
check_limits: false
user_outputs:
analog0_pin: NO_PIN
analog1_pin: NO_PIN
analog2_pin: NO_PIN
analog3_pin: NO_PIN
analog0_hz: 5000
analog1_hz: 5000
analog2_hz: 5000
analog3_hz: 5000
digital0_pin: NO_PIN
digital1_pin: NO_PIN
digital2_pin: NO_PIN
digital3_pin: NO_PIN
arc_tolerance_mm: 0.002
junction_deviation_mm: 0.010
verbose_errors: false
report_inches: false
enable_parking_override_control: false
use_line_numbers: false
planner_blocks: 16
NoSpindle:
Startup Messages
[MSG:INFO: FluidNC v3.4.5]
[MSG:INFO: Compiled with ESP32 SDK:v4.4-beta1-189-ga79dc75f0a]
[MSG:INFO: Local filesystem type is SPIFFS]
[MSG:INFO: Configuration file:config_01.yaml]
[MSG:INFO: Machine TMC2130 ZenXY]
[MSG:INFO: Board FluidNC Pen/Laser 2130]
[MSG:INFO: SPI SCK:gpio.18 MOSI:gpio.23 MISO:gpio.19]
[MSG:INFO: SD Card cs_pin:gpio.5 detect:NO_PIN]
[MSG:INFO: Stepping:RMT Pulse:2us Dsbl Delay:0us Dir Delay:1us Idle Delay:255ms]
[MSG:INFO: Axis count 3]
[MSG:INFO: Axis X (0.000,450.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2130 Step:gpio.14 Dir:gpio.12 CS:gpio.16 Disable:NO_PIN Index:-1 R:0.110]
[MSG:INFO: Neg Limit gpio.39]
[MSG:INFO: Motor1]
[MSG:INFO: Axis Y (0.000,885.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2130 Step:gpio.25 Dir:gpio.26 CS:gpio.17 Disable:NO_PIN Index:-1 R:0.110]
[MSG:INFO: Neg Limit gpio.36]
[MSG:INFO: Motor1]
[MSG:INFO: Axis Z (-1000.000,0.000)]
[MSG:INFO: X Axis driver test passed]
[MSG:INFO: Y Axis driver test passed]
[MSG:INFO: Kinematic system: CoreXY]
[MSG:INFO: Using spindle NoSpindle]
[MSG:INFO: STA SSID is not set]
[MSG:INFO: AP SSID FluidNC IP 192.168.0.1 mask 255.255.255.0 channel 1]
[MSG:INFO: AP started]
[MSG:INFO: WiFi on]
[MSG:INFO: Captive Portal Started]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
User Interface Software
webUI
What happened?
I can’t get any movement out of the steppers at all. I’m fairly certain I’ve gone wrong somewhere in my config file. I’ve attempted to create one by merging the example code for a coreXY plotter using 2209 drivers (https://github.com/bdring/FluidNC/blob/main/example_configs/TMC2209_corexy.yaml) and the example config for a cartesian plotter using TMC2130 drivers (https://github.com/bdring/FluidNC/blob/main/example_configs/TMC2130_pen.yaml).
Other Information
No response
Activity
bdring commented on Aug 12, 2022
I think you need shared disable pin defined.
I put a pinout image for the controller here.
http://wiki.fluidnc.com/en/hardware/official/FluidNC_Pen_Laser_CNC_Controller_SPI
codingishard404 commented on Aug 12, 2022
We’ve got movement! Thank you. Now to work on the homing.
codingishard404 commented on Aug 13, 2022
New problem: if I over-travel while jogging it refuses to move in any direction until I restart FluidNC. Moving from 0 to 100 and back to 0 is fine, but -100 breaks all movement in both axes.
Is this how the soft-limit function is supposed to function?
bdring commented on Aug 13, 2022
What is the error?
codingishard404 commented on Aug 13, 2022
It doesn’t error, it just doesn’t move.
Trying it again I’m now getting connection errors on negative movement. I recently swapped the motor plugs to correct the axis movement direction but I can’t see how that would’ve affected it.
bdring commented on Aug 13, 2022
Check your startup messages for the range on that axis.
codingishard404 commented on Aug 13, 2022
Well that would explain a lot, it’s now “skipping configuration file due to panic.” Not sure why the X and Y are working at all since it looks like the default is cartesian not corexy. That aside, if I’m reading it correctly X and Y are -1000, 0
Is there a list of the various error messages? I tried searching the wiki without much success.
bdring commented on Aug 13, 2022
Paste the startup messages before the panic.
codingishard404 commented on Aug 13, 2022
Feels like I’m chasing my tail here. I think movement commands stopped working at the first connection error message. Pasting the whole log since I ran $SS twice and got different results.
I restarted FluidNC and tried again, different movement commands but same overall result, the correct config at first startup, followed by the panic after the movement breaks.
bdring commented on Aug 13, 2022
I need to see the startup messages or I cannot help you.
Connect with Fluidterm only. Cut and paste the startup messages here.
http://wiki.fluidnc.com/en/support/requesting_help
codingishard404 commented on Aug 13, 2022
Roger. Let me get that installed, I’ve been connecting via the web interface.
EDIT: This might be a little while, my computer doesn’t recognize my COM port. Thanks again.
codingishard404 commented on Aug 13, 2022
Resetting MCU
ets Jun 8 2016 00:22:57
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1184
load:0x40078000,len:12804
ho 0 tail 12 room 4
load:0x40080400,len:3032
entry 0x400805e4
[MSG:INFO: FluidNC v3.4.5]
[MSG:INFO: Compiled with ESP32 SDK:v4.4-beta1-189-ga79dc75f0a]
[MSG:INFO: Local filesystem type is SPIFFS]
[MSG:INFO: Configuration file:config_02.yaml]
[MSG:INFO: Machine TMC2130 ZenXY]
[MSG:INFO: Board FluidNC Pen/Laser 2130]
[MSG:INFO: SPI SCK:gpio.18 MOSI:gpio.23 MISO:gpio.19]
[MSG:INFO: SD Card cs_pin:gpio.5 detect:NO_PIN]
[MSG:INFO: Stepping:RMT Pulse:2us Dsbl Delay:0us Dir Delay:1us Idle Delay:255ms]
[MSG:INFO: Axis count 3]
[MSG:INFO: Shared stepper disable gpio.13]
[MSG:INFO: Axis X (0.000,450.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2130 Step:gpio.14 Dir:gpio.12 CS:gpio.16 Disable:NO_PIN Index:-1 R:0.110]
[MSG:INFO: Neg Limit gpio.39]
[MSG:INFO: Motor1]
[MSG:INFO: Axis Y (0.000,885.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2130 Step:gpio.25 Dir:gpio.26 CS:gpio.17 Disable:NO_PIN Index:-1 R:0.110]
[MSG:INFO: Neg Limit gpio.36]
[MSG:INFO: Motor1]
[MSG:INFO: Axis Z (-1000.000,0.000)]
[MSG:INFO: X Axis driver test passed]
[MSG:INFO: Y Axis driver test passed]
[MSG:INFO: Kinematic system: CoreXY]
[MSG:INFO: Using spindle NoSpindle]
[MSG:INFO: STA SSID is not set]
[MSG:INFO: AP SSID FluidNC IP 192.168.0.1 mask 255.255.255.0 channel 1]
[MSG:INFO: AP started]
[MSG:INFO: WiFi on]
[MSG:INFO: Captive Portal Started]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
Grbl 3.4 [FluidNC v3.4.5 (wifi) ‘$’ for help]
[MSG:INFO: ‘$H’|’$X’ to unlock]
bdring commented on Aug 13, 2022
I don’t see a panic. Can you cause the panic in Fluidterm?
codingishard404 commented on Aug 14, 2022
Working on learning the proper commands here.
If I’m understanding things correctly, this should’ve moved 100mm in X, then in Y. I got no movement at all in either axis.
Okay. I got it to break by connecting over the webUI and jogging via that interface. Not quite sure why I can’t get it to move via the terminal.
MitchBradley commented on Aug 14, 2022
Please revert to 3.4.4. 3.4.5 is bad
8 remaining items
codingishard404 commented on Aug 14, 2022
I’m fairly certain disabling the wifi fixed it, I was still getting the reset with 3.4.4.
MitchBradley commented on Aug 14, 2022
Both are important
MitchBradley commented on Aug 14, 2022
3.4.5 is unstable even with STA mode
MitchBradley commented on Aug 14, 2022
With 3.4.5 you would likely still have crashes, but they would be much less frequent, typically happening sporadically in the middle of long jobs. Unless you did something that explicitly accesses FLASH, such as reloading WebUI in the middle of a GCode job run – that will crash 3.4.5 pretty quickly.
codingishard404 commented on Aug 15, 2022
Hello again. I thought I had the homing figured out, but while trying to make it home faster I came across another error. Below is the logs from two config files, the only change between the two is I increased seek_mm_per_min: from 200 to 600 under axes, x, homing.
If I’m understanding correctly, I should be able to have any value between 1 and 100,000?
Output below, split into two for readability.
bdring commented on Aug 15, 2022
Maybe line 45 has an error?
MitchBradley commented on Aug 15, 2022
We cannot see syntax errors in the config file from the $CD output. $CD reconstructs the configuration from the in-memory copy of the config tree, supplying default values for items that are not present in the actual file. If there is a syntax error in the file, the information on that line will not be incorporated into the in-memory tree.
The error message says that there is a problem on line 45 of the config file. That is not the same as line 45 of the $CD output. The line numbers in $CD do not track the line numbers in the file.
You should look at line 45 of your file and figure out what is wrong – probably either a missing colon or a misspelling or some extraneous junk. If you want us to look at it, you will need to attach the file.
codingishard404 commented on Aug 17, 2022
Line 45 should be microsteps: 32. The only change I made was the value for line 27. I’ve tried a few different values (I think 400, 600 and 800) and they all gave an error. I also tried adding an additional “:”, but that upload failed (160, followed by an error 2 on each line).
Maybe this is a dumb question. Is the microsteps value dependent on the seek/feed value?
Changed it to a text file for uploading.
config_01a.txt
MitchBradley commented on Aug 17, 2022
I tried your config_01a.txt on a test machine. There were no error message from the parsing phase.
The driver test errors were because this machine does not have TMCs. I did not expect that to work, I was just looking for config file syntax errors; there were none.
If you are still getting an error message, try re-uploading the file. Perhaps it got corrupted. We have seen cases where the SPIFFS filesystem has errors.
Regarding your question about “the seek/feed value”, I cannot answer that because there are several config options related to seek and feed, so “the seek/feed value” does not uniquely identify what you are asking about.
codingishard404 commented on Aug 17, 2022
Thanks for giving that a try Mitch. Can’t even get it to upload now… I’m sure I’m missing something obvious. I tried re-uploading the current config file (which doesn’t give errors), and got the below
bdring commented on Aug 17, 2022
I just loaded your file on a Pen Laser 2130. I used Version 3.4.4
bdring commented on Aug 17, 2022
We need to start a new issue or at least rename this issue.
codingishard404 commented on Aug 17, 2022
Okay. I’ll close this out and start a new one.
closed this as completedon Aug 17, 2022
bdring commented on Aug 17, 2022
Thanks, my phone is so slow with long Github issues.