Schneider, APC support forum to share knowledge about installation and configuration for Data Center and Business Power UPSs, Accessories, Software, Services.
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.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-08-0706:43 AM
ACRD100
I have several ACRD100 around the US. With firmware
Network Management Card AOS v3.9.2 ACRP-TK APP v3.7.6
When we connect to the unit via the web, there are no errors. However, EcoStruxure IT notified us with the following:
Temperature sensor "Unit Suction Air Temperature" on device "SRM01-AIR-CON-IDF-04" at 11.9 °C / 53.42 °F is below the threshold "AMER-Temperature Alert 80 or more" of 12.7778 °C / 55 °F
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-08-0705:27 PM
Perhaps someone has set a threshold on that sensor's reading within EcoStruxure IT. This would explain why the device itself doesn't show an alarm. Possible reasons I can think of for creating such a threshold could include:
to implement a conservative early warning before the point at which the ARCD itself considers there to be a problem
to provide an independent warning threshold which does not have an operational impact on the ACRD
perhaps the ACRD does not alert on this particular sensor natively
In any case, there may be a legitimate reason why the threshold was set. I suggest trying to understand who did it and why, before making changes.