Software Solutions for Factory Connectivity and Advanced Motion Control

List of Known Defects for ECCE

This page contains a list of known defects for ECCE and any fixed issues. If you have discovered any further defects, please report them to Customer Support via e-mail at support@cimetrix.com.

Any fixed defects are listed in the ECCE release note. It is available from Downloading ECCE.

• The ECCEConsumer web service always responds affirmatively to the equipment-initiated SessionPing message. The side effect is that if a session is not closed correctly from the ECCE GUI, then the equipment does not have a method to detect that the session is no longer active and will keep the session active. In this situation, please close the session from an admin session or using an equipment utility. When the ECCE GUI window is closed properly with the ECCEConsumer web service, the session is closed correctly.
• The New Connection dialog in ECCE does not have a cancel button and if you close it by clicking the "x" in the upper right corner, you end up with a not quite actually closed window behind it (the Minimize, Maximize, and Close buttons for it all still exist). This can be demonstrated by simply launching ECCE, closing the New Connection dialog as described and looking at the upper left corner of the ECCE window--you will see 2 sets of Minimize, Maximize, and Close buttons (one for the main window and one for a non-existent connection windows).
• All obj instances from all source IDs are displayed all under the top level equipment node. they should have been distributed to their respective source ID nodes.
• Problem selecting an exception when creating a DCP. There is a model with a single Equipment element and 10000 exceptions. In ECCE, user try to create an exception request. Selecting Equipment in the left hand tree displays all of the exceptions in the Exception list box. Selecting an exception from that list box causes ECCE to get stuck in a loop in the listViewExceptions_SelectedIndexChanged method. For some reason, it keeps getting a selected index changed call.
• ECCE displays a state machine instance like:
  + StateMachines | |-+ MyStateMachine | |-+ States | |-+ Name of top state | |-+ Name of substate 1 | |-+ Name of substate 2
  In this tree representation, the second level "States" is not necessary. This is because each state machine has one and only one top state. See E125-1105 and all previous versions.
• ECCE re-closes already closed session when session window is dismissed. From the ECCE's session window's diagnostics tab, you click the "Close Session" button to close the current session. Then when you dismiss this window by clicking its close icon, ECCE sends CloseSessionRequest again to the equipment. ECCE should have remembered that the session was closed and it does not re-send the CloseSessionRequest.
• ECCE always includes two extra things in the command data and response data:
  (1) The xml declaration line
  (2) The xsd and xsi prefix declaration
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" In fact, they are not in the actual transmitted SOAP command and response. They are a result of ECCE using the Serializer object to serialize the command or response as "root element". Therefore they must be removed and should not be shown in ECCE. Besides, the utf-16 is not correct. SOAP defaults to UTF-8. This must be done in the GUI displayed data as well as in the logged file.
• Sometimes ECCE displays some of the SEMI object instances in duplicates.
• ECCE does not displays base64 binary value correctly . On the ECCE's Get Parameter Values tab, when a base64Binary value is obtained, such as "PRJobPRMtlType", which is Bi type in GEM, the ECCE displays the value as "B64 System.byte[]". This display is meaningless. It should display the value.
• There is a reported case where ECCE had an Unhandled Exception when pressing Rule Assignment / Add ACL Entry.
• In the ECCE, the icons for modules and iodevices are swapped. the module is a 'mouse' icon and the iodevice is a 'computer'. It is correct in Equipment Model Developer.
• Can't Save DCP file when ECCE is installed on Win XP Japanese version. Save DCP and the PC OS is Windows XP Japanese version. The saved DCP file does not contain BOM as its first character in the file. Therefore, the XML file can't be opened and treated as an invalid file. Manually, user has to put missing BOM character in the file by using binary editor.
• ECCE does not support <TypeHint>. Currently, it is supporting <TypeHintType>.

Aditional ECCE Information

• Equipment Client Connection Emulator General Information
• ECCE Open Source Request
• Downloading ECCE
• EDA Connectivity Test
• Troubleshooting Guide

Download the Cimetrix White Paper on the SEMI EDA Standards.