Feature Suggestions | Bug Report - Share your ideas.

I have not gotten time to play with it today.

Nomograph didn't seem to be working. The line was not straight when I tried it out yesterday.

 

Ok, is it slow because you are getting other data all at once? If that's the case, is it possible to separate it into another page since MG1 and ICE rpm change quickly?

 

Thanks, will give it a try. We are still going through Irene and replanning our one week delayed vacation.

 

Re: 115200 baud for bluetooth test

Ok I downloaded the file and it works with the laptop driving a Roving Networks RN-42 Bluetooth-UART connected to a SprakFun UART-OBDSol_STN11xx in the driveway and for a mile on the road when it goes into the familar lock-up mode.

I think the problem is the chopped up packets caused by the slow (115200 bps) uplink speed. The documentation says that Bluetooth algorithms may chop up the data packet and cause problems further upstream.

The intent this weekend is to set the Bluetooth speed higher to 1000000bps using the SZ command, change the Bluetooth algo latency using the SQ command and run the 1Mbps version of the PriiDash application.
I may end up having to incorporate the changes that seem to be required by the USB Link method.
w.

 

Add Command Line options

Just wondering if it was possible to add command line support so that you could set the baud rate and enable/disable the debug log.

just a though
Steve

 

Can I help with development of this for a GEN I Prius? I have a 2003 and could REALLY use this app! I have Linux laptops and desktops and am RHCE V6.

 

This is a great program and group. While I find it impressive as it is, and I want to say thanks again for all the work that has gone into it, my one comment is that the GUI is a bit more info rich than I can make use of while driving. In particular, I am most concerned with monitoring data that changes relatively slowly, mostly related to the temperatures of the main components, and the condition of the battery systems. Also, I do not use the GUI to read data that is already in the MFD or on the dash. Clearly some of the other details are useful to someone doing a hyper-miling research project, but I am more concerned with keeping things cool.

With that in mind, I have put together a first pass at a simplified set of gauges. I hid the ones that seem optional (to me) and enlarged the ones that are of most interest so as to make a quick glance all that is needed to seem them on a small screen. I have attached a screen shot and the resulting file, call it priidash_lite.fld (get rid of the txt). I don't have the compilation software setup, so I am hoping that someone would be able to create a version using this file. I have been using the Windows executable in XP. This ought not change any of the logging functions, if I am not mistaken.

Any comments or suggestions?

 

Ah so, I wasn't sure about what depended on what. I have updated the above priidash_lite.fld file to include all gauges, unchecking some of the attributes "Visible" and "Active", instead of deleting them.

 

No, I didn't look for releases....so here is priidash2_lite.fl. Engine specific at the top right, temp gauges bottom left, hybrid specific on the right. Any suggestions as for inclusions or further deletions?

 

I still have not gotten CygWin going here, but will do so. It will take some time to download all that, due to my Internet connection. Perhaps someone could make another Windows executable, as with the previous version.