Text preview for : Series 3700 Release Notes V1.41.pdf part of Keithley Series 3700 Release Notes V1.41 Keithley 3706 fw Series 3700 Release Notes V1.41.pdf
Back to : Series 3700 Release Notes | Home
Series 3700 System Switch/Multimeter
Keithley Instruments, Inc.
28775 Aurora Road
Firmware Release Notes
Cleveland, Ohio 44139-1891
1-888-KEITHLEY
http://www.keithley.com
Contents
General Information ............................................................................................................................... 3
Supported models ........................................................................................................................... 3
Installation instructions.................................................................................................................... 3
Upgrade considerations for Models 3706, 3706-S, 3706-NFP, 3706-SNFP................................ 3
Version 1.41 Release............................................................................................................................. 4
Overview .......................................................................................................................................... 4
Version 1.41 installation notes........................................................................................................ 4
Upgrading from firmware version 1.31a or any earlier version .............................................. 4
Upgrading from firmware version 1.32a .................................................................................. 5
Critical fixes ..................................................................................................................................... 6
Enhancements................................................................................................................................. 7
Noncritical fixes ............................................................................................................................... 8
Known issues ................................................................................................................................ 13
Version 1.40 Release........................................................................................................................... 14
Overview ........................................................................................................................................ 14
Version 1.40 installation notes...................................................................................................... 14
Upgrading from firmware version 1.31a or any earlier version ............................................ 14
Upgrading from firmware version 1.32a ................................................................................ 15
Critical fixes ................................................................................................................................... 16
Enhancements............................................................................................................................... 18
Noncritical fixes ............................................................................................................................. 24
Known issues ................................................................................................................................ 28
Version 1.32a Release......................................................................................................................... 30
Overview ........................................................................................................................................ 30
Version 1.32a installation notes.................................................................................................... 30
Critical fixes ................................................................................................................................... 31
Enhancements............................................................................................................................... 31
Noncritical fixes ............................................................................................................................. 31
Known issues ................................................................................................................................ 32
Version 1.31a Release......................................................................................................................... 33
Overview ........................................................................................................................................ 33
Critical fixes ................................................................................................................................... 33
Enhancements............................................................................................................................... 34
Noncritical fixes ............................................................................................................................. 34
Known issues ................................................................................................................................ 34
Version 1.30j Release.......................................................................................................................... 35
Overview ........................................................................................................................................ 35
Critical fixes ................................................................................................................................... 35
Noncritical fixes ............................................................................................................................. 36
Known issues ................................................................................................................................ 37
Version 1.24b Release......................................................................................................................... 38
Overview ........................................................................................................................................ 38
Critical fixes ................................................................................................................................... 38
Enhancements............................................................................................................................... 38
Noncritical fixes ............................................................................................................................. 38
Known issues ................................................................................................................................ 38
Version 1.22d Release......................................................................................................................... 39
Overview ........................................................................................................................................ 39
3700S Release Notes V1.40 / May 2010 1
Series 3700 Firmware Release Notes Contents
Critical fixes ................................................................................................................................... 39
Enhancements............................................................................................................................... 39
Noncritical fixes ............................................................................................................................. 39
Known issues ................................................................................................................................ 39
Version 1.22c Release......................................................................................................................... 40
Overview ........................................................................................................................................ 40
Critical fixes ................................................................................................................................... 40
Enhancements............................................................................................................................... 41
Noncritical fixes ............................................................................................................................. 41
Known issues ................................................................................................................................ 41
Version 1.21 Release........................................................................................................................... 42
Overview ........................................................................................................................................ 42
Critical fixes ................................................................................................................................... 42
Enhancements............................................................................................................................... 43
Noncritical fixes ............................................................................................................................. 44
Known issues ................................................................................................................................ 44
Version 1.20 Release........................................................................................................................... 45
Overview ........................................................................................................................................ 45
Critical fixes ................................................................................................................................... 45
Enhancements............................................................................................................................... 47
Noncritical fixes ............................................................................................................................. 47
Known issues ................................................................................................................................ 48
Version 1.10 Release........................................................................................................................... 49
Overview ........................................................................................................................................ 49
Critical fixes ................................................................................................................................... 49
Enhancements............................................................................................................................... 50
Noncritical fixes ............................................................................................................................. 52
Known issues ................................................................................................................................ 54
Version 1.03 Release........................................................................................................................... 55
Overview ........................................................................................................................................ 55
Critical fixes ................................................................................................................................... 55
Enhancements............................................................................................................................... 56
Noncritical fixes ............................................................................................................................. 58
Version 1.00 Release........................................................................................................................... 59
Overview ........................................................................................................................................ 59
2 3700S Release Notes V1.40 / May 2010
Series 3700 Firmware Release Notes General Information - Supported models
General Information
Supported models
This firmware is used on the following Keithley Instruments products:
Models 3706, 3706-S, 3706-NFP, 3706-SNFP, and all Series 3700 cards
Installation instructions
NOTE Upgrading to firmware version 1.40 or greater may require special installation steps that are
not required for other firmware upgrades. Carefully read the Version 1.41 installation notes
below before upgrading your Series 3700.
For other releases, firmware installation instructions are given in the "Upgrade Procedure using the USB Flash
Drive" section in the Series 3700 User's Manual (document number: 3700S-900-01). This manual is available the
Keithley Instruments website at http://www.keithley.com/support. Alternatively, you can get upgrade assistance
from Keithley by calling your local Keithley support office.
Upgrade considerations for Models 3706, 3706-S, 3706-NFP, 3706-SNFP
This release updates the firmware for the Series 3706 mainframe and the optional digital multimeter (DMM).
The following table lists the considerations that should be made when deciding whether or not to upgrade to this
version from any previous version.
Upgrade considerations
Existing Recalibration Requalification Backward Should you upgrade?
firmware required? suggested? compatibility
version concerns?
1.00 No Yes No Yes
1.03 No Yes No Yes
1.10 No Yes No Yes
1.20 No Yes No Yes
1.21 No Yes No
1.22c No No No Yes, if using a Model
3740 card
1.22d No No No Yes, if using a Model
3740 card
1.24b No No No Yes, for web-based
charting feature; Model
3731 card supported
1.30j No No No Yes, to avoid security
warning
1.31a No No No Yes, if using Ethernet
1.32a No No No Yes, if using a Model
3732 card
1.40 No No No Yes
3700S Release Notes V1.40 / May 2010 3
Version 1.41 Release - Overview Series 3700 Firmware Release Notes
Version 1.41 Release
Overview
The Series 3700 version 1.41 firmware is an enhancement and problem fix release. Some problem corrections
may impact compatibility, please review the corrections prior to installation.
NOTE Upgrading to firmware version 1.41 from a version below 1.40 requires special installation steps that
are not required for other firmware upgrades. Carefully read the Version 1.41 installation notes below
before upgrading your Series 3700.
The following table lists the exact version numbers of the available Series 3700 components when the firmware
upgrade is complete.
Model Version
Series 3700 Mainframe 1.41c
Series 3700 High Performance DMM 1.41b
3720 Dual 1x30 Multiplexer 1.40h
3721 Dual 1x20 Multiplexer 1.40h
3722 Dual 1x48 High Density Multiplexer 1.40h
3723 Dual 1x30 High Speed Reed Relay Multiplexer 1.40j
3724 Dual 1x30 FET Multiplexer 1.40j
3730 Dual 6x16 High Density Matrix 1.40h
3731 Dual 6x16 High Speed Reed Matrix 1.40j
3732 Quad 4x28 High Speed Reed Matrix 1.40m
3740 32 Channel Isolated Switch 1.40h
3750 Multifunction I/O Card 1.40j
Version 1.41 installation notes
Upgrading to firmware version 1.41 requires special installation steps that are not required for other firmware
upgrades. Carefully perform the following procedures to successfully upgrade to version 1.41.
First, determine your instrument's current firmware revision. With the instrument powered on, press the SLOT
key. The instrument's current firmware version is displayed. Based on the current firmware revision, follow the
instructions in the appropriate section below.
Upgrading from firmware version 1.31a or any earlier version
Download the nk_5001607.nb0 and main_p37xx_0141c.CAB files from the
Keithley Instruments website (www.keithley.com).
To perform the upgrade:
1. Place the nk_5001607.nb0 and main_p37xx_0141c.CAB files in the root directory of a
blank USB flash drive (make sure drive size is large enough for the size of the upgrade files).
2. Ensure that the Series 3700 mainframe power is turned off, and then connect the flash drive
to the Series 3700 and turn on power to initiate the upgrade process.
NOTE The upgrade process will take three to five minutes and the instrument will reboot
several times during the process. Do not disturb the instrument until the normal front
panel display has been present for at least 30 seconds.
4 3700S Release Notes V1.40 / May 2010
Series 3700 Firmware Release Notes Version 1.41 Release - Version 1.41 installation notes
3. On the front panel, press the MENU key, select LAN, select APPLY, and then press ENTER
to resume normal Ethernet connectivity following the upgrade.
4. Disconnect the USB flash drive from the Series 3700 mainframe.
NOTE Alternatively, you can have Keithley Instruments assist you with the upgrades by calling
your local Keithley support office.
Upgrading from firmware version 1.32a
Download the main_p37xx_0141c.CAB files from the Keithley Instruments website
(www.keithley.com).
NOTE The following steps force the instrument to upgrade its firmware twice. This is
necessary to ensure everything is upgraded properly. Follow the steps below carefully.
To perform the upgrade:
1. Copy the main_p37xx_0141c.CAB file to a blank USB flash drive (make sure drive size is
large enough for the size of the upgrade file).
NOTE Verify that the USB flash drive is blank.
2. Turn on the Series 3700 power.
3. Install the USB flash drive in the front panel connector.
4. On the front panel, press the MENU key.
NOTE If your model does not have a front panel, upgrade over the bus using the
upgrade.unit()command.
5. Turn the navigation wheel to scroll to UPGRADE, and then press the navigation wheel.
6. The question UPGRADE UNIT? displays. Select Yes, and then press the navigation wheel.
The Series 3700 upgrade status displays on the front panel, including the percentage
completed. When the file has been unpacked, the upgrade status is displayed as the upgrade
progresses (first cards installed in the slots are upgraded (including the DMM, if installed),
and then the Series 3700 mainframe).
NOTE For models without a front panel, the LAN status and clock status LEDs blink in unison
during the upgrade process.
7. Wait for the Series 3700 to reboot automatically. When the reboot is complete, press the
MENU key on the front panel.
NOTE If your model does not have a front panel, upgrade over the bus using the
upgrade.previous() command.
8. Turn the navigation wheel to scroll to UPGRADE and press the navigation wheel.
9. The question UPGRADE UNIT? is displayed. Select Previous, and then press the navigation
wheel (note that in this step you are selecting "Previous" instead of "Yes," as was done in
step 6). The Series 3700 upgrade status displays on the front panel, including the percentage
completed. When the file has been unpacked, the upgrade status is displayed as the upgrade
progresses (first cards installed in the slots are upgraded (including the DMM, if installed),
and then the Series 3700 mainframe).
The Series 3700 reboots automatically when the upgrade is complete.
3700S Release Notes V1.40 / May 2010 5
Version 1.41 Release - Critical fixes Series 3700 Firmware Release Notes
Critical fixes
PR42627 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
The instrument may generate a fatal error if another node on the TSP-Link network performs a
tsplink.reset() while the instrument is powering up.
Resolution:
This issue has been corrected.
PR42632 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
Selecting a script to load from a sub-directory on the thumb drive may cause the unit to lock up or
reset.
Resolution:
Scripts can now be loaded from any thumb drive directory level without issue.
PR41811 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
In version 1.40, single channel scans with high scan counts would sometimes yield an out of power
error.
Resolution:
This problem has been resolved.
PR41968 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
The node parameter being returned by errorqueue.next() is always nil.
Resolution:
The node parameter is correctly returned as described in the manual.
PR42189 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
Some thumb drives are not recognized quick enough to perform an OS upgrade.
6 3700S Release Notes V1.40 / May 2010
Series 3700 Firmware Release Notes Version 1.41 Release - Enhancements
Resolution:
If available, try another thumb drive.
PR42473 Models affected:
3706, 3706-NFP
Symptom:
External reference temperature may not function properly.
Resolution:
In 1.40, external temperature reference only worked on slot 1. Slot 2-6 are now available. Four wire
external temperature reference is now available on all slots.
PR42528 Models affected:
3706, 3706-NFP
Symptom:
Occasionally when using the tspnet.tsp.rbtablecopy() ICL, the error "2413, TSPnet invalid
reading buffer table" would be generated when asking for the some of the synchronous tables like
relativetimestamps but, not for readings.
Resolution:
The issue has been resolved.
PR42680 Models affected:
3706, 3706-NFP
Symptom:
The reading buffer channel names are not as expected according to the manual guidelines..
Resolution:
Channel patterns only use the first 7 characters in the channel names if the pattern name exceeds 7
characters. Also, patterns now have a + at the end of them to indicate multiple items closed.
PR42751 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
In previous versions, TSPnet would not connect to some telnet servers.
Resolution:
TSPnet now connects to all Telnet servers.
Enhancements
PR42773 Models affected:
3700S Release Notes V1.40 / May 2010 7
Version 1.41 Release - Noncritical fixes Series 3700 Firmware Release Notes
3706, 3706-S, 3706-NFP, 3706-SNFP
Error checking when using temperature with an external reference junction has been improved. This
improvement prevents the use of an external reference junction for channel one (which is the external
reference junction) and forces the user to measure the external reference junction before it using it for
another channel.
PR40792 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
A Save button has been added to the Web page Channel Pattern Dialog to better guide the user to
their desired operation.
PR41493 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
The tspnet.tsp.rbtablecopy() command will default and use the readings synchronous table to a
reading buffer if one isn't specified in the name parameter.
PR41938 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
The System Web page now allows the creation of a script representing the state of the unit (see
Create Config Script feature in the manual).
PR41976 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
A screen containing the status of memory usage has been added to the front panel display. It can be
accessed from the menu item MENU->SYSTEM-INFO->MEMORY-USAGE.
PR 39612 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
The front panel display now indicates when a scan is being run. The selected channel will be replaced
with the word SCAN for the duration of the scan. Any DMM attribute information will also be removed.
PR41936 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Scripts generated with the createscript command or front panel option under MAIN MENU -> SETUP -
> CREATE-SCRIPT no longer have a warning message to not modify the file since auto generated.
Noncritical fixes
PR41691 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
8 3700S Release Notes V1.40 / May 2010
Series 3700 Firmware Release Notes Version 1.41 Release - Noncritical fixes
In 1.40a labels were no longer allowed in channel lists when used to denote a range (for example,
START:END).
Resolution:
The feature has been restored.
PR41801 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
In some cases when DMM math was enabled, the front panel units continued to follow the selected
function.
Resolution:
The units now follow the math option.
PR41947 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
The eventlog.overwritemethod attribute is not stored when using the save setup feature or
when generating a script by createscript.
Resolution:
The attribute is properly stored.
PR42129 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
Connecting to the web page of an instrument with a running scan will cause the scan to stop.
Resolution:
Connecting and disconnecting from the web page does not impact the state of a scan.
PR42302 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
After running a script generated by createscript, a scan list may be incorrect. Scan steps that were
added to a scan with the command scan.addimagestep() are not being recreated correctly with
createconfigscript()
Resolution:
A scan is accurately recreated.
PR42303 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
3700S Release Notes V1.40 / May 2010 9
Version 1.41 Release - Noncritical fixes Series 3700 Firmware Release Notes
Symptom:
Some commands are not included in a script generated by command createscript.
Resolution:
The following commands are now included: lan.trigger[N].ipaddress,
trigger.timer[N].delaylist, tsplink.writeprotect,
tsplink.trigger[1].pulsewidth, tspnet.tsp.abortonconnect, tspnet.timeout,
scan.bypass, scan.mode.
PR42309 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
The script created from createscript doesn't have commands for row and column label settings.
Resolution:
Issue has been resolved.
PR42364 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
The Scan Start Event and Scan Complete event may be out of order when the scan count is greater
than one.
Resolution:
When a scan has greater than one scan count, the Scan Start Event and Scan Complete Event on a
scan pass greater than one are now in the correct order.
PR42548 Models affected:
3706, 3706-NFP
Symptom:
DMM Auto Delay set to Once does not give expected performance.
Resolution:
DMM Auto Delay set to Once, for readings greater than 1, gives performance equal to DMM Auto
Delay Off.
PR42735 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
An aperture setting is not saved with "create config script" for period and frequency. Recalling a setup
or executing a script from "create config script" generates a data type error message (-104).
Resolution:
10 3700S Release Notes V1.40 / May 2010
Series 3700 Firmware Release Notes Version 1.41 Release - Noncritical fixes
Issue has been resolved. In addition, the following settings are not part of a setup or create config
script:
schedule.alarm[N].enable
schedule.alarm[N].seconds
schedule.alarm[N].fractionalseconds
schedule.alarm[N].ptpseconds
PR41753 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
The beeper.enable setting is not affected by a system reset, saved in a setup, or saved in a script
generated by createconfigscript().
Resolution:
A reset() command will set the beeper.enable attribute back to 1. The setting will be maintained by
a setup file or script generated by createconfigscript().
PR42033 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
Setting the period, repetition, seconds, fractionalseconds or ptpseconds of a schedule alarm with a
negative value doesn't generate an error. Afterwards, the setting has an incorrect value when queried.
Resolution:
An out of range argument generates an error. The value for fractionalseconds neeeds to be less than
1 and greater than or equal to 0 to not generate an error message.
PR42058 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
None
Resolution:
The undocumented createscript() ICL command has been changed to createconfigscript(). Calling the
orginal function will result in an error.
The location of the feature on front panel has changed from the CREATE-SCRIPT option of SETUP
submenu under MAIN menu, to CREATE-CONFIG option of SCRIPT submenu under MAIN menu.
On the System Web page, a Create Config Script button has been added.
PR42613 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
3700S Release Notes V1.40 / May 2010 11
Version 1.41 Release - Noncritical fixes Series 3700 Firmware Release Notes
Some users may experience inappropriately degraded performance when using the Ethernet raw
socket and telnet sockets. The degradation may occur when a number of small packets are
exchanged across the socket. This is caused by the Nagle algorithm which delays Ethernet packets
for up to 200 mS waiting to combine small packets for network efficiency.
Resolution:
In most cases packet immediacy is more desirable than network efficiency. The Nagle algorithm is
now disabled by default to eliminate this delay. If necessary for Ethernet efficiency, use the lan.nagle
ICL to enable the algorithm.
PR41324 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
An error is not logged when an empty parameter string is passed to dmm.configure.delete(),
dmm.configure.query(), or dmm.configure.recall().
Resolution:
Issue has been resolved.
PR42057 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
In 1.40 the front panel calibration screen did not display the calibration information.
Resolution:
The information is now properly displayed. At no time was the calibration information lost.
PR42310 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
The user screen is blank at power up and after a reset.
Resolution:
At power up, the user screen now shows USER SCREEN and is not cleared with a reset operation.
PR42519 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
The password mode ICL is not be utilized by the web pages.
Resolution:
The applet will read the password mode at logout time and at powerup/initialization only. If the user
changes the password mode via non-web interface while the applet is running, the applet will not be
notified of this change until a reload or logout event.
12 3700S Release Notes V1.40 / May 2010
Series 3700 Firmware Release Notes Version 1.41 Release - Known issues
PR41691 Models affected:
3706, 3706-NFP
Symptom:
The command dmm.calibration.unlock() generates a -151, Invalid string data error message.
Resolution:
Now, the command generates a -150, String data error message.
Known issues
PR41421 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
The maximum number of characters that can be sent to the instrument without a newline character
depends on which remote interface is being used. Limiting line length to less than 950 characters
without a newline character will ensure interface independence.
PR41556 Models affected:
3706, 3706-NFP, 3706-S, 3706-SNFP
Symptom:
Creating a reading buffer with the same name as a script already in the system will prevent normal
access to the reading buffer. Choose unique names for reading buffers.
3700S Release Notes V1.40 / May 2010 13
Series 3700 Firmware Release Notes Version 1.40 Release - Overview
Version 1.40 Release
Overview
The Series 3700 version 1.40 firmware is an enhancement release including control and operation of the Model
3732 Quad 4 x 28 Ultra-High Density Reed Relay Matrix Card, as well as some problem fixes. Some problem
corrections may impact compatibility, please review the corrections prior to installation.
NOTE Upgrading to firmware version 1.40 requires special installation steps that are not required for other
firmware upgrades. Carefully read the Version 1.40 installation notes below before upgrading your
Series 3700.
The following table lists the exact version numbers of the available Series 3700 components when the firmware
upgrade is complete.
Model Version
Series 3700 Mainframe 1.40k
Series 3700 High Performance DMM 1.40k
3720 Dual 1x30 Multiplexer 1.40h
3721 Dual 1x20 Multiplexer 1.40h
3722 Dual 1x48 High Density Multiplexer 1.40h
3723 Dual 1x30 High Speed Reed Relay Multiplexer 1.40j
3724 Dual 1x30 FET Multiplexer 1.40j
3730 Dual 6x16 High Density Matrix 1.40h
3731 Dual 6x16 High Speed Reed Matrix 1.40j
3732 Quad 4x28 High Speed Reed Matrix 1.40m
3740 32 Channel Isolated Switch 1.40h
3750 Multifunction I/O Card 1.40j
Version 1.40 installation notes
Upgrading to firmware version 1.40 requires special installation steps that are not required for other firmware
upgrades. Carefully perform the following procedures to successfully upgrade to version 1.40.
First, determine your instrument's current firmware revision. With the instrument powered on, press the SLOT
key. The instrument's current firmware version is displayed. Based on the current firmware revision, follow the
instructions in the appropriate section below.
Upgrading from firmware version 1.31a or any earlier version
Download the nk_5001607.nb0 and main_p37xx_0140k.CAB files from the
Keithley Instruments website (www.keithley.com).
To perform the upgrade:
10. Place the nk_5001607.nb0 and main_p37xx_0140k.CAB files in the root directory of a
blank USB flash drive (make sure drive size is large enough for the size of the upgrade files).
11. Ensure that the Series 3700 mainframe power is turned off, and then connect the flash drive
to the Series 3700 and turn on power to initiate the upgrade process.
NOTE The upgrade process will take three to five minutes and the instrument will reboot
several times during the process. Do not disturb the instrument until the normal front
panel display has been present for at least 30 seconds.
3700S Release Notes V1.40 / May 2010 14
Series 3700 Firmware Release Notes Version 1.40 Release - Version 1.40 installation notes
12. On the front panel, press the MENU key, select LAN, select APPLY, and then press ENTER
to resume normal Ethernet connectivity following the upgrade.
13. Disconnect the USB flash drive from the Series 3700 mainframe.
NOTE Alternatively, you can have Keithley Instruments assist you with the upgrades by calling
your local Keithley support office.
Upgrading from firmware version 1.32a
Download the main_p37xx_0140k.CAB files from the Keithley Instruments website
(www.keithley.com).
NOTE The following steps force the instrument to upgrade its firmware twice. This is
necessary to ensure everything is upgraded properly. Follow the steps below carefully.
To perform the upgrade:
14. Copy the main_p37xx_0140k.CAB file to a blank USB flash drive (make sure drive size is
large enough for the size of the upgrade file).
NOTE Verify that the USB flash drive is blank.
15. Turn on the Series 3700 power.
16. Install the USB flash drive in the front panel connector.
17. On the front panel, press the MENU key.
NOTE If your model does not have a front panel, upgrade over the bus using the
upgrade.unit()command.
18. Turn the navigation wheel to scroll to UPGRADE, and then press the navigation wheel.
19. The question UPGRADE UNIT? displays. Select Yes, and then press the navigation wheel.
The Series 3700 upgrade status displays on the front panel, including the percentage
completed. When the file has been unpacked, the upgrade status is displayed as the upgrade
progresses (first cards installed in the slots are upgraded (including the DMM, if installed),
and then the Series 3700 mainframe).
NOTE For models without a front panel, the LAN status and clock status LEDs blink in unison
during the upgrade process.
20. Wait for the Series 3700 to reboot automatically. When the reboot is complete, press the
MENU key on the front panel.
NOTE If your model does not have a front panel, upgrade over the bus using the
upgrade.previous() command.
21. Turn the navigation wheel to scroll to UPGRADE and press the navigation wheel.
22. The question UPGRADE UNIT? is displayed. Select Previous, and then press the navigation
wheel (note that in this step you are selecting "Previous" instead of "Yes," as was done in
step 6). The Series 3700 upgrade status displays on the front panel, including the percentage
completed. When the file has been unpacked, the upgrade status is displayed as the upgrade
progresses (first cards installed in the slots are upgraded (including the DMM, if installed),
and then the Series 3700 mainframe).
The Series 3700 reboots automatically when the upgrade is complete.
3700S Release Notes V1.40 / May 2010 15
Version 1.40 Release - Critical fixes Series 3700 Firmware Release Notes
Critical fixes
PR38770 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
Functions on the advanced trigger web page do not operate correctly.
Resolution:
The advanced trigger web page now operates correctly.
PR39078 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
Recalling a saved setup takes too long to complete.
Resolution:
This issue is resolved.
PR39569 Models affected:
3706, 3706-NFP
Symptom:
Measurement timestamps show excessive jitter.
Resolution:
Measurement timestamp jitter has been significantly reduced.
PR39802 Models affected:
3706, 3706-NFP
Symptom:
When measuring temperature, the internal measured reference junction value is not used when using
the dmm.close() command for a configuration that includes an internal reference junction or when
changing the DMM transducer type with a channel closed on the temperature function.
Resolution:
This issue has been corrected.
PR39903 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
Having a reset command in the autoexec script causes the instrument to generate a -222,
parameter data out of range error message, and the reset command is not executed.
16 3700S Release Notes V1.40 / May 2010
Series 3700 Firmware Release Notes Version 1.40 Release - Critical fixes
Resolution:
The issue has been corrected.
PR39944 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
The lan config DNS verify setting and the lan config DNS dynamic setting operate incorrectly when
accessed from the instrument's front panel.
Resolution:
This issue has been corrected.
PR40259 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
An instrument downgraded below version 1.30b may no longer be capable of upgrading back to a
higher revision. The upgrade process now warns of this possibility. Instruments without front panels
will no longer downgrade past 1.30b.
Resolution:
Do not downgrade an instrument's firmware to 1.30b or earlier unless you are certain you will not want
to upgrade to a newer firmware version.
PR40353 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
Using os.date with invalid format specifiers may cause the instrument to stop responding.
Resolution:
Invalid format specifiers now return an Invalid Format message.
PR40953 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
Changing the TSP-N termination in the middle of a connection to a TSP instrument will confuse the
processing of the connection.
Resolution:
TSP-Net termination will generate an error if modified during a connection to a TSP instrument. The
termination is always set to linefeed.
PR41359 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
3700S Release Notes V1.40 / May 2010 17
Version 1.40 Release - Enhancements Series 3700 Firmware Release Notes
Symptom:
For the Models 3723, 3724, and 3731 cards, the user settle delay (channel.setdelay() command)
is incorrectly applied to open actions, rather than close actions only.
Resolution:
This issue has been corrected.
PR 41891 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Symptom:
Disabling the Ethernet Ping protocol also disables most other Ethernet functionality
Resolution:
The ability to disable Ethernet Ping protocol has been removed. Ping is now always enabled.
Enhancements
PR33446, Models affected:
PR39259
3706, 3706-S, 3706-NFP, 3706-SNFP
Firmware updates can now be initiated from the web interface by pressing the Upgrade Firmware
button on the system web page. Download the firmware image file from www.keithley.com before
initiating the update from the instrument's web interface. Follow the dialog box prompts after selecting
this button. During the upgrade, the instrument will disconnect from the web interface. After the
upgrade finishes and the instrument reboots, close all browser windows to clear any cached
information, and then open a new browser window to reconnect to the web interface.
PR 36048 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Scripts that utilize the channel.*() ICL commands may exhibit performance improvements. This
improvement may be most noticeable when the channel list contains a high number of channels.
PR37683 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
The instrument will no longer support specifying a pseudocard using a constant, for example,
slot[2].pseudocard = slot.PSEUDO_3722. Pseudocards will now be specified by using the
model number only, for example, slot[2].pseudocard = 3722. For consistency, Keithley
recommends using this new convention for all cards. However, to ensure backward compatibility,
constants for existing cards will continue to be available, but constants will not be added for future
cards.
PR 38853 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
The Log menu item on the instrument's main web page has been moved to the main LXI web page.
PR 39230 Models affected:
18 3700S Release Notes V1.40 / May 2010
Series 3700 Firmware Release Notes Version 1.40 Release - Enhancements
3706, 3706-S, 3706-NFP, 3706-SNFP
The system web interface now contains the card serial numbers in the report list.
PR 39612 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
Front panel and web interface enhancements have been made to support the large number of
channels available on the Model 3732 card. For details about these enhancements, refer to PA-1021,
Model 3732 Reed Relay Matrix Card Connection Information, which is supplied with the Model 3732.
PR39911 Models affected:
PR39915
3706, 3706-S, 3706-NFP, 3706-SNFP
The following ICL commands have been added:
trigger.blender[N].reset()
trigger.timer[N].reset()
digio.trigger[N].reset()
tsplink.trigger[N].reset()
These commands reset the associated N blender, timer, or trigger attributes back to the factory default
settings, as indicated below.
NOTE For details, including default settings for each command, refer to the Series 3700
Reference Manual (document number 3700S-901-01).
The trigger.blender[N].reset() command resets the following back to factory defaults:
trigger.blender[N].orenable
trigger.blender[N].stimulus[M]
It also clears the overrun:
trigger.blender[N].overrun
The digio.trigger[N].reset() command resets the following back to factory defaults:
trigger.timer[N].count
trigger.timer[N].delay
trigger.timer[N].delaylist
trigger.timer[N].passthrough
trigger.timer[N].stimulus
It also clears the overrun:
trigger.timer[N].overrun
The digio.trigger[N].reset() command resets the following back to factory defaults:
digio.trigger[N].mode
digio.trigger[N].pulsewidth
digio.trigger[N].stimulus
It also clears the overrun:
3700S Release Notes V1.40 / May 2010 19
Version 1.40 Release - Enhancements Series 3700 Firmware Release Notes
digio.trigger[N].overrun
The tsplink.trigger[N].reset() command resets the following back to factory defaults:
tsplink.trigger[N].mode
tsplink.trigger[N].stimulus
It also clears the overrun:
tsplink.trigger[N].overrun
PR 40328 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
The eventlog.next() command takes an optional integer parameter ranging from 1 to 50,
indicating the number of events desired in the response. If the parameter is not specified, then it
defaults to 1 to mimic the behavior of the command before the enhancement.
PR 40661 Models affected:
3706, 3706-S, 3706-NFP, 3706-SNFP
A new ICL function that creates a string channel descriptor from a series of card-dependent integer
arguments has been added:
channel.createspecifier()
Usage:
There are five variants of this function that can be used, depending on the type of card in the specified
slot:
= channel.createspecifier(, , , )
= channel.createspecifier(, , )
= channel.createspecifier(, , )
= channel.createspecifier(, )
= channel.createspecifier(, )
Where:
slot Specifies the slot number to use
bank Specifies the bank number to use (if applicable)
row Specifies the row number to use
column Specifies the column number to use
index Specifies the index to use
backplane Specifies the backplane to use
This function creates a string channel descriptor from a series of card-dependent integer arguments.
20 3700S Release Notes V1.40 / May 2010
Series 3700 Firmware Release Notes Version 1.40 Release - Enhancements
The arguments are dependent on the card type in the specified slot. The channel.createspecifier
command can only create valid channel descriptors; if an illegal argument is sent for the type of card in
the specified slot, an error is generated.
Variants of this function can be used, depending on the type of card in the specified slot:
Type of card in slot Function variants to use
Matrix card containing banks Variant 1 or 5
Matrix card without banks Variant 2 or 5
Multiplexer cards Variant 3, 4, or 5
Example 1:
To create a channel descriptor on the Model 3732 card configured as a single 4x112 matrix in Slot 3,
Bank 1, Row 2, Column 101:
cd = channel.createspecifier(3, 1, 2, 101)
print(cd)
312A1
Example 2:
To set the pole setting to 2 for all channels in Bank 1 on a Model 3732 card configured as a dual 8x28
matrix in Slot 1:
for row = 1,8 do
for col = 1,28 do
ch = channel.createspecifier(1,1,row,col)
channel.setpole(ch, 2)
end
end
Example 3:
To create a channel descriptor on a Model 3724 multiplexer card in Slot 2, Bank 2, Index 1:
cd = channel.createspecifier(2, 2, 1)
print(cd)
2031
Example 4:
To create a channel descriptor on a Model 3724 multiplexer card in Slot 1, Backplane 911:
cd = channel.createspecifier(1, 911)
print(cd)
1911
PR40699 Models affected:
3706, 3706-S
The front-panel display functionality has been improved to increase usability. The plus (+) sign
indicator has moved to the second line of the display and is no longer after the selected channel
description. Now, the plus (+) sign denotes that a channel other than the selected channel is closed.
To see which channels are closed, use the DISPLAY button to cycle to a new front-panel screen that
3700S Release Notes V1.40 / May 2010 21
Version 1.40 Release - Enhancements Series 3700 Firmware Release Notes
lists the closed channels. If the closed channel list exceeds the screen size, use the navigation wheel
to scroll through the list.
PR 40707 Models affected:
3706, 3706-S
A new ICL function that allows inclusion of multiple channels in a single scan step has been added:
scan.addimagestep()
Usage:
scan.addimagestep(, [])
Where:
String specifying a list of channels
Optional string specifying a DMM configuration
This function adds a list of channels to be closed simultaneously in a single step of a scan. An optional
DMM configuration can be added to force the scan to take a measurement during the same step.
The scan.addimagestep function is an advanced command; the channel list parameter must
specify appropriate relays to support the requested DMM configuration, or an invalid measurement will
result.
Unlike the scan.add() function, paired channels and backplanes necessary for measurement are
not automatically added to the step. Use the channel.setpole() command to indicate if the paired
channel should be added or not. Backplanes assigned to channels by the
channel.setbackplane() command will not be added to the image step automatically. For
example, if a measurement is taken on a 4-wire ohms configuration without designating 4-pole with the
channel.setpole() command, the corresponding paired channel will not be added, and the
specified "dmm config" will not cause additional relay closures as it normally would. Backplane
channels that are needed for the desired measurement must be specified in the channel list
parameter.
If you have changed the pole setting on any of the channels in the list (using channel.setpole()),
an additional paired channel will be added or removed appropriately. For example, to ensure that the
proper channels close to enable a 4-wire measurement, set the pole setting in addition to using the
4-wire ohms DMM configuration.
When a DMM configuration (other than "nofunction") is specified, the instrument will take the
appropriate measurement based on the function set in the configuration; if no DMM configuration is
specified with the command, no measurement will be taken.
Example 1:
This example adds a single step that closes Channel 1001 and takes a DC voltage measurement.
Note that the voltage measurement will be inaccurate if this is the only step in the scan (because the
backplane channels are not closed).
scan.addimagestep("1001", "dcvolts")
22 3700S Release Notes V1.40 / May 2010
Series 3700 Firmware Release Notes Version 1.40 Release - Enhancements
Example 2:
To add a single step that closes Channels 1001 and 1911, and then takes a DC voltage
measurement:
scan.addimagestep("1001, 1911", "dcvolts")
Example 3:
This example first sets Channel 1001 to 4-pole, then adds a single step that closes Channels 1001,
1031, and 1911, and then takes a DC voltage measurement.
channel.setpole("1001", 4)
scan.addimagestep("1001, 1911", "dcvolts")
Example 4:
This example adds three steps with the following actions: