You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: bloom_lims/docs/printer_config.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,17 @@
1
1
# Zebra Printer Configuration
2
-
Bloom relies on [zebra_day](https://github.com/Daylily-Informatics/zebra_day)to administer the lab printerfleet and broker print requests. Please see that repository for printer-specific setup details. The notes below are a Bloom-focused quick reference.
2
+
Bloom relies on [zebra_day](https://github.com/Daylily-Informatics/zebra_day)as the authoritative printer-fleet service. Bloom fetches shared printer, template, and label-profile state from the zebra_day API and submits print jobs back to zebra_day for delivery. Please see that repository for printer-specific setup details. The notes below are a Bloom-focused quick reference.
3
3
4
4
5
5
## Printer Setup
6
-
*From the venv you are running Bloom from, the `zebra_day` package should be pre-installed. To start the admin web interface, from your venv, run `zday_start`. This will start the admin web interface on port 8118 on the machine you are running Bloom from.
6
+
* Bloom does not start or manage zebra_day. Configure the running zebra_day service with `bloom.zebra_day.base_url` and `bloom.zebra_day.token` or the equivalent `BLOOM_ZEBRA_DAY__*` environment variables.
7
7
8
8
### Detect Printers On Your Local Network
9
9
_this MUST be done at least once when setting up a new bloom install_ && _done again when adding new printers_
10
-
*`zebra_day` can scan the local network (barring firewal rules blocking this) and update the venv printer config file with detected printers. Open the `Scan Network For Zebra Printers` page @ `http://localhost:8118/build_new_printers_config_json`. You IP prefix should be auto detected, else enter the first three sections (ie `192.168.1`). Enter a few character 'Lab Code' (only alphanumeric, no whitespace, etc.), this will be the code under which detected printers are added to the json config. The scan might take a few minutes to complete.
10
+
*Use the zebra_day admin UI to discover printers, assign printer IDs, and manage default label profiles. Bloom reads those shared records remotely; it no longer rebuilds local printer JSON.
11
11
12
12

13
13
14
-
* The scan will return all detected printers. The `Lab Code` + `Printer Name` will uniquely identify each printer config. There are several label styles included with `zebra_day`, you may specify a label style with each print request. Make sure the label stock matches the label style. See `zebra_day` docs for more information on label styles. I will use the common `2x1in` label style for the rest of this document. From the `zebra_day` admin web interface, you can print a test label to verify the printer is working.
15
-
16
-
* The printers visible in the Scan Report will be the printers available in the bloom UI. NOTE- you may change names of the printers, see the zebra_day docs for more information.
14
+
* The printers visible in zebra_day are the printers available in the Bloom UI. Bloom stores the selected zebra_day `printer_id` as the user preference value and uses zebra_day label-profile names for `label_zpl_style`.
0 commit comments