Label printing flow from Zebra ZPL files directly to the printer without broker
RespondidaHello Community,
I would like to submit a feature request that could significantly improve the efficiency of our printing processes. In our environment, the broker is currently located in a German data center, and communication with it requires a VPN connection. This VPN is set to be phased out, which makes our dependency on the broker unsustainable in the long term.
Problem Statement:
-
VPN Dependency and Phase-Out: Since the broker is only accessible through the German data center, all print jobs in our distributed environment are reliant on the VPN. With the planned discontinuation of the VPN, this connection will no longer be available, and seamless print operations through the broker cannot be guaranteed. Direct transmission of print files from the scanner to the printer would help us overcome this dependency.
-
Efficiency Through Small File Size: CR and ZPL files are generally very small, which allows for quick transfer when the scanner and printer communicate directly. By enabling direct transmission, print files could be processed without delays, as they generate minimal data traffic. This would notably speed up the print process and avoid unnecessary latency.
-
Increased Latency and Performance Issues: Routing print jobs through the German data center introduces unnecessary latency, particularly under high print volume, which leads to delays. Direct transfer of the small CR and ZPL files would eliminate these delays, thus accelerating the overall printing process.
-
Stability and Fault Tolerance: The broker-based solution is also vulnerable to network and connectivity issues. Any downtime or instability with the broker or VPN directly impacts the print process, causing disruptions in production workflows. Direct transmission of CR and ZPL files from the scanner to the printer would eliminate this risk entirely.
Proposed Solution:
An option to transmit CR and ZPL files directly from the scanner to the printer, without requiring the broker as an intermediary. This change would make the printing system more future-proof and less prone to disruptions, especially given the planned VPN shutdown. Additionally, due to the small file size, the printing system could become particularly efficient and easier to maintain.
Benefits of the Proposed Solution:
- Independence from the VPN and central broker
- Improved print performance due to fast processing of small files
- Increased system stability and fault tolerance
As the planned VPN shutdown necessitates an alternative, we would greatly appreciate the implementation of this feature. The reasons would likely benefit many companies with similar infrastructures. If further details or testing are needed, I’m happy to assist.
Best regards,
Christian Multrus
-
Hi Christian,
Firstly thanks for taking the time to elaborate on the idea. The idea of redesigning the printing processes both on Scan and WMS is gaining points, your idea is one within the possibilities that I am considering. I am at the discovery phase of this opportunity:- A/ (Your line) Use intermediate files (zpl, xml,csv…) for impression instead of the report launched directly to the printer. A light middleware managing these files is needed.
- B/ Directly generate Control Printing Language for printers instead of using Crystal Reports
- C/ Hybrid solution using files and an external controller. Implement an internal queue table (status, printer, template, retry), generate printing files (by a hookflow in WMS) and use an external service for reading the queue and trigger printing jobs.
Print&Delivery could be the middleware solution as cloud a Bridge managing files, priorities, launch printing jobs and managing errors, retries, logs…this idea have been proposed to the P&D Product manager.
-
Hi Miguel,
when I understood you correct you said you will do an development.
Have you already any news for us.
Does you already sucess implemented something?
What is the current Status?
Do you have any workaround for it
Iniciar sesión para dejar un comentario.
Comentarios
2 comentarios