OPC Server communication problems
Dear Mr. Slavomir Seman,
the cable to connect to EIB from the EIB OPC Server is the same as for the ETS2. This is indeed a "plain serial cable", meaning, all wires shall be connected "1-to-1" (This means: pin 1 on the male side with pin 1 on the female side, pin 2 on the male side with pin 2 on the female side, and so on.) This is to differentiate with so-called "null-modem cables" in former days often used as direct connection between computers without modem.
You do not mention the ETS version. In case you would have installed the ETS NT Update (meanwhile deliverable for free on request), it would be interesting to know whether that software has bus communication or not.
Some further questions:
- Were you able to retreive the project information from ETS (via the odd "print" way) and import that information in the OPC Server?
- Can you communicate with EIB directly from the OPC Server's user interface? Write group values AND read group values?
- What is the error message if there is one?
- Did you disable the FIFO in your computer?
- Falcon, on which the OPC Server bases, creates error log files typically in a directory named c:\Program Files\Common Files\EIBA s.c.\Log. These are files with the extension .hlg. You can delete all these files, redo the problem, and send us these log-files.
- The OPC Server itself has no logging. If the problem would thus be due to a communication problem between the OPC CLIENT and the EIB OPC Server, we can not find it, and you should contact the provider of the OPC Client software (Iconag).
Best regards,
Mr. Steven De Bruyne
System Department - KNX Association
Lesezeichen