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

I notice that some of the gauges in the Windows exectutable Lite version are not displaying, but the labels are there: dhBV, dsc, wTobd(F), regenkw, kw, kw2, eff%, Load%. The same gauges and others are not displaying in the Windows executable for the standard version. This using either Win XP or Wine on Ubuntu.

I think the Lite version does what I was wanting, and looks good, what's there of it.

Which is odd enough...Running a program, compiled using Cygwin on a Windows machine, on a Linux machine running Wine. Hey, can you install Wine into Cygwin?

 

Yes, but my compilation skills are pretty much limited to typing ./configure, make, make install. I use Ubuntu Lucid.

So far I am just using Simulation mode. I have now gotten my Cygwin installation running on the XP machine, and I see the same missing gauges running the Cygwin exectutable as with the Windows exectuable on XP:

wTobd(F),
dhvBV(%),
dsc(%),
line/s,
req/s,
hvFanV,
Load(%),
gph,
ODOint,
DTC dist,
kW,
kW2,
icekWt,
regenkW,
eff(%),
eff2(%),
frickW,
frickW2

The labels are still there. Does the log file tell you anything in simulation mode? I see that it also creates the empty .csv file, but it does not write anything to it.

 

Ah so. I will get the laptop out to the car for more testing. Part of this effort at making an alternate GUI is to make more clear what I will use to get a permanent installation going in the car. I guess a small netbook might end up being the way.

I am not sure, but I would think there is some tool of some sort that will take a project and create a configure script, that will allow for "make make install" type installation.

I looked at CPU usage in both the Windows native and the Cygwin version in simulation mode, and the Windows native version updates the display more quickly, and with lower CPU load, than the Cygwin.

I am still wondering how many times one could recursively install Wine into Cygwin and vice versa before some melt down occurs.

 

I am curious as to what anyone thinks might be the minimum specs for a netbook that will be dedicated solely to living in the car and running Priidash?

Edit: I picked up an Aspire One netbook, so will see how that does.

 

2009: love the new edition. I'm using the Win version-can you tell me how to read the new PSU gauge? I think the lines are KW's but I'm not sure

 

Ok that certainly does help a lot but still leaves me with one actually two questions....How come there is often times space between the bottom of the ICE and MG2 bars? In other words say ICE is producing 10kw, the top of the bar will often be at 12 or 14kw and the bottom of the bar at 2kw. This is the aspect I don't understand.

The second question: next to that gauge are the numerical kw's for ICE and the MG's....I notice at highway crusing that MG1 is shown to be using power and MG2 is a negative number indicating it producing power and not using any....Is this a bug because I always thought that MG1 served mostly as a generator at crusing speeds and MG2 worked with the ICE to drive the car at those crusing speeds. Thanks!

 

Fantastic!!! Only just found this part of Prius chat.
After converting my Windows Phone to Android just to be able to run Torque... And still in the process of finding USB-drivers so I can utilise my old ELM327-based OBD-reader with it instead of buying a new Bluetooth version...

And all this time this was right under my nose!

 

Thanks! Just sat in the car for half an hour (in which the HV battery drained from 7 to 2 bars in minutes. I did have the AC on without noticing, but when turning that off it still dropped like a stone. Creepy...

But my question: I get this error:
openport: Unable to open /dev/ttyS3
!!! Error open port /dev/ttyS3 -> UI stopping.

My OBD-reader is on COM3, so should I indeed fill out /dev/ttyS3 ? As I tried googling and found e.g. /dev/ttyUSB1. As I don't have a clue what I'm doing here, I think it is safer to ask

I did set the baudrate to 115200 on both the Priidash as on the USB-device (in device manager, othere options were 460xxx and 920xxx but I thought it safest to not assume anything (like 1M=920xxx) and just go for the slowest setting first). Did not alter any other settings (like data bits o parity)

Any thoughts?

 

I am using XWin Server (which is part of CygWin, right?) to get to the PriiDash program and to start it.

I think I assumed there could be the standard computermixup of starting to count at zero or at one, and I did try ttyS2, but now that I know that is the correct setting, I will try again with more confidence (read: more patience ).

My USB-device is a generic (read cheapest I could find*) ELM327. In device manager, I can select a baudrate up to 920000 (iirc, which equals 1M I assume).
I will try several combinations and start with 1M at both ends.

* the USB-OBD device was purchased for a gearboxproblem with my Volvo (worst case was a D in my display while it was in R ). The reader showed an electrical fault in the automatic gearbox. I cleaned the connectorplug to the gearbox and sprayed it with contact cleaner. No errors since (4 years ago). Random anecdote to show this reader can do no wrong.

 

If the cheap OBD ELM327 is the same one that I purchased, it will only go to .5m and has to be programmed with STNterm. Hope this helps.

John (Britprius).

 

Thanks , atm that's over my head... but I'll Google STNterm whenever I get some spare time.