Looks like you're trying to use the "regular" (standard?) HP Universal Printing Driver. On the Designjet printers, you cannot use the "regular" HP Universal Printing drivers (any flavor, any version). You have to instead use the "Designjet Universal" driver. (yeah, "universal" drivers that are not really universal)
That is what I have to do with all of the Designjet printers we have if I need to use a driver other than the model specific HP-GL/2 driver.
Hope that helps.
- Paul L.
Can I ask you what the Preferences and Defaults are for the plotters that you have setup?
Usually (but not always), the driver defaults have been sufficient. However, sometimes that isn't sufficient and depending on the printer model you might be unsure what settings to use. Some methods we've used to "import" the printer's settings goes like this:
1. Create (on your Uniprint server) a printer using the Windows method (not Pharos) and point that printer object at the TCP/IP address of the printer during the driver install. HP's drivers (as do most printer drivers) does a query of the printer during the printer setup to determine the option/features/configuration of the printer and set the driver accordingly. Use those detected settings as a "guide" for configuring your Pharos queues for the printer.
2. Temporarily direct the print queue directly to the TCP/IP address of the printer and trigger a auto-configure. For HP drivers, there is in the Device Settings tab a "Automatic Configuration" you can toggle from Off to On, then wait a few seconds while it talks to the printer and pulls in the configuration, after which the printer will update the driver config and switch "automatic Configuration" back to Off. Click Apply.
NOTE: Often, these auto-config methods may not pick up the current paper settings, or will set all installed trays to "Letter" instead of the actual size (or Roll) the printer is set to.
For the settings of these printers in Pharos Uniprint, the Uniprint settings are just like any other printer (but with a designjet driver), except for the Job Cost Method. We have our designjet Job Cost Method set to "Area Costing" at a $ rate per square inch. Something like $0.0032 per square inch, though that may be too low depending on what your users typically print at the location. Our approach was to help the print jobs cost similar to the cost of printing on our color lasers, but a little higher than using the color lasers since more paper is usually used and somethings substantially more ink.
For the settings at the print queues (driver settings at the Windows level):
- For most of our wide-carriage printers, we've been able to leave the Paper source to "Printer auto select" with the Paper Type set to "Any". I usually set the Print Quality to Standard options, "Quality" (rather than "Speed"), or half-way in-between (depending on the level of graphics the location typically prints).
- For those locations where the "default" Paper source may not be specific enough (locations where unit has two rolls, one of "Plain" and the other "Photo" ) we'll take the time to Specify the Paper Source to the Roll that should have the "Plain" paper (typically set to type "HP Universal Bond Paper") and make sure the paper type for Roll 2 has also been specified. We'll often also set the "default" Document size to "Arch D" (36x24 inches)
- If the driver has the option, we've chosen to leave "Show preview before printing" turned off.
- If the location frequently print items smaller than the width of the paper roll, we like to set the driver to "Rotate by 90 degrees" or allow "Autorotate" so that most print jobs are oriented long edge first, thus creating less paper waste.
Does that help?
- Paul L.
We don't have this exact model, but we have lots of designjets. They work no issue using the device specific driver which is generally best. As Paul mentioned, you have to be careful with the settings in the device on the server before packing up the driver for clients. The automatic queries will cause the clients to try to talk to the server like it's a printer which will fail, and that's the biggest issue when using Universal drivers. Make sure all the settings are manually configured as needed before building the package and you should be fine. That said, we also only use PS drivers so we have the best cross platform compatibility, so if the GL give you further trouble try the PS (if available on that device)?