Technical writing help


by david90
Tags: technical, writing
david90
david90 is offline
#1
Jan2-12, 03:19 PM
P: 303
I'm writing a report and I'm having trouble coming with the right words to describe a procedure.

Is there a better way to say "Before wiring PB2 (pushbutton) to the relay, refer to the wiring label on the relay to find the relay socket terminals function." ?

What I want to say is learn where the screws on the relay socket go to (coil, contacts etc) before wiring to it.

Phys.Org News Partner Engineering news on Phys.org
PsiKick's batteryless sensors poised for coming 'Internet of things'
Researcher launches successful tech start-up to help the blind
Researchers propose network-based evaluation tool to assess relief operations feasibility
sandy.bridge
sandy.bridge is offline
#2
Jan2-12, 03:26 PM
P: 767
Perhaps direct the reader to a set of schematics which will depict the function of each of the sockets?
technician
technician is offline
#3
Jan2-12, 03:28 PM
P: 1,506
May not be much help but I would say that, in a report or set of instructions, it is not good to say "BEFORE........"
I feel you should say what needs to be done in order !!!!
Imagine a cake recipe.... put 4 eggs in a bowl, add flour , add water, before you put the eggs in the bowl take them from their shells....that sort of thing.

david90
david90 is offline
#4
Jan2-12, 03:29 PM
P: 303

Technical writing help


Quote Quote by sandy.bridge View Post
Perhaps direct the reader to a set of schematics which will depict the function of each of the sockets?
The relay cube that can be inserted into the relay socket has a wiring label (kinda like a schematic) on it.
AlephZero
AlephZero is offline
#5
Jan2-12, 04:07 PM
Engineering
Sci Advisor
HW Helper
Thanks
P: 6,344
I would say something like

Look at the wiring label on the relay and identify the .... and .... terminals. (You might want to add something about HOW to identify them, e.g. the relevant color codes, symbols, or whatever). Then wire PB2 to these terminals.
sandy.bridge
sandy.bridge is offline
#6
Jan2-12, 04:08 PM
P: 767
Then I think it would be suffice to merely prompt the reader to analyze the physical device before attempting to wire it.
Averagesupernova
Averagesupernova is offline
#7
Jan2-12, 07:35 PM
P: 2,451
As someone who has done technical writing for electronic assembly and sub-assembly I have to say that no matter how clear it is made some idiot will find a way to mis-interpret it. Assembly sheets would be distributed at the beginning of a production run and if there was something that was unclear to an assembler they would question me on it and I would explain it to them with some handwritten notes added. Then at the end of the run these sheets would be turned in. I would ask if there are ANY other things that they don't understand and should be made more clear. The answer was no so I made the handwritten notes permanent. What do you suppose happened the next production run? The SAME assembler couldn't understand a different part of the procedure. Hmmmm, last run it was crystal clear and now suddenly you don't get it? After 5 or 6 production runs less than a couple of months apart? I wanted this employee gone so bad.
AlephZero
AlephZero is offline
#8
Jan2-12, 08:30 PM
Engineering
Sci Advisor
HW Helper
Thanks
P: 6,344
Quote Quote by sandy.bridge View Post
Then I think it would be suffice to merely prompt the reader to analyze the physical device before attempting to wire it.
That works (sometimes!) for assembling flat-pack furniture, but not for anything that might be life-threatening. Not unless you want to get sued for damages, anyway.
turbo
turbo is offline
#9
Jan2-12, 08:44 PM
PF Gold
turbo's Avatar
P: 7,367
Technical writing is fraught with pitfalls. First, avoid writing in the passive voice. You will lose a lot of people that way.

My method was to write up a step-by-step procedure (in a list format), and then turn that into prose, with explanations for *why* things should be done in a certain order, including the repercussions for screwing it up. You can include a version of the list before or after the prose, but you really need to get descriptive above and beyond the list. All concerns about safety for the humans and equipment involved ought to be laid out up-front, so there is no room for gross errors. Good luck.

BTW, much of my technical writing was aimed at providing better documentation and system descriptions for the operators of Kraft chemical-recovery boilers in pulp mills. Those monsters generally operated at 600 psi to 900 psi and they could be pretty dangerous if feed-liquor fell out of acceptable solids-concentration parameters. I carried $1M in liability insurance just so I could write those manuals, though a disastrous boiler explosion would eat up the whole $1M in one shot.
jim hardy
jim hardy is offline
#10
Jan3-12, 12:07 AM
Sci Advisor
jim hardy's Avatar
P: 3,138
don't assume the reader will remember the pin-out long enough to wire it up.

if you wish , give him a list of functions of pins

but make your wiring directions one action per step -
eg "connect red wire AA to coil+ , which is terminal 2 ."
action first, location next
order of sentence above tells him he'll need a screwdriver in one hand and red wire AA in other, then directs his eye to where to put them.

little details like that make a procedure followable.


Register to reply

Related Discussions
Electrical Engineering - How important is technical writing? Career Guidance 4
New Forum: Technical Writing Questions Forum Feedback & Announcements 0
Circuit Diagrams in technical writing Academic Guidance 1
Technical Writing Career Guidance 4
Technical Writing - Online Textbook Academic Guidance 0