avolobuev

To add to that, if you configure areas properly, system has a muster report which works fine.

No problem. It's best not to look for answers in the database.. relationship between tables is quite complex one. In the app, you should enable reader ports under hardware / reader tab. Ones enabled, you need to add that reader to access rights. Only then you will see valid transactions in the monitoring. Personnel records and settings are kept in the main database, all activity and events - in History database, referencing person ID numbers, etc, specified in the main database, so again, looking at SQL alone will not be very easy, since data is spread across a minimum of 2 databases. Try to follow the manual how to create a reader, access right, person, etc.

I'm wondering if anyone tried to flash the firmware from ProWatch to Lenel, sicne these are the same boards... you are correct that is a honeywell pro watch system. I had to swap out about 65 of them systems to LENEL at a local refinery here. They use mercury branded boards.

Hi, You may already have that reader port enabled, this is default setting. You need to make sure you use correct reader. Best, use the same reader as you already have. GE uses proprietary format F2F. Here is a link to Secure Perfect manual available through Google search: http://fitch.ca/fs_upload/support/product7-1360704576184.pdf?lbisphpreq=1 Good luck! Alex

Hi Ian, I am wondering if your client was still trying to connect to the old "production" server, since that server was still available online? Also... old school question. Is your network mask 24 bit? Can you IP your new server and close your subnet mask the way that it cannot reach the old server even if it wanted too?

Sure. Most software can be configured to fire a lock output 3 ways: 1. On duration. So, ones valid card read is recognized, output is energized for a certain amount of time. Usually, 5 seconds for door and 1 second for gate control. In good systems, while output is activated, door alarms are shunted, since door is expected to be opened, but software continues to look at door contact status to know that granted entry was actually used or if door remained shut. Some basic soft simply ignores door contact status during this time. 2. On door open. Software detects that door has been opened and re-locks the door as soon as it detects that door contact changed state. Useful to shorten the actual time lock is open to help prevent tailgating, when someone has passed through, door had closed, but lock is still engaged. Works best with maglocks. 3. On door closed. Software detects that door has been opened, and re-locks the door as soon as the door had returned to closed position. In all of the above cases there should be no door forced alarms while the door is legitimately open. On some systems there is a separate setting for alarm shunt time (not to be mistaken with door held alarm time) As far as jitter, in some cases you won't be able to see it without an oscilloscope. Some systems allow you to enter debounce settings, typically in 1/10 secon increments. This is very important for setups 2 and 3, but should be irrelevant for 1, since it is covered by default firing time. Hope it helps, Alex

Easy. Provided that both users do close the door behind them, the door is not possible to open before card releases the strike, both open the door with about the same strength and speed, the issue is strictly inside the "no name" software. Otherwise I would suspect that door contact produces 2 or more changes of status during door opening, or jitter, first one being masked by the software while next ones are not - again, software fault. When set to fire on duration, door contact should be masked for that entire time. Maybe it is worth getting a trusted name access control software...

What kind of strike? Door contact integrated? Is A a stronger man than B? Is the REX set to unlock the door? Door contact jitter? Does "Generic" means "no name"?

I am dealing with a whole bunch of Casi this spring, migrating one huge client over to Lenel, and needed to lookup something - found this page and bunch of struggling folks, decided to help a little. It is a shame that UTC is killing that line. If you are still working at the same place, say hi to folks for me. )

Scott! I wondered if it was you )

Hi, all. Secure Perfect has been replaced by Facility Commander WNX (not to be mistaken with Facility Commander Classic, which is a Linux based video management system for Picture Perfect). While I have most of important versions starting from 6.1.1, having the software will not do anyone much good without a license. There are couple of things I can help with: 1. If you have a system with failed windows / HDD going bad, etc., I may be able to help you to recover the system. Crucial things will be the database files, it uses MS SQL. Typically you can find the files inside Casi / GE folder in Program Files, sometimes SQL databases are placed within SQL folder. In any case, I would try to get the whole drive copied / recovered where possible, there may be older back up files which are needed, plus a billion non-database objects (such as personnel pictures, card layouts, etc) It is extremely important to also gather hardware info, such as windows version, MAC addresses for all network adapters and taking note of computer name and IP addresses used. This all could lead to successful system recovery. 2. If you have your license key, things are good. If you can, look for it. Typically it was sent as an e-mail or given over the phone. If you can find that e-mail or a printout, great - it will tell you proper software version, license, and system ID. We can work with that. If not, you can attempt to contact UTC/Lenel and see if they can find your old key. If you don't have any head end computers, documentation with license key, and UTC can't retrieve your data (may be registered under previous company, etc.) they may tell you who the integrator on file is or was. There is a little chance your integrator has the info. 3. If you cannot get anything besides what you see on the wall, you will need to buy a new license for FCWNX. Current release is 7.7, no more releases expected. 4. Final option without rewiring the whole place is to upgrade to Lenel OnGuard. There are special Mercury boards they have to replace boards inside the Micro. Hope it helps, Alex Here.SecurePerfect.zip