Verifying the time on your biometric device before integration

Before your biometric device is connected to OrangeHRM through the CAMS integration, its clock needs to keep the correct time on its own. This guide takes you through three short tests: the first records the time on the device exactly as you find it, the second confirms it holds that time after being switched off and on again, and the third confirms it holds that time with the internet disconnected. Together they take about half an hour per device, most of it waiting.

If all three tests show the correct time, the device clock is not affected by a power outage or an internet outage, and the device is safe to integrate.

Before you start

• You need physical access to the device and the admin PIN or password for its menu. Without it, the menu will not open.
• Navigation: press M/OK to open the Main Menu and to select an item, the arrow keys to move, and ESC to go back a level.
• Have a reliable time reference to compare against. A mobile phone set to automatic network time works well.
• Photograph each screen before and after you change it. If something does not work afterwards, these photos let our team pinpoint the cause quickly.
• Run the three tests in order, one device at a time, and keep the test log at the end of this guide to hand.

Test 1 — Check the clock as you find it

Change nothing on the device for this test. It records the time the device is showing right now, which gives us a starting point to compare the other two tests against.

1. Look at the clock on the start screen and at your phone at the same moment.
2. Record both times in the test log against Test 1, together with the difference in minutes and whether the device is ahead of or behind your phone.
3. Photograph the start screen showing the device clock.

Test 2 — Check the clock after a power restart, disconnected from CAMS

While the device is connected to the CAMS server, it takes its time from CAMS, so its own clock is never really tested. This test removes that connection first, then switches the device off and on again to confirm that it comes back with the correct time by itself.

Step 1 — Check whether the device is connected to CAMS

1. From the start screen, press M/OK to open the Main Menu.
2. Move to COMM. and press M/OK.
3. Move down to Cloud Server Setting and press M/OK.
4. Photograph the screen before you change anything.

Look for the server address entered during the device compatibility check, for example, 2xapi.camsbiometrics.com. If it is there, the device is still connected to the CAMS server — go to step 2. If the field is already empty, the device is not connected, and you can go straight to step 3.

Step 2 — Disconnect the device from the CAMS server

1. Write down the exact value of Domain Name (DomainNm) before you change anything. You need it again in step 5.
2. Move to that field and press M/OK. The field turns green while you edit it.
3. Clear the value and press M/OK to save.
4. Press ESC until you are back at the start screen.

Step 3 — Switch the device off and on again

1. Switch the device off and unplug it from the power supply.
2. Wait five minutes.
3. Plug it back in and switch it on.

Step 4 — Check the clock again

1. Once the device is back at the start screen, compare its clock with your phone at the same moment.
2. Record both times in the test log against Test 2, together with the difference in minutes and whether the device is ahead of or behind your phone.
3. Photograph the start screen showing the device clock.

Test 3 — Check the clock with the internet disconnected

Leave the device switched on, with the server address still cleared from the previous test. This test takes the device off the network altogether, which shows whether it can hold the correct time without depending on any server.

1. Remove the network cable from the device, or switch Wi-Fi off.
2. Leave the device switched on and off the network for five minutes.
3. At the end of the five minutes, compare the clock on the start screen with your phone at the same moment.
4. Record both times in the test log against Test 3, together with the difference in minutes and whether the device is ahead of or behind your phone.
5. Photograph the start screen showing the device clock.

Step 5 — After the tests — restore the settings

Do this once all three tests are recorded, so the device goes back to normal operation.

1. Reconnect the network cable, or switch Wi-Fi back on.
2. Go back to Main Menu > COMM. > Cloud Server Setting.
3. Re-enter the Domain Name value you noted in Test 2, step 2.
4. Press M/OK to save, then ESC until you are back at the start screen. The device reconnects on its own.

Leave the field cleared only if your OrangeHRM Implementation Consultant has asked you to.

What your results mean

All three tests match your phone. The clock keeps the correct time on its own, through a power cycle and with no network connection, so it is not affected by a power outage or an internet outage. The device is ready for the integration — contact your OrangeHRM Implementation Consultant, who will take you through the next steps.

Test 1 matches, but Test 2 does not. The device does not hold the correct time through a power cycle, so a power outage would leave its clock wrong. Send us all three results before going any further.

Tests 1 and 2 match, but Test 3 does not. The device is relying on a server to stay right, so an internet outage would leave its clock wrong. Send us all three results before going any further.

Test 1 does not match. The clock is already wrong before anything is changed. Send us all three results, and we will look at the device settings with you.

You are done when

• All three tests are recorded in the log, with times, differences, and photographs.
• The device is back on the network, and the Domain Name value is as you found it.
• The log has a Test 1, Test 2, and Test 3 row for every device you tested.

What To Send Us

Email the following to your OrangeHRM Implementation Consultant, and we will take you through the next steps:

• The completed test log, with all three tests filled in for each device.
• The device model, serial number, and firmware version for every device you tested.
• Your photographs of the screens, and anything unusual you noticed — an error message, or the device restarting on its own.

Test log

Fill in three rows for each device, one per test. The first three rows are an example — you do not need to complete them.