Telos TWOx12 - General Troubleshooting

TELOS TWOX12 USER’S MANUAL
TECHNICAL DATA & TROUBLESHOOTING
CHAPTER 8 145
• Near the back of the main PC board (PWB) you will see a power harness from the power
supply to the motherboard with a 4-pin white Molex style connector and a very small PC
board (the SIMM module) directly in front of it.
• Push gently outward on the two metal catches on either end of the SIMM module. It
should pop toward you.
• Pivot the top of the SIMM module toward you and then lift it out. Note the grooved notch
on the right end.
4) Install the new SIMM module.
• Locate the notch on the SIMM module to your right (towards the rear of the TWOx12).
• At a 30 degree angle from vertical, insert the SIMM module into its socket. It should
slide in with no resistance. The module will be angled towards you.
• Using your two thumbs push on the green area near either end of the SIMM module. The
top of the SIMM module should pivot back and the catches on either side should click. If
this does not happen remove the SIMM module (see step 3, above) and try again.
5) Reinstall top cover
6) You may need to reprogram some of your settings, check them after installing the new
software.
Please return the old SIMM module to Telos, via regular US Mail. Your prompt return of this
module will allow us to continue to offer you upgrades in the future, at the lowest possible
cost.
8.3 General Troubleshooting
Thinking About Problem Solving
Despite best intentions, something could always go wrong. Sometimes troubleshooting a
balky set-up can make even the toughest engineer a Maalox and Rogaine addict.
You can't fix any system without the right world view; a zeitgeist of suspicion tempered by
trust in the laws of physics, curiosity dulled only by the determination to stay focused on a
single problem, and a zealot's regard for the scientific method. Perhaps these are
characteristics of all who successfully pursue the truth. In a world where we are surrounded
by complexity, where we deal daily with equipment and systems only half-understood, it
seems wise to follow understanding by an iterative loop of focus, hypothesis, and experiment.
The notions here apply whether you are solving problems at the system level or at the
component level. At the system level, the actions you might take would be very different –
checking cables, trying different menu settings – but the thinking is the same.
Too many times, we fall in love with our suppositions. We are quick to overtly or
subconsciously assume the problem being chased is due to lousy design, the stupid phone
company, or the manager’s latest memo.
Armed with a healthy skeptical attitude, the basic philosophy of troubleshooting any system
is to follow these steps:
• Observe the behavior to find the apparent problem;