Measuring Task |
|
What is the intended test method:
|
*
Eg radiated immunity, BCI or alternator ripple test
|
|
What is the EMC standard:
|
Eg ISO 11452-2, MAN 3850
|
Which algorithm shall be used
to control the EMC measuring: |
Eg closed loop method, substitution method |
Room for specifics or remarks
concerning the EMC test execution: |
Eg deviating modulation methods,
blanking of the RF field when changing the frequency, etc. |
 |
Functionality Of Our Tool |
|
Type of software: |
Eg device driver, DLL, stand-alone application
or 'I don´t know' |
|
What shall the software be used for: |
*
Eg control the EMC test, acquiring or
filtering EUT data, Slave-Modul |
|
What functionality shall our software comprise: |
*
Eg GOOD / NO GOOD detection, determining a threshold
of EMC impact, EUT data reporting, EUT data processing,
controlling the EMC test system or the EUT |
How many signals are to be monitored,
which kinds of signals are to be monitored: |
Eg 2x analog voltage, 3x 16 bit word |
Room for specifics or remarks
concerning the functionality: |
Eg report format, closed-loop control
with two controlled values
|
|
|
Your Hardware - The Equipment Under Test (EUT) |
|
Short description of the EUT: |
Eg instrument pack, electronic seat adjustment, ABS ECU |
|
Type of the communication interface: |
*
Eg K line, CAN 1 MBit/s, VAN, LIN
|
Room for specifics or remarks
concerning the EUT:
|
|
|
|
Your Diagnosis Tool |
|
Supplier and type of your diagnosis system:
|
*
Eg Vector CanOe, Peak PCAN, internal company tool
|
Which interfaces does your diagnosis tool provide to communicate with our software:
(Note: Herewith is NOT meant the diagnosis interface of your ECU!)
|
*
Eg environment variable, DLL, serial interface,
no interface available
|
|
Please complete the next fields only, if your diagnosis tool doesn´t provide an additional communication interface:
(Note: In this case our software shall communicate with your ECU directly.)
|
|
Which protocol shall be used to communicate with your ECU: |
Eg KWP2000 |
|
The primary purpose of our software is acquiring data. Are there additional functions needed? |
Eg diagnosis, initialization, reset control, erasing a fault recorder |
Room for specifics or remarks
concerning the diagnosis system: |
|
|
|
The EMC Test System |
|
Where shall our software be used (name of the EMC lab): |
|
Which EMC software is used in this EMC lab:
(This information is needed, because our software shall use the existing EMC calibration data and the devive drivers in certain cases.)
|
*
Eg RSUS, EMS-K1 |
|
Please complete the next fields only, if our software shall control the EMC test:
|
Give us a list of the used test equipment:
(Kind of instrument, manufacturer, type and remote control interface) |
Eg RF generator R&S SMG GPIB, power meter R&S NRVD GPIB,
antenna mover Deisel HD100 GPIB, E-field probe W&G EMR20 RS232
|
Room for specifics or remarks
concerning the EMC test system: |
|
|
|
Who Are You? |
|
Name: |
* |
|
Company: |
* |
|
Department: |
|
|
Street, number: |
* |
|
Postal code / zip code, City: |
* |
|
State (USA only): |
|
|
Country: |
* |
|
Phone (please include your country code): |
* |
|
Fax: |
|
|
e-Mail: |
* |
|
Room for miscellaneous: |
|
|
|