Device Specific control in Automation Option

When an Imaging Configuration is set by a Hot Folder or by XML Access, it sets everything that can reliably be set for all of the hundreds of devices that Wasatch supports. That includes ICC profiles, linearization, halftoning, and a very few things that may be device-specific. It does not necessarily set things that are device-specific, such as white ink usage in some cases, and a variety of other things.

It does not set things that are device-specific because of the variability of all of these hundreds of devices. We can't test all of it, and we do know that many device-specific settings cannot be made without involving physical interaction by a human operator. We're not sure about all of them, and we really can't be sure without requiring that all devices come into the Wasatch office for testing. That is not feasible.

It may not work with some of our older drivers for reasons that we can fix with small changes to how the driver initializes itself. Such changes fall into the category of software development, and not service, but they may still sometimes be available for customers under service.

This is the reason that this special control is part of the extra-cost Automation Option. This generally restricts its use to customers who are making an extra investment, and prepared to make extra efforts at system integration.