Bah! I'm speaking from the future 3.4 would be the version
It is an IT500 at version 5.4. Battery has good voltage yet the power monitor service still says the battery is bad.
Any ideas?
Bah! I'm speaking from the future 3.4 would be the version
It will take some time for it to fully charge. Look at it again.
Sent from my XT1053 using Tapatalk
It has been a few weeks now and the guy that went back by to check it said it was over 13vdc.
I'm not familiar with an IT500, but I do remember the older R2 Jaces with the plastic covers had a little bus fuse or two in it. Its been a long time, but I think I remember one of them being tied in with the battery charging circuit and it was not uncommon for the fuse to blow.
I was assuming that "IT500 at version 5.4" was a venders branding of an Ax jace. If not, my comment may not be applicable.
Sent from my XT1053 using Tapatalk
The 5.4 was a typo but I a reply to correct it instead of editing the post.
I thought IT500 was the generic Tridium name. My bad It is Niagara AX 3.4. It is one of the discontinued models like a JCI FX40 except with 4 RS485 ports on the bottom of the board instead of one on the left side.
There were a few at a site showing battery fault so we replace the batteries and even after a few weeks they still say the battery is bad.
Look into homebrewny's comment.
Sent from my XT1053 using Tapatalk
I don't see any fuses on the board. The image is of a spare I have at my office.
See this thread:
https://community.niagara-central.co...ionThread/9398
Also, see this one, it explains how the charging cycle/battery test is done:
https://community.niagara-central.co...onThread/13385
If the new battery has been installed for weeks, I'd try a different battery before condemning the JACE.
Thanks. Good info in there. Passing on to the tech who reported the battery issue.
Just to follow up on this, the battery was not bad. The supervisor at the site runs version 3.7 but the JACE panels are at 3.4. Viewing the info from the supervisor shows the battery failed but connecting directly with a 3.4 workbench does not. It appears that something doesn't quite line up with the power monitor service between those versions I guess.