Facepass 7 PRO changes its time ramdomly

Products Time Attendance
1

Hello, we have 2 Facepass 7 PRO in a stand alone installation (we do not use Crosscheck software, instead a propietary software), both conected by wifi.

Totally we have 4 Facepass 7 PRO and 1 C2C PRO in the same installation.

The devices are working fine for 1 year, but about 3 weeks ago we are experiencing the following issue.

In one of them, the time changes ramdomly with 1 hour less, and then ramdomly again it changes for the right hour.

This device is configurated as the same than the other Facepass7Pro, it has DST set, no time zone set, no Group set and no schedule set.

Firmware ver:03.76.B6_dark_BT107
Kernel Ver. :g4aaa48c
File system ver. :01.76.02

In other Facepass7PRO device, with the same settings than before, this morning we have been noticed that it has the time 1999-11-30 00:28:46

Firmware ver:03.76.B6_dark_BT107
Kernel Ver. :g4aaa48c
File system ver. :01.76.02

I will appreciate any helping tips.

Thank you in advance.

2

Hello,

I see that the topic has been posted for several days and there is no response.

This exact same thing is happening to me with another Facepass7PRO terminal.

In case it helps, it always happens at the same time (between 2 and 3 p.m.), but it doesn’t happen every day.

I have tried disabling WAN mode in case it was taking the time from a time server.

It’s strange that it hasn’t happened to anyone else.

Where can I download updated firmware?

Any suggestions?

Thank you so much.

3

Hi @ingeniatec,

Give it a try to disable the DST function if it’s used in the devices.

4

Hello, thank you for your response.

DST is a valuable feature that we can not sotop of use.

Finally we have changed the NTP server in all of our terminals since 2 weeks ago, and for the moment we have received any time issue.

So I guess that the problem was realated with the NTP server.

Best regards.

5

Hello, Ingeniatec

When using the device with your own proprietary software, will you sync the time with the device? If you do, you don’t need to set DST on the device. If it’s related to NTP settings, you can try other server and see if it can solve the problem.

Have you tried factory resetting the device and see if it works? If the issue still not solved, please reach us at support@anviz.com. We will check if there’s any proper firmware you can upgrade to.

Best Regards,
Zac

6

Hello,

Thanks for your answer.

We do not sync the time by our software because we did not find that option in the API documentation.

If you have updated documentation of the API please let me know.

Anyway it seems all work fine since we moved to another NTP server.

Best regards.

7

Hello,

Good to hear that you sort of fix the problem. If the issue emerge again, please feel free to contact us at support@anviz.com/

8

Hi,

We experienced exactly the same issue, multiple times, over 2 of our 4 FaceDeep3 units. Our supplier advised us to install it with a specific ntp server. We applied, we found it not to work. We changed setting on each to manual time, not ntp. It still reset to 30 November 1999 00:30. After some head-scratching, we found that the ip address we were given for NTP was in China (for no good reason) and our firewall blocks all connections to certain geopolitical locations. So, we picked an IP address in the address pool of 0.pool.uk.ntp.org and applied a different one to each of the 4 Facedeep 3 we have. Since then we have had one of these devices demonstrate the fault, with a working NTP server (unless it has gone offline after only 1 week of us using it, not checked). Regardless of ntp address or if it is set top manual time, it has happened more than once (maybe twice, maybe thrice) between 17:00 and 23:00 on Thursday evenings, but this may be a coincidence.

Takeaway: did it on manual time, did it on ntp where the server couldn’t be reached, did it on ntp it can access, more than one has done it, it did it at a certain time of the week, it has been doing it repeatedly, they’ve been in production for about a month. I’m the onsite IT technician and I’ve been working on this with the supplier and our HR dept for a month. A real puzzler. And, a little annoying that you can’t use an FQDN to connect to NTP, only an IPv4 address.

9

We’ve got 30+ FaceDeep 3 units here, spread across a metropolitan area cable network and several buildings (firmware version 03.74.CC-M-ARF-MI). We tried manual date setting, NTP both from internet/nist pool servers and onpremise stratum 3/4 ntp servers with the same behaviour. No DST needed. No crosschex version being used. No pattern noticeable for the random time change. We eventually cronned a reboot command, not knowing for sure it that helps, since problem eventually persists. Any firmware upgrade or tip?