From Shopbot Wiki

Basic: What you see in almost all cutting files. Moves, jogs, move speed...

Examples are:

MS,3.5,2 ...

M2,24,12.5 JZ,1 MZ,-0.5 ...

JH ...

The statements are:


Call file conversion utilities. Files of the following type can be converted to ShopBot Part Files (.sbp): 'dxf' files (drawing exchange format); '.plt' or '.hpg' files (HP graphics language plotter); '.nc' or other formats of CNC files (standard G-code files); and '.tif' files (a raster type file bitmap file in which gray scale is extracted as 3D). If ShopBot is provided a filename with one of these listed extensions, it will convert the file using the appropriate converter and create a '.sbp' Part File. Depending on the type of conversion, the user may be prompted for additional information. If the file that is submitted for conversion does not have a recognized file type extension, the user will be prompted for the type of conversion to attempt.


Open a file for editing with a text editor; most likely SbEdit which is the SB text editor. If you prefer another text editor, you can set another one with UN command.


Programming: What you see in routines like homing and Z zeroing.

Examples are:

IF &count > 8 THEN GOSUB END ...

PAUSE, 2 ...

The statements are:

CLOSE #openfilenumber

Closes a file that has previously been opened with OPEN statement. If used without the (#openfilenumber) then ALL open files will be closed. Be tidy and close files after you are finished using them. It is particularly important when writing to a file to make sure all data is saved in event of a subsequent crash. All user files are automatically closed when Part File finishes. Note: be sure to read about the OPEN statement further down this list.


Terminates execution of the Part File and returns to ShopBot Main Menu. It is sometimes useful in a file to place an explicit END statement to stop processing and make certain that processing can not move into a section of the Part file such as a section that should only be entered with a GOTO or GOSUB. The use of an END statement can also add clarity to understanding the flow of a program. However, since Part Files are sequential and execute from the first line to the last (unless redirected by a GOSUB or GOTO statement), an END statement is not required in a Part File as the action of the file will terminate on execution of the last statement. Note that an END statement in a nested Part File that is being used as a sub-routine will end the execution of that File and return control to the Command Prompt or the higher level Part File that started or called it.


User variables: User set variables used for advanced programming.

Examples are:

&x_size = 24

&next_file = star.sbp

&my_ZzeroThickness = 0.121

System variables: Variables based on ShopBot control system informations.

Examples actually depends on system states at the moment.

%(1) = X current working coordinate

%(2) = Y current working coordinate

%(3) = Z current working coordinate

%(4) = A current working coordinate

In progress...

Personal tools