Record Raven PS3 Eye driver bring-up

This commit is contained in:
Meta Vens 2026-05-21 23:50:18 +01:00
commit 03cd8e4b1f
3 changed files with 42 additions and 5 deletions

View file

@ -425,3 +425,35 @@ Conclusion: the split-host local set is viable when the Focusrite is not on the
Leap's USB neighborhood. Full-height Leap stereo is still a little below the
old ~110.8 fps best result, but the catastrophic ~81 fps band was caused by the
local USB layout, not by needing every camera off the machine.
## 2026-05-21: Raven PS3 Eye Driver Bring-Up
Raven initially enumerated the PS3 Eye composite and media interfaces, but the
raw `VID_1415&PID_2000&MI_00` camera interface had no driver binding and showed
`Error`.
The working Mimir host binding was exported and installed on Raven:
- provider: `libwdi`;
- service: `WinUSB`;
- local source INF: `oem26.inf`;
- Raven published INF: `oem34.inf`;
- device interface GUID from the INF: `{6ACBF2FC-1246-418C-A63D-0FE38B45129B}`.
The libwdi self-signed catalog certificate had to be copied to Raven and added
to both `Root` and `TrustedPublisher` before `pnputil /add-driver ... /install`
would accept the package.
After binding, Raven's raw Eye interface reported `OK` and the copied
`ps3eye_dual_cadence.exe` could open the camera. Cadence is not yet viable:
| Raven PS3 Eye Mode | Delivered FPS | Notes |
| --- | ---: | --- |
| 320x240@187 | 132.24 | first run, max gap 202.841 ms |
| 320x240@187 | 78.93 | second run, max gap 283.247 ms |
| 640x480@60 | 6.32 | max gap 2998.965 ms |
Conclusion: Raven's PS3 Eye driver binding is fixed enough to open the device,
but the current Raven USB path/device state is not delivering usable cadence.
Next Raven work is port/controller isolation and a clean single-process cadence
run before treating the Eye as a usable remote timing witness.

View file

@ -18,3 +18,4 @@
{"ts":"2026-05-22T01:10:00+00:00","type":"verification","status":"partial","note":"Port isolation follow-up put Leap alone on the blue rear USB3 group/root_hub30#5 port 3, Kiyos together on root_hub30#7&18eea21b, and Eyes on remaining front/back USB-A ports. Only one PS3 Eye enumerated. Visible simultaneous pull with PS3 Eye at 320x240@187 delivered Leap stereo 80.99 fps, Kiyo Pro 24.93 fps, Kiyo 30.37 fps, and PS3 Eye 185.85 fps. Leap did not recover to its solo ~110 fps cadence despite root-hub isolation, so the bottleneck is not only same-row/same-root-hub contention; investigate broader xHCI scheduling, CPU/interrupt pressure, or KS/usbvideo behavior under multi-device load."}
{"ts":"2026-05-22T01:30:00+00:00","type":"verification","status":"partial","note":"After splitting cameras across Mimir and Raven, the local Mimir host enumerated LeapUVC, regular Kiyo, and one PS3 Eye. Local simultaneous pull with PS3 Eye 320x240@187 delivered Leap 81.34 fps, Kiyo 30.27 fps, and PS3 Eye 185.56 fps. Leap+Kiyo only delivered Leap 82.77 fps and Kiyo 16.83 fps. Leap-only same-session baseline delivered 84.18 fps, with best fast-combined scenario 92.87 fps and 640x120 baseline 173.62 fps. Offloading Kiyo Pro and one PS3 Eye did not restore the previous ~110.8 fps Leap result; current hypothesis shifts to Leap port/controller/device state or KS/usbvideo behavior, not only total local camera bandwidth."}
{"ts":"2026-05-22T01:45:00+00:00","type":"verification","status":"ok","note":"Moving the Focusrite Scarlett Solo away from the Leap USB neighborhood substantially recovered local split-host cadence. Leap-only baseline rose to 95.48 fps, best fast-combined scenario to 101.67 fps, and 640x120 baseline to 192.83 fps. With local Leap + regular Kiyo + one PS3 Eye at 320x240@187 active, Leap delivered 105.10 fps, Kiyo 30.17 fps, and PS3 Eye 185.81 fps. The split-host local set is viable; the prior ~81 fps Leap band was caused by local USB layout including the Focusrite, not just camera count."}
{"ts":"2026-05-22T02:05:00+00:00","type":"verification","status":"partial","note":"Raven PS3 Eye raw interface initially had no driver binding. Exported the working Mimir host libwdi WinUSB driver package from oem26.inf, copied it to Raven under C:\\Meta\\mimir-ps3eye-winusb-driver, added the libwdi self-signed certificate to Raven Root and TrustedPublisher stores, and installed it as oem34.inf with pnputil. Raven now reports VID_1415&PID_2000&MI_00 as USBDevice OK, provider libwdi, service WinUSB. The copied ps3eye_dual_cadence.exe opens the device, but cadence is not viable yet: 320x240@187 delivered 132.24 fps then 78.93 fps, and 640x480@60 delivered 6.32 fps with multi-second gaps. Driver open is solved; Raven USB path/device cadence still needs isolation."}

View file

@ -126,10 +126,14 @@ current_status:
95.48 fps, best full-height scenario to 101.67 fps, and the local split set
delivered Leap 105.10 fps, regular Kiyo 30.17 fps, and one PS3 Eye 185.81
fps. The split-host layout is viable if the Leap's USB neighborhood stays
free of the Focusrite and other heavy devices.
free of the Focusrite and other heavy devices. Raven's PS3 Eye raw interface
now has the same libwdi WinUSB binding as the local Eye and can be opened by
the copied cadence probe, but Raven Eye cadence is currently unusable:
320x240@187 delivered 132.24 fps then 78.93 fps, and 640x480@60 delivered
6.32 fps with multi-second gaps.
next_action: >
Move the raw PS3 Eye probe into the repo or replace it with the first
runtime capture driver, then rerun the six-optical-sensor pull from repo
probes after deliberate USB topology changes. Keep high-rate cameras split
across controllers/hubs deliberately, because current shared-load tests show
Leap is no longer a stable timing authority under the present USB topology.
runtime capture driver, then isolate Raven's PS3 Eye port/controller until
its raw WinUSB cadence is stable. Keep high-rate cameras split across
controllers/hubs deliberately, because current shared-load tests show Leap
and the Eyes are sensitive to non-camera USB neighbors.