USB Mimaki port cannot be opened
Problem/Question
Printing is not possible, the Mimaki printer rejects the data when sending a job from the PrintQueue.
The message above indicates, that the USB communication cannot be established properly.
The communication between the PC and the printer (firmware) is managed by a USB driver provided by Mimaki.
Solution/Work-Around
Most probably, you won't be able to fix this within Ergosoft. Still, there are some attempts you should consider.
- If supported, connect your device via TCP-IP port.
- Contact your Mimaki dealer to clarify whether your printer's firmware matches the Mimaki USB driver.
- Reach out to Mimaki regional/global support.
Related Articles
Mimaki USB connectivity issues
Problem/Question RIP PC or Ergosoft gets no connection to the printer or data transfer stops in the middle of printing using a USB connected Mimaki printer. Solution/Work-Around Check the connection of the USB Cable Remove the USB cable at the end of ...
Connect Multiple Mimaki USB printers
Problem/Question When connecting several Mimaki USB printers to one Ergosoft RIP PC, connection problems might come up and the question arises “How do I set up multiple Mimaki USB Printers to run on the same PC?" Mimaki has no set restriction on how ...
Use Epson USB port
Problem/Question How is an Epson USB Port added to the Print Environment? Since there is no Option for it when adding a new Port. Solution/Work-Around As Epson USB does not have its own interface between the Ergosoft RIP and printer, a Windows ...
Mimaki – Parameter Error (PICT)
Problem/Question When sending a job to a Mimaki printer, the job is not printed and you get an error message on the printer display. The print settings and device options of the current Print Environment are not supported by the printer. This may be ...
Mimaki – Missing job details in Mimaki PICT
Problem/Question Printed jobs with the Ergosoft RIP miss job details (e.g., media name) in Mimaki’s dashboard of the Cloud Technology PICT (https://mimaki.com/product/software/remote/pict/). This may be because you are using a Print Environment that ...