|
MESSAGE
BOARD
FREE
USER
MANUALS
ALARM
COMPANIES
Alarm Installation
P. I.
Patrol Services
Central Stations
Fire Alarm
Locksmith
ALARM
EQUIPMENT
DSC
ADEMCO
PARADOX
FBI
Wireless_Devices
Central
Station
CCTV
Fire Alarm
Gas/CO-Detectors
Dual Detectors
Glass Break Detector
PIR (motion detector)
Environmental
Magnetic Contacts
Transformers
Batteries
Siren
Discontinued
Items
POINTS
of
INTEREST
Metric Imperial
US
Conversion
Frequently
Asked Question
Statistics
How Devices
Works
Y2K
FALSE
ALARMS
False Alarms Fees
British Columbia
California
Other US Cities
FREE LINK
TO
AlarmsBC


CONTACT US
|
BACK TO Y2K MAIN PAGE
BACK TO POINTS OF INTEREST
Year 2000
Compliance DSC Products-- July 06, 1999
This document supersedes any previous DSC Year 2000 Readiness Disclosure.
DSC recognizes the concerns of the electronic industry with the transition to the year
2000 fast approaching. The following information reflects current testing results, and
addresses all DSC products that have been tested.
The time- and date-sensitive components (hardware and software) of DSC products are
designed to correctly make the transition from Friday December 31st, 1999 to Saturday
January 1st, 2000.
Some non-critical issues are addressed under Year 2000 Readiness Issues,
below.
| Product & Version |
Year 2000 Readiness Issues |
|
| DC1664 v3.40 |
Leap year: see note 1, below |
| DC1664 v3.50 |
Leap year: see note 1, below |
| P1664 v2.00 |
Leap year: see note 1, below |
| P1664 v2.01 |
Leap year: see note 1, below |
|
| PC1555 v2.01 |
None |
| PC1565-2P
v2.21 |
None |
|
| PC1575 v1.00 |
None |
| PC1575 v1.01 |
None |
| PC1580 v1.01C |
None |
| PC1580 v1.01J |
None |
| PC1580 v1.01U |
None |
| PC1580 v1.10C |
None |
|
| PC2550 v1.01 |
Leap year: see note 1, below |
| PC2550 v1.02 |
Leap year: see note 1, below |
| PC2550 v1.10 |
None |
| PC2550 v1.10AUS |
None |
| PC2550 v1.10D |
None |
| PC2550 v1.10J |
None |
| PC2550 v1.10P |
None |
| PC2550 v1.11A |
None |
| PC2550 v1.11P |
None |
| PC2550 v1.20 |
None |
| PC2550 v1.20A |
None |
|
| AX8
v1.30 |
None |
| AX8
v1.2 |
None |
|
|
| PC2580 v1.10 |
None |
| PC2580 v1.20 |
None |
| PC2580 v1.30 |
None |
| PC2580 v1.40 |
None |
| PC2586 v1.00C |
None |
|
| PC3000 v7.00 |
Leap year: see note 1, below |
| PC3000 v7.10 |
Leap year: see note 1, below |
| PC3000 v7.20 |
Leap year: see note 1, below |
| PC3000 v7.30 |
Leap year: see note 1, below |
| PC3000 v7.40 |
Leap year: see note 1, below |
| PC3000
V7.40AUS |
Leap year: see note 1, below. Also does not recognize the end of year in 2001,
& 2002 i.e. on Dec. 31 rolls over to Dec. 32, then Dec. 33 etc. See note 1a,
below. |
| PC3000 v7.40C |
Leap year: see note 1, below |
| PC3000 v7.40MKS |
Leap year: see note 1, below |
| PC3000 v7.41A |
Leap year: see note 1, below |
| PC3000 v7.41C |
Leap year: see note 1, below |
| PC3000 v7.41MKS |
Leap year: see note 1, below |
| PC3000
V7.42A |
Leap year: see note 1, below |
| PC3000 v7.43A |
Leap year: see note 1, below |
| PC3000 v7.44A |
Leap year: see note 1, below |
| PC3000 v7.50 |
None |
| PC3000 v7.50C |
Leap year: see note 1, below |
| PC3000 v7.50D |
None |
| PC3000 v7.50P |
None |
| PC3000 v7.51 / AX-16 |
None |
| PC3000 v7.51C |
Leap year: see note 1, below |
| PC3000 v7.51D |
None |
| PC3000 v7.51J |
Leap year: see note 1, below |
| PC3000 v7.51P |
None |
| PC3000 v7.52 |
None |
| PC3000 v7.52D |
None |
| PC3000 v7.52J |
Leap year: see note 1, below |
| PC3000 v7.52P |
None |
| PC3000 v7.53P |
None |
| PC3000 v7.54Q |
None |
| PC3000 v7.6 / AX-16 |
None |
|
| PC4000 V1.0 |
Year display: see note 2, below |
| PC4000 V1.10 |
Year display: see note 2, below |
| PC4000 V1.20 |
Year display: see note 2, below |
| PC4000 V1.34 |
Year display: see note 2, below |
|
| PC4010 V1.04 |
Day of week incorrect (in scheduling): see note 3, below |
| PC4010 V2.0 |
Day of week incorrect (in scheduling): see note 3, below |
| PC4010 V2.14 |
Day of week incorrect (in scheduling): see note 3, below |
| PC4010 V3.00 |
None |
| PC4020 V1.04 |
Day of week incorrect (in scheduling): see note 3, below |
| PC4020 V2.0 |
Day of week incorrect (in scheduling): see note 3, below |
| PC4020 V2.14 |
Day of week incorrect (in scheduling): see note 3, below |
| PC4020 V3.00 |
None |
| PC4020 KT V1.01 |
None |
| PC4020A V3.11 |
None |
| PC4820 V1.21 |
None |
|
| PC5008 v2.00 |
None |
| PC5010 v1.00 |
Wrong year in event buffer on display: see note 4, below |
| PC5015 v1.01U |
Wrong year in event buffer on display: see note 4, below |
| PC5010 v1.03 |
Wrong year in event buffer on display: see note 4, below |
| PC5010 v1.03J |
Wrong year in event buffer on display: see note 4, below |
| PC5010 v1.04DK |
None |
| PC5010 v1.10 |
None |
| PC5010 v1.10A |
None |
| PC5010 v1.20 |
None |
| PC5010 v2.02 |
None |
| PC5015 v1.00C |
None |
| PC5015 v1.00U |
Wrong year in event buffer on display: see note 4, below |
| PC5015 v1.01C |
None |
| PC5015 v1.02C |
None |
| PC5015 v1.03C |
None |
| PC5010 v1.03DK |
Wrong year in event buffer on display: see note 4, below |
| PC5015 v1.10U |
Wrong year in event buffer on display: see note 4, below |
| PC5015 v1.20U |
Wrong year in event buffer on display: see note 4, below |
| PC5015 v2.00U |
None |
| PC5015 v2.20 |
None |
| PC5015 v2.40U |
None |
|
| PC5016 v1.00 |
Wrong year in event buffer on display: see note 4, below |
| PC5016 v1.10 |
Wrong year in event buffer on display: see note 4, below |
| PC5016 v1.11 |
Wrong year in event buffer on display: see note 4, below |
| PC5016 v1.12 |
Wrong year in event buffer on display: see note 4, below |
|
| PC580/1555/5008 v2.10 (A) |
None |
| PC580/1555/5008 v2.11 (A) |
None |
| PC585/1565/5008 v2.11C |
None |
| PC585/1565/5008 v2.11DJRU |
None |
| PC580/1555/5008 v2.30 (A) |
None |
|
| WLS900 v2.21 |
None |
| WLS900 v2.22 |
None |
|
| WSS5010 v1.00 |
Wrong year in event buffer on display: see note 4, below |
| WSS5010 v2.00 |
None |
| WSS5010 v2.10 |
None |
|
| Modules |
|
|
| PC5400 v1.00TA |
None |
| PC5400 v1.00TZ |
None |
| PC5400 v2.00 |
None |
| PC5400 v2.20TAFNZ |
None |
|
| NOTES:
- COSMETIC - Panel does not
recognize 2000 as a leap year. The panel will change from Feb. 28th, 2000 to
March 1st, 2000. None of the products listed will suffer critical failure
because of this. The only items that will be affected are the date display, event buffer
log, and on-site printout, where applicable.
Correction:
To correct the problem in the field,
reprogram the date on Wednesday, March 1st, 2000.
1a. The product will not
recognize the end of the year, beginning with the start of the year 2001 (and subsequent).
The panel will continue to increment the day of the month as December. For example,
December 31st, 2000 will roll over to December 32, 2000, then December 33,
2000, etc. The product will not suffer critical failure because of this. The only items
that will be affected are the date display, event buffer log, and on-site printout (where
applicable). Programmed test transmissions and auto-arming will continue as programmed,
since these are not tied to date.
Correction:
To correct the problem in the field,
reprogram the date on January 1st each year, starting with the year 2001.
- COSMETIC - Date rolls over to
100, not 00; this is ONLY evident through DLS software.
- COSMETIC - Day of the week,
during 2001, is incorrectly displayed (Scheduling). The product will properly roll over
from Friday, December 31st, 1999 to Saturday, January 1st, 2000;
however the product will begin to incorrectly determine the day of the week when the date
rolls over from the year 2000 to the year 2001. The date will change from Sunday, December
31st, 2000 to Saturday, January 1st, 2001. This will only have an
adverse effect on products that are scheduled to perform certain functions on certain days
of the week.
Correction:
To correct the problem in the field,
manually program the date via a system keypad or via the downloading computer software at
some time during the year 2000. Manually programming during the year 2000 clears a
software flag that is the cause of the problem. Once the flag is cleared, the rollover to
the year 2001 will happen correctly.
- COSMETIC - The wrong year is
recorded in Event Buffer when viewed from LCD Keypad. The product will display a random
2-digit year for previous events when the event buffer is viewed via a system LCD
keypad after the rollover to the year 2000, and at the beginning of every subsequent
year. The printout of the event buffer, or viewing the event buffer via the downloading
computer software, will not be affected. None of the products listed will suffer critical
failure because of this.
Correction:
To correct the problem, simply wait
until 128 new events have been logged to the event buffer. New events created in the new
year will display correctly. Once 128 new events have been created, the previous
years events will be overwritten.
The foregoing statement and all
other information provided to you regarding Digital Security Controls Ltds state of
Year 2000 compliance or its Year 2000 data processing capabilities, either in writing or
via electronic form, including via our Internet web sites, either in the past or present,
regarding any products or services offered by Digital Security Controls Ltd are Year
2000 Readiness Disclosures in conformity with the Year 2000 Information and
Readiness Disclosure Act of 1998 (Public Law 105-271, 112 Stat. 2386), enacted on
October 19, 1998. This designation applies to all information delivered directly to you,
or derived from our Internet web site, both in the past and present, and includes all
other related Year 2000 materials.
|
AREA FOR
ALARM COMPANIES
AND SECURITY
EMPLOYEES
=CENTRAL STATIONS
PROTOCOLS
=SOFTWARE
=INSTALLATION
TIPS
and
NOTES
=FORMS
=PRODUCTS
OVERVIEW
=TECH
SUPPORT PHONE NUMBERS
WEB HOSTING
=DATA
CENTER and
CONNECTIVITY
=VIRTUAL PACKAGES
DETAILS
=VIRTUAL
PACKAGES PRICES
=WEB CONTROL PANEL
=POLICIES
LINKS TO
RELATED SITES
JOKES
DAILY NEWS
CANADA MAP
GLOSSARY
SEARCHING
WWW
UNIVERSAL CURRENCY CONVERTER
CONTACT US
|