Kitview Connect WiFi Camera Setup

Introduction

In order to setup a WiFi Camera with Kitview Connect, here are the main steps :

1. Install the camera software on the computer ;
2. Install KitDesktop on the computer ;
3. Configure Kitview Connect (Accounts).

1. Camera Software installation

Pre-requisites : 

• Physical access to the camera ;
• Access to the computer inside the network with administrator rights ;
• SSID and password of the WiFi network.

That section is specific to each camera / company, so please refer to the dedicated documentation.

When setting up the target folder, use a path like : C:\Orqual\Wifi\<camera_name>

Each camera must have a specific folder.

2. KitDesktop installation

Pre-requisites : 

• Access to the computer inside the network with administrator rights ;
• KitDesktop latest package.
• KitDesktop should be defined into Windows FIREWALL
   

KitDesktop is a software which allows communication in-between Kitview Connect and the computer.

1. Install KitDesktop under C:\Orqual\KitDesktop folder
2. Double click on it : a dedicated icon should be shown on your taskbar
   
3. Right click on the icon > Auto Start
   It must looks like this :
   

Use this for WebApiUrl

PROD - https://accounts-api.orqual.org/api
PREPROD - https://accounts-api.preprod.orqual.org/api
STAGING - https://accounts-api.staging.orqual.org/api

1. Right click on the icon > PMS Link
   1. SyncMode : WebApi
   2. WebApiUrl : https://accounts-api.orqual.org/api
   3. WebApiEmail : Your Kitview account’s email
   4. WebApiPassword : Your Kitview account’s password
   5. WebApiPractice : Your Kitview practice’s name
   6. WebApiWorkstation : Select your <First Name LAST NAME> in the list
   7. Click on “Save and Load”

1. Right click on the icon > File check
   1. Setup the camera (to be done for each camera)
      1. Click on the “+” icon
      2. Type : pooling
      3. Name : Camera’s name
      4. Path : Path setup during the Camera Software installation (something like C:\Orqual\Wifi\<camera_name>)
      5. Exclude : .TMP
      6. Camera : Full model name (e.g. CANON EOS 90D)
      7. Wait (ms) : -1
      8. Click on “Apply”
   2. Global setup (common to all camera)
      1. Pooling (ms) : 500
      2. Wait after file (ms) : 0
      3. Kitview Import : checked
      4. Keep other fields empty
   3. Click on “Save and Load”

3. Kitview (Accounts) Configuration

Who :

• Kitview Support

1. Access to the practice’s Account entry https://accounts.orqual.org/fr/practices 
2. Go to “Preferences” 
   1. Open Cameras preferences edition
      1. If there is a preference named “Cameras (Caméras)” click on edit
         
      2. else click on “Add a preference” and search “Camera”
   2. Write your camera’s name > hit the enter key > click on Confirm
      1. In the screenshot below, the “MY NEW CAMERA” has not been validated (user did not hit the “ENTER” key) while “CANON EOS 90D” is correct.
         
      2. The value must be the same as the Camera’s name in KitDesktop Installation step 5.a.v (File Check > Full Model Name)

The camera value will be visible in the Kitview to the users only after a disconnection/reconnection.

Validation

To ensure everything is working :

1. Go to Kitview Connect
   1. Select a patient folder
   2. Click on the Camera icon (top right)
   3. WiFi import > Select your camera in the list > Apply
2. Start your Camera and select “WiFi/Bluetooth connection”
3. Take a picture

After few seconds, the photo should be displayed inside Kitview Connect

Debug

In case the validation is not successful, check the following when taking the picture :

• Is the photo sent into the configured folder during the Camera Software installation ?
  • No : the camera installation failed (wifi issue, configuration error, …)
  • Yes : after few seconds, is it being removed from the folder ?
    • No : check the configuration of the KitDesktop installation steps (Path folder, Kitview Import, Pooling, etc. values could be wrong)
    • Yes : check KitDesktop logs ( C:\Orqual\KitDesktop\<today_date>.log), it could be linked to a connection error with Kitview Connect.