What this analyzer observes
PGN 60928 (0xEE00) carries an eight-byte NAME. The input parser retains file order, row number, bus and optional seconds. NAME is interpreted little-endian using 64-bit integer arithmetic, avoiding rounding when the value exceeds JavaScript’s safe Number precision.
Three different findings
Multiple distinct NAMEs observed at one source address on the same bus require timeline review. They may reflect contention, a replacement ECU or legitimate reuse over a long window. The same NAME at several source addresses is reported separately as movement. Repeated identical claims alone do not create a conflict. SA FE is Cannot Claim, not a normal address; SA FF and non-global destinations are flagged and excluded from normal address groups.
Example and next decision
The synthetic sample repeats one claim, observes a second NAME at source 00, then observes that second NAME at 01 and a Cannot Claim at FE. It produces one potential-contention/reuse group, one movement and one Cannot Claim event. Do not count these as three proven ECU faults.
Lower NAME is priority, not proof
Lower numeric NAME has arbitration priority in a contention. The smallest NAME in a file does not prove successful ownership: a passive partial capture cannot establish settlement, whether a contender stopped transmitting, or which physical node is currently connected. NAME fields are numeric identities, not a manufacturer lookup database.
Keep the original trace and equipment context for an authorized engineer. No new address, device replacement, firmware change or safe-operating recommendation is generated. An absent conflicting claim is not proof of a conflict-free network.
Passive capture review only. No connection to equipment, no bus transmission, no safety clearance and no protocol certification. A clean result describes the supplied bytes, not the completeness of the original recording.