The Xovis multisensor combines 2–350 sensors into a single logical unit with seamless cross-sensor tracking. This guide covers the full setup process using Firmware 5.9 (current). Source: Xovis Knowledge Base.
All sensors must be reachable on the network and visible to each other
All sensors must run the same firmware version
If a SPIDER is used, it must have the same firmware as the sensors
Privacy level must be set to 0 during stitching setup (can be raised afterwards)
All sensors must be recalibrated
All sensors must be time-synced to the same NTP server
Minimum 30cm overlap between adjacent sensors
PC-Series parent | Up to 9 sensors · Uses legacy Multisensor algorithm · Cannot include PF sensors |
PF-Series parent | Up to 15 sensors · Uses new Multisensor Tracker algorithm · Can include PC-Series sensors |
SPIDER | Up to 350 sensors · Supports both PC and PF sensors mixed |
Floor Stitching | Original algorithm. Points placed on the floor only. Minimum 3 stitching points. Any device can be parent. |
Space Stitching | New in FW5.9. Points can be placed anywhere — floor, walls, objects. Minimum 5 stitching points. PF-Series must be parent (PC-Series can be children). |
When upgrading an existing multisensor to FW5.9, it keeps the old Floor Stitching algorithm. Change to Space Stitching in the multisensor UI (☰ menu → Mode).
Multisensor Legacy | Pre-5.9 algorithm. Used by default when upgrading existing multisensors. |
Multisensor Tracker | New in FW5.9. Better tracking accuracy when people transition between sensors. PC+PF mixing requires this algorithm. |
People attributes (gender, age, etc.) from PC-Series sensors are not supported with the Multisensor Tracker algorithm. If people attributes are required on PC sensors, use Multisensor Legacy.
Go to Settings → Multisensor → +
Add each sensor via IP address, MAC address, or launch the Sensor Explorer to scan the network
Click two neighboring sensors → click Stitch
Floor Stitching: Place at least 3 reference points on the floor in a triangle shape with maximum spread. Points must be on the floor only.
Space Stitching: Place at least 5 matching points anywhere in both sensor views (same physical point visible in both images)
Click Save → review the stitching quality → stitch all neighboring sensors
Click Apply computation
Format: PNG only
Size limit: <1MP and <1MB (single sensor parent) / <100MP and <100MB (SPIDER parent)
Best workflow: export .dwg → PDF → convert to high-quality PNG via pdf2png.com
Set the coordinate zero (0,0) point — defaults to top-left
Set a reference distance using the longest available distance for best accuracy
Check all sensors show green in the multisensor status after setup
Verify tracking quality 2–3 months after installation
If a single sensor's password is changed, you must manually update it in the multisensor settings (Settings → Multisensor → three-dot menu for that sensor → update password)
Exclusion masks drawn on individual sensors have no effect inside a multisensor — draw exclusion masks at the multisensor level
Double bubbles | Bad stitching. Restitch the problem sensors with reference points in a large triangle. Check single-sensor mounting height, floor mask, and recalibration first. |
Hole in tracking area | Obstacle blocking view, or gap in coverage. Add a Path Stitcher zone to bridge the gap. |
Jumping bubbles | Time sync issue. Check all sensors use the same NTP server and can reach it. |
Multisensor won't create | Check that privacy level is 0, all sensors have the same firmware, and all sensors can reach each other on the network. |
Licences are applied to individual sensors, not to the multisensor. For a people attribute to work across the whole multisensor, every child sensor must have a valid licence. Check licensing status in the Multisensor settings.