Problem with new controller board

Software Carbide Motion
1

i just needed a new controller board.
Now the VFD router does not start to cut a project. I attach the files, one was cut before, and both do not let the spindle start. M3S10000 works fine via MDI.

There must be something wrong in the project file. Can anyone look in depth? I do not have any chance to troubleshoot G-code.
armchair7-1.c2d (76 KB)
armchair4-2.c2d (136 KB)

2

When I output G-code from the first file I get:

image
image1920×1152 104 KB

which has:

(TOOL/MILL,6.35, 0.00, 0.00, 0.00)
M6T205
M03S18000

and should work

3

Will: yes, should. But does not. When I enter M03S10000 into the MDI it lets the spindle run.
I played little with the speeds there, if I enter M03S18000 also in the MDI window the spindle does not start, the spindle controller does not react. When I enter different speeds lets say 15000 the display only shows 11000.

Will try to re-assign the speed in the project file to 10000, and re-start then.

But there is something unusual inside the machine. Is it a curse? I almost think so.

4

Did you configure for a BitRunner or a VFD Spindle in the Setup Wizard?

5

VFD spindle. But let me re-check.

6

config file:

Machine: Shapeoko
GRBL Version: 1.1f

Carbide Motion 635
Machine Controller State: INIT
Grbl Cycle: Idle

{
“bitRunnerEnabled”: false,
“bitSetterEnabled”: true,
“bitSetterX”: -0.5,
“bitSetterY”: -853.0,
“bitZeroType”: 2,
“connection”: 1,
“lastConfigSent”: 5,
“lastProbeIndex”: 0,
“lastSizeOption”: 0,
“odometer”: [
{
“cleared”: true,
“minutes”: 959.2804666666749,
“startDate”: “2024-02-15”,
“travelX”: 1050464.817564249,
“travelY”: 910937.8576011658,
“travelZ”: 46798.427693367004
},
{
“cleared”: false,
“minutes”: 1110.3806666666771,
“startDate”: “2024-03-28”,
“travelX”: 1056775.8064097892,
“travelY”: 1244392.8490552902,
“travelZ”: 82551.49006947875
}
],
“showCarbideRouterRpm”: true,
“spindleType”: 1,
“travelX”: -865.0,
“travelY”: -859.0,
“travelZ”: -95.0,
“version”: 0,
“webhooks”: ,
“workOffsetX”: 839.0499877929688,
“workOffsetY”: 831.4749755859375,
“workOffsetZ”: -29.845000000000002
}

0 = 10, Step pulse, microseconds
1 = 255, Step idle delay, milliseconds
2 = 0, Step port invert, mask
3 = 5, Direction port invert, mask
4 = 0, Step enable invert, boolean
5 = 0, Limit pins invert, boolean
6 = 0, Probe pin invert, boolean
10 = 255, Status report, mask
11 = 0.02, Junction deviation, millimeters
12 = 0.01, Arc tolerance, millimeters
13 = 0, Report inches, boolean
20 = 0, Soft limits, boolean
21 = 0, Hard limits, boolean
22 = 1, Homing cycle, boolean
23 = 0, Homing dir invert, mask
24 = 100, Homing feed, mm/min
25 = 2000, Homing seek, mm/min
26 = 25, Homing debounce, milliseconds
27 = 3, Homing pull-off, millimeters
30 = 24000, Max spindle speed, RPM
31 = 0, Min spindle speed, RPM
32 = 0, Laser mode, boolean
100 = 40, X steps/mm
101 = 40, Y steps/mm
102 = 200, Z steps/mm
110 = 10000, X Max rate, mm/min
111 = 10000, Y Max rate, mm/min
112 = 1000, Z Max rate, mm/min
120 = 500, X Acceleration, mm/sec^2
121 = 500, Y Acceleration, mm/sec^2
122 = 270, Z Acceleration, mm/sec^2
130 = 845, X Max travel, millimeters
131 = 850, Y Max travel, millimeters
132 = 95, Z Max travel, millimeters

Maintenance:

Travel (km) 1.06, 1.24, 0.08, 18.51 Hours since 2024-03-28
Travel (km) 1.05, 0.91, 0.05, 15.99 Hours since 2024-02-15

Queue Empty

so it looks like bit runner is off.