Driver Download
To download the Boca Systems Mac printer drivers go to our web site, Printer Drivers, Apple/Mac and click on the boca_driver to save the MAC file on the PC. Next, double click on boca.pkg.zip to unzip the file. Boca.pkg will appear on your desktop. Be careful to select the proper print resolution (200, 300 or 600 dpi).
Printer Driver Installation
USB
All instructions are based upon the use of the Intel-based Mac OS X 10.4.9. Other versions of the Mac OS X operating system will operate in a similar, but not identical manner.
-
Double click on boca.pkg to start the install process
-
Hit Continue, Agree and Upgrade as prompted
-
Enter your password and hit ok when prompted
-
Hit Close to complete driver installation
-
Click Add from Printer List
-
Select Printer Name (44 300, 46 200, etc.) from Printer Browser
-
Go to “Print Using”
-
Select correct BOCA printer model (same as the name appearing in the Print Browser)
-
Click Add
Ethernet
All instructions are based upon the use of the Intel-based Mac OS X 10.4.9. Other versions of the Mac OS X operating system will operate in a similar, but not identical manner.
-
Double click on boca.pkg to start the install process
-
Hit Continue, Agree and Upgrade as prompted
-
Enter your password and hit ok when prompted
-
Hit Close to complete driver installation
-
Click Add from Printer List
-
Select IP Printer
-
Go to “Protocol” and select Line Printer Daemon – LPD
-
Enter IP address of printer
-
Go to “Print Using”
-
Select correct BOCA printer model (verify correct print resolution – 200, 300 or 600 dpi)
-
Click Add
If the BOCA printer model is not available under “print using”, you can either restart your computer or reset the printing system as described below. Please note that resetting the printing system will delete all of your previously installed printers from the Printer List.
-
Go to finder/applications/utilities/printer setup utility
-
Go to the “printer setup utility” menu at top of the screen
-
Pull down and hit reset printing system
-
Enter password
General
A printer driver translates the graphical information displayed in your Mac application into a printer friendly format. In order to properly format the data, the user must correctly establish the page size and margins. In general, you should use the smallest margins which do not cause the data to wrap around to the opposite side of the ticket. Apple supports the following methods of defining page sizes:
-
Vendor (BOCA) Defined - We have pre-defined some common page (ticket) sizes which can be used with any Windows application. You must use a BOCA defined page size to define your document. If you cannot locate the proper size, choose the next larger size and use the margins to define your ticket size.
-
Custom Size - This option does not work properly. We do not recommend the use of this method.
Linux Printer Drivers
Driver Download
To download the Boca Systems Linux printer drivers go to our web site Printer Drivers, Linux and click on one of the driver files listed. The 32 bit files can be used with either intel or amd based computers. The 64 bit drivers must be targeted for the appropriate manufacturer’s hardware. The .deb files are intended for Ubuntu, Debian and most other Linux versions with the exception of Suse and Redhat which should use the .rpm files.
Place the appropriate driver file on your desktop. Be careful to select the proper print resolution (200, 300 or 600 dpi).
Printer Driver Installation
Parallel, Serial, USB
All instructions are based upon the use of the Ubuntu version of Linux. Other versions of the Linux operating system will operate in a similar, but not identical manner.
-
Right click on the driver to start the install process (kubuntu package menu/install package)
-
Enter your password
-
Hit enter to exit installation as prompted
-
Go to System Settings/Printers
-
Click Add from Printers – System Settings
-
Add Printer/Class
-
Hit next and select local printer (parallel, serial, USB)
-
Select BOCA printer from Local Port Selection
-
Select correct BOCA printer model (verify correct print resolution – 200, 300 or 600 dpi) from Printer Model Selection
-
Select Driver from Driver Selection
-
Continue hitting “next” as required until printer name is requested
-
Enter a printer name from General Information
-
Hit next until installation complete
Ethernet
All instructions are based upon the use of the Ubuntu version of Linux. Other versions of the Linux operating system will operate in a similar, but not identical manner.
-
Right click on the driver to start the install process (kubuntu package menu/install package)
-
Enter your password
-
Hit enter to exit installation as prompted
-
Go to System Settings/Printers
-
Click Add from Printers – System Settings
-
Add Printer/Class
-
Hit next and select network printer (TCP)
-
Enter Printer IP Address from Network Printer Information
-
Select correct BOCA printer model (verify correct print resolution – 200, 300 or 600 dpi) from Printer Model Selection
-
Select Driver from Driver Selection
-
Continue hitting “next” as required until printer name is requested
-
Enter a printer name from General Information
-
Hit next until installation complete
If the BOCA printer model is not available in “Printer Model Selection”, you can either re-install the driver or restart your computer.
General
A printer driver translates the graphical information displayed in your Linux application into a printer friendly format. In order to properly format the data, the user must correctly establish the page size and margins. In general, you should use the smallest margins which do not cause the data to wrap around to the opposite side of the ticket. Apple supports the following methods of defining page sizes:
-
Vendor (BOCA) Defined - We have pre-defined some common page (ticket) sizes which can be used with any Windows application. You must use a BOCA defined page size to define your document. If you cannot locate the proper size, choose the next larger size and use the margins to define your ticket size.
-
Custom Size - This option does not work properly. We do not recommend the use of this method.
Printer Models (adjustable vs. fixed and reverse adjustable)
Due to a variety of legacy issues and driver limitations, an adjustable FGL printer operating in portrait mode requires an command in order to properly format the ticket. This command only needs to be sent once as it is permanently stored in the printer's memory. (You can send the printer an command to reverse an erroneously sent command.) Please note the manner in which the printer formats the ticket in the various scenarios shown below.
NOTE: The , and commands should not be used with any Mag printers printers.
MAGMINI SEQUENCE
|
MAG/Lemur-M SEQUENCE
|
MAG/Lemur-M SEQUENCE
|
INITIALIZATION SEQUENCE
|
INITIALIZATION SEQUENCE
|
INITIALIZATION SEQUENCE
| -
Ticket feeds forward through magnetics module to register ticket
|
Ticket feeds forward into burster
|
Ticket feeds forward into burster
| -
Ticket reverses to encode position
|
Burster separates ticket
|
Burster separates ticket
|
|
|
|
|
|
|
NORMAL OPERATION
|
MULTIPLE TICKET OPERATION
|
SINGLE TICKET OPERATION
| -
CPU sends magnetics data, followed by ticket data
|
CPU sends magnetics data, followed by ticket data
|
CPU sends magnetics data, followed by ticket data
| -
Printer starts encode process
|
Printer starts encode process
|
Printer starts encode process
| -
Burster separates ticket
|
Magnetics data is verified
|
Magnetics data is verified
| -
Ticket moves through print station, while the next ticket is reversed through magnetics to the pre-encode location
|
Ticket moves through print station, while the next ticket is separated in the burster
|
Ticket moves through print station, while the next ticket is separated in the burster
| -
Ticket ejected after printing
|
Next ticket starts to encode and verify magnetics data (note: this step is bypassed if valid data is not received from CPU prior to this point)
|
Current ticket ejected
| -
Next ticket starts encoding
|
Current ticket ejected after printing, while next ticket completes mag verification
|
Next ticket starts encoding
|
(NOTE: The “next ticket starts encoding” function will eventually be performed while the ticket is being printed)
|
Repeat “ticket moves through print station” step
|
|
Please note that the Mag/Lemur-M’s multiple ticket mode is significantly faster than other modes of operation. However, the multiple ticket mode requires the new ticket data to arrive at the printer prior to printing the previous ticket data.
COMMAND FORMATS and COMMUNICATIONS
-
All printing related commands will be handled in accordance with BOCA’s FGL IV programming guide.
-
Any error in writing to the magnetic strip will cause the printer to automatically print a “void” ticket.
-
To print a ticket without magnetics, just send a valid ticket with a print command. The printer will automatically bypass the encoding operation. Note: The operation of the write magnetics command “” is undefined unless magnetic data is sent to the printer. If printing tickets without magnetic data this command should be removed from the ticket format along with the magnetic track commands “ - ”.
-
All transmissions to and from magnetics will be as defined below. These functions will follow normal FGL formats.
CPU COMMANDS
COMMAND
|
Definition
|
Printer Response
|
|
|
|
|
write track 1 magnetics
|
|
|
write track 2 magnetics
|
|
|
write track 3 magnetics
|
|
|
write track 4 magnetics
|
|
|
start writing magnetics
|
ACK or NAK after completion of encode
|
|
burst length
|
|
The burst length is preset at the factory and should not require adjustment by the customer. In the event that the ticket is not bursting at the proper location, the burst length # should be adjusted to a value slightly greater than or less that the actual ticket length. The ticket length is defined as the number of dot columns in the ticket. (For example, a 8”, 203.1 dpi ticket is approximately 1624 dots long; at 305 dpi, the ticket is 2440 dots long.)
The magnetics section of the printer is shipped from the factory in either the ATB or ISO (1 thru 3 track) configuration. Please address the magnetics in the format appropriate to your configuration type:
ATB FORMAT
The data for each track must be terminated with either an EOT (04H) or a lower case z . All data must be sent in accordance with the ATB specification.
Typical ATB data stream
block1 ; block2 ; block3 EOT
block1 ; block2 ; block3 EOT
block1 ; block2 ; block3 EOT
block1 ; block2 ; block3 EOT
NOTES:
-
Do not insert spaces in data stream. Spaces are for readability only.
-
All 4 tracks support alphanumeric data.
-
The “;” (block separator character) must be sent between blocks whether or not there is any data in a given block.
-
Maximum number of characters per block: Block 1 = 60; block 2 = 60; block 3 = 40.
ISO FORMAT
The data for each track must be terminated with either an EOT (04H) or a lower case z. All data must be sent in accordance with the ISO specification.
Typical ISO data stream
block1 EOT
block1 EOT
block1 EOT
NOTES:
-
Do not insert spaces in data stream. Spaces are for readability only.
-
ISO data contains only one block of data and no block separator characters.
-
A start, stop and LRC byte are automatically inserted into each track of data. These three characters are counted among the maximum characters allowed per track.
-
Tracks 1 supports alphanumeric data. Tracks 2 & 3 are numeric only.
-
Maximum number of characters per track: Track 1 = 79; track 2 = 40; track 3 = 107
Share with your friends: |