Hi I'm trying to cut out insert holes for my spoilboard. I'm going referencing from the centre but when I try to run the file I get the error message shown in with the attached image. screen record explanation Loom | Free Screen & Video Recording Software This is a previous thread with Peter (this might help with trouble shooting)? X Axis Homing to the right (wrong direction) I'm wondering whether this is correct. Openbuilds controller setup [18:37:18] [ 3D Viewer ] WebGL Support found! success: this application will work optimally on this device! [18:37:18] [ websocket ] Bidirectional Websocket Interface Started Succesfully [18:37:30] [ connect ] PORT INFO: Port is now open: /dev/tty.usbserial-AH01LBGP - Attempting to detect Firmware [18:37:30] [ connect ] Checking for firmware on /dev/tty.usbserial-AH01LBGP [18:37:30] [ connect ] Detecting Firmware: Method 1 (Autoreset) [18:37:30] [ connect ] Detecting Firmware: Method 2 (Ctrl+X) [18:37:31] [ connect ] Detecting Firmware: Method 3 (others that are not supported) [18:37:31] [ ] Grbl 1.1g ['$' for help] [18:37:31] [ ] [MSG:'$H'|'$X' to unlock] [18:37:32] [ $$ ] $0=10 ;Step pulse time, microseconds [18:37:33] [ $$ ] $1=255 ;Step idle delay, milliseconds [18:37:33] [ $$ ] $2=0 ;Step pulse invert, mask [18:37:33] [ $$ ] $3=0 ;Step direction invert, mask [18:37:33] [ $$ ] $4=1 ;Invert step enable pin, boolean [18:37:33] [ $$ ] $5=0 ;Invert limit pins, boolean/mask [18:37:33] [ $$ ] $6=0 ;Invert probe pin, boolean [18:37:33] [ $$ ] $10=1 ;Status report options, mask [18:37:33] [ $$ ] $11=0.010 ;Junction deviation, millimeters [18:37:33] [ $$ ] $12=0.002 ;Arc tolerance, millimeters [18:37:33] [ $$ ] $13=0 ;Report in inches, boolean [18:37:33] [ $$ ] $20=1 ;Soft limits enable, boolean [18:37:33] [ $$ ] $21=0 ;Hard limits enable, boolean [18:37:33] [ $$ ] $22=1 ;Homing cycle enable, boolean (Grbl) / mask (GrblHAL) [18:37:33] [ $$ ] $23=1 ;Homing direction invert, mask [18:37:33] [ $$ ] $24=25.000 ;Homing locate feed rate, mm/min [18:37:33] [ $$ ] $25=750.000 ;Homing search seek rate, mm/min [18:37:33] [ $$ ] $26=250 ;Homing switch debounce delay, milliseconds [18:37:33] [ $$ ] $27=1.000 ;Homing switch pull-off distance, millimeters [18:37:33] [ $$ ] $30=1000 ;Maximum spindle speed, RPM [18:37:33] [ $$ ] $31=0 ;Minimum spindle speed, RPM [18:37:33] [ $$ ] $32=0 ;Laser-mode enable, boolean [18:37:33] [ $$ ] $100=200.000 ;X-axis steps per millimeter [18:37:33] [ $$ ] $101=200.000 ;Y-axis steps per millimeter [18:37:33] [ $$ ] $102=200.000 ;Z-axis steps per millimeter [18:37:33] [ $$ ] $110=1000.000 ;X-axis maximum rate, mm/min [18:37:33] [ $$ ] $111=1000.000 ;Y-axis maximum rate, mm/min [18:37:33] [ $$ ] $112=1000.000 ;Z-axis maximum rate, mm/min [18:37:33] [ $$ ] $120=10.000 ;X-axis acceleration, mm/sec^2 [18:37:33] [ $$ ] $121=10.000 ;Y-axis acceleration, mm/sec^2 [18:37:33] [ $$ ] $122=10.000 ;Z-axis acceleration, mm/sec^2 [18:37:33] [ $$ ] $130=745.000 ;X-axis maximum travel, millimeters [18:37:33] [ $$ ] $131=1200.000 ;Y-axis maximum travel, millimeters [18:37:33] [ $$ ] $132=85.000 ;Z-axis maximum travel, millimeters [18:37:33] [ $$ ] ok [18:37:33] [ $I ] [VER:1.1g.20181112:CUSTOM] [18:37:33] [ $I ] [OPT:V,15,128] [18:37:33] [ $I ] ok [18:37:34] [ $G ] [GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0] [18:37:34] [ $G ] ok [18:37:34] [ connect ] Firmware Detected: grbl version 1.1g on /dev/tty.usbserial-AH01LBGP Thanks
the problem is that you are not using the OB post for Fusion (the default GRBL post sucks because the folks at Autodesk have not read the GRBL wiki) Code: (spoilboard_insert_step1) (spoil board) (Machine) ( vendor: Ratrig ) ( model: KillerBee 1000 x 1500) ( description: 1000mm x 1500mm X 750mm > Y 1205mm > Z 85mm Suhner UAK 30 RF Spindle 1530W) (T2 D=6 CR=0 - ZMIN=-5.5 - flat end mill) it is allowing a multiline comment which is illegal in Gcode for GRBL and GRBL is then complaining that 750mm is not a number. this docs:software:fusion360 [OpenBuilds Documentation] will solve the problem
Our post is fantastic and a lot less buggy than Autodesk's - just a reminder to remember to HOME, then SetZero before running gcode from our post (it uses both machine and work coordinate systems)
So before you start the job one should set WCS and then home the machine set zeros there as well and then start the job?
Other way round. Home first, then setzero. Machine Coordinates is the base coordinate system. Every other coordinate system and stored position is an Offset from MCS. See above
Home the machine (Machine Coordinates) . Then jog the machine to where you want to start cutting, and zero your X,Y and Z. This is where you are conducting the work (Work Coordinates) and you control this location.
