09.11.2012 Views

Agilent Technologies N2600A WireScope 350 User's ... - messkom.de

Agilent Technologies N2600A WireScope 350 User's ... - messkom.de

Agilent Technologies N2600A WireScope 350 User's ... - messkom.de

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Technical Support<br />

Before you call<br />

��������������<br />

����������������<br />

If you have questions or comments about your <strong>WireScope</strong> <strong>350</strong>, contact<br />

our Technical Support <strong>de</strong>partment.<br />

�������� ���������������<br />

��� �����������<br />

������ �����������<br />

������ �������������<br />

�������ÃÉÃ�����Ã������� ��Ã���������Ã��������<br />

����������� �����������������������<br />

����� �������������<br />

�������Ã�������ÃÉÃ����Ã<br />

����<br />

���������������������������<br />

Additional numbers and locations are available in the <strong>WireScope</strong> Help<br />

menu un<strong>de</strong>r Technical Support. You can also get help at the <strong>Agilent</strong><br />

Technical Assistance Website: http://www.agilent.com/find/assist<br />

Try to solve any problems using the <strong>WireScope</strong> <strong>350</strong>’s built-in Help<br />

system. (See Online Help, on page 1-15.)<br />

When contacting the Technical Support <strong>de</strong>partment, please be ready to<br />

provi<strong>de</strong> the following information:<br />

• Serial numbers and software version of the <strong>WireScope</strong> and<br />

DualRemote units (see Viewing Software and Hardware Version<br />

Information, on page 2-8.)<br />

• Detailed <strong>de</strong>scription of the problem, including the exact wording<br />

of any error messages and what was being done when the error<br />

occurred.<br />

• Company name and street address.<br />

• Contact name and telephone number.<br />

1−21

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!