panda siren on ignition off
Not sure if fully reliable, but this happened for me after disengaging and quickly turning vehicle off at the end of this route: https://connect.comma.ai/b9d015f8ff659e1e/0000043a--98baf2b862
from greg:
RAM device beeping when I shut the vehicle off at the end of this route and when I turned the vehicle back on it also beeped. I think it was the panda alert beeping. b3c7f01bb05086ee/000001c2--6b7293f525
This has been happening for quite a while for me also. I never made an issue due to not being sure of how to reproduce it.
What are your dongle IDs?
9a31d18cd1a79c69
I have this issue as well sometimes, albeit on SunnyPilot 0.9.7.1 (I know, not stock).
I see this when restarting op/device while car still on (and possibly engaged).
I see this when restarting op/device while car still on (and possibly engaged).
That's expected.
I see this spammed when the car turned off, the can packet dropped out, and it reports 500+ can core resets, so perhaps the siren was valid here?
478.353119] selfdrive/pandad/spi.cc:280 - wait_for_ack: SPI: got NACK, waiting for 0x79
[478.353519] selfdrive/pandad/spi.cc:280 - wait_for_ack: 361421 / 0x81 / 0 / 1984 / tx:
[478.354722] selfdrive/pandad/spi.cc:242 - spi_transfer_retry: NACK sleep 53
[478.354850] selfdrive/pandad/spi.cc:242 - spi_transfer_retry: NACK sleep 53
[478.355444] selfdrive/pandad/spi.cc:242 - spi_transfer_retry: 361421 / 0x81 / 0 / 1984 / tx:
[478.355585] selfdrive/pandad/spi.cc:242 - spi_transfer_retry: 361421 / 0x81 / 0 / 1984 / tx:
[478.361214] selfdrive/pandad/spi.cc:280 - wait_for_ack: SPI: got NACK, waiting for 0x79
[478.361343] selfdrive/pandad/spi.cc:280 - wait_for_ack: 361422 / 0x3 / 14 / 0 / tx: 11030e000000fc14
[478.361860] selfdrive/pandad/spi.cc:242 - spi_transfer_retry: NACK sleep 7
[478.361936] selfdrive/pandad/spi.cc:242 - spi_transfer_retry: NACK sleep 7
[478.362163] selfdrive/pandad/spi.cc:242 - spi_transfer_retry: 361422 / 0x3 / 14 / 0 / tx: 1414141414141414
[478.362223] selfdrive/pandad/spi.cc:242 - spi_transfer_retry: 361422 / 0x3 / 14 / 0 / tx: 1414141414141414
@adeebshihadeh Want me to look into this further?
I see this spammed when the car turned off, the can packet dropped out, and it reports 500+ can core resets, so perhaps the siren was valid here?
That's just because the ECUs on the bus go offline before we finish TX'ing all our msgs; it's fine that the TX fails. Those are some pretty low level logs.
@adeebshihadeh Want me to look into this further?
Yes
See https://github.com/commaai/panda/issues/2132