Skip to main content

Scanning to USB with the Xerox WorkCentre 3210 and 3220 (part 1)

The WorkCentre 3210 and WorkCentre 3220 are two variants of an entry level Xerox business level multifunction printer.  The couple bring a lot to the table in terms of features and longevity, but it's not always clear as to how to operate the machines.  While the printers do come with a manual, like most documentation for consumer devices, it's awful.  Well, awful in that it's brief.

It's a catch 22 situation really.  Literature for consumer devices is seldom referred to, but there's, for some reason, a demand for it.  As a consequence, it's typically brief and offers no assistance when problems arise.  This is the first of a two-part piece on extending the documentation that comes with the 3210/3220.


Scanning to USB:  The media


This first piece is actually a log of the troubleshooting steps used to resolve a problem with the scan to USB feature.

The WorkCentre has a feature whereby it can scan documents directly to a drive through its built-in USB port.  Upon attempting this for the first time, there was some difficulty getting the device to scan.  In fact it wouldn't even try.  Instead what happened was the printer stepped through some output on the LCD display panel.  It said, "Updating Data Please Wait...."  The printer would go through this step and then just return to the state it was in before.  After trying a few things such as using different SD cards, verifying that there was enough space on the disks, and reformatting one, all attempts were abandoned.

The disk that was connected to the printer was an SD card via a USB card reader.  The next attempt was with an actual USB flash drive and this was the ticket!  For whatever reason, card readers are not allowed.  Using the flash drive however, the scanner started right away without a hitch.  It should be noted though, that the "Updating Data Please Wait..." operation was run again.  Only this time, it was after the scan.  It's not clear what this step in the process is actually accomplishing, but it will likely run with each scan.

Part 2:  The document files

Comments

Popular posts from this blog

Skype Now Supports Emergency Calls In the US

With the latest round of updates to Skype , it was noticed today that the instant messaging and VoIP phone service now supports emergency calling in the United States. The release notes for the most recent update to the Android version of Skype indicated that the service now allows calls to be made to US emergency calling systems via 911.  Telephony services like Skype, Google Voice , and Vonage typically don't offer this emergency calling ability without some sort of intermediate step like deferring to the phone's default dialer, as is the case with Voice, or setting up a physical address location ahead of time which is how Vonage handles it. The indication is that Skype will handle the 911 calls natively, but when verifying with an account that does not have a Skype phone number assigned to it, it was found that the instructions in the FAQ explaining how to turn on emergency calling are not accurate. Emergency calling support in Skype for the United States Interestingly, th...

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ).  From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.

Chrome Itself Logs Into Google When Logged Into Company's Services

Google has taken the liberty of logging Chrome into the user's account whenever logged in to any Google service. Some time ago, Google introduced the ability to have its browser, Chrome, log into the user's Google account whenever the user authenticated for any Google service.  That is, log in to Google Docs, for example, and the browser would be logged in as well. The pitch was that this relationship between being logged in to a service and the browser also being logged in, can help mitigate confusion when a user logs out of a Google service but fails to realize the browser is still logged in.  The mystery can be eliminated if the browser keeps the two in the same state automatically. There is the added benefit that the browser would be better able to synchronize the user experience across each browser that was also logged into the user's account. For example, Chrome on a mobile device could have access to the history from Chrome on a laptop. The idea is not nove...