Controlling the Instrument Cluster's Display

Figured I'd give a quick update on the state of the code. I've been working casually on it and have gotten a lot done since the most recent demonstration video (https://www.youtube.com/watch?v=OXi7dnEgSMg). Also been squashing various bugs.

You can configure 16 different parameters to show in the MPG area (as demonstrated in that video), but it's now possible to configure the gauges as well and to show things on what I'm calling the "FCD numbers" - the 50, 100, and 150 above the instantaneous MPG gauge. There's a menu system to configure all these that I think is pretty simple after a quick explanation. I tried to make it as intuitive as possible, given the limited display capabilities.

I have a Pegasus board installed in my Insight, of course, so I can test it every day. When I have new firmware to put on it I can just upload it over the USB cable that I left hanging out by the OBD-II port. Very useful!
I currently have Pegasus set up like this - autostop light shows whether I'm in lean burn or not. Fuel gauge shows TPS, 0-100%. Battery gauge shows actual SOC, 20-80%. Assist/regen gauges show IKW (IMA request in kilowatts), 0.0-9.0kW. On the FCD 50/100 I'm showing assist/regen limit flags (those are just 0 or 1). And on the FCD 150 I'm showing instantaneous MPG, calculated from RPM, speed, and fuel injector time as discussed before.

I have gotten the instantaneous fuel equation to be pretty good - I'm assuming 145cc/min and it seems accurate up to about 110mpg, but higher than that and the number I calculate is higher than what the bar graph seems to show. I may need to tweak it a little still.

It's coming along quite well! Still a lot of features to implement for what I would call v1 of the software, but it's going well.

Who would like a prototype Pegasus system?
Read the whole post first, please!
It is not first-come-first serve, so no need to rush to send me a message. The prototype boards won't be ready for another month or maybe two.

Now that I have your attention... (don't get your hopes up, there is only one available at the moment)

Work on Pegasus is coming along, albeit slowly because I've been splitting my time among several projects, but it is coming along!
In the meantime, I've been using Pegasus every day in my car and I have it set up how I like, and it just seems second-nature to me now. But I realized I should be having other people test it, too - that way I can find more bugs, see what features people really want, and be more motivated to work on it because people other than me will be using it.
So I'm putting together a quick second revision of the PCB that implements a few fixes for problems I found on the first one, and will be making five prototypes.

Two of them I have offered to a couple members personally because I'd prefer they use it. One I'm offering up here. The remaining two I'll be keeping - one to put in my car, and one to develop the code on.

Here are the requirements, in order of most to least important:
- Already have an OBDIIC&C and use it often (it's not required for Pegasus to work, but I want somebody who is interested in these sorts of systems/extra info)
- Be willing to give good feedback. I want feedback on ideas for new features, how Pegasus could be improved or made easier to use, any bugs found, etc.
- Have a UK car. I have a US car, so I've done plenty of testing there, but I want testing in UK cars as well.
- Have a CVT (same reason as above)

To install Pegasus, you'll need to take apart your dashboard. It involves dropping the steering wheel, pulling off the trim, and taking out the instrument cluster. It's not too bad, the entire install will probably take you two hours if you've never done it before.

As a reward for helping, you can keep the whole system, free of charge. It is possible the hardware may change enough later that future versions of the firmware may become incompatible, so no promises about long-term support... but hey, it's free, right?

If you'd like to apply, send me a private message.
Edit: To clarify, you don't need to meet every requirement to apply. But the more requirements you meet, the more likely you are to be chosen. Really, the only one I'll actually require is that you be willing to give good feedback, because the whole exercise is pointless if I don't get any test data back.

Revision 2 of the PCB sent out for fabrication!
It'll still be a while yet before prototype rev2 units are ready, though, because I still need to make the cables, joystick boards, etc. Gotta find a source for some OBD-II plugs, as well.

It may not look like it, but this version is much simplified and cleaned up. It uses fewer components and I've consolidated some stuff and gotten rid of other things.

I've changed user GPIO so there are 4 ports, all the same, each with 12V, 5V, and an I/O pin. The I/O pin has the ability to read analog/digital values in and also output a low signal so you can drive 12V relays, lamps, etc. There is also the capability for UART communication on one of them for future expansions. I have a couple ideas in mind for what could plug into that.

I've added a button for test functionality - this allows you to, before even taking apart your dashboard, test the whole Pegasus system and make sure it can communicate with the car, joystick, etc and that everything is working fine.

For the user GPIO, you can draw up to about 1.5A on the 12V and 5V rails combined. Those are both powered from the OBD-II port and includes a polyfuse in case you short something out.

I still need to design a tiny joystick PCB, but that'll be fast and easy. I'll also model and 3D-print some new expansion covers (the little plastic plugs next to the driver inside the car) that have mounts for this PCB so it's a quick and easy installation.