.Net 8, cross platform, and Windows 7/8

[zack4200]

I still have a lot of work to do, but the UI rewrite is almost usable now. Windows only - I haven't even looked at any other platforms yet.

If you want to try it, you'll need to use this tool to install the dependencies, and be prepared to wait a while, as it takes forever to download SDKs for iOS and Android: https://platform.uno/docs/articles/exte ... bs=windows

Then switch to the nsfw/net8-uno-ui branch, build the solution, and set the PcmHacking.UnoUI project as the startup project.

while I'm waiting for uno-check to run so I can build and test it - I saw a few posts back you were planning to get Crank Relearn working; did you get it completed? Do you happen to know if it's the same procedure for all supported PCMs? I need to do a relearn on my P04, so I'll be testing that for sure and probably do some test reads/writes and a bit of logging.

Anything else specifically need to be tested out?

[zack4200]

By the time I got all the dependencies installed, it was too late to start the car and try doing a crank relearn but I did a test read and it went well - after I finally remembered I needed to copy over the kernels lol.


Noticed a couple things - first, when I was attempting to read before I had the kernels in place, PCM Hammer just disconnected from my OBDX Pro VT and gave an error for that. no error/warning that the kernel wasn't present.
Second, and I just noticed this because I was going to post my debug logs along with this reply - debug logs don't seem to actually save. I chose a folder for them in settings before doing anything else, and specifically went to the debug logs screen and hit save but I can't find them anywhere.

[NSFW]

The crank relearn stuff is written, but not at all tested. It's worth a try on the P04, but literally everything I know about crank relearn came from the thread that you saw... plus a post someplace where someone said you should hold the brake pedal down throughout the test.

I have been working on editing data-log profiles for the last week or so, but haven't tested that stuff yet in my car. I've just been opening log profiles that were created with the WinForms app. It should now be possible to make your own in the Uno app now, but if you're testing that stuff in-car you're actually ahead of me.

And I don't know whether logging will work on a P04 - it might, but we won't know you try. But, if it worked with the WinForms app it should work with the Uno app too.

Note that saving data logs has not been implemented yet - it should display live data, but that's it. There are buttons to control saving, but they don't do anything. That should change this weekend though, or next week at the latest.

The UI to set the log directory was really intended for data logs, not debug logs, but in hindsight it really should save both types of logs the same place. I think you'll find the debug log in whatever folder the .exe was run in.

[zack4200]

ah gotcha, I don't really know anything about the relearn except what I read in GM's service info about the procedure (for reference).. Which thread are you referring to? The post where I saw you mention working on relearn was a few replies back in this thread, so I probably should give that other one a read. Interesting, in that case I probably need to run a wire from the brake switch to the pcm lol, my swap doesn't have one.

I still haven't used the logger in either UI version yet so I'll likely mess around with both of them some this weekend.

okay good to know that data logs currently can't be saved, thanks for the heads up.

Oh you're right there are some logs in the folder with the exe, but I don't think they're the debug log? They're just hundreds or thousands of lines repeating

Code: Select all

PcmHacking.UnoUI.Services.LogEntry
PcmHacking.UnoUI.Services.LogEntry
PcmHacking.UnoUI.Services.LogEntry

and nothing else.

[NSFW]

Apparently my LogEntry class needs a ToString() method.

Kur4o described crank relearn in the 4th post in this thread: viewtopic.php?t=8536
It sounds pretty simple, and I've tested the UI to show the different conditions that need to be met (ECT, RPM, brakes) but I haven't tried the actual process yet.

My interest in the relearn feature tapered off after I added a section to my XDF to look at the crank learning data - there are four 16-bit values, all close to 32768, but one was an outlier. I made the outlier close to the other values, and stopped getting misfire codes. I still want to try doing a relearn, I just have been too obsessed with idle and return-to-idle tuning lately.

[NSFW]

Debug logging is fixed, and data-log saving is implemented but not yet tested in-car. I'll try it this weekend though.

[NSFW]

Halfway through my testing today, my car got into a state where the logger doesn't work right when I log with the new app, but works fine with the WinForms app. Not sure how/why but it uncovered an error scenario that isn't handled correctly in the shared library so at least now it shows an error message rather than showing garbage data.

And I'm pretty sure I just figured out why I haven't been able to log the idle feedback parameters, and it was just a broken int-to-float conversion formula in the ram-parameters XML file.

[NSFW]

I fixed the logger issue, the new UI was passing the OS ID from a variable that I meant to get rid of, so it wasn't initialized.