Page 1 of 1

Two PRs related to CAN logging

Posted: Sat Jul 05, 2025 3:33 pm
by NSFW
This one is small, it just adds some logging to show what messages it finds on CAN bus at the start of a logging session:
https://github.com/PcmHammer/PcmHammer/pull/12

This one is bigger:
https://github.com/PcmHammer/PcmHammer/pull/13
  • It can now extract multiple parameters from a single CAN message. (This was the intent from the start, but wasn't finished.)
  • CAN messages can arrive at a higher frequency than PCM data, and now it can average the data that it received, or just take the last one. I think averaging might help for AFR in particular.
  • Fixes a couple bugs in CAN message parsing.
  • Adds some unit tests for CAN message parsing.
I just noticed that the Windows version we've been using for the CI builds (2019) is no longer supported, and the newer Windows releases don't have .Net 4.6.1. Looks like we can use 4.6.2 though so I'm trying that.

https://github.com/PcmHammer/PcmHammer/ ... 8532?pr=13

Re: Two PRs related to CAN logging

Posted: Sat Jul 05, 2025 4:41 pm
by NSFW
The 4.6.2 upgrade touched a lot of generated files in addition to the .csproj files, so I made a third PR for that:

https://github.com/PcmHammer/PcmHammer/pull/14

After this is merged, I'll update the other two so that their CI builds will pass too.

I just learned more about .Net installers than I ever wanted to know. :)

Re: Two PRs related to CAN logging

Posted: Sat Jul 05, 2025 6:15 pm
by antus
Good stuff. I tried 4.6.2 and got in to a world of pain and moved to 4.8 instead. But i'll throw that away as 4.6.2 is a better target for now. Hopefully the readme explain how to configure the OS for the build. I was also testing on studi 2022, not sure if that was part of the problem but it couldntvsee the 4.6.2 sdk installed with what I tried.

Re: Two PRs related to CAN logging

Posted: Sun Jul 06, 2025 6:30 am
by NSFW
I updated the readme to add instructions for both users and contributors. I'm using 2022 and it's working for me, but they have been putting out incremental updates pretty frequently and I think they fixed something in this area. I ran into a bunch of headaches when I tried to change the .Net version last fall, but this time it went smoothly.