New and Noteworthy
Key | Component | Summary | Description |
|---|---|---|---|
PROFINET Master | Support of PNIO modules with input and output data | Modules which contain input and output data shall be supported by the PNIO Master. | |
Core | Add a refresh of available network interfaces | If the ICE is started before a required network interface is available (due to non plugged cable for example) there is no way of refreshing the list of available "Network Interfaces". The tool has to be restarted to visible it. The network list can be refreshed by a right click on „Network Interfaces“ and left click on „Refresh Interfaces“. | |
Core | Add Mac OS support | Add support for Mac OS X including EtherCAT proxy. | |
EtherCAT Master | Add feature SII (eprom) initialisation for EtherCAT master. | It should be possible to configure the content of the dut SII (eeprom) from the ICC. Data for the eeprom is available as binary files, generated by the design tool. | |
EtherCAT Master | Add options for ESM states to EtherCAT master | It should be possible to directly choose each possible ESM state of the slave. Following buttons should be presented to the user:
| |
PROFINET Master | Add Alarm handling to PROFINET master | The PROFINET master should support PROFINET alarms. This requires to acknowledge received alarms from the DUT. Beside that, alarm information (diagnosis, …) should be displayed to the user. | |
PROFINET Master | Improve IOxS handling for PROFINET master | The IOxS, which are settable by the Master should automatically be set to GOOD in case of a successful connection. Still those values should be changeable as of now. | |
PROFINET Master | Process Data Tests | The PNIO Master shall allow to define basic tests of process data. Therefore the cyclic data exchange is initiated, alternating data is written and (optionally) the result is compared with the data sent. The following method shall be provided for data generation:
|
Bugfixes
Key | Component | Summary | Description |
|---|---|---|---|
PROFINET Master | Non-continuous slots lead to invalid connection configurations | GSD files that use non continous slot list like 0,2,3 lead to wrong connect request using wrong slot/subslot configurations. This results in denied connect requests. | |
EtherNet/IP Master | Negative "Remaining time" when scanning for EIP devices | The "Remaining time" is counting from 0 to negative value, if the request protocol _EIP_ has been choosen for scanning network. | |
EtherCAT Master | Error while reading more than 124 CM variables per EtherCAT EoE | Ethernet frames with more than 1200 bytes were discarded by the EtherCat proxy. This results in failure to read configuration with more than 120 CM variables. | |
Firmware Update | Firmware update fails if device has no permanent IP address | If a device has no permanent IP address (GOAL_ID_NET:VALID == 0), the ICE detects this situation and allows to set the IP address to valid (GOAL_ID_NET:VALID = 1). However this operation is not executed and the firmware update does not proceed. It stays in step “Sanity check”. | |
EtherNet/IP Master | EIP: typo in EIP Master UI | There is a typing mistake in window EtherNet/IP Master -> I/O Data. "Assembly Instance ID" and "Assembly Data Size" is written with 3x "s" for "Connection Parameter O->T" and "Connection Parameter T->O". | |
EtherNet/IP Master | EIP: wrong amount of assembly data | ICE sends 32 byte assembly data in first O->T frame, even if the amount of data was changed. | |
EtherNet/IP Master | EIP: non-visible input assembly data | Input assembly data is always shown in the same size as the output assembly data. This leads to empty input assembly data when when the output assembly data has zero size. | |
EtherCAT Master | EtherCAT: FoE firmware updates allegedly succeeded, although BOOTSTRAP state could not be entered | By default firmware update in the CCM example applications is configured to require BOOTSTRAP state. The example application ugoal/06_ethercat_minimal although does not support bootstrap mode. Therefore firmware update over FoE is not possible with this application. The ICE although shows “firmware update succeeded” for the failed firmware update. | |
PROFINET Master | Large amounts of cyclic data leads to a frozen PROFINET master | Large amounts of data may freeze the PROFINET Master and the GUI. | |
EtherNet/IP Master | EIP: non-refreshed input assembly data | The byte field "I/O Data T->O" is not refreshed, when the Assembly Data Size is greater than 128 Byte. It shows zeros, even if the traffic is visible in wireshark. | |
PROFINET Master | Missing data in process data view of profinet modules | The process data view for profinet modules only shows 8 byte. Output data is shown completly as a hover over window. Editing of output data is also possible completely. However, input data cannot be accessed beyond the first 8 bytes. | |
PROFINET Master | Import error with GSDML using separate slots instead of lists | The import of a GSD file fails when the physical slots list of a DeviceAccesPointItem is not a list (0..2) but contains separate slots (0 1 2). | |
EtherCAT Master | Mapped objects of type OCTET_STRING are not visible and editable in the I/O Data view | Mapped objects of type OCTET_STRING are not shown in the I/O data view, neither for Rx or Tx PDOs. | |
PROFINET Master | Parse error for ranges of allowed slots | When plugging a module with a range for allowed slots, an error occurs saying NumberFormatException. | |
EtherNet/IP Master | EIP: invalid format of device IP | Scanning for devices with preference "EtherNet/IP" finds connected slaves but the endianess of the IP in window "Network Navigator" is invalid. | |
Core | Configuration of IP address in Config Manager limited | A dut is configured with the IP address 10.10.0.2. Now it is not possible to enter an IP address with 3 digit values (e.g. 192.168.0.100). | |
Core;Firmware Update | Unsuccessful firmware update isn't communicated to the user | After execution of a firmware update, the version information shall be checked whether equal to the expected firmware version. Both the version string from the bundle and the signature from the bundle should be checked against the provided values in the CM variables. |