Alarm Lock DL2800 strange problem

[cledry]

Had a strange issue with a DL2800 Trilogy. The manager code and employee code suddenly stopped working.

We dumped the log file only to find that at midnight on 03/27/2013 the clock reset to 01/01/2000 and lost all of the codes but kept the schedules.

Wondering if anyone else has run across this?

[LockDocWa]

Just a guess here: You will get more response from a professional locksmith website
Assure... no offense to the lock picking 101 crowd.

It's just that most folks here are more into picking locks than installing Alarm Lock Systems

[cledry]

Just a guess here: You will get more response from a professional locksmith website

Assure... no offense to the lock picking 101 crowd.

It's just that most folks here are more into picking locks than installing Alarm Lock Systems

I reckon you are correct. I know there are a few other locksmiths on this forum though, so thought I would post here just on the off chance.

[2octops]

Call their tech support and they should be able to explain it to you.

[cledry]

Call their tech support and they should be able to explain it to you.

They claim to have never heard of it before.

[2octops]

If they've never heard of it, then you're most likely looking at a chip issue on the board.

Replace the lock with new and move on.

[cledry]

If they've never heard of it, then you're most likely looking at a chip issue on the board.

Replace the lock with new and move on.

I'm letting Apple corporate fight it out with Alarm Lock. They supplied the lock we install and program them. Lock is 3 months old.

[MacGyver101]

Pure guess here... but if you're unfortunate enough to run into this again on some other lock, and you have to start investigating this further, I'd check:

• Does the user database inside the lock have a record of when the user was added? (i.e., if you add a new user today, and then set the time in the lock back to yesterday, does it refuse to recognize the user?)
• Did the second lock also have this problem after the 1,599th log entry... or immediately after midnight?

There's a whole host of possible bugs -- but, based on weird software errors I've had to diagnose in the past, one of my first checks would be to see whether the 1,600th log entry overwrites the current time in memory. (Do you have other locks with a similar number of log entries? That's not really that high for a high-traffic door, so my first guess may be way off here.)

Anyhow, without actually being able to properly examine the software in the lock, I'm just guessing. Fingers crossed that this is the only time you see this.

[2octops]

It's a warranty issue.

Let them get a replacement and charge them to change it out.

[cledry]

Pure guess here... but if you're unfortunate enough to run into this again on some other lock, and you have to start investigating this further, I'd check:

• Does the user database inside the lock have a record of when the user was added? (i.e., if you add a new user today, and then set the time in the lock back to yesterday, does it refuse to recognize the user?)
• Did the second lock also have this problem after the 1,599th log entry... or immediately after midnight?

There's a whole host of possible bugs -- but, based on weird software errors I've had to diagnose in the past, one of my first checks would be to see whether the 1,600th log entry overwrites the current time in memory. (Do you have other locks with a similar number of log entries? That's not really that high for a high-traffic door, so my first guess may be way off here.)

Anyhow, without actually being able to properly examine the software in the lock, I'm just guessing. Fingers crossed that this is the only time you see this.

Yes, plenty out there with far more entries, so I know that isn't the issue. I think it is the clock chip. No changes in programming were done to trigger any change. However at midnight one of the user codes is locked out until the first manager comes in the following day and enters a valid manager code.

[HeadHunterCEO]

Ask for Gregg in tech Support. I have half a dozen of these systems out there and have not seen this

* none of these within Apple

[Squelchtone]

Normally I see the outdoor keypads which they claim are fully potted get full of ice and water and stop working, but the prox still works. This issue is new to me.

When you run the DL-Windows utility, is there a place that it gets system time from, such as the current computer you are running it on, or perhaps pointed to a Network Time server? When you poll logs from other locks/readers is their time the year 2000 as well, or was it just that one lock?

Check the settings for the gateway that controls the suspect lock(s).

Good Luck,
Squelchtone

[HeadHunterCEO]

not a networx lock
DL-Windows gets time from the cpu at the time of install which is passed to the lock on the first initialization . 2800 is interrogated by the AL handheld or a laptop after you put it in link mode. I wonder if you can flash the lock from the software.

[C locked]

Read the manual
Page 10
Do not press any buttons while batteries removed
Or the lock will lose (read reset) its time

http://data.manualslib.com/pdf2/45/4496/449598-alarm_lock/trilogy_dl2800_programming_instructions.pdf?a2ccb6bf53d0d2b49b1bfcc8f6018c0f


Best of lock

[C locked]

I mean id think someones been tampering
But "midnight" is very specific so it could be a fault