Skip to content

[12.0][ADD] pos_self_service_print_zpl#656

Closed
vvrossem wants to merge 1 commit intoOCA:12.0from
coopiteasy:12.0-add-pos_self_service_print_zpl
Closed

[12.0][ADD] pos_self_service_print_zpl#656
vvrossem wants to merge 1 commit intoOCA:12.0from
coopiteasy:12.0-add-pos_self_service_print_zpl

Conversation

@vvrossem
Copy link

@vvrossem vvrossem commented May 28, 2021

This module extends pos_self_service_base (#655) and handles barcode label printing from the browser using ZPL and Internet Printing Protocol (IPP).

In pos.config (POS Settings), several ZPL related fields are added :

  • Printer Name: Found in CUPS at localhost:631/printers
  • Label Offset X: Origin point of the contents in the label, X coordinate.
  • Label Offset Y: Origin point of the contents in the label, Y coordinate.
  • Label Width: ZPL ^BY command argument
  • Label Height: ZPL ^BY command argument
  • Darkness: ZPL ~SD (set darkness) command. 0 to 30.

Screenshots:
POS Settings
pos_self_service_print_zpl-pos-config

Missing Printer Name
pos_self_service_print_zpl-printer_name

Credits:

@etobella
Copy link
Member

@Fkawala
Copy link

Fkawala commented May 29, 2021

@etobella As far I understand, the module you refer to could be used to format the labels. This add-on handles a different use case. Here @vvrossem and Grégoire Leeuwerck implemented a method to send print jobs to a ZPL-II capable printer using IPP. This enables us to print simple barcode labels straight from the web browser.

@etobella
Copy link
Member

That module depends on base_report_to_printer, that allows to send a report or, in this case, a ZPL Label to a printer using a cups server. So, IMO, you can reuse it.

In my case, I have used this module for 2 years for printing labels, so I am pretty sure that you can use it to solve your issue.

@Fkawala
Copy link

Fkawala commented May 29, 2021

@etobella ok got it, thank you for the comment, it still looks like somehow a different use case, here we are closer to what has been done to print the receipt from the POS. Here, the printers won't necessarily be accessible from the server (actually they should not since that could be a security issue). Or did I miss something @vvrossem ?

@etobella
Copy link
Member

The print server can be another one, so I don't see your point...

@Fkawala
Copy link

Fkawala commented May 30, 2021

@etobella I'm not saying that the print server and the odoo server must be co-located. I'm saying that in order to use https://github.com/OCA/report-print-send/tree/12.0/printer_zpl2 one should have the printer server resolvable FROM the odoo server. Given that we're in a POS-like situation the printer server will not be on a public-facing network (rather on some kind on LAN). Hence the print server should not be accessible from the outside world (nor from the odoo server).

@etobella
Copy link
Member

Well, I do not agree on how you made the integration with the printer, as it depends on localhost... in any case, I would not use this kind of integration as you need to configure all your POS specifically, adding a nginx and so on. I think it is specific for a single implementation.

However, I will not add more comments as I am not an expert in PoS infrastructure.

@legalsylvain
Copy link
Contributor

legalsylvain commented May 30, 2021

Hi @etobella. All the POs devices are depending on the posbox usually installed on localhost. (Or on a common local server).
So the odoo server can not reach thermical printer, scale, led display, payment terminal. Etc.
By design, PoS should work offline.

@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Feb 20, 2022
@legalsylvain legalsylvain added this to the 12.0 milestone Mar 6, 2022
@github-actions github-actions bot closed this Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale PR/Issue without recent activity, it'll be soon closed automatically.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants