Introduction
In order to setup a WiFi Camera with Kitview Connect, here are the main steps :
- Install the camera software on the computer ;
- Install KitDesktop on the computer ;
- 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. |
- Install KitDesktop under C:\Orqual\KitDesktop folder
- Double click on it : a dedicated icon should be shown on your taskbar
- 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
- Right click on the icon > PMS Link
- SyncMode : WebApi
- WebApiUrl : https://accounts-api.orqual.org/api
- WebApiEmail : Your Kitview account’s email
- WebApiPassword : Your Kitview account’s password
- WebApiPractice : Your Kitview practice’s name
- WebApiWorkstation : Select your <First Name LAST NAME> in the list
- Click on “Save and Load”
- Right click on the icon > File check
- Setup the camera (to be done for each camera)
- Click on the “+” icon
- Type : pooling
- Name : Camera’s name
- Path : Path setup during the Camera Software installation (something like C:\Orqual\Wifi\<camera_name>)
- Exclude : .TMP
- Camera : Full model name (e.g. CANON EOS 90D)
- Wait (ms) : -1
- Click on “Apply”
- Global setup (common to all camera)
- Pooling (ms) : 500
- Wait after file (ms) : 0
- Kitview Import : checked
- Keep other fields empty
- Click on “Save and Load”
- Setup the camera (to be done for each camera)
3. Kitview (Accounts) Configuration
Who :
- Kitview Support
- Access to the practice’s Account entry https://accounts.orqual.org/fr/practices
- Go to “Preferences”
- Open Cameras preferences edition
- If there is a preference named “Cameras (Caméras)” click on edit
- else click on “Add a preference” and search “Camera”
- If there is a preference named “Cameras (Caméras)” click on edit
- Write your camera’s name > hit the enter key > click on Confirm
- 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.
- The value must be the same as the Camera’s name in KitDesktop Installation step 5.a.v (File Check > Full Model Name)
- 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.
- Open Cameras preferences edition
| The camera value will be visible in the Kitview to the users only after a disconnection/reconnection. |
Validation
To ensure everything is working :
- Go to Kitview Connect
- Select a patient folder
- Click on the Camera icon (top right)
- WiFi import > Select your camera in the list > Apply
- Start your Camera and select “WiFi/Bluetooth connection”
- 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.
Comments
0 comments
Please sign in to leave a comment.