GalaxyGuy

Eg. 15 mins in a year. (15*60)/52 = 18 seconds a week.

You need to work out the adjustment in a week. How long has it taken to lose 15mins ?

Modify -> Time & Date -> Press # It's in the manual.

Galaxy G2-12, MK7 Keyprox, new 12v 7ah Yuasa battery and LCE module will be the cheapest hard wired IP panel at under £150. Wire 1 zone per sensor.

The panel temperature can impact the drift. The design guide suggests automatic temperature based compensation be implemented, but the design doesn't implement a temperature sensor for this, so Honeywell provide an adjustment parameter in the panel menu.

Yes, the monthly server costs alone are in the hundreds, so would be too much of an overhead for a small company with an estate of only a few hundred sites. The main SelfMon platform has processed over 30M events so far and has very little overhead apart from the points where Amazon force database or EC2 service updates. The forced updates require intervention to re-build the platform on new instance versions to allow seamless transition. Ie. the servers need to keep receiving, or the panels complain of ARC failure.

There's another developer involved who would provide continuation. We're working to package the whole platform up for companies who want to buy it to provide the service themselves, but it does require technical knowledge of Linux, database internals and aws, so not many alarm companies would cope with running the platform themselves.

The selfmon platform has been running since 2011. Uptime has been better than 99.999%, with a couple of minor short outages caused by Amazon who host the servers. The future plan is to enable a push notification message queue with the selfmon keypad apps and this will allow customers to direct all lower priority events to the push queue, while directing actionable events to all message queues.

The latest GX Android app seems to have push capability in the latest release. Not sure how good the service will be, but there's always Selfmon for those who aren't happy with it, or want more than push notifications.

Use the seconds advance/retard per week option in the time/date menu. The Atmel CPU's real time clock is sourced from the usual 32.768kHz crystal, so depending on the precision, this can impact the accuracy. As things move forward, IP connected panels can reference NTP servers for better accuracy. This can be performed at the moment with the Galaxy panels, but it's an ARC push, rather than a panel pull to align the clock.

There's a lot more going on in the WiFi modules to gain and keep a connection going 24x7. So, the issues are likely a combination of WiFi signal issues, customer configuration issues, ISP connection issues and immature firmware.

Nah, 95% of the COM-IP is the Lantronix module (Serial to Ethernet) - made in... China. Might get a bit of additional testing performed in the UK, but most outsourcing strategies placed exactly the same test suites in China that were in place in the originating countries. From my previous experience in a mass manufacturing environment (much bigger volumes than alarm panel assy's); Boards assembled in China were just as good, if not better than in the UK. One of the main things that has increased DOA and reduced long term reliability has been the introduction of RoHS - making solder joints more brittle and prone to fracture in transit or over time with thermal cycling.

It's looking for the SIA handshake. Look up the opengalaxy project.

Module probably needs power cycled. I've seen this happen, but quite rare. If not under contract and you have engineering code, it's easier to power cycle the whole system (batt and mains disconnect momentarily), then correct the time and date.

I've no interest in capturing anyone's details. The link takes one or more serial numbers and provides a CSV file with the original tag ID you provided and the max id. I will post along with password in the engineering area.

Dan, did you get this resolved ? I can give you access to a converter app that I have on my website. This allows you to convert the cheap tags/cards serial number (the one that's scanned by the keyprox) to the one that the external MAX uses. At least you can use this to validate the etched code is correct from the keyprox scanned serial number.

Only this one works with the Flex and ARC who have invested in the receiver from Honeywell. https://www.securitywarehouse.co.uk/catalog/honeywell-pir-night-vision-10m-ib-p-4916.html

No. With each sensor costing £130, it's not something I've looked at.

The Flex supports a PIR sensor with integrated camera for intruder verification images. The images can only be pulled by the ARC and the app doesn't receive them.

The stand alone max reader uses a different algorithm to decode the prox tag serial number. The tags that work with the keyprox also work with the max, but you need the max based decoded serial number. If you have a user who needs to use both the stand alone max reader and the keyprox, then you need to add two accounts to the system. One with the etched serial number (from the thin Galaxy tag) for the stand alone max and one with the 1+'A' scanned tag number for the keyprox. The thin Galaxy tags have the stand alone max based algorithm number etched on them. The cheaper 125khz tags or cards from eBay have the standard serial number etched/printed. The cheaper ones work, but you need to decode the serial number into standalone max reader format before they will work with the standalone max reader. The reason for this ? Honeywell probably wanted to monopolise on sales of the access cards/tags. Dan, your scanned tag will be working with the keyprox, but will be locking out when used with the max. Add another user and add the etched number to that account.

Is the bootup from your reboot of the panel, or is the panel rebooting itself ? You say that the fobs are accepted sometimes. You're using the black Honeywell etched fobs and adding the etched number manually against the user ?

Connect with RSS and pull the log when it's locking you out. See what the log is saying. If the reader was faulty I would expect the log to show all devices dropping from the bus. Could be lockout related too.

Someone else had the same idea with the two they had the other day... http://offer.ebay.co.uk/ws/eBayISAPI.dll?ViewBidsLogin&item=122376450807&rt=nc&_trksid=p2047675.l2564

The good thing about this design is that the firmware can be upgraded from the LAN in less than 5 seconds. This makes it easier to create special firmware to do things like dumping out settings/PINs. I would probably lock those to specific 'engineers' hardware.

The Honeywell GX app will only work on the Honeywell E080-2/4 & A083 (Flex) Ethernet modules. The E080-2 should be at V2.11 and the E080-4 should be at V3.06 to work with all combinations of panels.