Supplementary English-Only Training Materials
Note: These materials are offered only in English as supplementary examples for a deeper dive into Fiery LLC products.

ADA Driver - Setup

---

Assumptions:

So as to avoid needless redundant setup and a lot of wasted time and effort, it is much more efficient to make sure the "base" selected driver is driving the machine exactly as it needs to and any technical problems have been resolved. Therefore, verify that is the case before beginning.

For this example, we will use the "Mach 3 Controller No ATC" driver as the foundational driver on which the customizations are based.

Step 1:

In Engraving Default, select the foundational driver, then use the "Create Custom Copy of Selected Driver" to create the new driver. The correct naming of each driver is critical to the ADA Plot system being able to identify the valid drivers. Those unique names can probably go at the beginning or the end of the base driver name, but prefer the beginning.

The Braille driver MUST have "ADA Braille"

The Raised driver MUST have "ADA Raised"

The Visual driver MUST have "ADA Visual"

Step 2:

Setup the Engraving Defaults for the custom drivers.

ADA Braille:

ADA Raised:

ADA Visual:

Step 3:

Test that the ADA Plot dialog is functioning correctly. Meaning, selecting the "Setup" button beside each of the given types should automatically find and display the corresponding driver that were created and setup in steps one and two.

For Example, selecting the "Setup..." button beside the "Cut Braille Text" button must display the dialog with the "ADA Raised - ...." driver automatically selected. If it does not, there is likely a typographical error in the custom driver name (see instructions in Step 1 for proper driver naming).

Step 4:

Customize the driver ini files as appropriate:

Generally, the ADA Raised and ADA Visual drivers do not need any additional customization to what was already setup within the Engraving Defaults dialog.

Customization for the ADA Braille driver:

• Step A. Add a braille tool (type 6) to the tool list and set it as the default tool.

Since there is a maximum of four tools allowed, this almost always requires one to sacrifice an existing tool.

Discuss this with the end user so as to choose wisely. In the example case, Tool 4 was sacrificed.

[TOOLS]

Number Of Tools=4

Tool 1 Name=Default tool

Tool 1 Type=9

Tool 2 Name=Tool 2

Tool 2 Type=9

Tool 3 Name=Multi-pass 1

Tool 3 Type=8

Tool 4 Name=Braille

Tool 4 Type=6

Number Of Selected Tool=4

Step B. Setup [MoveControl] section

[MoveControl]

Variables=7 ;Incremented VARIABLES= from "6" to "7"

*Vn=Name,Units,lowlimit,highlimit,command

V1=Plunge velocity,in/sec,0,10000,~

V2=Move velocity,in/sec,0,10000,~

V3=Clearance height,.001in,0,30000,~

V4=Cut velocity,in/sec,0,10000,~

V5=Tool Change, ,1,20,T%d

V6=Spindle speed,RPM,0,21600,S%d M03

V7=Braille Depth,.001in,-10000,10000,~ ;Added the V7 line and syntax.

;V5=Dwell,sec,0,500,G04 X%d

GCodeBrailleVar=7 ;Identifies that there is a Braille depth variable and specifies the variable number

Step C. Setup the individual Tools sections to respect the new variable.

It is undesirable to have the Braille control show up in the Tool Options if the selected tool is something other than the Braille tool. Therefore, setting each tool to the correct number of options is desirable. In the example below, notice that variables=6 for all except Tool4, where Variables=7.

[Tool1]

ToolInit=

ToolEnd=

Variables=6

Camera=0

[Tool2]

ToolInit=

ToolEnd=

;MoveZ=G01W%.3lf

Variables=6

Camera=0

[Tool3]

ToolInit=

ToolEnd=

Variables=6

Camera=0

[Tool4]

ToolInit=

ToolEnd=

Variables=7

Camera=0

XYSpeed=4

ZSpeed=1

Step d. Add to driver's "[Setup]" section: "zerofromtable=1" (without the quotation marks).

This step may NOT be required but - for the example driver - was needed to ensure that the selected braille drill depth would actually be inserted into the output stream. Without that setting, the Z value was being erroneously set to zero.

This step may soon (some time after 23Dec2021) not be required as a code change may soon be in the works to make the Braille depth be respected without any special mystery settings.