146• Components of WAGO-I/O-PRO 32

General Online Functions

be established to the selected gateway address — possibly because it has not been started or the address is incorrect — the phrase 'not connected' appears in brackets after the address and a message 'No gateway with these settings could be found' appears. In this connection, see for further information under 'Quick check in the event of unsuccessful connection attempt to gateway'.

Once the desired channel is set up, close the dialog using OK. The settings are saved with the project.

4.6.27Setting up a new channel for the local gateway server

You can set up new channels for the currently connected gateway server, which are then available for establishing further connection from the server, a connection to a controller for example. The options that you have in this regard depend on the particular choice of the number of device drivers installed on your computer.

Press the New button. The dialog 'Communication Parameters: New Channel' comes up:

x Example dialog, installing a new channel

The input field Name automatically contains the name used for the last inputted channel. If no channel has yet been defined, the current gateway name will be offered, followed by an underline character , e.g. 'localhost_'. You can edit the channel name at this point. The channel name is purely informative, it does not have to be a unique name but it is recommended to use one.

The device drivers available on the gateway computer are listed in the table under Device. In the Name column, select by mouse click one of the available drivers; the corresponding comment, if any, appears in the Info column.

If you close the '...New Channel' dialog with OK, the newly defined channel appears in the 'Communication Parameters' dialog as a new entry in Channels at the lowest position under the minus sign. So far, it is only stored locally in the project (see above). At this point you can edit the Value column (see tips

WAGO-I/O-SYSTEM 759 WAGO-I/O-PRO 32

below). Now confirm the entered parameters with OK, thus leaving the 'Communication Parameters' dialog.

In order for the newly entered gateway channel and its parameters to also be known to the gateway server xy, and thus also to make it available to other computers that access this gateway xy, you must log into the run-time system. If you then re-open the 'Online' 'Communication parameters' dialog, the new channel appears in the "channel tree", not only in its previous position but also indented under the address or name of the gateway server xy. This indicates that it is known to the network. You can now open the Communication Parameter dialog on a computer other than the local one, select gateway xy and use its new channel.

If a communications error occurs when logging in, it is possible that the interface cannot be opened (e.g. COM1 for a serial connection) possibly because it is being used by another device. It is also possible that the controller is not running.

The parameters for a channel already known by the gateway server can no longer be edited in the configuration dialog. The parameter fields appear grey. You can, however, delete the connection as long as it is not active.

Note:

Please not that the deletion of a channel is not reversible. It occurs at the moment that you press on the button Remove!

4.6.28 Tips for editing the parameters in the communications parameters dialogue

You can only edit the text fields in the column Value.

Select a text field with the mouse, and get into the editing mode by double clicking or by pressing the space bar. The text input is finished by pressing the <Enter> key.

You can use <Tabulator> or <Shift> + <Tabulator> to jump to the next or the previous switching or editing possibility.

To edit numerical values it is possible with the arrow keys or the Page Up/Down keys to change the value by one or ten units respectively. A double click with the mouse also changes the value by increasing by one unit. A typing check is installed for numerical values: <Ctrl> + <Home> or <Ctrl> + <End> deliver the lowest or the highest value respectively for the possible input values for the type of parameter in question.

4.6.29 Quick check in the event of unsuccessful connection attempt to the gateway

You should make the following checks if the connection to the selected gateway computer is not successful. (You get the message "not connected" in

WAGO-I/O-SYSTEM 759 WAGO-I/O-PRO 32

148• Components of WAGO-I/O-PRO 32

General Online Functions

the Communication Parameters dialog behind the gateway server address in the field Channels):

Has the gateway server been started (the three-color symbol appears in the bottom right portion of the toolbar) ?

Is the IP address that you entered in the 'Gateway: Communication Parameters' dialog really that of the computer on which the gateway is running ? (use "ping" to check)

Is the TCP/IP connection working locally? The error may possibly lie with TCP/IP.

4.6.30'Online' 'Sourcecode download'

This command loads the source code for the project into the controller system. This is not to be confused with the Code that is created when the project is compiled! You can enter the options that apply to Download (time, size) in the 'Project' 'Options' 'Sourcedownload' dialog.

4.6.31'Online' 'Create bootproject'

With this command, the compiled project is set up on the controller in such a way that the controller can load it automatically when restarted. Storage of the boot project occurs differently depending on the target system. For example, on 386 systems three files are created: default.prg contains the project code, default.chk contains the code's checksum, default.sts contains the controller status after restart (start/stop).

The command 'Online' 'Create bootproject' is also available in offline mode if the project has been built without errors. In this case the following files are created in the projects directory: <projektname>.prg for the bootproject code, and projektname>.chk for the checksum. These files can be renamed as necessary and then be copied to a PLC.

4.6.32'Online' 'Write file to controller'

This command is used for loading any desired file onto the controller. It opens the dialog for 'Write file to controller' in which you can select the desired file.

After the dialog is closed using the 'Open' button, the file is loaded into the controller and stored there under the same name. The loading process is accompanied by a progress dialog.

With the command 'Online' 'Load file from controller' you can retrieve a file previously loaded on the controller.

4.6.33'Online' 'Load file from controller'

With this command, you can retrieve a file previously loaded into the controller using 'Online' 'Write file to controller'. You receive the 'Load file from controller' dialog. Under Filename, provide the name of the desired file,

WAGO-I/O-SYSTEM 759 WAGO-I/O-PRO 32

and in the selection window enter the directory on your computer into which it is to be loaded as soon as the dialog is closed with the "Save" button.

4.7 Log

The log stores in chronological order actions that occur during an Online session. For this purpose a binary log file (*.log) is set up. Afterward, the user can store excerpts from the appropriate project log in an external log.

The log window can be opened in either Offline or Online mode and can thus serve as a direct monitor online.

4.7.1 'Window' 'Log'

To open, select the menu item 'Window' 'Log'.

x Log window

In the log window, the filename of the currently displayed log appears after Log:. If this is the log of the current project, the word "(Internal)" will be displayed.

Registered entries are displayed in the log window. The newest entry always appears at the bottom.

Only actions belonging to categories that have been activated in the 'Filter' field of the menu 'Project' 'Options' 'Log' will be displayed.

Available information concerning the currently selected entry is displayed below the log window:

Category: The category to which the particular log entry belongs. The following four categories are possible:

User action: The user has carried out an Online action (typically from the Online menu).

Internal action: An internal action has been executed in the Online layer (e.g. Delete Buffers or Init Debugging).

Status change: The status of the runtime system has changed (e.g. from Running to Break, if a breakpoint is reached).

Exception: An exception has occurred, e.g. a communication error. Description: The type of action. User actions have the same names as their corresponding menu commands; all other actions are in English and have the

same name as the corresponding OnlineXXX() function.

Info: This field contains a description of an error that may have occurred during an action. The field is empty if no error has occurred.

System time: The system time at which the action began, to the nearest second.

WAGO-I/O-SYSTEM 759 WAGO-I/O-PRO 32