UPS input comes from the ignition-switched socket via a 15 V PD
trigger, so input loss means cranking or ignition off. The INA219
(monitor-only) gives the battery current sign; a host service would mark
cranks, then after a grace period close the recording and power off,
with a voltage floor as backstop. Records the open hardware problem:
after poweroff the UPS keeps the board powered, so it drains and
doesn't auto-start at ignition on.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
15-19 V in, 3S 21700 pass-through UPS with an INA219 that the car unit
sees on I2C bus 7 at 0x41 (read-only check: 12.34 V, idle). Bench test
held the Orin >=20 s across a supply swap. Notes the 20 V PD caveat and
the intended ignition-off shutdown via battery current direction.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
In the car with ignition on, the listen-only probe found 500 kbps (2673
frames in 3 s, zero RX errors; nothing at other rates). The OBD port
isn't gatewayed: 27 periodic IDs, ~893 frames/s. A udev rule now starts
can-up@can_pcan on boot and hot-plug with 500k and listen-only, to be
dropped when obd-poller becomes the single writer.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The backup pin doesn't charge, so a rechargeable ML2032 would just
drain with a third of the capacity. Adds the expected life (~1.5-2 yr
typical), polarity and post-fit test notes, and marks the item low
priority since NTP covers almost every online boot.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The dev kit carrier has pads but no connector populated, so the RTC
resets whenever power is removed. Captures the connector part NVIDIA's
docs reportedly specify, the community substitute, and the R560 note;
battery type and footprint still need checking against the schematic.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mttcan and pcan both load at boot, so the PCAN adapter could take can0
and push the onboard controller to can1. A udev rule now names them
can_onboard (platform c310000.mttcan) and can_pcan (USB 0c72:000c),
both outside the canN pool so a transient canN can never collide.
Also records why the SIM7600 needs nothing more: ModemManager and NM
don't use ttyUSB numbers, and gpsd already uses a symlink.
can_onboard is verified live; can_pcan is checked against the driver
source only (adapter not plugged in).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The L4T kernel ships without qmi_wwan/cdc-wdm, and PPP dial-up made KDDI
detach the povo SIM (attach APN was au's; PPP re-activating the default
bearer still detached). Built both modules out of tree from v5.15.148
into ~/infra/qmi_wwan, set the attach APN to povo.jp, and added an NM
connection at metric 1000 so LTE ranks below Ethernet and WiFi.
GNSS autostarts on the modem and gpsd reads /dev/sim7600-gps (udev
symlink on interface 01); no fix yet, tested indoors.
BOM: NMEA is on ttyUSB1 not ttyUSB3, and the data path is QMI, not
RNDIS/PPP.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Orin Nano Developer Kit exposes no DSI connector — the module carries DSI
on SODIMM pins but the reference carrier board does not break them out, and
DisplayPort is its only display output. The Waveshare panel is also a
Raspberry Pi accessory and mechanically incompatible. It could not have been
connected without a custom carrier board.
Moot regardless: the tablet is the display, and no dedicated display is in
scope. The entry was still marked research pending / TBD.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013kj58Jugkic783b8ZrtTVZ
Replaces `type: default` — one value across every document, read by nothing.
Types are now reference, guidelines, plan and report; plans carry status and
updated, reports carry date. Convention documented in project-yukart REPOS.md.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013kj58Jugkic783b8ZrtTVZ
mikkeli
mikkeli