FAQ
MECip
SECURE
- 47 -
10
FAQ
•
I lost the Device Certificate. What can I do?
Take an ETS project where it is contained and open the Project Certificates Report.
•
I opened a new project in ETS and added the Device Certificate. But the
download to the secure MECip-Sec doesn´t work.
Either use Commissioning Password and Authentication Code from your former
project or make a factory reset to set MECip-Sec´s tool key back to its FDSK.
•
I lost the Device Certificate and the password for the project where it was
contained. What can I do?
Make a factory reset and use the device only unsecured from then.
•
The firmware update finished successfully but the device doesn´t work.
To restart turn the power off and on again (dis-/reconnection of KNX TP line).
•
Is it Ok to connect and disconnect the Ethernet cable quickly?
No! Don’t do this. Before reconnection, wait for a few seconds.
•
What shows the Programming LED if the Ethernet cable is not connected?
Similar to having no IP network available, the Programming LED is blinking red.
•
What can be a transmission error when LED 2 Bus State KNX TP is lighting red?
For every telegram sent out on KNX TP, MECip-Sec waits for an acknowledgement on
the TP line. When the receiver was busy (BUSY) or received an incorrect telegram
(NACK) or MECip-Sec didn´t receive an acknowledgement (missing IACK), LED 2 is
lighting red to show a transmission error exists on the line.
•
LED 2 Bus State KNX TP is continuously blinking green. Why?
This indicates MECip-Sec is waiting for his firmware file download. For more
information and how to switch back to normal operation please see chapter
