User Manual Phase Tools Release 9.1 Doc. 48000000002 - ENG
User Manual Phase Tools Release 9.1 Doc. 48000000002 - ENG
SUMMARY
1. Introduction .............................................................................................................................. 5
1.1 Installation requirements .........................................................................................5
1.2 Installation steps .....................................................................................................5
2. Cockpit main view.................................................................................................................... 5
2.1 Main screen view.....................................................................................................5
2.2 User interface window .............................................................................................6
2.3 Catalog window .......................................................................................................6
2.4 Connection status window ........................................................................................7
2.5 Output window ........................................................................................................7
2.6 Monitor window .......................................................................................................7
2.7 Status bar ...............................................................................................................8
3. Managing projects ................................................................................................................... 8
3.1 Create a new project ................................................................................................8
3.2 Add a device to the project ......................................................................................9
3.2.1 Add a device from catalog ....................................................................................9
3.2.2 Add a device from automatic scanning ................................................................11
3.3 Delete a device from the project .............................................................................17
3.4 Open an existing project ........................................................................................17
3.5 Save the project ....................................................................................................17
3.5.1 Saving changes to the project.............................................................................17
3.5.2 Saving to an alternative location .........................................................................18
3.6 Close the project ...................................................................................................18
4. Managing AxX devices family ............................................................................................... 18
4.1 Device information ................................................................................................19
4.2 Full configuration download ...................................................................................19
4.3 Application selection .............................................................................................20
4.4 Device configuration ..............................................................................................20
4.5 Target information .................................................................................................21
4.6 Monitor page.........................................................................................................22
4.7 Alarm information .................................................................................................24
4.7.1 Alarm history information ...................................................................................24
4.8 Back to the project ................................................................................................25
5. Managing TW devices family ................................................................................................ 25
5.1 Device information ................................................................................................26
5.2 Full configuration download ...................................................................................26
5.3 Device configuration ..............................................................................................27
5.4 CANOpen configuration .........................................................................................28
5.5 Target information .................................................................................................28
5.6 Monitor page.........................................................................................................29
5.7 Alarm information .................................................................................................30
5.7.1 Alarm history information ...................................................................................31
5.8 Back to the project ................................................................................................32
6. Parameters management ...................................................................................................... 32
6.1 Node tree .............................................................................................................32
6.2 Parameters table ...................................................................................................33
6.3 Read/Write one parameter ......................................................................................34
6.4 Read/Write parameters ..........................................................................................35
FIGURES.
1. INTRODUCTION
Phase tools is the setup and management tool for Phase Motion Control servo drives (including the Ax Drives
Series and TW integrated motors). Cockpit
For further details on servo drives features and capabilities, please refer to the corresponding reference
manuals.
Cockpit
Double click the shortcut icon , Cockpit main screen is illustrated as Figure 1 . It consists of those
main panels: user interface window, catalog window, connection status window, output window, monitor
window and status bar.
Other View
The monitor window is activated with Monitor View and also activated with the
3. MANAGING PROJECTS
Cockpit is managed as projects, one project consists of one or more devices, which are including AxN, AxM-II
family and TW integrated motors.
To start a new project, double click the shortcut of Cockpit icon where you install the Phase Tools.
T New File menu of Cockpit main window and it is
also activated with the corresponding button on the toolbar of an already opened project. The startup
Cockpit window is shown in Figure 8.
Cockpit supports two kinds of products series, which are Ax drives series and TW series as you can see from
the main page. First of all you have to select the target product series.
If your target is Ax drives series, click the Ax Drives Series(AxM-II,AxP,AxW) bar on the main page; If your
target is TW series, click the TW Drives Series(TW3,TW5,TW7) bar on the main page.
A project at least contains one device. Next section explains how to add a device to the project.
Click the Ax Drives Version 1.9 bar on Ax catalog to add a new device, the main page of the new device will
be shown. You can also click the icon to add a new device. The added device will be shown directly in
the device list.
be shown. You can also click the icon to add a new device. The added device will be shown directly in
the device list.
When the current project is already existing one or more device shown in Figure 11, you can also add a device
from catalog by clicking the corresponding bar or the icon of the target device you want to add. It is the
same way as above. The only difference is that, a message will pop up to require you confirming the operation.
Confirm
The following procedure shows you how to make automatic scanning for Ax drives:
Click the Automatic Scan for AxX bar on the main page. Before starting scan, press the Advanced
bar to check the communication parameters in Figure 12. Modbus is the default protocol for Ax
drives; setup the correct COM port by which PC connects with the device; select the baud rate range
from a starting point to an ending; enter the addres Advanced
again, the window retracts back and the settings are persisted. Refer to Chapter 7 for more details
on communication parameters settings.
Usually when there is only one device of TW series on the network, Single node scan is preferred to be used.
Once it is found out one device, the single node scan procedure stops immediately. Network scan has to be
used when there are more than one device on the network.
The following procedure shows you how to make automatic single node scanning for TW series:
Click the Automatic Scan for TW bar on the main window. Before starting scan, press the
Advanced in Figure 15. CanOverIp is the default
protocol for TW series. Refer to Chapter 7 for more details on communication parameters settings.
The following procedure shows you how to make automatic network scanning for TW series:
Make sure the cables physical connections are ready. Then press the Network Scan Start bar, the
automatic scan is running with the selected baud rate and the node id range from 1 to 127 in Figure
19.
Note that such functions are useful when there is only one kind of products series. For example, only existing
Ax drives or only TW series on the same fieldbus. If there are both Ax drives and TW series on the same
fieldbus, such functions may not support.
The found devices are listed in the main window. You can press either the corresponding bar or the icon
to add the target device into the current project. The difference is that, if you press the corresponding bar to
add the device, a message will appear to inform that you can connect to the drive and update all parameters;
if you press the icon, the target device will be added and shown directly under the device list.
Note that if the target device is already added on the project, you cannot add it to the same project anymore.
When you try to do such operation, a warning message will be appeared.
To delete one device, click the corresponding icon on the selected device, a message is appeared to ask
if you are sure to delete the selected device or not Confirm
the project.
You can also open an existing project from the item Most Recent Projects on the main window.
Note that Most Recent Projects only contains the projects files that is used recently. And if the
directory of the project file is moved to another path, the project cannot be opened correctly.
Cockpit is the dedicated software environment that is parameterizing and monitoring the AxX family operating
conditions with a serial interface RS232. Moreover, the graphic interface makes it easy and versatile the drive
configuration.
This chapter is to focus on how to manage devices of AxX family. When entering an AxX device, the main page
is shown in Figure 21. It is the startup entrance of an AxX device, on which there are all the components of
device configurations.
Name is
If there are more than one device of AxX family in one project, the number will increase by one. It is also
possible to modify the device name as you prefer. Insert a new name on the textbox Enter it
will be updated immediately.
Disable Communication option is not selected by default. If selected, the communication for the device is not
able to connect.
Address is the address value of communication. Refer to Chapter 7 for more details.
Port is the COM port setting of communication. Refer to Chapter 7 for more details.
Note that it is the only function that can write correctly all the configuration parameters into the drive.
Click the Full Configuration Download bar on the main page, a message is appeared to inform you
that such procedure will overwrite any user application and parameters already in the drive with data
in the actual parameters table.
Confirm . It is necessary to connect the target device before making such
operation. Refer to Chapter 7 on how to communicate with one device.
If the drive is not connected yet, a message for online mode is required. Press Confirm
procedure will try to connect the device automatically. After connection is ok, the full configuration
download starts to process with a processing bar.
In the end, the procedure executes successfully Full configuration download terminated
message.
Note that, if any failure happens during the procedure, please back to the first step and start again.
If one application already exists in the device, after clicking the selected application bar, a message is
appeared to warn you that actual application and related parameters will be deleted. Confirm , the
selected application will be added into device but the actual application and relative parameters will be
deleted.
Back to the main page by clicking the icon on the left top of Cockpit window.
On the configuration window clicking the bar of the selected item, you can enter into parameters
configuration in details. Please refer to AxX software manual for system parameters explanations in details in
order to configure appropriate values.
On each parameters configuration page, you can back to the configuration window by clicking the Done bar
Back to the main page by clicking the icon on the left top of Cockpit window.
System ID contains the device type, serial number and production date.
System firmware contains the firmware type and firmware version number.
User Application contains the PLC application name and version number.
Controlboard ID contains hardware controlboard type and version number.
Powerboard ID contains hardware power stage type and version number.
FPGA ID contains hardware FPGA type and version number.
Drive time contains the drive power-on time.
Press refresh button on the left sidebar of the target info window, you can get the latest data from a
connected device.
Back to the main page by clicking the icon on the left top of Cockpit window.
main page. You can also activate it with the corresponding icon on the toolbar.
Monitor page provides you a friendly interface to verify the connections and settings between the motor and
the drive.
Please setup drive with on-line mode before making operations on monitor page. Refer to Chapter 7 for
communication settings. After the drive is connected, the monitor page refreshes every 400ms.
Power Stage
Current Loop value and the actual current when
drive is in operation mode.
Speed Loop tion, it shows the speed reference and the actual speed of the connected device.
Encoder section in Figure 27 is shown by default. You can get the encoder reading values: position turn
number and angle degree for both main encoder and auxiliary encoder.
Note that on this window auto refresh mode is enabled. In this ca Settings
written into the drive if you modify them.
Back to the main page by clicking the icon on the left top of Cockpit window.
To enter into alarm information window in Figure 30, you can click the Alarm button on the left sidebar of
the main page. You can also activate it with the corresponding icon on the toolbar. Moreover, the same
command is also available by double clicking the device column on the connection status window.
Back to the main page by clicking the icon on the left top of Cockpit window.
Here are the explanation for each column on the alarms history table.
You can save all the content on the alarm history window to a file with the extension name .csv / .txt
clicking the Save to CSV file Save to TXT file button on the left sidebar.
You can refresh the actual alarm history window by clicking the Refresh button on the left sidebar of alarm
history window.
Note that, it is necessary to connect the device before viewing the alarm history window. Please refer to
Chapter 7 for communication in details.
Back to the alarm window by clicking the Alarms button on the left sidebar of alarm history window.
Back to the main page by clicking the icon on the left top of Cockpit window.
When you enter into TW series from Cockpit startup window, two kinds of TW products are shown on the
device catalog window. They are:
TW0503 series
TW drives series
Please refer to TW manual for TW motors identification and selecting the correct device catalog when
connecting one TW motor. All TW motors can be programmed and monitored via Cockpit interface.
This chapter focuses on how to manage TW servomotors. When entering a TW device, take TW3 as example,
the main page is shown in Figure 32. It is the startup entrance of a TW device, on which there are all the
components of device configurations.
Disable Communication option is not selected by default. If selected, the communication for the device is not
able to connect.
Status the state of the NMT (Network Management) on the target device.
If the target device is connected, the state attribute is one of the values: STOPPED, PRE-OPERATIONAL,
OPERATINAL and INITIALIZING.
Note that, the setup of node id and baud rate is optional. If the configured parameters of node id and baud
rate are the same as the actual communication settings, the full configuration download will setup all the user
parameters excepting the node id and baud rate. If different, it will first setup the configured node id and
baud rate, and then download other user parameters, in this case one more message will be displayed that
informs you to connect only one TW motor on the network.
Full Configuration Download bar on the main page, a message is appeared to inform you
that such procedure will write any user parameters data in the actual parameters table.
Confirm
Press Confirm again, the procedure will try to connect the device automatically. If the node id or
baud rate is not matched, Retry on the popup window to enable the
automatic scanning.
After connection is ok, the full configuration download starts to process with the processing bar. In
the end, the procedure exe Full configuration download terminated
message.
Note that, when node id and baud rate are not the same as the values by which Cockpit is connecting to the
target, to avoid affecting the CAN network, it is also necessary to connect only one TW device per time during
making full configuration download.
Generally speaking, If there is an existing TW parameters file, you can connect to a TW motor without knowing
its node id and baud rate, and then parameterize all the user configurations by making full configuration
download. Note that, if any failure happens during the procedure, please back to the first step and start
again.
On each parameters configuration page, you can back to the configuration Done bar
Back to the main page by clicking the icon on the left top of Cockpit window.
After setting up the parameters for node id and baud rate, clicking Set NodeId/Baudrate n the
left sidebar of the CANOpen configuration window, the TW motor can be configured for a CANOpen network
without using any devices and the configuration can be stored on a non-volatile memory.
Note that, when configuring the node id and baud rate, there must be only one TW motor per time
communicating on the CANOpen network.
Node id and baud rate will be automatically setup by using full configuration download.
Back to the main page by clicking the icon on the left top of Cockpit window.
refresh on the left sidebar of the target info window, you can get the latest data from a
connected device.
Back to the main page by clicking the icon on the left top of Cockpit window.
main page. You can also activate it with the corresponding icon on the toolbar.
Back to the main page by clicking the icon on the left top of Cockpit window.
To enter into alarm information window in Figure 38 Alarm on the left sidebar of
the main page. You can also activate it with the corresponding icon on the toolbar. Moreover, the same
command is also available by double clicking the device column on the connection status window.
Back to the main page by clicking the icon on the left top of Cockpit window.
Here are the explanation for each column on the alarms history table.
You
Save to CSV file Save to TXT file button on the left sidebar.
Note that it is necessary to connect the device before viewing the alarm history window. Please refer to
Chapter 7 for communication in details.
Back to the main page by clicking the icon on the left top of Cockpit window.
6. PARAMETERS MANAGEMENT
All parameters sets for the system configuration and operation both on the AxX drive family and TW family are
resident in the memory. They are accessible from Cockpit configuration tool. The application parameters,
which are located at defined memory addresses in the dedicated application, can be also managed by Cockpit.
Generally, parameters sets organized in hierarchical menus can be subdivided into three classes. which you
can distinguish by colors on the parameter table.
PAR parameters identified with Black color are read/written from Cockpit configurator and could
be saved in the drive flash memory. In some cases Cockpit will inform some PAR system
paramerers need a system reset after modifications.
VAR parameters identified with Green color are read-only variables. They are used as diagnostic
parameters in order to allow monitoring the drive variables.
WKS parameters identified with Purple color are used to control drive behavior. They can be
read/written from Cockpit configurator but restored to zero after drive reset.
Usually parameters sets are aligned with logic blocks and some principal sections collect more commonly
used parameters. The default values set by the manufacturer are appropriately used in most cases. It could be
necessary to tune them for particular applications in order to optimize the drive performances. Note that the
user must be aware that the changes introduced assume a very deep knowledge of the drive firmware and
function control blocks implementation. Please refer to reference manuals for system parameters descriptions
in details.
This chapter focuses on how to manage (read/write) parameters with the device.
Generally the parameters are structured in hierarchic subgroups collecting all parameters related to the
different catalog devices. Take Motor parameters table for example, click the menu on the node
tree, it is shown as Figure 41.
For further information on all system parameters in details please refer to related reference manuals.
Note that in next sections the drive is reqired in connected mode, refer to Chapter 7 for drive connection.
Assumed that drive is in connected mode, after selecting one parameter from the parameter table or the page,
you have several ways to read and get the value stored in the drive:
Assumed that drive is in connected mode, after selecting one writable parameter from the parameter table or
the page, click the Value field and put the modified value on it, it will be visualized in red to indicate that it is
not written yet. Then you have several ways to write and send the value to the drive:
After Read/Write operation is done successfully, the parameter value is displayed in black.
Note that, on the parameters table, those above operations are also available when selecting more than one
parameter by CTRL. Especially, you can use those above operations to read/write all parameters on the
parameter grid select all Select all item Parameter menu, the
corresponding icon A
Note that, on the parameters grid, it is also possible to write the default values of the selected parameters on
the Write default values Parameters menu.
Assumed that drive is in connected mode, after parameters modifications are done, you have several ways to
write and send the values to the drive:
After Read/Write operation is done successfully, the parameter values are displayed in black.
To write all the visuable parameters, the following ways can be done:
Note that, such commands can not write all the device parameters. Full configuration downlaod is
suggestable to make all the parameters written into the device.
permanently. It is possible to lose the data at system drive reset. Flash saving is necessary to store the
parameters values permanently into the drive.
7. COMMUNICATION
Cockpit provides the communication interface to establish a connection with the target device in order to
monitor and debug the device. This chapter focuses on the communication operation required to connect to a
target device.
The protocol default settings are: Jbus, address 1 and timeout 1000. Note that the setting address number
must be identical to the address given to the drive.
Refer to AxX software manual for Modbus protocol and communication parameters specifications in details.
The communication settings by default are baudrate 125Kb, Interface i/f 0, Node Id 1, TCP timeout 3000 and
Rx timeout 400. It is necessary to choose and setup the baudrate and node id with appropriate values of the
target device.
Refer to TW software manual for CanOpen protocol and communication parameters specifications in details.
You can disable and re-enable the communication using the same command. When the connection is active,
Connected mode ponding icon appears as pressed.
Especially, when enabling the communication on one TW motor, if the node id or baud rate does not match
the actual communication settings, a message will pop up to inform you Retry
single node scan. In this case, Cockpit will automatically search the target node id and baud rate. Note that,
single TW motor connected per time on the network is required. During search, the procedure messages are
printed in the Output window. After the device is found, the target node id and baud rate are updated on the
configuration table of main page.
Configurator allows the user to specify for each device its own communication settings to let the configurator
communicate with each of the physical target devices of the project. It is possible to connect to physical
targets once configured communication settings for each device in the project.
When the connection is active, the configurator starts communicating with targets using specified
communication settings. Polling of a parameter is used to understand if the target is actually connected. If
any of the target devices cannot be reached, the connection still remains active and continues polling devices
but connection status indicated ERROR. When all the targets answers correctly to the polling requests
connection status indicates CONNECTED.
The state of communication is shown in the right border of the status bar. If you have not yet attempted to
connect to the target, the state of communication is set to .
When you try to connect to the target device, the state of communication becomes one of the following:
Saving the project file can obtain to save the communication settings in the meanwhile. Refer to Chapter 3.5
Save the project
You can also refer to hardware manual for hardware reset operation.
8. CONTROL PANEL
The integrated control panel, which is one of the useful functions that Cockpit embodies for AxX family, allows
It allows monitoring
and controlling the I/O interface of the device. When acting as a monitor, it is shown the actual status of the
physical I/O; when controlling is enabled, the physical I/O are virtually disconnected and not used, the control
panel will simulate the I/O interface to work with the drive.
This chapter focuses on the control panel operation to monitor and control the I/O interface of the device.
On AxX family the control panel consists of eight digital inputs, eight digital outputs, four analog inputs and
four analog outputs by software. Instead, there are only physically eight hardware digital inputs, four hardware
digital outputs, four hardware single ended analog inputs and two hardware differential analog outputs.
Digital I/O is represented by means of buttons and icons, analog I/O by means of sliders and progress bars
and the values are also available in the form of textboxes shown as Figure 45 and Figure 46.
Digital Inputs/Outputs
Analog Inputs/Outputs
After activating the control panel, there are two switchable panels:
Standard panel
Enhanced panel
9. FIRMWARE UPGRADING
Firmware upgrading is released embodied in the Phase Tools setup at regular period on the Phase Motion
Control web site, which could include new functions and generic enhancements. It could be done completely
via Cockpit, that applies extension tools for both AxX family and TW family to upgrade firmware
independently.
To open the firmware upgrading window, you have the following ways:
Note that the operation of firmware upgrading has to be performed by technical people trained in the Phase
Motion Control.
press the icon to enter into communication setting window, refer to Chapter 7 to connect the
device in details.
With Browse , select the target firmware file to be downloaded.
Firmware file info
Drive firmware info
Download
Synchro
synchronization executed operation
connected.
Note that, if any troubles occur during the firmware upgrading, it is necessary to start from the beginning the
load of the selective firmware file. If the download is successfully completed, the device will reset and send a
bootup message on the output window. In addition, you can reset the device manual Reset
button.
To import all settings of an old .par Cockpit II parameters file, including communication parameters COM port,
address, baudrate and node id, follow the procedure below:
Create a new project in Cockpit 3, selecting the device catalog according the application;
Select Import Cockpit II parameters file Service menu;
Locate and select the .par Cockpit II parameters file to be imported;
At the end Cockpit 3 will signal the result of the operation.
Note that, when creating a new project, the same device catalog as the original .par parameters file should be
selected. E.g. if .par file was made for TW3 firmware release 2.5.12 when creating the new project the TW
Drives Version 2.5 should be selected. If it is shown only the latest releases on the Cockpit main window,
Show all versions in catalog Options in catalog.
By double clicking the selected parameter Differences , you may update the value in the current
project device with the one in the compared project, and simultaneously the selected parameter will be
removed from the table.
The usage of devices in communication networks requires the configuration information of the devices
parameters and communciation fancilities. Both CANopen and EtherCAT define standardized methods to
access the devices parameters via object dictionary. The standardized file format EDS is described for
CANopen devices and the standardized file format XML is for EtherCAT devices.
By clicking the item Export parameters to EDS on Service , a pop-up window is appeared to let
you define a file name and choose a destination dictionary for the EDS f Confirm an EDS file
with standardized format including user specific application configuration information are exported.
The same way as above, by clicking the item Export parameters to XML on Service , you can
export an XML file with standardized format, which includes user specific application configuration
information.
Note that if the PLC application in the Cockpit working session is selected from catalog, after selecting the
Open with LogicLab a dialog window is appeared to create a new folder in the
location and copy the PLC project from catalog.
During dowloading, the procedure messages are reported in the Output window.
In the project both system device and application catalog vresions can be upgraded. Note that it operates on
the Node tree. Refer to Chapter 6.1 for activating the Node tree. To upgrade system device catalog, you may
right click the device root node in the Node tree. To upgrade application catalog, you may right click the
application node in the Node tree. Change popup menu, The Device catalog
window in Figure 52 is shown with the latest catalog version for the selected node in the Node tree.
10.6 Recipes
Recipes consist a set of parameters that user can compose to define specific values of the parameters, which
including system parameters and user application parameters. User can setup the parameters in the recipes
to configure different applications in an intuitive way.
To delete a recipe from the Recipes node, you have to select the recipe in the node tree, and then there are
the following ways to delete it:
After OK Recipes.
To delete parameters from a recipe, you can select the parameters to be removed in the recipe, and then click
the Delete parameters from recipe Recipes menu.
User can simply apply the recipe to the target device. by selecting all the items of the recipe and clicking the
Write default values Parameters menu Recipe value
into target.
After clicked, select the .RCP file to be imported from the open file dialog, the recipe will be added as
Recipes
In addition, recipes can be exported and saved in .RCP file to be used in other configurations. To export a
recipe, select on the node of the recipe to be exported, then you have the following ways:
After clicked, specify a name of the .RCP file in the save file dialog, the recipe will be exported in the location.
Monitor window
SoftScope (not available for TW0503 series)
This chapter shows you how to debug devices using these tools.
Being an asynchronous tool, the monitor window does not guarantee synchronization of values. Therefore,
when reading the values of the parameters in the monitor window, please mind that the parameters are
refreshed according to the entire cycle time of readings.
corresponding button again. Alternatively, you can click the icon in the top right corner of the
monitor window.
Please note that, in both cases, closing the monitor window means simply hiding it, not resetting it. Actually,
if you close the monitor window and reopen it again, you will see that it still contains all the parameters you
added to it.
To remove one parameter from the Monitor window, you can select it in the Monitor window and press the
Delete
However, this action is carried out asynchronously, that is, it may happen that a higher priority task modifies
the values of some parameters while they are being read. Thus, at the end of a refreshing process, the values
displayed in the monitor window may refer to different execution states of the project.
When the target device is disconnected, the Value field in the monitor window will get frozen with the last
updated value until communication is restored.
11.2 SoftScope
SoftScope is a powerful debugging tool, which can be working either as the asynchronous debugger or as the
synchronous debugger. Being an asynchronous tool, SoftScope allows you to plot the evolution of the values of
a set of parameters. In addition, being a synchronous tool, it allows you to select a set of parameters, to have
them sampled synchronously which occurs when the processor reaches the position where you place the
trigger and to have their curve displayed in a proper window.
The following sections will introduce you how to operate the SoftScope in details.
Open Softscope Target menu or clicking the corresponding icon on the toolbar.
The Output bar prints the communication messages and acquisition status to give user more information.
Output bar View
: File O
this command you can open an existing acquisition file while the actual acquisition will be closed
automatically. It is the same operation as 4.
: On-line
when the communication is disconnected with the device. Refer to Chapter 7 for setting up communication in
details.
mode, the acquisition starts running immediately when you press the command regardless of the trigger
condition. The Auto trigger mode is enabled by default.
command .
is the trigger condition is still false but you have pressed the command .
the command on the vertical axis instead of horizontal axis. It enlarges the selected curve in vertical axis
of the Chart area.
the command on the vertical axis instead of horizontal axis. It shrinks the selected curve in vertical axis
of the Chart area.
Note that all the commands in the Graph toolbar are disabled if no parameter has been added to the Tracks list
window.
Time prescaler is an editable value to amplify or reduce the base sample time with an integral number.
Sample time base displays the base sample time depending on the value of Time prescaler. Once the base
sample time is modified, the maximum acquisition time is changed dependently.
Acquisition time is an editable value to apply the required acquisition time. It must be less than or equal to
the Max acquisition time.
Note that, the trigger source can be only selected from the parameters dragged in the Tracks list window and
the trigger value has the same measure unit as in the Tracks list window.
Samples acquired shows the number of samples in the current record set.
Status is to show the status of acquisition processing. The acquisition status can assume one of the following
values:
In normal trigger mode, no samples are taken as the trigger condition is false.
In normal trigger mode, the trigger condition becomes true and it starts acquisition.
The samples are acquiring.
The current acquisition process is stopped.
Note that, if the communication is disconnected, three dots are filled in the Status instead of above values.
Generally, SoftScope applies default scales to the axes; however, you can customize the appearance of the
View on the Settings bar. It is
appeared in Figure 61.
Show time bar is a selective option to show/hide the time scroll bar at the bottom of the Chart area.
Show tracks list is a selective option to show/hide the Tracks list window below the Chart area.
Horizontal scale is to set how many milliseconds per unit of horizontal axis. The unit is the space between two
vertical lines of the background grid.
Tracks list table allows you to adjust some graphic properties of the plot for each parameter. There are the
following fields:
Note that, you have to press the Apply button to make you changes effective; or press the OK button to
apply your changes and close the Graph Settings window.
On the Tracks list window the parameter is added and queued, in the meanwhile, on the Chart area a new track
identifying the parameter with the same color in the Tracks list window is also added. Once the first parameter
is dropped, the control commands on the Main toolbar and the Graph toolbar are automatically enabled to
allow user setup sampling and visualizing.
You can do the same procedure to apply all the parameters you want to investigate. You can also select more
than one parameters per time using the Ctrl key from the parameter table, then drag and drop them to
SoftScope.
Different parameters in the Tracks list window and Chart area are distinguished by different colors. There is the
maximum number of tracks supported by different product families. Especially, the max number for Ax series
is 8; and the max number for TW series is 4. The read-only item Tracks supported Settings bar
displayed the correct value depending on different selected device.
Note that, if the communication is disabled, you cannot add any parameter to SoftScope. The icons and
on the Main toolbar are communication relative commands. Refer to Chapter 7 for communication setup
in details.
Note that, you can add to Softscope all the parameters in the parameters table, but also all the variables and
parameters defined in the LogicLab. Please refer to LogicLab manual on how to operate in details.
To remove one parameter from SoftScope, you can select it by clicking in the Tracks list window, then press
Delete Remove selected track Edit menu. You can also remove it by
clicking the corresponding icon on the Main toolbar.
Note that the communication must be enabled in order to make acquisition either on Auto trigger mode or on
Normal trigger mode. Refer to Chapter 11.2.3 for communication commands.
Auto trigger mode is an acquisition mode without any trigger source. After dragging and dropping parameters
into SoftScope, the Auto trigger mode starts acquiring Run acquisition
button . In the meanwhile the status of acquisition in the Settings bar is changed to . Figure
62 is an example for acquisition in Auto trigger mode.
11.2.7 Run acquisition to start the Normal trigger mode. If the trigger
Run acquisition
button. At this moment the acquisition status in the Settings bar is . Once the trigger condition
becomes true and the acquisition status is changed to , data acquisition starts and now the
status is . Figure 63 is an example for acquisition in Normal trigger mode.
Especially in Normal trigger mode, when the trigger condition is false, you can press the button to force
the trigger and start acquisition immediately.
Both in Auto trigger mode and in Normal trigger mode, during acquiring, you can press the button whenever
you prefer to stop acquisition.
When acquisition is completed, SoftScope plots the curves of dragged-in parameters to the axes as default
scales in order that all data fit in the Chart area. To better analyse the acquisition data, you may expect to
adjust the scales and viewings.
You may zoom in and out on horizontal axis or vertical axis by corresponding buttons , , and .
Refer to Chapter 11.2.4.
You may quickly adapt the scales of horizontal axis, vertical axis or both to display all the samples by
You may expect to split the respective tracks by the button when you have sampled two or more
parameters.
You may expect to highlight the single values detected during acquisition by the button .
You may expect to apply a different scale of the horizontal axis, which is common to all the tracks, or specify
a distinct scale for vertical axis of each dragged-in parameter by opening the Graph settings shown in Figure
61. Refer to Chapter 11.2.7.
Especially you may expect to load other tracks from other existing acquisition files to the current in order to
better analyse and investigate data. To do this, you can click the
File
the number of tracks loaded is limited by the max number of supported in the current device.
You may also save the acquisition to an alternative location by clicking the corresponding icon on the
Main toolbar. Refer to Chapter 11.2.3
After saving the acquisition, you can terminate SoftScope explicitly closing the current working session or
exiting it. To do Exit File on the right
top of SoftScope.