Deutschmann Automation GmbH & Co. KG
7
The Debug-interface
7.1
Overview of the Debug-interface
®
The UNIGATE
CL features a Debug-interface, that allows a step-by-step processing of a Script.
Normally this interface is only required for the development of a Script.
7.2
Starting in the Debug-mode
When applying power to the UNIGATE
0 (0x00) after a self-test was carried out on this interface. If the UNIGATE
acknowledgement via this interface within 500 ms, it is in the Debug-mode. The
acknowledgement is the ASCII-character O (0x4F).
With the start in the Debug-mode the further execution of Script commands will be put to a stop.
7.3
Communication parameter for the Debug-interface
The Debug-interface is always operating with 9600 baud, no parity, 8 data bit, 1 stop bit. It is not
possible to change this parameter in the PROTOCOL DEVELOPER. Please consider the fact
that these settings have to be in accordance with those of the PC-COM-interface and that the
flow control (protocol) has to be set on „none" there.
7.4
Possibilities with the Debug-interface
Usually the PROTOCOL DEVELOPER is connected to the Debug-interface. With it a
step-by-step processing of a Script, monitoring jumps and decisions and looking at memory
areas is possible. Moreover breakpoints can be set. It basically possesses all characteristics a
software-development tool is typically supposed to have. However, it is also possible to carry out
a Scrip-update via this interface.
From Script version [27] on you can also output data with the Script command
"SerialOutputToDebugInterface". Please also pay attention to the remark in the manual
'Protocol Developer'.
7.5
Commands of the Debug-interface
The commands for the use of the Debug-interface are described in the instruction manual
PROTOCOL DEVELOPER.
15.8.14
UNIGATE
®
(power up) the firmware will output the binary character
®
fieldbus gateway UNIGATE
The Debug-interface
®
CL PROFINET 2Port V. 1.6
®
receives an
16
Need help?
Do you have a question about the UNIGATE CL and is the answer not in the manual?