Vendor access
This part is for Aigna staff
Vendors see their own installation and the device reference they need to build it: device types, setup guides and models. Everything else stays with Aigna.
Go to your installationModule
Projects is switched off
Projects, the schedule, planning, the work plan and the Lab. This demo has the Projects module switched off in Organisation settings.
Batch 6 of 9 · Project PRJ-18Simulated live
1 INOGENI U-CAM adapter
0 of 1 unit set up · nothing to reviewchecked just now
Setup is done by Aigna's engineers. Your installs are on the Deploy page.
Once for all 1
Through Device web interfaceSet on each unit by hand Device web interface. Keia Atlas cannot read these back, so a person confirms them.
6 settings to set and 2 to check; 0 left at the manufacturer's default.See every settingThe setup guide
The same on every unit
- REST API bearer token
- Generated, not left blank
- Standby mode
- Disabled
The units
Only what differs per unit. Each unit's build sheet has every setting worked out.Nothing is ready for you here. Keia Atlas keeps checking these units.
| Unit | Provision | Install | Configure | |
|---|---|---|---|---|
| Build sheet | ||||
Setup order
Optional: tick as you go, or let the checks do it1Connect the space's USB camera (and, if separate, its USB audio device) to the two USB 3.0 input ports.0/1
2Connect HDMI OUT to the switcher/scaler input.0/1
3Connect the LAN port to the AV VLAN.0/1
4Power from the included 100-240VAC to 12V/1.2A supply.0/1
5Browse to the device's webpage (self-signed HTTPS certificate, so expect a browser warning) and change the default admin/admin login.0/1
6On the CONFIGURATION tab, set the HDMI resolution, camera source and audio input for the space.0/1
7Check the STATUS tab shows the expected firmware version and that video/audio devices are detected.0/1
Every setting
8 in the setup guide, as patternsValues marked Per unit are patterns here. Each unit's build sheet has them worked out: 15.03 Heron.
Network1
- IP addressingCheck it is DHCP (default), with a reservation on the AV VLAN
Why
Aigna's AV devices sit on a DHCP-reserved address on the AV VLAN rather than a hand-typed static one.
Security2
- Web/API passwordPer unitSet to From the password vault, per siteWorked out on the build sheet
Why
The device ships with username admin and password admin, which must be changed before it goes into service.
- REST API bearer tokenSet to Generated, not left blank
Why
Adds authentication to the REST API rather than leaving it open to anything on the AV VLAN.
Video and audio3
- HDMI output resolutionPer unitSet to The room display/switcher's native input resolutionWorked out on the build sheet
Why
Matches whatever the connected Kramer switcher input expects, up to 4K30.
- Camera sourcePer unitSet to The space's USB camera on USB 3.0 input 1Worked out on the build sheet
Why
Selects which of the two USB inputs the HDMI output is captured from.
- Audio inputPer unitSet to The space's USB camera or a separate USB audio device on input 2Worked out on the build sheet
Why
Lets audio be taken from a separate soundbar/mic rather than forcing the camera's own mic.
Power management1
- Standby modeSet to Disabled
Why
Keeps the bridge live and ready between meetings rather than dropping the HDMI signal to the switcher when USB streaming stops.
Control1
- RS-232 baud rateCheck it is 9600 baud, 8N1, no flow control (fixed default)
Why
Matches whatever room controller, if any, talks to the bridge over its 3-pin terminal block.