Known issues – Keri Systems Doors.NET Manual User Manual

Page 46

Advertising
background image

Doors.NET Reference Manual

- 46 -

l

Corrected an issue when creating monitoring filters. Certain filter types would not
save properly, rendering those filters unavailable.

l

Corrected an issue when applying either the Mask Forced or Mask Both filters. A
Reader Contact - Door Closed event message would display in Live Events, but its
corresponding Reader Contact - Door Opened event would not. Both events now
appear in Live Events in proper order.

l

Corrected an SQL issue where database backups would only be successfully per-
formed if the default backup name was used.

l

Corrected a database issue where the database was not updated in a timely man-
ner following a controller deletion, allowing stale information to be displayed in the
grid.

l

Corrected default settings for the Vivotek video driver.

l

Corrected a positioning issue with the Photo Recall feature where horizontal dock-
ing would come up initially in a vertical orientation. Horizontal docking now comes
up in the correct orientation all of the time.

l

Corrected a template display difference between the program client and the Photo-
ID client that could make it difficult to properly edit the template.

l

Removed the Factory Defaults option from the Mercury Inside controller options
pull-down list as it does not apply to this controller type.

l

Corrected a Mercury Inside gateway issue that had the Gateway Wizard auto-
matically assigning a default Mercury controller type to the gateway, even if None
was selected.

l

Corrected an issue when assigning an IP address to a controller with Mercury
Inside firmware. When configuring a panel and assigning an IP address, you must
save the IP address before performing other tasks. The warning message to alert
the user to this requirement was not appearing when needed, allowing a user to
make other changes that invalidate the IP address assignment.

l

Corrected an issue with the Request Status command when using Mercury hard-
ware or NXT hardware with Mercury Firmware. Not all status fields would be
updated and the controller date stamp would not be updated.

l

Corrected a parameter update issue with NXT controllers using Mercury Firmware.
Certain parameter changes require the controller board to be reset, and this wasn't
always being announced to the user. When necessary, the program now will auto-
matically perform the reset as a part of the parameter save operation.

l

Extended IP addressing support in the Gateway for Mercury products.

l

Added Suspend/Restore functions for Door override functions on NXT controllers
with Mercury Firmware.

Known Issues

l

Door strike outputs cannot be reassigned from a controller to a 4x4. This should be
allowed in the software, but when you assign a 4x4 output to be a "Strike," the cor-
responding drop-down list is not displaying the Readers that can be reassigned to

Advertising