Common G-Code Filename Barcode Formats and Strings

Reference: Common G-Code Filename Barcode Formats & Strings

Various CNC machines differ in their part barcode requirements from the manufacturer, and also in the way they are set up by the machine technician. It is necessary to know those requirements when a part label is configured that contains a file name barcode. 

Some of the commonly used barcode formats are included in Microvellum, but it is impossible to identify all the possible combinations of formats. Therefore, Microvellum provides two other mechanisms for customizing barcodes to match the format required by the machine, or set up by the machine technician. 

One is by creating a custom barcode string in the part label report. This involves setting up a combination of hard strings and field values in the report text component or the report barcode component. If you are using a spreadsheet toolfile, this is the only way to customize a barcode format. 

If you are using an IPP toolfile (Integrated Post Processor), there is another option using the custom string writer described at the end of this article. 

The purpose of this article is to document the commonly used barcode format requirements to use when customizing a label barcode. It will demonstrate some of the typical requirements for a barcode. Be sure to check with your machine technician if you are unsure about the exact format required for your machine!

Spreadsheet Toolfile Face 5 & 6 "Barcode Format" Values:

mvNone
0
mvBarcodeAuto
1
mvBarCodeCNC90
2
mvBarCodeWinCode3
3
mvBarCodeWinCode4
4
mvBarCodeGenesis
5
mvBarCodeFileNameOnly
6
mvBarCodeFileNameandRunField
7
mvBarcodeBiesseCID
8
mvBarcodeBiessePan
9
mvBarcodeWeeke
10
mvBarcodeHolzHer
11
mvBarcodeWinner90
12
mvBarcodeEvolution
13
mvBarcodeOmal
14
mvBarCodeGenCode
15
mvBarCodeFileNameRunfield
16

Manufacturer Barcode Formats:

Auto (filename)
*filename*
CNC90
*filename>>ZONE>>%*
WinCode3
*filename>>ZONE>>%*
WinCode4
*filename>ZONE%*
Genesis
*filename!ZONE* - Default was P&W
File Name & Extension
*filenameExtenstion*
File Name & Run Field
*filename.ZONE*
Biesse CID
*filename>1*
Biesse Pan 
*filename>1*
Weeke
*ZONEFilename*
Holzher
*filename.ZONE*
Winner90
*filename>ZONE%*
Evolution
*%11filename.CNC>ZONE* - Default was P&W
Omal (Not Shown)
*filename>>ZONE%* - Default was S&R
GenCode (Not Shown)
*%11filename>ZONE%* - Default was P&W

Barcode Format Notes: 

">" = Single Space

">>" = Double Space

"ZONE" = Run Field name if populated - second column on the toolfile fields tab. 

"ZONE" = Default Normal Zone or Default Mirrored Zone if Run Field is blank - first column of the toolfile fields tab. 

Spreadsheet Toolfile "Horizontal Barcode Format" Values:

mvNone
0
mvFileName
1
mvFileNameandZone
2
mvAccusystems
3
mvBiesse
4
mvGannomat
5
mvKoch
6
mvOmal
7
mvWeeke
8

Manufacturer Horizontal Barcode Formats:

Auto (filename)
*filename*
File Name & Run Field
*filename.ZONE*
Accusystems
*filename*
Biesse
*filename>1*
Gannomat
*filename*
Koch
*filename*
Omal
*%11filename*
Weeke
*ZONEFilename*

Once the barcode string modifications have been completed, the next step is to verify that the part label barcode scans. A barcode scanner is usually set up to give an audio confirmation when the barcode has been recognized by the scanner as a valid barcode. This is often a beep or other tone. 

If the scanner does not give the audio confirmation, there are a few possible causes. One is that the font of the label barcode component is not one that is supported by the scanner. Confirm from the scanner documentation that the font and font size for the label barcode is correct. 

Another cause may be that barcode string or formatted data is incorrect, even if the format selected is from the dropdown list, as seen below. This is possible because the format may have been altered from the machine default when the CNC machine was setup. To confirm whether that is the case, you will need to get the specific string format information from the machine technician, and then reproduce the elements of that string in the label barcode. Set the Barcode Format to Custom. 


If the scanner gives the audio confirmation, it is still possible that the CNC machine will not load the correct G-Code file and perform the machining operation. 

There are several reasons for this. One is that the part may not be correctly set. Thus, although the file exists somewhere on the machine, and the barcode was recognized as a valid barcode by the scanner, the machine cannot find the file to load. Correct the path before continuing. 

Another potential cause of the problem may be that the file was not created, or contained an error and was deleted. You will need to resolve the cause of that error before proceeding. 

The list of barcode formats above also applies to IPP Toolfiles. To set a custom string, display the IPP Settings interface after purchasing the module and configuring the toolfile as described elsewhere. Once that is complete, open the IPP toolfile in the interface and click Custom Sequence Strings > Custom Barcode. Enter the custom string there. 

See the article "Integrated Post Processor Toolfiles" for more information in the section for Custom Sequence Strings. 


    • Related Articles

    • Auto-Labeling and Creating New G-Code

      Microvellum includes the ability to modify the nest drawings by repositioning parts within the nest. This includes moving parts to another location on the same sheet they originally assigned, rotating parts on the sheet they were initially assigned ...
    • Using Barcode Fonts "3 of 9" and "Code 128b" in Microvellum (Overview)

      The Microvellum reports support a variety of barcode fonts to match the scanning requirements of many popular barcode scanning devices. The two fonts most often used are “3 of 9” (referred to as “Code 39” in this article), and “Code 128b.” This ...
    • Using Barcode Fonts "3 of 9" and "Code 128b" in Microvellum (Tutorial)

      This is a tutorial explaining how to use the Code 128b barcode font and how to install and use the 3 of 9 barcode font in Microvellum reports.   Using Code 128b You do not need to install Code 128b on your machine as the Microvellum Report Designer ...
    • View Single Part G-Code Results

      If you would like to see the single part g-code files that were created for a Single Part G-Code processing station, you can select the View Single Part G-Code Results menu item in the Processing Center. This will display the results window. From ...
    • Issue: Reports Do Not Display Correct Barcode Data in Version 15.6

      Symptom: Reports displaying barcode data from the Parts table are inconsistent or incorrect. This issue has a different cause than when a Part Label displays incorrect face 5 or face 6 barcode data. Click here for more information about that issue. ...
    • Recent Articles

    • Microvellum Foundation Library Release Notes | Build 22.0520

      The following release notes apply to Microvellum Foundation Library, Build 22.0520 Please make sure you are selecting the correct specification group when drawing products. There may be specification groups for both metric and imperial. Additions: ...
    • The Range Hood - Add-on

      About the Library Add-on This is a “Master” Range Hood product capable of being used as is or saved back to the library numerous times in unlimited number of different combinations.  This Library Add-on is compatible with the Foundation Library. This ...
    • Toolbox Release Notes | Build 22.1.0406.641

      The following Release Notes apply to Toolbox Build 22.1.0406.641 Database Management Resolutions: Resolved an issue that caused template level projects to be deleted when deleting a seemingly “empty” category (this was caused by a mix-up in the ...
    • Microvellum Foundation Library Release Notes | Build 22.0407

      The following release notes apply to Microvellum Foundation Library, Build 22.0407 Please make sure you are selecting the correct specification group when drawing products. There may be specification groups for both metric and imperial. Additions: ...
    • Toolbox Release Notes | Build 22.1.0325.641

      The following Release Notes apply to Toolbox Build 22.1.0325.641 Toolfile Resolutions: Resolved an issue in certain post names where the pecking number was not working. Resolved an issue in certain post names where some face 6 machining was falling ...