Just had a look at the logs which show something interesting. When disarmed the heat sensor activates and shows no area - when armed it does show the correct area and you can see the bell is triggered. See attached. Does this prompt any ideas? This actually seems to be the case for everything that triggers when not armed like the tamper when I open up the psu200xp.
Texecom Exodus - keypad sounds - bell doesn't
- Thread starter matt-uk
- Start date
that my explain what is going on, I just had a lok at the one in the office for the tests conducted on 10th January and the area is showing in the log when it activated unarmed.
you can power cycle the panel and default he reporting codes. I could look at the profile in full and see if can see if there is any differences if you email to me. In my case it was in rea A on the 168 and was zone 14 but it was a wireless smoke.
you can power cycle the panel and default he reporting codes. I could look at the profile in full and see if can see if there is any differences if you email to me. In my case it was in rea A on the 168 and was zone 14 but it was a wireless smoke.
Okay. Power cycle I can do. Sorry to sound stupid but how do I default the reporting codes?
you can do it in wintex and send cross reporting codes or you can do it in engineer utilities and default NVM data, scroll through to default reporting codes then yes
I am shocked - I did a power cycle of the panel, pulled the fuse and the battery and now it works as it should. Just activated the zone when unarmed and the external sounder worked!
Cant believe the solution was ultimately to 'turn it off and on again'!!
Is a power cycle a common requirement for panels? - I had the same issue when connecting the ComIP to the panel - it just wouldn't get an IP address whatever I did until I power cycled. I had forgotten about that or I might have tried it sooner.
Cant believe the solution was ultimately to 'turn it off and on again'!!
Is a power cycle a common requirement for panels? - I had the same issue when connecting the ComIP to the panel - it just wouldn't get an IP address whatever I did until I power cycled. I had forgotten about that or I might have tried it sooner.
lol it’s always worth doing as sometimes the changes don’t register and the power cycle makes it checking its settings are pulled in, well that’s how I think of it.
Settings check first, then power cycle. IP you can turn off in comport setup and clear out in modem setting ip settings and then switch it back on after going out and back into engineering (I do first, then power cycle last). Then tech support, but finding in many different scenarios tech support isn’t what it used to be across many different manufacturers.
had a fall out with Hikvision over support and attitude recently, we no longer offer there products to new customers. Two wasted sites visits and had to fight to get any support because it was EZVIZ on hik connect, which they no longer offer cross support on.
Took back to the office, couldn’t get it to work still, down powered it over night and bing bang Bosch got it all working, trip back to site on a Sunday and moments later all up and running.
The power of, off and on. When I advised them of the what worked there reply was even more shocking.
I suspect that was some kind of settings messed up by the customer and locked into the devices involved and the long power down facilitated recovery as new devices, but no such recommendations offered by support, I didn’t get firmware file updates but they did nothing. very expensive for us.
had a fall out with Hikvision over support and attitude recently, we no longer offer there products to new customers. Two wasted sites visits and had to fight to get any support because it was EZVIZ on hik connect, which they no longer offer cross support on.
Took back to the office, couldn’t get it to work still, down powered it over night and bing bang Bosch got it all working, trip back to site on a Sunday and moments later all up and running.
The power of, off and on. When I advised them of the what worked there reply was even more shocking.
I suspect that was some kind of settings messed up by the customer and locked into the devices involved and the long power down facilitated recovery as new devices, but no such recommendations offered by support, I didn’t get firmware file updates but they did nothing. very expensive for us.
Well massive thanks for all your help and guiding me through the troubleshooting.
I have 4 more buildings to add to the system as different areas over the next few weeks so you may well see me popping up desperate for help again in the near future.
Thank you
I have 4 more buildings to add to the system as different areas over the next few weeks so you may well see me popping up desperate for help again in the near future.
Thank you
I am sure the community will help where it can
DIYnot Local
Staff member
If you need to find a tradesperson to get your job done, please try our local search below, or if you are doing it yourself you can find suppliers local to you.
Select the supplier or trade you require, enter your location to begin your search.
Are you a trade or supplier? You can create your listing free at DIYnot Local
