Jonny review #1

Closed
johannes.strobel wants to merge 146 commits from main into develop

@johannes.strobel : This Review should be the other way round develop -> main, but the main branch is further, so I do it like that.
I will put in my comments, onto the release.

@johannes.strobel : This Review should be the other way round develop -> main, but the main branch is further, so I do it like that. I will put in my comments, onto the release.
johannes.strobel added 107 commits 2025-09-03 12:28:56 +00:00
Reviewed-on: AllSpice-demos/Demos-home#4
B3 block diagram as a placeholder, needs updating for DVT
Proper version of "wrong" board. For testing
Test update 1
More content updates
johannes.strobel reviewed 2025-09-03 14:53:10 +00:00
johannes.strobel left a comment
Author
Owner

WIP review

WIP review
README.md Outdated
@ -0,0 +55,4 @@
<img src="images/Main_Pwr.jpg" width="600">
</p>
To see the location of the Jetson Nano (with the large heatsink), we remove the antenna mount and cooling cover just below the fan. The cover assists with airflow through the device and ensures air is pushed across the heat sink.
Author
Owner

Jetson Xavier NX (16GB)

Jetson Xavier NX (16GB)
Author
Owner

It still reads "Jetson Nano"
The Jetson Nano is a very old module, we havent used that since before the first pearl orbs

It still reads "Jetson Nano" The Jetson Nano is a very old module, we havent used that since before the first pearl orbs
Owner

You're right, looks like the commit didn't take. Should be fixed now

You're right, looks like the commit didn't take. Should be fixed now
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +69,4 @@
To start with, here is a full-system block diagram, color-coded by approximate function:
<p align="center">
<img src="images/BlockDiagramFunction2.jpeg" width="1200">
Author
Owner

can we use a vectorgraphic here ?
SVG or PDF

can we use a vectorgraphic here ? SVG or PDF
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +76,4 @@
One of the most complex systems of the Orb is the power distribution network. Below we describe the main power supplies, EXCLUDING the dedicated ones for the security subsystem which will be covered in its own section.
Since illuminating the eye sufficiently to capture the necessary detail requires a large amount of (pulsed) light and therefore energy, TFH designed their own battery pack to accommodate this requirement.
Author
Owner

Not entirely true, we did design the battery pack for the pearl orb but diamond battery (amber battery) was designed by highpower

Not entirely true, we did design the battery pack for the pearl orb but diamond battery (amber battery) was designed by highpower
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +78,4 @@
Since illuminating the eye sufficiently to capture the necessary detail requires a large amount of (pulsed) light and therefore energy, TFH designed their own battery pack to accommodate this requirement.
The battery is a custom Li-Ion pack consisting of 8x 18650 cells with 3.7V nominal voltage in a 2P4S configuration (14.8V) and a capacity of close to 100Wh. This voltage is transformed into several main rails that power other components:
Author
Owner

Its 3.6V per cell (nominal) which gives 14.4V

Its 3.6V per cell (nominal) which gives 14.4V
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +82,4 @@
(**Note**: It is easier to follow the power tree description by consulting the architecture diagram. We recommend inspecting the diagram in parallel with reading the below descriptions.)
- **+V_BAT** (**VBAT_SW** in the schematic): This rail is somewhat circular. In normal operation, it is generated directly from +VBAT. However, it can ALSO be supplied from the +12V_CAPS (which is generated from +17V_CAPS, which is charged from +V_BAT)
Author
Owner

This is a bit confusing. I would explain by splitting into two subpoints:
When battery is inserted: VBAT_SW is supplied from the battery. It can be disabled for powersaving (hence the suffix SWitched).
When the battery is removed: VBAT_SW is supplied by 12V_CAPS to keep the orb powerd for some time and allow a so called "gracefull shutdown", to avoid any damage to the components or corruped filesystem. (not sure if that should also be added here: “also the input of the 12V_CAPS converter is disconnected from the VBAT_SW net”)

This is a bit confusing. I would explain by splitting into two subpoints: When battery is inserted: VBAT_SW is supplied from the battery. It can be disabled for powersaving (hence the suffix **SW**itched). When the battery is removed: VBAT_SW is supplied by 12V_CAPS to keep the orb powerd for some time and allow a so called "gracefull shutdown", to avoid any damage to the components or corruped filesystem. (not sure if that should also be added here: “also the input of the 12V_CAPS converter is disconnected from the VBAT_SW net”)
Owner

Ah, I wondered if SW stood for software...

Ah, I wondered if SW stood for software...
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +84,4 @@
- **+V_BAT** (**VBAT_SW** in the schematic): This rail is somewhat circular. In normal operation, it is generated directly from +VBAT. However, it can ALSO be supplied from the +12V_CAPS (which is generated from +17V_CAPS, which is charged from +V_BAT)
- **+12V_CAPS**: This rail is created from the +17V_CAPS rail, and is mainly used as a backup to +V_BAT in the case the main battery is removed but shutdown operations are not yet complete. It also supplies the stepper motors, the cooling fan and the liquid lens focusing.
Author
Owner

When battery is inserted: supplied from VBAT_SW
When the battery is removed: Supplyied from Supercapacitors 17V_CAPS, to keep the orb powerd for some time and allow a so called "gracefull shutdown", to avoid any damage to the components or corruped filesystem.

Decide if to put that comment to the VBAT description or here or to both.

When battery is inserted: supplied from VBAT_SW When the battery is removed: Supplyied from Supercapacitors 17V_CAPS, to keep the orb powerd for some time and allow a so called "gracefull shutdown", to avoid any damage to the components or corruped filesystem. Decide if to put that comment to the VBAT description or here or to both.
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +88,4 @@
- **+17V_CAPS**: These supercapacitors provide the instantaneous current required to run all of the IR illumination LEDs. It is derived from +V_BAT.
- **PVCC (31V)**: Derived from +17V_CAPS, this is used to actually run the LEDs. Using 31V supercapacitors would be impractical due to size constraints, so the 17V rail is boosted as needed.
Author
Owner

31.5V if you want to be exact

31.5V if you want to be exact
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +90,4 @@
- **PVCC (31V)**: Derived from +17V_CAPS, this is used to actually run the LEDs. Using 31V supercapacitors would be impractical due to size constraints, so the 17V rail is boosted as needed.
- **5V**: Directly powers the Nvidia Jetson, stepper motor driver, polarizer motor. Switched down to several further rails:
Author
Owner

steppers are supplied by the 12V_CAPS, for the gimbal stepper controller 5V is only used for the controller internally (no need to mention, I would say)
You could mention the (UX + shroud illu) RGB LEDS on the frontunit

steppers are supplied by the 12V_CAPS, for the gimbal stepper controller 5V is only used for the controller internally (no need to mention, I would say) You could mention the (UX + shroud illu) RGB LEDS on the frontunit
Author
Owner

We should also mention that 12V_CAPS is supplied by the VBAT_SW when the battery is inserted and by 17V_CAPS when the battery is removed.
This was mentionend in one of the otter comments, I dont know why this is at the wrong line, though:

When battery is inserted: supplied from VBAT_SW
When the battery is removed: Supplyied from Supercapacitors 17V_CAPS, to keep the orb powerd for some time and allow a so called "gracefull shutdown", to avoid any damage to the components or corruped filesystem.

Decide if to put that comment to the VBAT description or here or to both.

The option to supply it from VBAT_SW as well is, to allow to power it up even when the supercaps are not charged up.

We should also mention that 12V_CAPS is supplied by the VBAT_SW when the battery is inserted and by 17V_CAPS when the battery is removed. This was mentionend in one of the otter comments, I dont know why this is at the wrong line, though: > When battery is inserted: supplied from VBAT_SW > When the battery is removed: Supplyied from Supercapacitors 17V_CAPS, to keep the orb powerd for some time and allow a so called "gracefull shutdown", to avoid any damage to the components or corruped filesystem. > > Decide if to put that comment to the VBAT description or here or to both. The option to supply it from VBAT_SW as well is, to allow to power it up even when the supercaps are not charged up.
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +91,4 @@
- **PVCC (31V)**: Derived from +17V_CAPS, this is used to actually run the LEDs. Using 31V supercapacitors would be impractical due to size constraints, so the 17V rail is boosted as needed.
- **5V**: Directly powers the Nvidia Jetson, stepper motor driver, polarizer motor. Switched down to several further rails:
- **3.3V**: These power WiFi, LTE, SSD, NFC, motor drivers, ALS, temperature sensors, IR & thermal cameras and most glue logic (port expanders, comparators etc)
Author
Owner

not sure if we should mention there are dedicated switching converters for some of the functions.
Also there is basically a missnomer (from legacy): the 3V3_SSD with is used for the SD card now -> not sure if we should adjust or just keep it as is.

Not sure if we should mention that the cameras (except 2D TOF) have there internal LDO, so we dont get shit for supplying the cameras with a switching converter.

not sure if we should mention there are dedicated switching converters for some of the functions. Also there is basically a missnomer (from legacy): the 3V3_SSD with is used for the SD card now -> not sure if we should adjust or just keep it as is. Not sure if we should mention that the cameras (except 2D TOF) have there internal LDO, so we dont get shit for supplying the cameras with a switching converter.
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +92,4 @@
- **5V**: Directly powers the Nvidia Jetson, stepper motor driver, polarizer motor. Switched down to several further rails:
- **3.3V**: These power WiFi, LTE, SSD, NFC, motor drivers, ALS, temperature sensors, IR & thermal cameras and most glue logic (port expanders, comparators etc)
- **1.8V**: TPM module, RGB camera, 2D Time of Flight
Author
Owner

there is no RGB cam, only RGB-IR, which is only taking 3V3 and generating all the voltages it needs on its own
Maybe you can add comunication interfaces going to the jetson, like audio amp, (I2C + triggers of the cameras)

there is no RGB cam, only RGB-IR, which is only taking 3V3 and generating all the voltages it needs on its own Maybe you can add comunication interfaces going to the jetson, like audio amp, (I2C + triggers of the cameras)
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +94,4 @@
- **3.3V**: These power WiFi, LTE, SSD, NFC, motor drivers, ALS, temperature sensors, IR & thermal cameras and most glue logic (port expanders, comparators etc)
- **1.8V**: TPM module, RGB camera, 2D Time of Flight
- **2.8V**: Thermal camera coprocessor
- **3.6V**: 2D Time of Flight
Author
Owner

just for the illumination, so for driving the VECSEL.
There is an 3V3_LDO for the analog supply of the IC

just for the illumination, so for driving the VECSEL. There is an 3V3_LDO for the analog supply of the IC
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +95,4 @@
- **1.8V**: TPM module, RGB camera, 2D Time of Flight
- **2.8V**: Thermal camera coprocessor
- **3.6V**: 2D Time of Flight
- **2.8V** LDO: Stable supply for RGB camera
Author
Owner

nope, this is removed, no RGB camera anymore

nope, this is removed, no RGB camera anymore
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +99,4 @@
- **5V_RGB**: This powers the single RBG LED on the Operator Interface board
- **3.3V_UC**: Powers the main microcontroller separately for power gating purposes
Author
Owner

maybe mention: this supply is allways on as long as the main battery is inserted

maybe mention: this supply is allways on as long as the main battery is inserted
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +110,4 @@
The main goal of the tamper detection is to quickly erase the security keys in the event of an intrusion, even if the main battery and the backup battery are removed.
This system consists of the following parts:
- **4.7V rail**: This rail powers the security subsystem and is derived from +VBAT. This rail also charges the single cell Li-Poly security backup battery. Note that it is NOT derived from VBAT_SW, in order to avoid charging the backup battery from the main supercapacitors in the event of a disconnected main battery.
Author
Owner

Note that it is NOT derived from VBAT_SW, in order to avoid charging the backup battery from the main supercapacitors in the event of a disconnected main battery.
the reason is different:
Note that it is NOT derived from VBAT_SW but VBAT, so that the backup battery gets recharged always when the main battery is inserted, even when the orb is not powered.

Background -> if the backupbattery would be discharged or removed the keys would be erased and the orb would be inoperatable

> Note that it is NOT derived from VBAT_SW, in order to avoid charging the backup battery from the main supercapacitors in the event of a disconnected main battery. the reason is different: Note that it is NOT derived from VBAT_SW but VBAT, so that the backup battery gets recharged always when the main battery is inserted, even when the orb is not powered. Background -> if the backupbattery would be discharged or removed the keys would be erased and the orb would be inoperatable
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +113,4 @@
- **4.7V rail**: This rail powers the security subsystem and is derived from +VBAT. This rail also charges the single cell Li-Poly security backup battery. Note that it is NOT derived from VBAT_SW, in order to avoid charging the backup battery from the main supercapacitors in the event of a disconnected main battery.
- **Small supercapacitor** (missing from block diagram): This acts as a temporary UPS in case even the backup battery gets removed, and provides enough runtime to delete the security keys.
Author
Owner

told Erkang to add it into the block diagramm

told Erkang to add it into the block diagramm
Owner

I did it myself, no worries

I did it myself, no worries
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +128,4 @@
Since the optical system will be discussed in detail in the next section, we will mention here only the non-imaging components connected to the Jetson.
- **WiFi**: Orbs include PCEe-based WiFi cards in a M.2 slot. The current Diamond Orb uses a standard AX200 card.
Author
Owner

AX210

AX210
Owner

Hmm, the schematic says AX200 everywhere, even in v 4.7...

Hmm, the schematic says AX200 everywhere, even in v 4.7...
Author
Owner

so than thats another thing we need to adjust, good catch

so than thats another thing we need to adjust, good catch
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +144,4 @@
- **Main MCU**: This MCU is responsible for controlling most Orb hardware aside from the imaging system. It communicates with the Jetson through a single-wire custom CAN implementation, and is discussed in the next section
- **MIPI**: This is a standard interface for most image sensors, and is used as such in the Orb for communicating with the main face detection IR-RGB camera and the iris scanning camera.
Author
Owner

2D TOF is also MIPI-CSI

2D TOF is also MIPI-CSI
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +148,4 @@
- **I2C**: Another standard interface, this is used by the Jetson to configure the imagers as well as the 2D Time of Flight sensor.
- **USB**: Several peripherals on the Orb are USB-based. These include the thermal imager, the BLE component of the WiFi card and an internal unused USB port for debugging.
Author
Owner

also connecton to the Cone / stand -> please clarify the naming of these accesoirs and which of them are actually gona be used.
WiFi card has USB, but USB is only used for the bluetooth on that combined wifi+ble module

also connecton to the Cone / stand -> please clarify the naming of these accesoirs and which of them are actually gona be used. WiFi card has USB, but USB is only used for the bluetooth on that combined wifi+ble module
Owner

Sorry, need more info besides clarifying the BLE and that it also goes to the stand. Did I miss any USB accessories?

Sorry, need more info besides clarifying the BLE and that it also goes to the stand. Did I miss any USB accessories?
Rafael_Send added 1 commit 2025-09-03 19:10:48 +00:00
Rafael_Send added 1 commit 2025-09-03 20:13:47 +00:00
Rafael_Send added 1 commit 2025-09-03 20:14:06 +00:00
Rafael_Send added 1 commit 2025-09-03 22:16:02 +00:00
Rafael_Send added 1 commit 2025-09-03 23:12:39 +00:00
Rafael_Send added 1 commit 2025-09-03 23:41:11 +00:00
Rafael_Send added 1 commit 2025-09-03 23:57:40 +00:00
Rafael_Send added 1 commit 2025-09-03 23:57:51 +00:00
Rafael_Send added 1 commit 2025-09-03 23:58:02 +00:00
Rafael_Send added 1 commit 2025-09-03 23:58:18 +00:00
Rafael_Send added 1 commit 2025-09-08 00:45:10 +00:00
Rafael_Send added 1 commit 2025-09-08 03:43:19 +00:00
Rafael_Send added 1 commit 2025-09-08 03:52:10 +00:00
johannes.strobel reviewed 2025-09-08 12:40:41 +00:00
README.md Outdated
@ -0,0 +66,4 @@
One often-asked question when trying to understand a complex hardware system is "How does this even go together?" To help our readers get that question out of the way, this diagram shows the arrangement of the major components by actual PCB or FPC.
<p align="center">
<img src="images/ConnectionDiagram.svg" width="800">
Author
Owner

Reset button is connected to the powerboard not to the mainboard.
SD Interface board is missing as well.
Polarizer wheel stepper is also not mentioned (not sure if we need)

Reset button is connected to the powerboard not to the mainboard. SD Interface board is missing as well. Polarizer wheel stepper is also not mentioned (not sure if we need)
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +133,4 @@
Since the optical system will be discussed in detail in the next section, we will mention here only the non-imaging components connected to the Jetson.
- **WiFi**: Orbs include PCEe-based WiFi cards in a M.2 slot. The current Diamond Orb uses a standard AX210 card.
Author
Owner

WiFi: Orbs include PCEe-based WiFi cards in a M.2 slot.
typo: PCIe

> **WiFi**: Orbs include **PCEe**-based WiFi cards in a M.2 slot. typo: PCIe
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +166,4 @@
- **Sensors**: The Orb contains many internal sensors, which are used for health and status monitoring.
- Temperature sensors in various places throughout the device for overtemperature conditions and adjust cooling.
- Voltage measurement on every rail to ensure the devices power supply is operating correctly. Also used for switching between available power sources
- Hardware version can be read as an analog voltage (industry standard practise)
Author
Owner

Hardware version for Frontunit, powerboard and mainboard is with digital inputs, a for digit binary number on 4 pins of a portexpander.
Only the security MCU has a analog value to detect the versioning.

Hardware version for Frontunit, powerboard and mainboard is with digital inputs, a for digit binary number on 4 pins of a portexpander. Only the security MCU has a analog value to detect the versioning.
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +167,4 @@
- Temperature sensors in various places throughout the device for overtemperature conditions and adjust cooling.
- Voltage measurement on every rail to ensure the devices power supply is operating correctly. Also used for switching between available power sources
- Hardware version can be read as an analog voltage (industry standard practise)
- IMU: The inertial measurement unit is used to detect Orb motion (drops, displacement, jerks), which can be used to inform tampering or theft decisions.
Author
Owner

IMU is only connected to the security MCU.
Just as a note: if you only mentioning the Main MCU peripherals here

IMU is only connected to the security MCU. Just as a note: if you only mentioning the Main MCU peripherals here
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +169,4 @@
- Hardware version can be read as an analog voltage (industry standard practise)
- IMU: The inertial measurement unit is used to detect Orb motion (drops, displacement, jerks), which can be used to inform tampering or theft decisions.
- **Cooling**: The main MCU controls the cooling fan, which mainly cools the Jetson module but also the imaging subassembly via indirect airflow.
Author
Owner

Cooling: The main MCU controls the cooling fan, which mainly cools the Jetson module but also the imaging subassembly via indirect airflow.

The airflow is guided trough the device by air deflectors in a way to have the highest deltaT for all the components. It starts with the lowest temperature rated Supercaps, than cameras and LEDs from the imaging unit followed by the jetson and in the end the highest rated power converters.

> **Cooling**: The main MCU controls the cooling fan, which mainly cools the Jetson module but also the imaging subassembly via indirect airflow. The airflow is guided trough the device by air deflectors in a way to have the highest deltaT for all the components. It starts with the lowest temperature rated Supercaps, than cameras and LEDs from the imaging unit followed by the jetson and in the end the highest rated power converters.
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +174,4 @@
- **Liquid Lens**: Part of the optical assembly includes a liquid lens for focusing. This is controlled from the main MCU.
- **LEDs**: All LEDs on the Orb are driven from the main MCU, though most are located on the Front Unit. Control signals are routed through the Power Board to the Front Unit. There are several sets of LEDs:
- **RGBW**: These are individually addressable (clock, data) and are used for indication of state and user positioning.
Author
Owner

RGBW: These are individually addressable (clock, data) and are used for indication of state and user positioning.

RGB, there is no white in the addressable LEDs
But, there are so called Booster LEDs (white LEDs) that can be dimmed but not indiviually. Purpuse is for illuminating the users face for RGB imaging.

> **RGBW**: These are individually addressable (clock, data) and are used for indication of state and user positioning. RGB, there is no white in the addressable LEDs But, there are so called Booster LEDs (white LEDs) that can be dimmed but not indiviually. Purpuse is for illuminating the users face for RGB imaging.
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +179,4 @@
- **Gimbal**: The eye camera sensor has a very narrow field of vision. Therefore, the Orb includes an X-Y scanning gimbal which allows the device to locate the user's eyes in the larger frame recorded by the RGBIR (face) camera. This gimbal is driven by two stepper motors.
- **Polarizer**: The third stepper motor controls the orientation of the polarizer wheel. This is used for recording IR images in two different light orientations, which helps resolve detail in iris structures.
Author
Owner

Polarizer: The third stepper motor controls the orientation of the polarizer wheel. This is used for recording IR images in two different light orientations, which helps resolve detail in iris structures

Purpose is to identifiy objects that try to manipulate and variate the Iriscode of a user, so it is basically tamper protection.
Buzzword is Birefringence, but not shure if this should be mentioned...
Part of the IR leds also have a polarisation filter on them.
Again, I dont know how deep we should go there.

> **Polarizer**: The third stepper motor controls the orientation of the polarizer wheel. This is used for recording IR images in two different light orientations, which helps resolve detail in iris structures Purpose is to identifiy objects that try to manipulate and variate the Iriscode of a user, so it is basically tamper protection. Buzzword is Birefringence, but not shure if this should be mentioned... Part of the IR leds also have a polarisation filter on them. Again, I dont know how deep we should go there.
Owner

The LEDs on Orb have polarizers over them? Which ones?

The LEDs on Orb have polarizers over them? Which ones?
README.md Outdated
@ -0,0 +189,4 @@
The Orb software runs several asynchronous "agents" that execute tasks more or less in parallel. Thus, in order to take images of the users's eye, the following biometric capture tasks run and deliver results to and from each other:
- Use the RGB/IR "face" camera to track the user's eyes within the frame
Author
Owner
  • Use the RGB/IR "face" camera to track the user's eyes within the frame

We also take a RGB image from the users face, for face recognition on the phone, to make sure the user identifying with this world-id is the same one that registered with the orb.
-> again, might be too detailed

>- Use the RGB/IR "face" camera to track the user's eyes within the frame We also take a RGB image from the users face, for face recognition on the phone, to make sure the user identifying with this world-id is the same one that registered with the orb. -> again, might be too detailed
Owner

Probably too detailed. That should go in (some) description of the PCP, not in EE open sourcing I think.

Probably too detailed. That should go in (some) description of the PCP, not in EE open sourcing I think.
Rafael_Send marked this conversation as resolved
johannes.strobel reviewed 2025-09-08 13:23:53 +00:00
README.md Outdated
@ -0,0 +209,4 @@
To achieve this, the Orb contains a large number of infrared LEDs in two wavelengths (32x 850nm and 40x 940nm), which flood the user's face during the imaging process described above and allow capturing the necessary amount of detail at the required distance.
We also have a number of RGBW LEDs positioned around the main camera that are used as a user interface of sorts, as well as state indication. The white component of the LEDs is further used to illuminate the entire face during the eye tracking stage of the process.
Author
Owner

We also have a number of RGBW LEDs positioned around the main camera that are used as a user interface of sorts, as well as state indication. The white component of the LEDs is further used to illuminate the entire face during the eye tracking stage of the process.

RGB and seperate White LEDs

>We also have a number of RGBW LEDs positioned around the main camera that are used as a user interface of sorts, as well as state indication. The white component of the LEDs is further used to illuminate the entire face during the eye tracking stage of the process. RGB and seperate White LEDs
Owner

Old typo, fixed!

Old typo, fixed!
Rafael_Send marked this conversation as resolved
README.md Outdated
@ -0,0 +214,4 @@
The following image shows the placement of all the LEDs inside the front unit. Please refer to the individual repository for further details.
<p align="center">
<img src="images/Illumination.png" width="600">
Author
Owner

maybe put an image of the frontunit without the face, to be able to see all the LEDs

maybe put an image of the frontunit without the face, to be able to see all the LEDs
Owner

We have it in the individual repository - I think that's good enough!

We have it in the individual repository - I think that's good enough!
Rafael_Send marked this conversation as resolved
Rafael_Send added 1 commit 2025-09-10 01:02:38 +00:00
Add updated security blurb and feedback section
Rafael_Send added 1 commit 2025-09-10 01:19:08 +00:00
Rafael_Send added 1 commit 2025-09-10 01:19:53 +00:00
Rafael_Send added 1 commit 2025-09-10 01:21:30 +00:00
Rafael_Send added 1 commit 2025-09-10 02:18:11 +00:00
Rafael_Send added 1 commit 2025-09-10 21:55:00 +00:00
Rafael_Send added 1 commit 2025-09-10 21:55:46 +00:00
Rafael_Send added 1 commit 2025-09-10 21:55:53 +00:00
Rafael_Send added 1 commit 2025-09-10 21:57:28 +00:00
Rafael_Send added 1 commit 2025-09-10 22:18:23 +00:00
Rafael_Send added 1 commit 2025-09-10 22:19:58 +00:00
Rafael_Send added 1 commit 2025-09-15 21:06:09 +00:00
Rafael_Send added 1 commit 2025-09-15 21:16:32 +00:00
Rafael_Send added 1 commit 2025-09-15 21:41:49 +00:00
Rafael_Send added 1 commit 2025-09-15 22:37:45 +00:00
Rafael_Send added 1 commit 2025-09-17 04:20:37 +00:00
Rafael_Send added 1 commit 2025-09-17 04:20:57 +00:00
Rafael_Send added 1 commit 2025-09-17 04:22:30 +00:00
Rafael_Send added 1 commit 2025-09-17 04:25:19 +00:00
Rafael_Send added 1 commit 2025-09-17 04:26:07 +00:00
Rafael_Send added 1 commit 2025-09-17 04:30:00 +00:00
Rafael_Send added 1 commit 2025-09-17 04:31:23 +00:00
Rafael_Send added 1 commit 2025-09-17 04:39:35 +00:00
Rafael_Send added 1 commit 2025-09-17 04:40:48 +00:00
Rafael_Send added 1 commit 2025-09-17 04:57:07 +00:00
Rafael_Send added 1 commit 2025-09-17 06:05:45 +00:00
Rafael_Send closed this design review 2025-09-18 02:09:34 +00:00

Design review closed

Sign in to join this conversation.
No Reviewers
No Label
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: WorldOrb/.profile#1
No description provided.