PriiDash(TM): Enhanced Instrument Panel / Data Logger - Now Open Sourced!

When my OBD module arrives I will do just that. Thanks.


One question, what does PIDs stand for?


John

 

Got it running finally, thanks for all your help. I used putty to talk to the ELM327, for the benefit of others the default baud rate is either 9600 or 38400 (mine was 38400) with 8 data bits, and no parity or handshaking. The fastest mine would go was .5 Meg being an inexpensive one so the divider is set to 8. I assumed that since all the devices are based on the ELM327 chip set that they would all achieve the same speed but what I learned is that while the ELM327 chip will run at 2M (at least with version 2.0, mine is 1.5) the USB to serial circuit may be a limiting factor especially if there is no buffering.

Setting the baud rate is not something the average user is going to be familiar with, I would add to the suggested improvements list auto baud rate setting to the highest speed the device will support, starting with the default baud rates and then testing using the BRD command until the highest rate is found, then setting that rate in both the ELM327 device and PriiDash.

I have a question about the "Read DTC" mode of operation. I recently had the check engine light and red triangle lit and when I did a "Read DTC" it returned the following codes which I expected (I had all the coils disconnected to test the compression):
P0351 - Ignition Coil 'A' Primary/secondary Circuit
P0352 - Ignition Coil 'B' Primary/secondary Circuit
P0353 - Ignition Coil 'C' Primary/secondary Circuit

P0354 - Ignition Coil 'D' Primary/secondary Circuit
I did not see anyway to clear them from PriiDash, is that possible, if not can you add that to the suggested improvements list?
I then pulled the DTC codes from my iPhone with Engine Link and got a whole different set of DTC:
P0403 - Exhaust Gas Recirculation Circuit Malfunction
C1103 - ABS Hydraulic Brake Switch Circuit Failure
C1203 - Engine Control System Communication Circuit Malfunction
C1303 - Right Front Isolation Clamping Circuit Failure
When I cleared them from Engine Link and rechecked in PriiDash there were no DTCs

Does PriiDash only report certain DTCs?

Finally I love the charts you have made from your logged data, I am particularly interested in the traction/HV battery health as the warranty is about to expire. How have you graphed the log data?

Thanks for all your hard work, it is a real service to the Prius community,

Glenn

 

Thanks for the offer to graph, attached is a run I did from Fort Collins to Boulder last week that should give a good indication of battery performance under a variety of conditions.

Thanks,

Glenn

 

That sounds like a plan, just point me to it.

Glenn

 

I can't get this to work. I have a mini vci that works perfectly with techstream; however, it won't communicate in priidash, no data shows up. It runs in Demo mode but not in normal mode. I have tried to set the baud rate to 9600 and 115000 but no success; tried to match the baud rate in Device Manager as well as Priidash. What am I doing wrong? Is there a step-by-step guide? Seems like information is scattered all over the place, does anyone have a straight-forward setup guide, don't just give the url to the priidash, please point out the precise info to get this working!!!

 

I don't think that the mini VCI works with PriiDash. You need an ELM327 compatible device. The VCI is Techstream specific, or at least not like the ELM327 protocol.

 

I see... Thanks to nh70, I learned that I needed elm327 device, the one that came with mini=vci is not elm327. I will also check the link 2009prius supplied above. Thank you!

 

Hello,
I must say, Prii Dash is certainly an impressive piece of work!!!!

I may be somewhat "Out of the Prius Club", but I recently purchased a 2015 Camry XSE V6. I have been playing around with the OBDII Unsolicited Messages, and have built a LINUX program that reads the Speed, Miles Traveled, Instant Fuel Consumption, as well as Average Fuel Consumption. This is work in progress, but it is using the data that is already on the bus, and matches the Fuel Trip computer PERFECTLY. (This was a major step )

I have a question about your PriiDash Software. I notice in your source code that you have parameter 0x520 commented out. Are you not using that for your calculation? I had to do a bit of "Searching" for the right parameters in my Camry, because they dont match the prius.

Once I figured out what parameter was for FUEL CONSUMPTION, I drove known trips and added up the "COUNT" in that parameter. Then, I used the indicated Fuel Consumption on the dash board to figure out how much fuel corresponded to one count. (For example, the number shown in 0x520 every approximately 1/2 second)

You seem to calculate "PER ROTATION" What was your methodology to figure out the "21600.0" constant?

I also notice in the service manual, there is a parameter from the scan tool which is "Number of ml injected for 10 injections for Cyl #1" I am wondering if this value (IE--In the prius----0x520) is this same parameter?

Just curious what you think. Any information/methodologies would be greatly appreciated, as I LOVE playing with this stuff!!!

Thanks

 

Hi!
Is there any way to control the acceleration of my car by OBDII or any interface from an android device or computer?
Thanks,
Fuge

 

Hi all, I'm new to PriiDash, has anyone succeeded in building it in Linux environment? I ran into this error:
XXXX@XXXXX:~/PriiDash20150807/Code/muparserx_v2_1_2_MinGW$ make

#########################################################
# #
# Building sample #
# #
#########################################################

g++ -O3 -Wall -ffast-math -fomit-frame-pointer -Iparser -L./bin -o ./bin/example ./sample/example.cpp ./sample/timer.cpp -lmuparserx -lm -static-libgcc -static-libstdc++
g++: error: ./sample/example.cpp: No such file or directory
g++: error: ./sample/timer.cpp: No such file or directory
Makefile:49: recipe for target 'example' failed
make: *** [example] Error 1

Really appreciate your help!

 

Thanks for posting the link.
I downloaded the program and it runs fine on my WiFi OBD2 device that I am working on, no locking up.
I had to raise the speed to 2Mb on the uart bus.
The OBDLink MX runs its uart bus at 115200 on the one that I bought a while back, The RN-171 Wi Fly module could be maxed out at 921600 on the latest data sheet that I have read.