1. Home
  2. Knowledge Base
  3. Help Guides
  4. Health Screening & Temperature Scanning Guides
  5. Configuring Temperature Sensor and Screening Settings
  1. Home
  2. Knowledge Base
  3. Hardware
  4. Temperature Scanner
  5. Configuring Temperature Sensor and Screening Settings

Configuring Temperature Sensor and Screening Settings

Overview

This guide describes the process of configuration for a temperature sensor to be used with EIOBoard Kiosk or Touchless Self Check-In.

 

The sensor can be connected via wifi connection or ethernet cable. A power cord and ethernet adapter are provided with the sensor. The temperature sensor is equipped with onboard wifi. Only the power cord is required to configure wireless access. If an ethernet connection is desired, the included ethernet adapter will also be required.

Sensor Setup

When the temperature scanning device is initially powered on the main screen will be displayed. The device employs infrared technology to read a person’s temperature. Temperature scanning is motion activated when a user aligns their forehead with the red dot shown below. During the temperature scan, users should keep as much of their face as possible inside the oval.

To begin the configuration, select the home button to navigate to the main menu. The newer devices hide the Home button on the right side. It will not appear as shown above. With those devices, you need to edge swipe left to see the Settings icon. The menu options will be the same, yet appear slightly different.

First go to System Settings and make sure that Temperature measurement and Stranger temperature measurement are set to Yes. If Mask Detection is Yes, it won’t take temperature unless it detects the person wearing a mask.

 

Establish the Internet Connection

In the Server tab, set Response Time to 3 seconds. If you don’t see Response Time, but instead see “Server Req”, click it and select Yes. Then go back to the Comm tab and make sure Mode is set to Internet, then Esc and reload settings. You may have to do this after setting the server IP.

Temp Scanner: All settings needed

    • Coms
      • Server
        • Server Required: Yes
        • User domainNm: No
        • Server IP: 192.168.0.1
        • SerPortNo: 8041
      • Ethernet
        • DHCP: No
        • IP Address: 192.168.0.2
    • System
      • Play Name Voice: Off
      • Multiple Faces: Can be either
        • No: Means they have to completely move their face out of the outline then back in to read in. No prevents it from constantly reading while their face is in, but might want to switch to Yes if having trouble scanning
        • Yes: Will always read the temperature if a face is detected on the screen.
      • Result Time: 3 sec
        • Can turn up if reading Temperature too often
      • Bio-assay: No
        • The Temperature Scanner will attempt to determine if it’s a living person before scanning. Can turn on but may have trouble scanning afterward
      • Stranger Temperature: Yes
      • Temperature Adjust: 00.0
        • Whether the temperature is adjusted by the specified number of degrees after reading. Useful if taking the temperature outside/in winter and need to adjust upwards.
      • Temperature calibration Positive: Positive
        • Whether the temperature adjustment value is added or subtracted from the reading
      • Fahrenheit: Yes
      • Temperature Voice: Off

There are three different configurations for providing a connection between the Temperature Sensor and Kiosk/Hardware Agent system.

  1. Isolated LAN Connection – the best practice configuration – the square, wire harnessed, RJ45 connector from the Temperature Sensor is connected to an ethernet port on the system where the Kiosk or Hardware Agent is installed via an ethernet cable
    1. The Enabled setting under Comm>Wifi must be set to No
    2. The Temperature Sensor may be connected to the host device’s built in ethernet port or to a usb to ethernet adapter
    3. If the host system will be connected to the network via a wired connection, an ethernet to usb connector must be used to provide a second wired network adapter
    4. If the host system will be connected to the network by a wireless connection no usb to ethernet adapter is necessary
  2. Wired LAN – the temperature sensor is connected by a wired connection to the same network and subnet as the Kiosk/HardwareAgent system using the round wire harnessed, RJ45 connector
    1. The Enabled setting under Comm>Wifi must be set to No
    2. A static ip address for the host system is required
    3. A consistent network connection with no intermittent issues of packet loss must be present for reliable performance
    4. DHCP may be used for the ip configuration on the temperature sensor but a static ip configuration is far more stable
  3. Wireless LAN – the temperature sensor is connected wirelessly to the same network and subnet as the Kiosk/HardwareAgent system
    1. The Enabled setting under Comm>Ethernet must be set to No
    2. A static ip address for the host system is required
    3. A consistent network connection with a strong signal and no intermittent issues of packet loss must be present for reliable performance
    4. DHCP may be used for the ip configuration on the temperature sensor but a static ip configuration is far more stable

It is nearly always preferable to use the 1st option. In the majority of use cases there is no benefit in connecting the temperature sensor to a network. Connecting the sensor directly to the Kiosk is more stable and requires no reserved ip address on the network for either the sensor or the host system. In any of the above configurations the server setting on the temperature sensor must be set to the ip address of a network adapter on the Kiosk/Hardware Agent system and the port setting must be set to 8041. These settings are found under Comms>Server in the temperature sensor settings. An example is shown below [Note: the Server setting IP address is simplified without additional 0s unlike the Ethenet or Wifi settings]

 

 

Isolated LAN Connection

To take advantage of this configuration, the host system ethernet adapter to be used, whether the usb or the built in, needs to be configured with specific settings for a static connection. To do this go to the Network and Sharing Center.

Check the local network addressing scheme. Isolating the IP addresses to and from the temperature sensor means using addresses outside the classful network, or the address range of the interface connected to the default gateway. If the intranet (local network) uses class A addressing scheme, then use a class C IP address.  If the intranet uses class A and C, then use a class B.

Example:

Server IP: 192.168.0.1

Kiosk IP Address: 192.168.0.2 (Outbound traffic hits the intranet and the internet.)

Then, you should use:

Kiosk Adapter 2 IP — 10.1.1.2 (Bound for the temp scanner)

Temp Scanner IP — 10.1.1.1 (Bound for the kiosk)

 

Open the Control Panel>Network And Internet>Network and Sharing Center. Then click Change adapter settings.

Or you can go to “Run”-> “ncpa.cpl”

Right click on the desired ethernet adapter and choose properties

 

Select Internet Protocol Version 4 (TCP/IPv4). Then click Properties. Set the ip address settings exactly as shown below. [Note: the IP addresses with 3 entries in each section where 0 is set to 000 must be set this way. All IP addresses should appear exactly as shown]

 

Configure the temperature sensor with the following settings under

Comm>Ethernet

Enabled = Yes

DHCP = No

IP Address = 192.168.000.002

Netmask = 255.255.255.000

Gateway =

DNS Server =

Comm>Server

Server = 192.168.0.001

Port= 8041

Comm>Wifi

Enabled = No

At this point, the temperature sensor is ready for use with the kiosk or hardware agent.

 

Networked Configurations – Wired or Wireless

Connect the device to the same network as the IP address set in the Server setting.  If an ethernet connection is preferred, Wifi must be set to disabled or vice versa. Other options should be set to the defaults. Both options are illustrated in the following screenshots. [Note the ip addresses have 3 entries in each section and 0 is set to 000] DHCP may be enabled in which case there is no need to set an IP address.

 

 

Units of Temperature measurement can be set to Celsius or Fahrenheit. To choose/change a unit of temperature navigate to System from Menu by tapping the System icon. Then, under General set the Temperature standard to the preferred unit of measurement.

 

At this point, the temperature sensor is ready for use with the kiosk or hardware agent.

 

Question Profile Configuration

First, in the web interface configure a question profile. Follow along with this video to learn how

Setting Up Temperature Screening Question Profile

 

Configure Screening Settings

After the desired profile and temperature question these settings must be configured in the Kiosk Administration Panel. In the Kiosk, select staff login and enter the admin password. The default is 7282623. If the Kiosk admin password has been changed contact support. In the admin panel go to Visitor Management and select the Screening Settings tab. Select the Question profile you created in the web application and then set your screening settings as you desire for that profile.

Settings Are

  • Use Celsius – use Celsius instead of Farenheit
  • Min Temp – minimum temperature a person must read to pass screening
  • Max Temp – maximum temperature a person may read without failing screening
  • Screening Alert Email – email to which notifications of failed screenings will be sent
  • Guest/Staff Passed Status – status a guest or staff user will be entered into when a screening is passed
  • Guest/Staff Failed Status – status a guest or staff user will be entered into when a screening is passed
    • More on creating statuses can be found here
      https://eioboard.com/Helpful-Guides-and-Pages.aspx

 

Once this is completed, click “Save” to keep your changes. If configuration is being done for temperature scanning using the Kiosk, configuration is complete at this point. If setting up Touchless Self Check In, proceed to the next section.

Hardware Agent Configuration

For use with touchless screening, a device running the Savance Hardware Agent must be installed to a device on the local network in order to relay data from the temperature sensor to EIOBoard.  To ready the Organization Account in EIOBoard for the connection, a hardware integration must be created for the Organization through the EIOBoard web application.  In the administration panel, select Hardware Integration and New Integration.

Select the appropriate device and name the integration.

Ensure the port is correct. If the Temperature Sensor will be used with only a QR Code for Touchless, configure Port Number 8041. If it will be used with both Touchless and the Kiosk, configure Port Number 8042. Then click Save Settings.

Next, install the Savance Hardware Agent on the device assigned the IP Address input in the Temperature Scanner’s Comm settings. To run it, right click and select Run As Administrator.  You can set the Desktop Icon to run it as an Administrator automatically through: Right Click-> Properties-> Compatibility-> Change Settings for All users-> Run as Admin First update the login with the EIOBoard administrator’s username, password, and the URL of the EIOBoard cloud or on-premise API Administration.  In this example we are using the EIOBoard cloud server.

Once updated, select the hardware integration from the dropdown, click start.  Once connection is established, setup is complete.

Setting up Forwarding from Kiosk to Hardware Agent

When using the temperature scanner for both the Kiosk and Self Check In, you can use one temperature scanner for both. To do this some extra configuration is needed.

  1. Have the temperature scanner set to send data to port 8041.
  2. Configure the Kiosk Screening settings to use port 8041.
  3. In screening settings for Forwarding address, use “http://localhost:8042/TempData
    1. If the Hardware Agent is running on a different machine than the kiosk, use that machine’s IP instead of localhost.
  4. Set up the Hardware Integration for the temperature sensor to use Port 8042.
  5. Run the Hardware Agent as Administrator

 

The way this works is: the temperature sensor will send data to the Kiosk. The Kiosk will check to see if it is currently on a Question that requires temperature. If so, it will consume the event. Otherwise it will forward the data to the forwarding address where the Hardware Agent will receive it and send a push notification to any waiting Self Check Ins.

Troubleshooting

Here are some steps to try when troubleshooting events from the temp scanner and the hardware agent:

    1. If you are able to ping the temperature scanner but it is not sending data to the Kiosk, ensure that under Comm>Server the Server address does not contain extra 0s. For example, if the Kiosk ip address the temp scanner should send data to is 192.168.0.2 the server address should read exactly that. It should not read 192.168.000.002 or anything like that.
    2. Counterintuitive to #2, settings under Wifi or Ethernet should have the extra 0s. If you are setting up the temperature sensor with a static ip under Ethernet of 192.168.0.3 it should read 192.168.000.003
    3. Double check settings in the Temperature Scanner for Comms. Compare to the pictures above.
      1. In the Comm tab, make sure Mode is set to Internet
      2. In the Server tab, make sure Response Time is 3
        1. If you don’t see Response Time and instead see Server Req, make sure that is set to Yes
      3. Make sure the IP is the address of the kiosk or Hardware Agent that will be receiving the events.
      4. Make sure only WiFi or Ethernet is enabled, not both.
      5. In System Settings, make sure Stranger Temperature is enabled.
    4. Make sure the Hardware Agent is running as Administrator. You can set the Desktop Icon to run it as an Administrator through: Right Click-> Properties-> Compatibility-> Change Settings for All users-> Run as Admin
    5. Make sure the Ports are correct in the Temperature Scanner, Screening Settings, and/or the Hardware Agent
    6. You can check to make sure the Kiosk or Hardware Agent are listening for Events by going to localhost:8041. You should get a Method not allowed page. This means the service is up, you would get a 404 otherwise.
    7. Make sure the ports you’re using are open in the Firewall.
    8. For the Hardware Agent, make sure there is an API Users with the name “HardwareAgent” and “MannedVMSuite”, case sensitive, specific to that Organization (not for All Organizations).
    9. Check the HardwareAgentAdmin.exe.config file and verify that APIURURoot, ApiPublicID, and ApiSecretKey are all correct.
    10. Check that the SelfCheckIn index.html references the root env.js file.
  • error – Invalid dev_id: 
    1. If you see this error, you need to set the Serial Number. It’s probably blank at this point.

 

Using Wireshark to Troubleshoot

  1. Download and install Wireshark on the machine that will be used as the server for the temperature scanner.
  2. Enter a capture filter that includes the IP of your temperature scanner.
    1. Ip.addr == [TempIP]
    2. OR just select the Ethernet Connection the Temperature Scanner is using if hardwired.
  3. If the Temperature scanner is setup according to the instructions in this document, communication will occur about every 3 seconds.
  4. Errors
    1. Black: Blocked by firewall
      • Make sure port in Server tab 8041
      • Check TCP rules are in Firewall to allow TCP port 8041
      • Add Rule:
        • Run ‘Windows Defender Firewall With Advanced Security’
        • Make sure there is a rule to allow local ports 8041,8042 on TCP
      • TCP
    2. Red: Can’t Translate
      • Make sure extra zeroes not in Server address

 

Temperature Data Never Shows on the Kiosk: Invalid Server Name

When the temperature scanner has the wrong server address. The temperature scanner will make a DNS query to resolve the type A record. Using WireShark, we see the temperature scanner queried DNS for a type A record for ” 192.168.0.1″ similar to the NTP Server above it.

We can resolve this issue by correcting the server address under Comm>Server

 

 

Was this article helpful?

Related Articles