Wiki Search Terms
none
Controller Board
rootcnc v3
Machine Description
foxalien vasto with rootcnc controller, all motors upgraded to closed loop.
dual y axis motors, single motors on x and z
limit switches for x and z axis. y axis has limit switches for one side only
Input Circuits
“yaml`
machine works fine with 3.9.1 and not 3.9.1 or 3.9.3 so I don't think its a wiring error.
Configuration file
`yaml
board: Root Controller ISO
name: VFD hard limits
meta:
arctolerancemm: 0.002
junctiondeviationmm: 0.010
verbose_errors: false
report_inches: false
enableparkingoverride_control: false
uselinenumbers: false
planner_blocks: 16
#NOTE pin 20 is relay 1
#NOTE pin 21 is relay 2
BUG status outputs are not set until after first physical movement!!
status_outputs:
reportintervalms: 500
idle seems to work on relays and motor output pins. idle ONLY when nothing else is happening including jogging
idle_pin: I2SO.15:high
#run pin is NOT active during jog. IS active on other gcode commands
run_pin: I2SO.15:high
#hold pin works when feed hold is pressed i.e. ! and goes back to 0 when ~ is pressed
hold_pin: I2SO.15:high
ALARM DOES NOT SEEM TO WORK. homing fail does not activate. E stop does not activate
alarm_pin: I2SO.15:high
start:
must_home: true
check_limits: false
stepping:
engine: I2S_STREAM
idle_ms: 255
pulse_us: 4
dirdelayus: 4
disabledelayus: 4
axes:
sharedstepperdisablepin: NOPIN
x:
stepspermm: 320.000
maxratemmpermin: 4000.000
accelerationmmper_sec2: 500.000
was
maxtravelmm: 422.000
max travel from home 0 to 1mm before end crash
# maxtravelmm: 445.000
soft_limits: true
homing:
cycle: 2
positive_direction: false
note once machine is hommed soft limits do not allow movement to the left of the home position regardless of mpos.
i.e. mpos does not allow you to set a soft limit to the left of the home X axis switch
mpos_mm: 0.000
feedmmper_min: 25.000
seekmmper_min: 1500.000
settle_ms: 500
seek_scaler: 1.100
feed_scaler: 1.100
motor0:
limitnegpin: NO_PIN
limitpospin: NO_PIN
limitallpin: gpio.34
hard_limits: true
pulloff_mm:1.100
standard_stepper:
step_pin: I2SO.7:low
direction_pin: I2SO.5:high
disable_pin: I2SO.3:high
y:
stepspermm: 320.000
maxratemmpermin: 4000.000
accelerationmmper_sec2: 500.000
was
maxtravelmm: 435.000
max travel from home 0 to 1mm before end crash
# maxtravelmm: 457.000
soft_limits: true
homing:
cycle: 2
positive_direction: false
mpos_mm: 0.000
feedmmper_min: 25.000
seekmmper_min: 1500.000
settle_ms: 500
seek_scaler: 1.100
feed_scaler: 1.100
motor 0 on labelled y output
motor0:
limitnegpin: NO_PIN
limitpospin: NO_PIN
#limit switches on y input
limitallpin: gpio.32
hard_limits: true
pulloff_mm:1.000
standard_stepper:
step_pin: I2SO.12:low
direction_pin: I2SO.10:high
disable_pin: I2SO.8:high
motor 1 on labelled b output
motor1:
limitnegpin: NO_PIN
limitpospin: NO_PIN
limitallpin: NO_PIN
hard_limits: true
pulloff_mm: 1.000
standard_stepper:
step_pin: I2SO.13:low
direction_pin: I2SO.11:high
disable_pin: I2SO.9:high
z:
stepspermm: 800.000
maxratemmpermin: 2000.000
accelerationmmper_sec2: 500.000
maxtravelmm: 105.000
soft_limits: true
homing:
cycle: 1
positive_direction: true
mpos_mm: 0.000
feedmmper_min: 25.000
seekmmper_min: 1500.000
settle_ms: 500
seek_scaler: 1.100
feed_scaler: 1.100
motor 0 on labelled z output
motor0:
limitnegpin: NO_PIN
limitpospin: NO_PIN
limitallpin: gpio.27
hard_limits: true
pulloff_mm: 1.000
standard_stepper:
step_pin: I2SO.18:low
direction_pin: I2SO.16:high
disable_pin: I2SO.14:high
i2so:
bck_pin: gpio.22
data_pin: gpio.12
ws_pin: gpio.21
spi:
miso_pin: gpio.19
mosi_pin: gpio.23
sck_pin: gpio.18
sdcard:
carddetectpin: NO_PIN
cs_pin: gpio.5
control:
safetydoorpin: NO_PIN
emergency stop connected to * input.
estop_pin: gpio.15
reset uses A input
reset_pin: gpio.26
macro0pin: NOPIN
macro1pin: NOPIN
macro2pin: NOPIN
macro3pin: NOPIN
feedholdpin: gpio.25
cyclestartpin: gpio.36
closed loop controller fault pins high when all is ok in parallel on input axis limit B
fault_pin: gpio.35:high
coolant:
floodpin: NOPIN
mistpin: NOPIN
delay_ms: 0
both probe and toolsetter generate probe notifications.
probe:
probe uses P input
pin: gpio.02
toolsetter uses C input
toolsetter_pin: gpio.14: high
checkmodestart: true
macros:
startup_line0:
startup_line1:
macro0:
macro1:
macro2:
macro3:
after_homing:
after_reset:
after_unlock:
user_outputs:
M67 E0 Q23.87 would enable output analog0_pin with 23.87% duty cycle. Q0 would it turn off.
analog0_pin: gpio.13
analog1pin: NOPIN
analog2pin: NOPIN
analog3pin: NOPIN
analog0_hz: 5000
analog1_hz: 5000
analog2_hz: 5000
analog3_hz: 5000
M62 P0 Would turn digital0 pin on. M63 P0 Would turn digital0 pin off
relay 1 is on pin i2so.21 ?
digital0_pin: i2so.21
relay 2 is on pin i2so.20 ?
digital1_pin: i2so.20
fet 2 is on pin i2so.22 ?
digital2_pin: i2so.22
uart1:
txd_pin: gpio.17
rxd_pin: gpio.16
rts_pin: gpio.4
baud: 9600
mode: 8N1
atc_manual:
safezmpos_mm: -1.000000
probeseekratemmper_min: 200.000000
probefeedratemmper_min: 25.000000
changemposmm: 200.000 200.000 -1.000
etsmposmm: 400.000 400.000 -85.000
etsrapidzmposmm: -65.000000
Huanyang:
uart_num: 1
modbus_id: 1
tool_num: 0
spinup_ms: 10000
spindown_ms: 10000
offonalarm: true
speed map or linear??
speed_map: 0=0% 0=20% 4800=20% 24000=100%
atc: atc_manual
`
Startup Messages
`text
since 3.9.1 IS working fine and 3.9.3 is NOT working correctly I will include startup message from both versions:
startup message from v 3.9.1 (working FINE)
[MSG:INFO: FluidNC v3.9.1 https://github.com/bdring/FluidNC]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is spiffs]
[MSG:INFO: Configuration file:foxalienVFD.yaml]
[MSG:INFO: Machine VFD hard limits]
[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 cspin:gpio.5 detect:NOPIN freq:8000000]
[MSG:INFO: Stepping:I2S_STREAM Pulse:4us Dsbl Delay:4us Dir Delay:4us Idle Delay:255ms]
[MSG:INFO: User Digital Output: 0 on Pin:I2SO.21]
[MSG:INFO: User Digital Output: 1 on Pin:I2SO.20]
[MSG:INFO: User Digital Output: 2 on Pin:I2SO.22]
[MSG:INFO: User Analog Output: 0 on Pin:gpio.13 Freq:5000Hz]
[MSG:INFO: Axis count 3]
[MSG:INFO: Axis X (0.000,422.000)]
[MSG:INFO: Motor0]
[MSG:INFO: standard_stepper Step:I2SO.7:low Dir:I2SO.5 Disable:I2SO.3]
[MSG:INFO: X All Limit gpio.34]
[MSG:INFO: Axis Y (0.000,435.000)]
[MSG:INFO: Motor0]
[MSG:INFO: standard_stepper Step:I2SO.12:low Dir:I2SO.10 Disable:I2SO.8]
[MSG:INFO: Y All Limit gpio.32]
[MSG:INFO: Motor1]
[MSG:INFO: standard_stepper Step:I2SO.13:low Dir:I2SO.11 Disable:I2SO.9]
[MSG:INFO: Axis Z (-105.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: standard_stepper Step:I2SO.18:low Dir:I2SO.16 Disable:I2SO.14]
[MSG:INFO: Z All Limit gpio.27]
[MSG:INFO: reset_pin gpio.26]
[MSG:INFO: feedholdpin gpio.25]
[MSG:INFO: cyclestartpin gpio.36]
[MSG:INFO: fault_pin gpio.35]
[MSG:INFO: estop_pin gpio.15]
[MSG:INFO: Kinematic system: Cartesian]
[MSG:INFO: Connecting to STA SSID:VM0210584]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connected - IP is 192.168.0.57]
[MSG:INFO: WiFi on]
[MSG:INFO: Start mDNS with hostname:http://fluidnc.local/]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
[MSG:INFO: Status outputs Interval:500 Idle:NOPIN Cycle:NOPIN Hold:NO_PIN Alarm:I2SO.15]
[MSG:INFO: ATC:atc_manual]
[MSG:INFO: Huanyang Spindle Tx:gpio.17 Rx:gpio.16 RTS:gpio.4 Baud:9600]
[MSG:INFO: Probe gpio.2]
[MSG:INFO: Toolsetter gpio.14]
startup message from 3.9.3 (DOES NOT WORK AS EXPECTED)
[MSG:INFO: FluidNC v3.9.3 https://github.com/bdring/FluidNC]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is spiffs]
[MSG:INFO: Configuration file:foxalienVFD.yaml]
[MSG:INFO: Machine VFD hard limits]
[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 cspin:gpio.5 detect:NOPIN freq:8000000]
[MSG:INFO: Stepping:I2S_STREAM Pulse:4us Dsbl Delay:4us Dir Delay:4us Idle Delay:255ms]
[MSG:INFO: User Digital Output: 0 on Pin:I2SO.21]
[MSG:INFO: User Digital Output: 1 on Pin:I2SO.20]
[MSG:INFO: User Digital Output: 2 on Pin:I2SO.22]
[MSG:INFO: User Analog Output: 0 on Pin:gpio.13 Freq:5000Hz]
[MSG:INFO: Axis count 3]
[MSG:INFO: Axis X (0.000,422.000)]
[MSG:INFO: Motor0]
[MSG:INFO: standard_stepper Step:I2SO.7:low Dir:I2SO.5 Disable:I2SO.3]
[MSG:INFO: X All Limit gpio.34]
[MSG:INFO: Axis Y (0.000,435.000)]
[MSG:INFO: Motor0]
[MSG:INFO: standard_stepper Step:I2SO.12:low Dir:I2SO.10 Disable:I2SO.8]
[MSG:INFO: Y All Limit gpio.32]
[MSG:INFO: Motor1]
[MSG:INFO: standard_stepper Step:I2SO.13:low Dir:I2SO.11 Disable:I2SO.9]
[MSG:INFO: Axis Z (-105.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: standard_stepper Step:I2SO.18:low Dir:I2SO.16 Disable:I2SO.14]
[MSG:INFO: Z All Limit gpio.27]
[MSG:INFO: reset_pin gpio.26]
[MSG:INFO: feedholdpin gpio.25]
[MSG:INFO: cyclestartpin gpio.36]
[MSG:INFO: fault_pin gpio.35]
[MSG:INFO: estop_pin gpio.15]
[MSG:INFO: Kinematic system: Cartesian]
[MSG:INFO: Connecting to STA SSID:VM0210584]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connected - IP is 192.168.0.57]
[MSG:INFO: WiFi on]
[MSG:INFO: Start mDNS with hostname:http://fluidnc.local/]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
[MSG:INFO: Status outputs Interval:500 Idle:NOPIN Cycle:NOPIN Hold:NO_PIN Alarm:I2SO.15]
[MSG:INFO: ATC:atc_manual]
[MSG:INFO: Huanyang Spindle with atc_manual Tx:gpio.17 Rx:gpio.16 RTS:gpio.4 Baud:9600]
[MSG:INFO: Probe gpio.2]
[MSG:INFO: Toolsetter gpio.14]
“
User Interface Software
using web gui or gsender in grbl or grbl hal mode
What happened?
machine works fine with fluidnc 3.9.1 and multiple earlier versions.
But with version 3.9.0 and 3.9.3, if I jog the dual motor y axis in the negative direction i.e. towards the front of the machine both y axis motors turn the correct way BUT when jogging the y axis in the positive direction i.e. towards the back of the machine one of the dual y axis motors (the one on the right hand side of the machine) turns the correct way and the other (on the left side of the machine) turns to move the axis towards the front of the machine skewing the gantry. . i.e. the left Y axis motor always turns the same way regardless of the requested y axis travel direction. It is always the same motor turning the wrong way. Reseting does not help, switching on and off does not help. This is 100% repeatable, using webui or gsender for jogging makes no difference. Eventually the left hand y axis hits the homing switch and that is ignored too. If I keep jogging the y axis eventually it will crash into the bearing support housing and the closed loop stepper driver detects the missing steps and errors out setting the fault pin, but no error is reported by fluidnc. If I hit the reset button then the controller says fault pin on startup. Z and X (both axis have single motors) work fine. Just downgrading the firmware to 3.9.1 with no config or other changes restores correct operation. The issue is 100% reproducible over multiple upgrade and downgrade cycles.
I therefore do not believe it is a problem with the hardware, wiring or gsender and is a problem triggered by some code changes in fluidnc versions 3.9.3 and 3.9.0.
GCode File
any Y axis jog at any stepping speed and any length in mm
Other Information
No response
评论 (30)
#2 – bdring 于 2024-12-18
What closed loop motors are you using?
#3 – jkingdcs 于 2024-12-18
> Just to clarify
>
> * It it does not work with 3.9.0 and 3.9.3.
> * It works with 3.9.1
> * It works with versions earlier than 3.9.0
this is correct
#4 – jkingdcs 于 2024-12-18
> What closed loop motors are you using?
nema 23 from stepper online 3nm model 23HS45-4204D-E1000 closed loop motors 4.2A per phase. motor controller is cl57T v4.1 closed loop drivers
#5 – bdring 于 2024-12-18
Is it possible to place an LED on the direction signal of the controller on the axis that is having trouble?
#6 – bdring 于 2024-12-18
#7 – jkingdcs 于 2024-12-18
> Is it possible to place an LED on the direction signal of the controller on the axis that is having trouble?
yes, I can put an led, oscilloscope or multimeter
(I can jog for about 10-20mm before the gantry skews so much it jams)
#8 – bdring 于 2024-12-18
The direction signal is persistent. just jog a few millimeters. The state of the direction signal will stay until you reverse.
#9 – MitchBradley 于 2024-12-18
It is very strange that there is different behavior between 3.9.0 and 3.9.1. The changes between those versions are in an area that is very far removed from the step/direction generation code.
#10 – jkingdcs 于 2024-12-18
Y motor connected to motor socket B on rootcnc : (bad motor always turns same way)
multimeter negative on dir and positive on ref = -4.95V (motor connector B)
Y motor connected to motor socket Y on rootcnc : (good motor operates as expected)
multimeter negative on dir and positive on ref = -0V (motor connector Y)
#11 – MitchBradley 于 2024-12-18
I presume that the voltage on the good motor socket changes depending on the command direction, while the bad one does not change?
#12 – jkingdcs 于 2024-12-18
> I presume that the voltage on the good motor socket changes depending on the command direction, while the bad one does not change?
correct the motor on socket B has -5V dir to ref regardless of the direction of travel Y requested,.
I just put 3.9.1 back on, switched off and on the power and jogged in the y positive direction and BOTH motors work correctly and both motors have 0V between dir and ref when moving positive Y and -5V when moving negative Y.
#13 – MitchBradley 于 2024-12-18
In the previous test, where the B voltage did not change, was it 3.9.0 or 3.9.3?
#14 – jkingdcs 于 2024-12-18
> In the previous test, where the B voltage did not change, was it 3.9.0 or 3.9.3?
3.9.3
(I had exactly the same motor behaviour from 3.9.0 but stopped using it when it got pulled from the releases)
#15 – jkingdcs 于 2024-12-18
I should mention I am using firmware (3.9.0 3.9.1 and 3.9.3) I compiled from sources in github and not running the pre compiled firmware in https://github.com/bdring/FluidNC/releases.
The only change I made was to uncomment the 8MB flash option and comment out the 4MB flash option in platformio.ini. the compile environment and version of visual studio code was the same for all. (I checked the processor and it is a 8MB flash version)
I am happy to test 3.9.1 and 3.9.3 original firmware downloads from git hub and/or compile with the 4MB flash option if that would help
#16 – MitchBradley 于 2024-12-18
Yes, please do test the released versions, just to eliminate variables.
#17 – jkingdcs 于 2024-12-18
using the original downloads from git hub
3.9.1 works as expected no issues
3.9.3 ALSO works as expected…
im going to try recompiling 3.9.3 but with the 4BM flash option and see if it works or fails.
#18 – jkingdcs 于 2024-12-18
UGH this is crazy,
I switched rootcnc back on with the firmware 3.9.3 downloaded from git hub and the Y axis problem has struck again. I did nothing expect reboot the pc and leave the rootcnc off from sometime.
#19 – oliof 于 2024-12-18
sounds like s loose crimp on one of the motor wires to me.
#20 – jkingdcs 于 2024-12-18
3.9.3 4MB flash from git hub does not work after the second reboot.
if I have 3.9.1 flash installed, run install-wifi to flash 3.9.3 git hub firmware download and then quickly power cycle the root cnc
3.9.3 works BUT when I power cycle the second time 3.9.3 fails with skewed axis. All subsequent power cycles 3.9.3 precompiled from git hub does not work. I even tried reflashing 3.9.3 git hub again over the 3.9.3 git hub and it still does not work
#21 – jkingdcs 于 2024-12-18
> sounds like s loose crimp on one of the motor wires to me.
just put 3.9.1 from git works first time reboot still works reboot again still works….
ok if I swap the Y and B cables at the rootnc, then if its bad wiring the problem will NOT move from the left motor to the right motor. If the problem is the rootnc not outputting the direction correctly then the problem will move to the right motor
lets see…
#22 – jkingdcs 于 2024-12-18
I swapped B and Y motor connectors at the rootcnc,
with all 3.9.1 (compiled by me 4BM flash and from github) motors run correctly
with 3.9.3 from git hub installed the right hand motor now moves the wrong way, if it was bad left hand motor wiring on the left motor then the left motor would still be doing incorrect things regardless of if it is attached to channel B or Y
I believe the B motor channel direction is jammed at -5V Y with 3.9.3 after flashing if you switch off for more than a second or two.
I guess the next step is to see if channels A and C have the same direction problem.
I will also unplug the control lines from the rootnc to the motors and test the voltages with no motor wiring attached.
#23 – jkingdcs 于 2024-12-18
B channel direction is locked to -5V with 3.9.3 if hand compiled as 4MB or hand compiled as 8MB or using original git hub download, this is the case even if the motor control wires are disconnected from the rootcnc. (Apart from the single time I went from 3.9.1 to 3.9.3 and did a very quick power cycle) all other experiments are consistent. I can’t get 3.9.3 to work correctly on channel B.
channel B always works as expected in every 3.9.1, (hand compiled 4MB or hand compiled 8MB or download from git hub.)
the problem consistently moves from left motor to right motor and back when I swap the B and Y channel wiring and now the right hand motor is on channel B I can’t get the left motor to misbehave at all.
its rather late now and so I’m not going to experiment with channels A and C tonight and I will be away for two weeks visiting over Christmas so I will run some ore experiments in Jan.
Thank you Mitch, bdring and oliof for your support.
#24 – MitchBradley 于 2024-12-19
We are at somewhat of a disadvantage as I don’t have a Root Controller. Maybe Bart has one but I don’t remember him mentioning it. Nor have I found schematics online.
One thing that comes to mind as a possibility is signal integrity problems causing the I2S shift registers to misread the serial data. The 3.9 series runs the I2S at a faster clock rate allowing higher pulsing rates. Bart’s designs, which feature careful layout for good I2S signal integrity, have no problems at the faster clock, but who knows for the root controller? The fact that both Y motors are on the same shift register chip makes this somewhat of a long shot though.
#25 – jkingdcs 于 2024-12-19
> We are at somewhat of a disadvantage as I don’t have a Root Controller. Maybe Bart has one but I don’t remember him mentioning it. Nor have I found schematics online.
>
> One thing that comes to mind as a possibility is signal integrity problems causing the I2S shift registers to misread the serial data. The 3.9 series runs the I2S at a faster clock rate allowing higher pulsing rates. Bart’s designs, which feature careful layout for good I2S signal integrity, have no problems at the faster clock, but who knows for the root controller? The fact that both Y motors are on the same shift register chip makes this somewhat of a long shot though.
hmm, that’s an interesting thought which makes me wonder if its possibly a marginal I2S shift register…
I definitely want to move a y axis motor to channel A and then C to see if they are equally effected.
#26 – jkingdcs 于 2024-12-19
Some GOOD progress:
I just tested with one Y axis motor on Y channel (always reliable) and the other on (the previously unused) A channel and quick testing with 3.9.1 shows correct operation.
channel A also seems to work with 3.9.3. So far 3.9.3 has survived 4 power cycles and works correctly. I tried leaving a longer time between power cycles and still correct operation. This is by far the most reliable I have ever had 3.9.3…
I think there is now good evidence to suggest that either there is a signal integrity problem that 3.9.3 is triggering on channel B or the shift register that channel B is on has a marginal bit that 3.9.3 is triggering the stick. This might also explain the single correct operation I had with 3.9.3 earlier and then after rebooting it lapsed into incorrect behaviour…
I repeated the testing for channel C and the channel C dir pin is stuck at -5V for BOTH 3.9.3 AND 3.9.1 – C direction is on the third shift reg. So far I have not been able to get channel C direction to work correctly at all.
went back to channel A and it works fine with 3.9.1 AND 3.9.3.
So it looks like:
channels A,Y,Z,X work with 3.9.1 AND 3.9.3
channel C stuck -5V direction with BOTH 3.9.1. AND 3.9.3
channel B stuck -5V direction with 3.9.3 only.
I guess i should try a pre 3.8.0 to see if channel C will work at all….
P.S.
I found a schematic for an older version (v2.1) of rootcnc and it shows SN74HC595DR shift registers.
#27 – mattydboom 于 2024-12-19
This all sounds like my previously reported issue with v3.9.0 here #1364
That version was ultimately pulled, but I was experiencing exactly the same gantry skewing problem, and run a RootCNC ISO v3 with similar set up (except standard high torque and not closed loop steppers).
Bart and I did a bunch of tests over DM to try and get to the bottom but never did pinpoint the exact culprit….. and was fixed (and remains so for me) in all subsequent releases.
Just thought I would share in case I can be of assistance in trouble shooting with the Root controller, or if my previously shared config file could be used for comparison / testing.
#28 – jkingdcs 于 2024-12-19
> This all sounds like my previously reported issue with v3.9.0 here #1364
>
thanks for the info.
is 3.9.3 ok for you? which motor control channel is your second y axis motor on?
#29 – mattydboom 于 2024-12-19
Uploaded 3.9.3 firmware last night and behaves correctly just like every release (including the Pre releases) for me since 3.9.0.
Yes, my Y2 is wired to B port like yours. See attached pin mapping cheat sheet I created when compiling my config.yaml file. It may help you check for similarities / differences in your set up.
#1 – bdring 于 2024-12-18
Just to clarify
– It it does not work with 3.9.0 and 3.9.3.
– It works with 3.9.1
– It works with versions earlier than 3.9.0