Datasheet

Sysmac Studio
8
Debugging
Forced refreshing
Forced refreshing allows the user to refresh external inputs and outputs with user-
specified values from the Sysmac Studio. The specified value is retained even if the
value of the variable is overwritten from the user program. You can use forced
refreshing to force BOOL variables to TRUE or FALSE in the Ladder Editor, Watch
Tab Page, or I/O Map.
All versions
Online editing
Online editing allows you to edit programs on systems that are currently in operation.
Online editing can be used to edit only POUs and global variables. User-defined data
types cannot be edited with online editing.
Cross Reference Tab Page
Cross references allow you to see the programs and locations where program
elements (variables, data types, I/O ports, functions, or function blocks) are used.
You can view all locations where an element is used from this list.
Debugging
Data tracing
Data tracing allows you to sample the specified variables and store the values of the
variables in trace memory without any programming. You can choose between two
continuous trace methods: a triggered trace, where you set a trigger condition and
data is saved before and after that condition is met, or a continuous trace, in which
continuous sampling is performed without any trigger and the results are stored in a
file on your computer. However, you can still display data retrieved on the Sysmac
Studio and save those results to a file even if you use a triggered trace. These same
functions can be used with the Simulator as well.
All versions
Setting sampling intervals
The interval to perform sampling on the target data is set. Sampling is performed for the
specified task period, at the specified time, or when a trace sampling instruction is
executed.
Setting triggers
To perform a triggered trace, you set a condition to trigger sampling. A suitable
trigger condition is set to record data before and after an event.
Setting a continuous trace The method to save the data traced during a continuous trace is set.
Setting variables to sample
The variables to store in trace memory are registered. The sampling intervals can also be
set.
Starting and stopping
tracing
The data trace settings are transferred to the NJ/NX-series CPU Unit or NY-series
Industrial PC and the tracing starts. If you selected Trigger (Single) as the trace type,
tracing waits for the trigger to begin sampling. If you selected Continuous, sampling
begins immediately and all traced data is transferred to the computer as it is gathered
and saved to a file.
Displaying trace results
You view the results of the traced data in either a chart or the 3D Motion Monitor.
After sampling begins, sample data is immediately transferred and drawn on the
graph. The trace target variable table shows the maximum, minimum, and average
values for each variable.
You can change the line colors on the graph. *10
You can consecutively read and display continuous trace results from more than one
file. *11
Exporting/ Importing trace
results
Trace results are saved within your project automatically when you save the project
on the Sysmac Studio. If you want to save this data as a separate file, you can export
the data to a CSV file.You can import trace results that you have exported.
Printing trace results You can print out data trace settings along with digital and analog charts.
Debugging Vision Sensors
You can debug the Vision Sensor offline.
Refer to "Function Specifications of Vision Sensor Functions".
Ver.1.01 or higher
Debugging Displacement Sensors
You can debug Displacement Sensors offline.
Refer to "Function Specifications of Displacement Sensor Functions".
Ver.1.05 or higher
Simulation
Programs for debugging
You can create programs for debugging that are used only to execute simulations
and specify virtual inputs for simulation.
All versions
Executing
a
simulation
Selecting what to simulate
You can select the programs to simulate from all of the programs in the Sysmac
Studio. Programs can be dragged to select them.
Setting breakpoints You can set breakpoints to stop the simulation in the Program Editor.
Executing and stopping
simulations
You can control simulation execution to monitor the user program or to check
operation through data tracing. Step execution and pausing are also possible.
You can perform a linked simulation between sequence control and continuous
control (operations controlled by Simulink) to debug the sequence control program
and continuous control program. *12
Ver.1.09 or higher
Changing the simulation
speed
You can change the execution speed.
All versions
Task period simulation You can display the task periods.
Batch transfer of the
present values of variables
You can save the values of variables at specific times during simulations in a file, or
you can write the values of variables that were saved in a file back to the Simulator.
This allows you to write the initial values of variables, e.g., for test applications,
before you start a simulation.
Ver.1.02 or higher
Integrated NS-series PT
simulation *13
You can simulate the linked operation of a sequence program and an NS-series
Programmable Terminal to debug the sequence program and screen data offline.
Simultaneous simulation of
Controller and NA-series PT
You can simultaneously simulate sequence control and NA-series PT operation,
including displaying pages and subroutines created with Visual Basic and debugging
the sequence programming.
Ver.1.11 or higher
Item Function
Applicable
versions
*10.Changing the colors of graph lines is supported by version 1.01 or higher.
*11.Consecutively reading and displaying continuous trace results from more than one file is supported by version 1.05 or higher.
*12.MATLAB
®
/Simulink R2013a or higher is required.
*13.CX-Designer version 3.41 or higher is required.