3-39
3
3.11 OEM DOCUMENTATION AND CONFIGURATION
3.13.1 Firmware Settings
OEM users can set the module's IDN message to identify the company and
product. The Digital I/O configuration can be set to the power turn-on values and
saved. The settings can then be locked so the end-user cannot change them.
3.11.2 WebServer Pages
The OEM can customize the 8099's WebServer configuration pages to identify
the product and incorporate the company logo by following the guidelines in
Application Bulletin AB80-5.
3.11.3 End-User Documentation
OEM users of the this interface 8099 should provide the end-user with the
instructions and utility programs necessary to operate the complete system.
This is not done by passing on the 8099 manual to the end-user since it does not
relate to the end product. In most cases the end-user needs directions for:
1. Setting the product's Network Settings.
2. Resetting the Network Settings when he forgets them.
2. Using commands to control the overall device. (Includes sending
outputs and reading inputs if applicable). The OEM needs to define
the commands in terms of what they do to the overall product and
show the end-user how to use them.
3. Using the trigger functions if applicable.
4. Using the 488.2 Status Reporting Structure. The OEM needs to define
what the digital inputs mean if they are part of the product, how to
enable Service Requests (SRQs) and how to read the registers.
The SCPI Standard requires that the SCPI command tree and SCPI confor-
mance information be passed on to the end-user. This means only the active or
applicable commands. Edit out all unused commands. All locked commands
become invisible to the end-user and should be omitted from the end-user's
SCPI command tree and list.
3.11.4 Utility Programs and Drivers
The following utility programs and drivers should be given to the end-user: