When the communication between the RIP/Calibrator and the HP Latex leads to errors that are not related to connectivy (like TCP issues, firewalls, etc) then a communication log needs to be created.
This applies to:
- HP Latex 630 series
- HP Latex 700 series
- HP Latex 800 series
- HP Latex 3600 series
- HP DesignJet Z6 series
- HP DesignJet Z9 series
- HP DesignJet XL series
- HP PageWide XL series
This option is available in version 6.7 and above.
To create a communications log create and empty log file at the following location:
- Windows: C:\Users\Public\PrintFactory\Logs\HPLog.txt
- macOS: /Users/Shared/PrintFactory/Logs/HPLog.txt
Logging will start the next time the RIP is started. As soon as the log file is in place all communication is logged until the HPLog file is no longer at the given location.
The log file can then be provided to the PrintFactory support department, who can escalate it to engineering for further investigation.
Related Articles
HP Job status reporting - settings in IPS
When enabling the Job Status tracking for HP Latex series, following setting on the IPS need to be enabled. The communication for copy count and ink status is reported back to the RIP via JMF notifications. In case the jobs are removed from queue, it ...
Installing an HP Scitex 15000: Driver Selection Guide
When setting up an HP Scitex 15000, it's crucial to select the correct driver for seamless integration with PrintFactory RIP. Here’s what you need to know: 1. Setting Up PrintAgent The HP Scitex 15000 requires the use of PrintAgent. Before ...
Community profiles
Printer profiles made available by either the dealer, manufacturer or PrintFactory can be imported directly into Calibrator after loading the driver to the RIP. A pop-up windows appears showing all new pmms/ iccs available to automatically install. ...
Canon Colorado communication triage
When the communication between the RIP/Calibrator and Canon Colorado leads to errors that are not related to connectivy (like TCP issues, firewalls, etc) then a communication log needs to be created. To create a communications log create and empty ...
Faulting module C:\Windows\SYSTEM32\MSVCP140.dll in Event Viewer
If an application is crashing and in the Event Viewer on Windows shows: Faulting module path: C:\Windows\SYSTEM32\MSVCP140.dll i Then this means that the Microsoft Visual C++ Redistributable Version is faulty or missing. To resolve, please download ...