Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[axgupta1]

I ran into an issue while testing SC1200. For testing, I had just put in a semi-exhausted battery in the door/window sensor and configured it as ZONE 1. After about a day, I saw LOW BATT 1 and a flashing 1 in the top left corner of LCD display.

Since the documentation does not show any such error, I assumed that the battery in ZONE 1 had run out. I replaced the batteries with fresh ones but the LOW BATT 1 would not go away. I deleted the zone and re-added the sensor to zone 1 and the LOW BATT 1 went away but came back about 5 minute later when I went into menu to check some other setting. I had to delete/re-add again and not touch the console.

What is a good way to reset the LOW BATT indicator after battery replacement without deleting/re-adding a zone?

Thanks...

[vlong]

I ran into an issue while testing SC1200. For testing, I had just put in a semi-exhausted battery in the door/window sensor and configured it as ZONE 1. After about a day, I saw LOW BATT 1 and a flashing 1 in the top left corner of LCD display.

Since the documentation does not show any such error, I assumed that the battery in ZONE 1 had run out. I replaced the batteries with fresh ones but the LOW BATT 1 would not go away. I deleted the zone and re-added the sensor to zone 1 and the LOW BATT 1 went away but came back about 5 minute later when I went into menu to check some other setting. I had to delete/re-add again and not touch the console.

What is a good way to reset the LOW BATT indicator after battery replacement without deleting/re-adding a zone?

Thanks...

I had the same problem awhile back just battery did not help I have to replace the new sensor some how the new SC1200 console did not work as good as the old console never have problem.

[Brian H]

Have you tried removing the sensor from the console?
Then removing the batteries from the sensor. Long enough so it had to have a new ID generated.
Then reinstalling it back to Zone 1.

[vlong]

Have you tried removing the sensor from the console?
Then removing the batteries from the sensor. Long enough so it had to have a new ID generated.
Then reinstalling it back to Zone 1.

back to my old day i did reset the console re-register all sensors still have the same problem but after replace new sonsor it fixed the problem i just have no idea what is wrong.

[axgupta1]

I tried a different sensor and the problem has not re-appeared for last 2 days. It could be that one particular sensor was bad.

[Brian H]

Has anyone ever actually tried forcing a new ID in the problem sensor and reregistering it before changing the sensor and saying "Wow it is fixed"?

[axgupta1]

Has anyone ever actually tried forcing a new ID in the problem sensor and reregistering it before changing the sensor and saying "Wow it is fixed"?

Can you please post some steps to do that? I am not that experienced with the system yet. I am still in the testing phase so I can test anything.

Thanks...

[phongluu]

Has anyone ever actually tried forcing a new ID in the problem sensor and reregistering it before changing the sensor and saying "Wow it is fixed"?

Brian, I tried that and it last for another 3 days max with DS10A. I don't have DS12A to try out.
What I also notice is: low batt on SC12A happen as same as on AHP showing.

@axgupta1: press & hold the test button until it blinks 3-4 times, remove batt while still hold down the test button, reinstall process.

[axgupta1]

@phongluu: I have done as you said. I will post back in a day or two whether the problem shows up or not.

[axgupta1]

The problem did not show up on the DS10 which originally had the problem. However, I configured a third DS10 and it showed the problem within hours. I followed the procedure to reinstall it with a new ID but it still had the problem. I have removed the battery and will test after 2-3 days. This is not a very good system.

[Brian H]

Thank you for your continuing tests and findings reports.