You need a chip with the 'real big chip' modification - an extra chip soldered on with a couple of linking wires back to the microprocessor. This gives it 128K of RAM. You load the firmware in the usual fashion. Software: Once you've loaded it you can check under hardware/controllers/info to verify that it's version 460 with about 20,000 users and 1000 history capacity. It should have 'programmable relays' ticked if it's come online. The majority of the changes are under the hardware/controllers/edit reader window. For each reader you can now select the reader type - iButton, wiegand, presco or clock and data. All of the 'door' features and 'pig' features have been combined in this firmware. Thus you can have the door functions (antipassback, parking) as well as the pig features (alarm areas and inputs) in a single controller. Just for fun it also supports temperature sensors. When you select a particular type of reader for a port it automatically inserts the 'don't scan for pigs' ticks under input options; vice versa if you select iButton it automatically unticks the 'don't scan for pigs'. You can have: - up to 250 relays - relays can be on-board, expansion relays driven directly from the controller pins, 16-way expansion board relays or pig relays - up to 250 areas - up to 250 inputs - inputs can be on-board, 16-way expansion board inputs or pig inputs - up to 250 temperature sensors - up to 4 readers which can have their type mixed (as long as the interrupts work) - each reader controls up to 2 relays for access control, 2 relays for exit request, has full alarm capability including arming, disarming, arming on third swipe, door open too long, forced door delay with an associated timezone so that the delay can be active only during the day if necessary. - readers can also have an 'arming input' defined - when this input is sealed the reader works, when unsealed it doesn't. Makes mantraps easy to implement. - access levels are definable so that users have antipassback/parking override and individual capacity for arming/disarming/access while armed - 1000 history transactions - 20000 users The antipassback feature has been expanded to allow readers to be defined as entry, exit, internal, external or don't care. The access level features allow individual users to be defined as to whether they are able to arm, disarm or access while armed. You can also tick the 'antipassback override' box for an individual user which also isolates that user from the parking features. The parking feature if ticked for a controller allows up to 63 different parking groups to be defined; these are associated with access levels and under devices/parking you can view the current status of a parking area and watch it change as people enter and exit. The users are stored in the same fashion as previously ie a full site code and card number for each user. The users are stored in a sorted list so if the user at the start of the list is deleted all the ones above have to be 'shifted' down one. Even with 20000 users in the system this takes less than 8 seconds and so performance should be quite acceptable. Validation of users is extremely fast. Ditto if a user is inserted at the start of the list. In theory this firmware will replace - all the R2 door firmware - all the R2 and R3 pig firmware - all the alarm firmware including self storage It won't currently replace the fire door firmware because of capacity issues. What's not in it: - the ability to dynamically change the history storage and user capacity. There just wasn't space to fit this in. - fire door capability - I'm working on this so that we have a single firmware for all non-lift functions. - an option to read iKey encoded numbers rather than iButton ID's - will implement this shortly. - there are only 9 'holiday types' defined - a customer has requested more so I'm looking at this. ---------------- There were lots of things under technician/site and technician/features which were appropriate for a workstation only. We have done a number of sites where they have remote locations each of which is running a PC. To reduce network traffic and make it work reliably we have 'programming disabled' on those pc's - they can be used for reports etc but not for programming users. When programming is disabled (under technician/pc setup) you can't get to the menus which allow you to do programming but sometimes there were settings which could be changed locally like the window title in fact everything which is now under administration/workstation settings without affecting the rest of the system. So I took all the relevant items out of technician/site and technician/features which apply to a particular workstation and put them under admin/workstation settings; these settings are stored locally for each PC rather than applying to the whole installation. Other new things - the system needed some way to tell the difference between this comprehensive R3 firwmare and the current sort - only very minor but what I've done to make these features work is under technician/compatibility added a new tickbox R3 universal which needs to be ticked for full functionality. There's also a checkbox for the controllers which allows you to set them as 'inactive' - this might be for a place where you want to add a new controller but not actually have it polled until you're ready to commission it - you can set up the database etc and it just won't try to communicate with it until you untick the inactive box. ----------------------------------------- New version of universal firmware R3 UB465.CST Fixes the problem with the users not working properly after 255 have been loaded in. Also incorporates tamper settings for keypad retries ------------------------------------------ New version of universal DOOR and LIFT firmware R3 UB465.CST Firmware changes: Universal door (UB467) - previous versions had expansion relays inverted Universal lift (UB468) - the first universal lift firmware. Requires this rev of Advent to access the advanced features. Advent 334 Lots of changes to accommodate the universal lift firmware. However also a bug found where when editing lift access levels the changed lift access level only loaded into the first controller in a lift bank. This is fixed in this version but this explains the problems experienced at Harrington Street with lift access levels. Anywhere with existing Advent and lifts should be upgraded to this version. Other changes in this version of Advent: - 'invert lift led' command wasn't working - fixed - lift level intercom and floor destination inputs now can be pigs (with universal lift firmware) - new controller screen for editing lift universal firmware (R3 controller screen changed) - new floor screen for editing floors with R3 lift firmware - allows definition of the 'relay number' (using the relay calculator) for each floor. - R3 relays now display the debugged unpacked name for R3 lift relays and door relays - improved online/offline synchronisation of controllers - now every second the status of the controllers is checked so it shouldn't be possible for an online controller to be displayed as offline. - under controller/info new information added for universal door and lift firmware - stopped being able to log in again once logged in - closes status window after midnight check for unused timezones - sets the 'don't scan for pigs' for IN1-IN8 automatically taking into account use of relay expansion and input boards and reader types - fixed negative percentage being displayed during bootstrap download on real big chips - fixed problem with lift access levels only being loaded into the first controller in a bank when new lift access level being created or modified. - changed door numbering for R3 lift firmware so floors report correctly - fixed problem with overriding floor timezone from devices/floors screen ----------------------------------------- New version of universal firmware R3 UB472.CST UB473.CST Following discoveries re the LED operation on the new universal firmware I've revamped the LED operation for both door and lift firmware. The enclosed is the new universal stuff UB472 and UBL473 for doors and lifts respectively. To access the new features you need Advent 340 which is also enclosed. For the door firmware, I've removed the 'invert led' checkbox under the relay programming and instead there are 4 new checkboxes on the R3 controller screen to allow inversion of the LEDs for any or all of the readers. This means that the inversion will work no matter what the LED is being used for - relay, reader or alarm area status display. LEDS can now be used for: - relay operation display (select the LED output under the relay screen) - reader operation display (select the LED output under the reader screen). On access denied the led will flash, on access granted the led will turn on for 2 seconds. - alarm area status display (select the LED output on the area screen). This means that you can set it up so that two readers are operating the same relay. The reader LEDs will operate correctly even if they're both operating a single relay. For the lift firmware, no changes to the screens but I've changed the firmware so that it works much more nicely. As soon as access is granted the LED will turn on. If no floor destination reporting the led stays on until the last relay which was activated turns off. If floor destination is turned on the LED stays on until a valid floor is selected. THis should make it better in highrise because as soon as a floor is selected the led will turn off so the next person knows they can now badge their cards. With both these new firmwares the invert led works now for all situations meaning presco prox readers make sense for all applications.