Support / FAQ

Hier findet sich eine Sammlung aller FAQ die für die Kunden des IO-Link Master-Testers von Interesse sind.

Sollte Ihre Frage nicht aufgelistet sein, können Sie das Kontaktformular zur Kontaktaufnahme nutzen.

Q: Loading of several IODD's by the device configurator dialog fails
     with error message e.g. 'Missing ProcessDataIn element in document'.

A: The version V1.0 of IO-Link Master Tester expects some optional XML entries
     as mandatory. This issue will be corrected in Version 1.1.
     As work arround you can add the missing XML entry in the IODD e.g. :
    <ProcessDataIn id="dummy" bitLength="0" />

Q: Trigger pulse at BNC to short.

A:  It is not possible to set a Trigger pulse with 24VDC

Q: A IO-Link Master with PROFIBUS interfaces is not able to establish
     a communication with the Master Tester System, using the default DUT_IF DLL (Hilscher).

A: The DUT_IF DLL V1.0.0 has a timeout of 10s for startup. If a DUT needs longer for startup,
     the connection fails.
     It is possible to change the source code of the DUT_IF DLL and build a new version
     (Source package is delivered on the Product CD). Please contact MESCO for support.
     The DUT_IF DLL V1.1.0 has an extendet timeout implemented. 

Q: At Win 7 the USB driver will not be automaticly installed with the setup.exe

A: If the Hardware Wizard does not find the preinstalled Golden Device Driver,
     you can select it manualy in the installation directory.

 Q: The IO-Link Master Tester expects  HW-Rev. 0100 (or higher) from the connected GD.
      But the GD has the HW-Rev. 0001.

A: In some delivered GD's, there  is a byte mismatch in the HW Rev.: '0001' is equivalent to '0100'.
     You can ignore such an error message and deactivate the Test Step 'Check GD Info' if needed.
     The Version >1.1.1.0 of the PC-SW accepts both HW-Revisions.