# Choosing & Connecting Printers

<p class="callout info">The Choosing and Configuring Printers process allows enforcement officers to connect and properly format their mobile Bluetooth printers within the Enforce application. Its primary purpose is to ensure the application communicates with the correct hardware drivers, allowing for clear and accurate physical ticket printing in the field. This article is intended for OPSCOM administrators and field enforcement personnel configuring their handheld devices.</p>

## Setup and Configuration

Before configuring the printer within the OPSCOM application, the physical printer must be powered o<span class="citation-2420 citation-2421 citation-end-2421">n and actively paired to the handheld device via the device's Bluetooth settings.<sup class="superscript embedded" data-turn-source-index="1"></sup></span><span class="citation-2420 citation-end-2420"><sup class="superscript embedded" data-turn-source-index="2"></sup></span>

**<span class="citation-2418 citation-2419 citation-end-2419">Admin Side: <sup class="superscript embedded" data-turn-source-index="3"></sup></span><span class="citation-2418 citation-end-2418"><sup class="superscript embedded" data-turn-source-index="4"></sup></span>**<span class="citation-2416 citation-2417 citation-end-2417">Administrators should ensure the organization's chosen Bluetooth printers (such as Star Micronics or Zebra models) are fully charged, loaded with paper, and paired<sup class="superscript embedded" data-turn-source-index="5"></sup></span><span class="citation-2416 citation-end-2416"> to the assigned handheld device.<sup class="superscript embedded" data-turn-source-index="6"></sup></span>

**<span class="citation-2415 citation-end-2415">User Side (Enforcement Staff): <sup class="superscript embedded" data-turn-source-index="7"></sup></span>**<span class="citation-2414 citation-end-2414">Enforcement officers must configure the application settings to recognize the paired printer and driver bef<sup class="superscript embedded" data-turn-source-index="8"></sup></span>ore issuing their first physical citation.

## Using this Feature

Officers must explicitly select both the appropriate software driver and the specific hardware device within the application's system settings.

### Accessing System Settings

1. Tap **System Settings** from the main menu of the OPSCOM application.
2. Scroll through the menu to locate the specific printer settings options.

### Selecting the Driver and Printer

1. Tap **Bluetooth print driver** to select the proper driver for the hardware you are using.
2. Tap **Bluetooth Printer** to open a list of paired Bluetooth devices.
3. Tap the name of the specific printer you are actively using to finalize the connection.

<p class="callout info">**Default Printer Driver** By default, the printer driver is set to Star Micronics. If you are using a Zebra printer, tap to select Zebra. Selecting the driver will automatically close the pop-up and return you to the main settings menu.</p>

---

## <span style="color: rgb(22, 145, 121);">Best Practices and Considerations</span>

- <span style="color: rgb(22, 145, 121);">**Match your drivers to your hardware:** **It is critical that the selected driver matches your physical printer type.** If these two settings do not match, the printer will either fail to work entirely or it will begin to print out unreadable code and odd characters instead of a properly formatted violation.</span>
- <span style="color: rgb(22, 145, 121);">**<span class="citation-2413">Verify functionality before patrolling:</span>** **<span class="citation-2413">Always issue a test violation after configuration.</span>**<span class="citation-2413 citation-end-2413"> Printing a test ticket ensures the printer is connected, formatting correctly, and working exactly a<sup class="superscript embedded" data-turn-source-index="9"></sup></span>s expected before you step out into the field to begin en</span><span class="citation-2411 citation-2412 citation-end-2412"><span style="color: rgb(22, 145, 121);">forcement.</span><sup class="superscript embedded" data-turn-source-index="10"></sup></span><span class="citation-2411 citation-end-2411"><sup class="superscript embedded" data-turn-source-index="11"></sup></span>