Re: Upload versus download

Subject: Re: Upload versus download
From: Chris Morton <salt -dot- morton -at- gmail -dot- com>
To: "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 27 Jan 2015 14:26:22 -0800

Within a communications connection section, this is how I'm taking care of
the problem:

*Note:* When referring to uploading/downloading in the context of
*<company>* PLCs, think of files
as already residing on a PLC. Therefore, you *upload* *from* the PLC to a
laptop computer running *<company's GUI app>*. Files to be transferred from
a laptop are *downloaded to* a PLC (Figure 8-9).

I've included a graphic that shows a picture a PLC on the left, a laptop PC
on the right. A --> arrow between them is labeled UPLOAD, a <-- arrow
labeled DOWNLOAD.

Elsewhere, I include this:

*Note:* Remember that you *upload* *from* a PLC to a laptop computer
running *<company's GUI app>*. Files to be transferred from a laptop
are *downloaded
to* a PLC (Figure 8.9).

> Chris

On Tue, Jan 27, 2015 at 12:38 PM, Andrew Warren <awarren -at- synaptics -dot- com>

> Chris Morton wrote:
> > As we all know, one uploads a file from a PC or similar device to a
> > server.
> > If a resource exists on a server, it is downloaded to the PC (or
> > similar device).
> Ok, but "upload" doesn't simply mean "away from a PC", and download
> doesn't simply mean "toward a PC".
> > John living in his own siloed/silo'd world, everythingâincluding his
> > GUIâis PLC-centric. Therefore, one uploads binaries *from* the PLC
> > to the PC for editing/viewing, then can *download* them back to the
> > PLC.
> >
> > These two terms, upload and download, are used in a way that's
> > counter-intuitive to the rest of us who understand the PCâserver
> > relationship.
> I've been uploading data from small embedded devices to PCs, and
> downloading files back to the devices from PCs, for decades. John's
> usage is certainly not counterintuitive to me, and it might be
> equally familiar to John's customers. You might want to ask.
> > It's one thing for me to make the changes in the manual, but
> > retooling the GUI is a far bigger kettle of fish that will likely
> > meet with much resistance.
> If you do make changes, consider replacing "upload" and "download"
> with "transfer" followed by an explicit direction.
> -Andrew
> === Andrew Warren - awarren -at- synaptics -dot- com
> === Synaptics, Inc - San Jose, CA
Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word |


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

Upload versus download: From: Chris Morton
RE: Upload versus download: From: Andrew Warren

Previous by Author: Upload versus download
Next by Author: Remove colon from TOC-linked Appx title?
Previous by Thread: RE: Upload versus download
Next by Thread: Chassis Ground Symbol

What this post helpful? Share it with friends and colleagues:

Sponsored Ads