CloudTesting™ Lab 2.46.00

1. Summary of revision

Revision number	Reason for revision
2.46.00	Addition of function, Functional improvements, Fixing issue

2. Addition of functions

2.1 Manual

(1) Added buttons to the following GUIs to open the manual related to the features of each GUI.

• Startup Window
• Main Window
  • Toolbar
  • Each Screen of the [Work Navigator] in the Standard Mode
  • Control Panel in the Expert Mode
  • Flow Item Area in the Expert Mode
• [Define Variables] Dialog Box
• [Message Area Settings] Dialog Box
• [Optimize Variable Evaluation at Interpose Execution] Dialog Box (Newly added, Expert Mode)

2.2 CT Command Client

(1) Feature to control CloudTesting(TM) Lab from the Java language

The feature to control CloudTesting(TM) Lab from the Java language is supported.
This Java language program is called the CT command client.
The CT command client provides the same functionality as the CT command.

Target firmware
CX1000_MCU, CX1000_MEMORY_TYPE_F

For details, refer to the “CT Command Client (Java version)”.
This manual can be found by selecting
[CloudTesting] > [CT Command Client (Java) Manual] from the Windows Start menu.

2.3 Expert Mode

(1) Interpose algorithm to display variable values

Added interpose algorithm to display variable values before or after the flow item execution.

For details, refer to the following section in the “CX1000 User’s Manual”. - “8.5 Flow Item Area” - “8.5.2 [Pre Interpose], [Post Interpose] tabs” - “Show Variable Values Algorithm”

3. Functional improvements

3.1 CT Command

(1) Improved that the CloudTesting(TM) Lab does not stop with IP update notifications when started with CT_Start.bat

Changed specifications so that the CloudTesting(TM) Lab does not stop with IP update notifications at starting with CT_Start.bat.

Target firmware
CX1000_MCU, CX1000_MEMORY_TYPE_F

3.2 Expert Mode

(1) Added an option to optimize variable evaluation at execution of interpose processing

An option is added to optimize variable evaluation at execution of interpose processing so that execution time is reduced.

Target firmware
CX1000_MCU, CX1000_MEMORY_TYPE_F

For details, refer to the following section in the “CX1000 User’s Manual”.

• “8.6 Menu Bar”
  • “Option”
    • “Optimize Variable Evaluation at Interpose Execution] dialog box”

4. Fixed issues

4.1 Expert Mode

(1) Measurement time slowed down when the measurement item numbers (Item ID) for the target of data log output were set.

Measurement time significantly slowed down when the measurement item numbers for the target of data log output were set to the [Item ID] of [Target] in the [Data Log Settings] dialog box.

• Behavior after improvement
  Significant delay in measurement time has been improved.

Revisions in which this phenomenon occurs	Target firmware
Rev 2.20.00 to 2.45.01	CX1000_MCU, CX1000_MEMORY_TYPE_F

4.2 Analysis Tools

(1) In the Shmoo Plot Tool, the tracking settings were disabled when loading the Shmoo conditions.

In the Shmoo Plot Tool, the tracking settings were disabled when loading the Shmoo conditions that had a resource specified for the axis with the same name as a variable.

• Behavior after improvement
  The tracking settings are enabled for the above conditions.
  Note that updating to this revision also requires updating to the following revision of the Shmoo Plot Tool. - Shmoo Plot Tool Rev 2.46.00 (PCXT01-M6001) - Shmoo Plot Tool for Memory Rev 2.46.00 (PCXT01-M8001)

Revisions in which this phenomenon occurs	Target firmware
Rev 2.24.00 to 2.45.01	CX1000_MCU, CX1000_MEMORY_TYPE_F

4.3 Setup and Execution

4.3.1 Pattern Conditions

4.3.1.1 CX1000_MCU

(1) Array variables of type String could not be used.

• Array variables of type String could not be used for the following settings.
  • [Start] and [Stop] of [Execution Section], [Compare Section], and [Loop Section]
  • [Mask Pins]
• Behavior after improvement
  Array variables of type String can be used for the above settings.

Revisions in which this phenomenon occurs
Rev 2.20.00 to 2.45.01

(2) If an incorrect value was set to the IDX when overwriting the IDX registers, an error occurred when executing the measurement even if it was not selected as the overwrite target.

• If an incorrect value was set to the IDX when overwriting the IDX registers, an error occurred when executing the measurement even if it was not selected as the overwrite target.
• Behavior after improvement
  The error does not occur for the IDX that is not selected as the overwrite target.

Revisions in which this phenomenon occurs
Rev 2.44.00 to 2.45.01

(3) After the measurement, only the first pin name appeared in the tool tip for [Mask Pins].

• After the measurement, only the first pin name appeared in the tool tip for [Mask Pins].
• Behavior after improvement
  The correct pin names appear in the tool tip.

Revisions in which this phenomenon occurs
Rev 2.20.00 to 2.45.01

4.3.1.2 CX1000_MEMORY_TYPE_F

(1) Array variables of type String could not be used.

• Array variables of type String could not be used for the following settings.
  • [Pattern]
  • [Mask Pins]
  • [CPE1] to [CPE4] and [DRE1] to [DRE2] in [Register Condition]
  • [File Name] in [Set Data Buffer Memory(DBM)]
• Behavior after improvement
  Array variables of type String can be used for the above settings.

Revisions in which this phenomenon occurs
Rev 2.20.00 to 2.45.01

(2) After the measurement, no pins appeared in the tool tip for [Mask Pins].

• After the measurement, no pins appeared in the tool tip for [Mask Pins].
• Behavior after improvement
  The correct pin names appear in the tool tip.

Revisions in which this phenomenon occurs
Rev 2.20.00 to 2.45.01

(3) When setting a variable to [Mask Pins], multiple pins separated by commas could not be specified.

• When setting a variable to [Mask Pins], multiple pins separated by commas could not be specified.
• Behavior after improvement
  When setting a variable to [Mask Pins], multiple pins separated by commas can be specified.

Revisions in which this phenomenon occurs
Rev 2.20.00 to 2.45.01