Troubleshooting "4417 DEVICE_ERR_NOADDR_I2C" errors seen in Controller's Error Log.
Building Automation Knowledge Base
Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…
Search in
Improve your search experience:
Exact phrase→Use quotes " "(e.g., "error 404")
Wildcard→Use * for partial words(e.g., build*, *tion)
AND / OR→Combine keywords(e.g., login AND error, login OR sign‑in)
Keep it short→Use 2–3 relevant words, not full sentences
Filters→Narrow results by section(Knowledge Base, Users, Products)
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
"DEVICE_ERR_NOADDR_I2C" errors are related to the internal bus to the peripherals and RealTimeClock.
DEVICE_ERR_NOADDR_I2C (no address response)
“DEVICE_ERR_NOADDR_I2C” errors are not I2 errors they are I2C errors. These errors are related to the internal bus to the peripherals (like an onboard RealTimeClock or the expansion bus (modules)).
There may have been an expansion module installed that has been removed while a PE program is still accessing an I/O on the module.
Resolution
Possible causes can be:
1. A defect with the onboard RealTimeClock. Check for 4417 errors followed by TimeSync errors and/or indications that the time clock is not stable similar to the following error lines.
01/01/1989 00:00:00.00 0x00004417 DEVICE_ERR_NOADDR_I2C (no address response)
01/01/1989 00:00:00.00 0x00010000 Clock change
2. An issue with the expansion bus modules. There may have been an expansion module installed that has been removed while a PE program is still accessing an I/O on the module.