Skip to end of banner
Go to start of banner

Unexpected result on import of Sycon.NET ENI

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Q
  1. Importing an ENI XML file exported from anSycon.net project, the import process fails, because an error is found. For example <VendorId>3758096452</VendorId>
  2. Even if ENI file import works without error message, no process values are visible.

 

A
  1. Sycon.NET exports a vendor ID as unsigned integer (3758096452), while according to ENI XML schema this should be a signed integer (-536870844). Thus, schema check for this file fails during import in netANALYZER Scope
  2. Even though, it is not recommended to use Sycon generated ENI files, as they miss all relevant syncmanager, FMMU and PDO assignment information which is necessary to import the process variables in netANALYZER Scope. You will be able to import the generated ENI file, but you will still not see any process variables due to the missing info in ENI.
    Following engineering tools seem to generate correct ENI files:

    • EtherCAT Workbench

    • KeStudioKeStudio

    • PLC Designer

    • TwinCat

 

Even though, you should not use Sycon generated ENI files, as they miss all relevant syncmanager, FMMU and PDO assignment information which is necessary to import the process variables in netANALYZER Scope. With the attached file you will be able to import, but you will still not see any process variables due to the missing info in ENI.

  • No labels