pEEf, I'm definitely interested in the concept as a (big) step up from the ScanGauge. :rockon: BTW, what do you call the unit? It would take two daisy-chained SGs to display the data shown on your unit. What are the dimensions of the display area? I'm hoping for something larger than the SG... What are the overall dimensions of the unit? Where is the rotary encoder (knob) w/built-in push button user interface located? I am interested in a kit and understand that it would come without a case.
hey pEEf, this looks completely awesome. i have a SG2 but i'd drop it in a second just to see SoC and current at the same time. i'm also a EE/CS guy and i live in the rockridge area. no gen 3, but 2 gen 2 priuses so if you need someone else local to test and debug let me know.
How programmable is the audio portion - I'm looking to recreate the upcoming Prius Japan 'sound' option - which varies with speed...
Sounds like an interesting product, put me down for one, should be fun using it on my 2008 Gen II. I would like to help where I can. I am a EE with SMD assembly skills, PIC Assembly Programing. I used a Cypress USB chip ( which was based on a C51 core) on another project. I have a microscope and the requisite soldering tools to assemble the projects that I am curently working on but I am not equipped for QFN or BGA parts. I have Tools for Altera, Lattice and Xilinx CPLD/FPGA +JTAG download cables.
Thanks for the offer, but a bunch of logs without corresponding data would be almost useless. FYI: All you need to log is a CANUSB or equivalent.
The microcontroller has a limited amount of flash, but the trip data can definitely be stored. I do not yet do this however. This could be done by adding more external memory. I think I'd implement this via a SD card. Personally I don't have this need, I usually just hook up the PC if I want to store lots of data. I'm trying to keep the hardware simple (read: low-cost), but if there is enough interest we could add this. BMS is my Battery Management System. It's explained in my PHEV post. It has nothing to do with reprogramming. The PC interface is standard USB, it would only take an application to reprogram it. This is interesting. Right now I have an indicator that shows when the Engine is in Closed loop. There might well be information on the bus to indicate this, but I haven't found it (nor have I looked for it). Of course, we do pretty much know what all the requirements for each stage are, and since we can read those it should be an easy matter to determine even if we can't find an existing "stage" parameter. I appreciate the offer. I will let everyone here know when I have something that we are ready to test. I will not send anything out that demands tricky assembly, don't worry.
I have a Trademark pending on "PRIUSCAN", so you can call it that if you like! My existing prototype (in the picture) is about 4" x 2" (10 x 5 cm) with a 20 character x 4 line display area of about 3" x 1" (7.6 x 2.5 cm). I'm likely going to switch to a larger graphic-capable display which has 192 x 64 pixels, which is about 2x the resolution. It's display area is 4" x 2.5" (5 x 3.8 cm). Both are monochrome displays that generate high-contrast white characters on a nice blue background. They also both use an LED backlight that's fully dimmable. For reference, the ScanGauge uses a 16 x 2 character (80 x 16 pixels) display. I've got the rotary encoder "knob" mounted on the side, but I'm not sure if this makes sense. I do love the encoder compared to buttons though! I actually had mine in a case (off the shelf), but the case simply made it bulky, and it wouldn't fit nicely over my mirror like it does now. I now have just the bare guts, but I've taped it all up with black gaffer's tape. It actually looks nicer this way than it did with the case, I was surprised!
I'm currently just using the built-in PCA (programmable counter array) to generate tones of any desired frequency, and that's driving a tiny speaker much like cell phones use for ringers. While I could combine the PCA's to make more complex tones, it's probably not sufficient to make that "Prius Noise". You'd also have to add an amplifier and external speaker. If I was going to tackle that, I would do it as a separate unit. Use a microcontroller with a design more suited for audio, or at least add an external audio DAC. The sound in that video doesn't sound complex at all, it seems like it's only a few frequencies with at 2 of them being close so there's a beat frequency. (can someone analyze it?) I think even with my limited audio experience, I could come up with a cooler sound though. It also doesn't seem to track the speed with much precision. There is high-resolution speed data on the CAN bus that could make this work better. But this is a topic for post (and time!) (Thanks for the Video BTW!)
very impressive pEEf, I would be interested in testing it in my 2010 Gen 3, of course I am on the right coast 2,500 miles from you... I would hate to see you distracted from finishing and documenting your great progress on your PHEV work, that seems actually the equivilant of the Ewerts software, and a modest sized 6.5KW lithium pack, that probably makes more sense for most average commuters. It would be nice if you could either open source your work on that, or work with an existing mfr to "package" your work. Using the A123 cells probably makes it fairly costly, perhaps using "ThunderSky" Lithiums along with an eLithion BMS and a Brussa charger would be a good compromise... anyway, you have done an impressive amount of work, for just a "hobby" Thundersky: Thundersky Lithium Batteries Elithion: http://www.evolveelectrics.com/Elithion.html 72 of the TS-40Ah are $50 * 72, or $3600 for the main component, of course just the batteries weigh in at 237.6 pounds (heavy, would require beefed up rear springs probably, and hmm, looks like about a 9.2KW pack too), plus of course you need the BMS and the Brussa charger, and of course your CAN microcontroller and a few more pieces of glue. sorry to take this post off topic, should probably have replied in the other thread.
That sounds great, I would buy one. Old time cars had ammeters, always liked the ammeter. As a casual suggestion your handle is a pretty good name for a device. Does it measure oil pressure and driver mood?
pEEF, if you ever just get a kit together with just parts, i can solder like a madman so would be interested in the basic kit. but great little priuscan.
pEEf - I'd buy a kit - especially sold like you intend with the SMD stuff done. Would it come with access to the source code? I encourage you to publish early and publish often.
Great work and wise men think the same! I have also been using the Scangauge for hypermiling and data logging. There are just too few parameters that ScanGauge can display at the same time, in addition to the shortcomings you already mentioned. I also would like to add customizable color lights or indicator colors depending on the value so one can easily glance by the color without having to read the number. I just started road testing yesterday and here is my humble effort. Please come visit. Wow! Do you mind sharing the CAN IDs and formula for them? I think (not 100% sure) I have the demand but not the actual. Thanks!
peef you can have the 8015 ISP port open to the user for software upgrades via a Silabs USB debug adaptor, just like in Norm's Canview.
Unfortunately due to the thriving business of Chinese knockoffs, I doubt I'd be able to share the source code (at least initially) and not be out of business. Developing code like this takes a solid time investment, and really, it's the largest part of this project. Giving it away free would likely make it impossible to continue to devote as much future time to the Prius as I'd like. I've always been an open-source guy and I am a generous person who shares my time time and knowledge freely, but sadly, there are people always waiting in the wings to exploit that. What I can do to offset this is make the thing highly customizable and easy to apply firmware updates in the field.
I suppose external outputs could be made available to drive LEDs and such, but I've got to really try to keep the hardware simple, and focus on the software. This will keep it manageable. If we allow feature-creep, you'll never see a finished device. In fact, I can easily spend the bulk of my free time just answering questions here and not have any time to work on it!
