This document shows basic setup, connection and available operations on GOC43 panel, which uses GOC Toolkit V3 (CoDeSys V3.5). In order to use GOC35, please install GOC Toolkit (CoDeSys V2.3).

Creating project, adding modules, setting parameters

When creating new GOC43 project, please select GOC43 template, as it preloads necessary content and creates correctly configured visualization task. It also allows for choosing correct hardware version of the GOC panel:

When target version 1.1.0.0 is selected, the following features are not available: Data Logging, Alarm Manager, Recipe Manager.

The navigation tree allows for creation of folders and moving its contents into those folders - the project structure may be suited to the individual preferences, or to f.e. resemble GX Works.

Extension units have to be added manually – there is no automatic recognition of connected modules.

This may be done by double-clicking on the Device (GC43) in navigation tree. Then, under Hardware Configuration tab, visual configurator is displayed. Modules are added by right-clicking on the desired slot and selecting Plug Device. Same may be done directly in said navigation tree by right-clicking on the correct element under IOExtensions or COMExtension and clicking Plug Device.

It is recommended to modify default PLC settings, namely Behaviour for outputs in Stop and Always update variables settings.

The first one is mostly a matter of preference, but in majority of cases, setting Execute program is advised.

In terms of the latter one, it is strongly advised to keep its value at Enabled 2. That way, monitoring and updating of any values is possible (in similar manner, as by default in GX Works), even if those are not used in a program. Otherwise, if not used, statuses of inputs, outputs and variables are not updated unless those are used in program. 

A side-effect of those changes is automatic writing of the program to the panel each time, when Login is issued (which means - monitoring is enabled) - which makes sense and prevents mistakes, as monitoring should be done with up-to-date project.

Each module’s parameters may be accessed and modified by double clicking on the target module in navigation tree.

Parameters of built-in peripherals, such as high-speed inputs and analogs are set in Device -> Parameter Configuration window.

Unlike in GX Works, parameters do not have Apply button - once entered, the project uses updated values immediately.

​

First connection to the panel

In order to connect to GOC, the PC running CoDeSys needs to be in the same subnet, as panel. The default IP address for GOC is 192.168.15.1

Connection is established in Device -> Communication Settings.

Connected panels may be confirmed in Scan network tab, where Wink function is also available for easy identification of units. It was observed that sometimes issues with connecting to physically available panel could be resolved by Scanning network -> Winking the panel (perhaps it unbinds hanging ports or whatever else could freeze communication).

In order to read, write or monitor anything that has been loaded into GOC panel, it is required to Login into it first:

After logging in, the software automatically goes into monitoring mode, and no changes can be made to the source program.

The monitoring capabilites do include Watch windows, which are similar to those available in GX Works software (specifying whole structure, single variable, or a single address is possible).

It is important to distinguish application program from source program:

1. Application program is a compiled file, loaded onto GOC and executed there. Decompilation of such program is not possible, and it cannot be restored. Application program is always transferred to GOC. 
   
2. Source program is a project file, which includes configuration of the device, as well as source code of the program. This is the editable form of file, which can be read back from GOC panel to CodeSys. The source program is not written to GOC by default - user must write it manually.
   

Provided, that source has been written to the GOC panel beforehands, the currently loaded project can be read back to CodeSys under File -> Source upload. Otherwise, user is informed that no source files exist in the device memory.

Writing of compiled program to the panel is done under Online -> Download.

Writing of source program to the connected device is done also under Online -> Source download to connected device,

or under File -> Source download, where target device can be specified (in case of multiple GOC panels in a network).

The default state of GOC panel after writing project is Stop. In order to switch mode to Run, user have to click on a Start (F5) button visible on the ribbon in the upper part of the window, or under Debug -> Start. Operating mode may be confirmed on the ribbon in the lower part of the window.

On startup of the GOC, the operation mode is always Run, there is no physical switch to run GOC once it has been stopped (unless power is cycled or Start is pressed in CodeSys).

I/O mapping, internal memory and IEC objects

Memory structure

Memory structure used in case of GOC system is based on IEC 61131-3 nomenclature, and does differ from the other Mitsubishi products. Physical addresses use % prefix.

The memory mapping uses certain input / output areas for the specific peripherals:

I/O mapping

The I/O mapping can be checked and modified in Device -> I/O Mapping. From there, user may check the memory addresses of specific physical inputs and outputs, as well, as it is possible to update variables' names bound with them (default _DI_MAIN_n etc.).

Likewise, panel's keys and LEDs mapping may be checked and modified by double-clicking Keys_LEDs element in the navigation tree:

System variables

The GOC panel comes with a structure of predefined system variables, which may be used for monitoring, readout, or setting of certain values. Those may be viewed in Device -> IEC Objects and used in program by calling those structures directly (f.e. _Base_Analog._AIData._AI_Data[0] for readout of built-in analog input CH0 value). Those variables are not stored under any specific, user-achievable physical address - access is obtained through IEC Objects.

IEC Objects of modules

In case of connected modules, their IEC Objects can be looked up by double-clicking on a specific module and accessing its IEC Objects from there:

​

The contents of the module's IEC Objects do differ depending on a module - some modules, like f.e. analog modules are controlled solely through those, as their IEC Objects mapping contain control & status bits (required to turn on or confirm correct processing), as well, as objects storing readouts / setting values of AI / AO.