Closed wvu closed 7 years ago
I'm a new contributor to the organisation and I'd like to be assigned to me. Any help on solving my first issue would also be very appreciated.
@wvu-r7 when the car was off, was the bridge still running or was that closed as well? Currently there isn't a method to determine if the state between the relay and the hardware client is still active. I can of course clean up some of these null errors but I'm wondering if there is a bigger problem that needs to be addressed and some more information on the condition at the time of failure would help.
@zombieCraig: The bridge was still running, yeah. It's just empty packets being dereferenced. If there's a better way to check for that instead of on a case-by-case basis, that'd resolve the crux of this issue. I can gather more info later today. Thanks for the swift response!
@wvu-r7 I found the core issue. The ELM327 reports CAN ERROR when sending packets and the relay was treating that as a valid CAN packet. Once I added a proper check for ELM327 so that it did not consider that valid CAN traffic (duh) then that fixed the null errors. I'll upload the fix once I clean up a few other things
Ahh, that makes sense. I haven't been deep in the code yet, so I can't comment on how anything is done. I'll be sure to test your fix when it's ready. Thank you!
I just realized how bad my bug report is, too. Will do better next time. Sorry about that.
this was fixed right, can we close it?
Not until #8031 lands. I'm still tracking down some remaining nil
bugs. I'm seeing sporadic get_current_data_pids
failures still.
Ran into these while my vehicle was off. No problem while on.
I am using live Kali at the moment, so please forgive me if these have already been fixed since the last update. I will retest with my dev env once set up.
Here's a good run (vehicle on):
Fun stuff! Thanks for the great work, @zombieCraig. This sure opens up a lot of doors for us.
7795