Odd Group: Texecom 168

[skywalker]

me and another engineer were on a site on friday because they've been having a few issues.

i was there to fix a maglock on a gate outside, and the other guy was there because their front door contact wasn't working.

 

i finished the maglock quite quickly so went and shadowed him (we came in one van) the contact works and everything, but upon looking through the zone config, we found this in the GROUP option:
 

 

its on network 1, expander 6, zone 4.
all the other zones from that expander seem to be in the same group, but the other zones work??

we temporarily fixed the fault by moving the front door contact to a fire door contact zone. but why could this of happened? corruption, low voltage, etc?

[Lwillis]

When you say it works how have you tested this?

Does it show up in walk test ?

How would moving it to a fire door zone fix the fault? Have you reprogrammed it as Final exit?

[reidy]

Ive had stuff like this happen when transferring a profile from one panel to another, all the zone and output attributes become enabled for some reason

 

Seems a bit weird if its just gone like that of its own accord

[sixwheeledbeast]

Yep, looks to me like the panel has possibly been sent saved data via Wintex, from a wrong Firmware version.

[skywalker]

When you say it works how have you tested this?

Does it show up in walk test ?

How would moving it to a fire door zone fix the fault? Have you reprogrammed it as Final exit?

on its original zone, it didn't work. when we went into 'view zone status' and opened/closed the zone, we could see the analog values changing. but it wouldn't move from 'secure'

moving it to the zone the fire door was on is only a temorary fix. it was done because the fire door has a shock on it as well, and they'd rather the front door contact worked than the fire door contact. - the zone the fire door contact was wired to worked, so we just moved the front door contact to it instead (and reprogrammed it accordingly)

it was half 4 on friday, so we were only there to get it working well enough for the premesis to be armed over the weekend and someone to come back and fix it properly on monday. 

Yep, looks to me like the panel has possibly been sent saved data via Wintex, from a wrong Firmware version.

would this cause a problem?

the panel firmware was upgraded about a month ago.

[sixwheeledbeast]

would this cause a problem?

the panel firmware was upgraded about a month ago.

Yep, different firmware versions store to the memory in different areas. If you update the firmware your suppose to bin the Wintex file and start again. This is updating between Major versions BTW (the number before the dot).

Common symptoms are Wintex errors on loading pages, programming not working correctly or only working from keypad and text in wrong places.

[AdrianMealing]

Yep, different firmware versions store to the memory in different areas. If you update the firmware your suppose to bin the Wintex file and start again. This is updating between Major versions BTW (the number before the dot).

Common symptoms are Wintex errors on loading pages, programming not working correctly or only working from keypad and text in wrong places.

you don't need to bin the Wintex profile on elite panels, but you did on some older versions, but you must change the software version in the wintex account, and always, always, always default the panel completely after flashing, both of these things not being done can cause issues with memory items from NVM being inn the wrong solace, both in the panel and in wintex.