Keithley 2450 Reference Manual page 826

Model 2450 Interactive SourceMeter® Instrument Reference Manual
Mapping events to bits
To program the Questionable and Operation Event Registers, you map events to specific bits in the
register. This causes a bit in the condition and event registers to be set (or cleared) when the
specified event occurs. You can map events to bits B0 through B14 (bit B15 is always set to zero).
When you have a mapped-set event, the bits in the corresponding condition register and event
register are set when the mapped-set event is detected. The bits remain at 1 until the event register is
read or the status model is reset.
When you have a mapped-clear event, the bit in the condition register is cleared to 0 when the event
is detected.
You can map any event to any bit in these registers. An event is the number that accompanies an
error, warning, or informational message that is reported in the event log. For example, for the error
"Error -221, Settings Conflict," the event is –221. Note that some informational messages do not have
a related event number, so they cannot be mapped to a register.
You do not need to map clear events to generate SRQs. However, if you want to read the condition
register to report status, you must map both a set event and a clear event. If no clear event is
mapped, the bits are cleared only when the instrument power is turned off and turned on.
You can use the following SCPI commands to read and map events to bits in the programmable
registers:
•
:STATus:OPERation:MAP
This command maps the set and clear events to a specified operation event register bit. Use the
query form of this command to read the mapped set and clear status.
•
:STATus:QUEStionable:MAP
This command maps the set and clear events to a specified operation event register bit. Use the
query form of this command to read the mapped set and clear status.
You can use the following TSP commands to read and map events to bits in the programmable
registers:
•
status.operation.getmap()
This command reads the mapped set and clear status for the specified operation event bit.
•
status.operation.setmap()
This command maps the set and clear events to a specified operation event register bit.
•
status.questionable.getmap()
This command reads the mapped set and clear status for the specified questionable event bit.
•
status.questionable.setmap()
This command maps the set and clear events to a specified questionable event register bit.
You can map any event that appears with a number in the event queue to any available bit in a
programmable register. The programmable registers and their relationships to the Status Byte
Register are shown in the
example event queue log entries contain actual events that can be mapped to a status model bit.
2731 Trigger Model Initiated "Trigger model #1 has been initiated"
2732 Trigger Model Idle
4917 Reading buffer cleared "Reading buffer <buffer name> is
4918 Reading buffer full "Reading buffer <buffer name> is
5080 SMU Source Limit Tripped "Source limiting is active on output"
5081 SMU Source Limit Cleared "Source limiting is no longer necessary and
output is normal"
See Using the event log
2450-901-01 Rev. B/September 2013
(on page 6-91)
(on page 6-94)
(on page 8-156)
(on page 8-157)
(on page 8-159)
(on page 8-160)
Programmable status registers diagram
"Trigger model #1 has been idled"
(on page 2-117) for additional information on finding events.
Appendix C: Status model
(on page C-6). The following
0% filled"
100% filled"
C-9