Here is the .csv output from my test run
https://www.dropbox.com/s/6ymke7yo41...i-log.csv?dl=0


Oh i should also mention that i was not using a raspberry Pi as it is committed to another project at the moment.
The test was performed with an Odroid C1 Running Ubuntu 14.04. i have added the product link below as it is a powerful little device and it is in the same price bracket as the Raspberry Pi, it also runs android for those who are trying to make a full in dash entertainment/nav/ECU logging system.
http://www.hardkernel.com/main/produ...=G141578608433

 

Alright, finally got a working capacitive touchscreen on the pi. Going to run a ribbon cable to it instead in the car so that it becomes very slim. Then maybe make a bracket and mount it near my air vents.

I re-imaged my entire pi so when I have Raspexi installed and running on it again, i'll put it in my car and post some videos.

 

So my Pi is broken at the moment ( plugged in at the mains at home and had a lightning strike ) So i started to design new gauges and dashboards . I will finalize and upload them hopefully tomorrow .
I took some screengrabs on windows and attached them , let me know what you think

 

Wow awesome news , can't wait for the videos

 

Raspberry pi2 arrived today . Managed to set up everything today , so hopefully testing on the car tomorrow

 

Nice !
I'm still yet to take a video but I've noticed that the pi displays the gauges a little behind real-time, so when I boot it and my revs go up fast I'll hit red line before the pi shows it . I'm not sure where the latency is coming from, though. Any ideas?

Will also be good to hear how the raspi 2 performs.

 

Well you can try to adjust the refresh time in the cfg file . We just set it to 35 ms that time but I haven't tested while driving . So maybe try a lower setting and see if the pi and the interface copes with it . I hope I can do a drive test real soon , but tonight I hope I can do a quick stationary test .

 

I completely forgot that setting was there, thanks Markus
I'll give it a go this weekend. 35ms is pretty short, though.
I'll go through the code and see if I can find anything, perhaps there is too much processing before the data can make it to the GUI, not sure.

I haven't tested anything other than RPM because I need to implement 'single-click' gauge swapping because my touch screen doesn't have a keyboard with matchbox-window-manager haha.

 

Well the only other option would be to only query the data currently shown on the screen seperately for each gauge "basic info " but that would be a long implementation I suppose . Maybe the advanced info is too much data at once . This was suggested by SonicRat to increase performance

 

That would definitely increase the speed that it can update, there are multiple ways it can be done. I need to investigate it more anyway perhaps it's not even an issue for other people.

I might see if I can look at implementing some code to only ask the PowerFC for data that is currently displayed, though, this would mean that logging wouldn't work properly. I'll have a think.

 

Just tested stationary with my raspberry Pi2 , Check it out



AUX inputs work great as well as the Analog Equations , i am still finetuning the dashboards and new gauge looks .

 

Can't wait to see some of the new gauges and dashboards!
I have pushed a few more Nissan ones to the repository for small screens.

I have also pushed a few more changes...
From now on you can single click on the dashboard to cycle through the dashboards, a single left click previously did nothing and so there is no loss here (single click drag and move should still work which was the only use for single left click).

I have pushed a new datasource to the repository, it took me a while to get working properly but now you can create gauges for Instantaneous Vehicle Power.
For it to work you need to add the vehicles mass in kilograms to the raspexi.cfg file (the readme file in the repo or the github home page will explain this more).

It works by integrating the Speed datasource to find acceleration and then a little more math to calculate power in kiloWatts. I haven't added the acceleration datasource yet but it shouldn't be too far behind.
(for those who are interested I am using an averaging filter with a moving window of size 20. With the default 35ms update interval in the cfg file this works out to be an averaging window about 0.7s long. The reason for this is because we are integrating over finite data points and the vehicle speed is quantised to km/h)

Let me know if anyone tests it and finds bugs, I tested on my car and it seemed to be pretty good (might just need to add some friction coefficients etc for more accuracy)

bad news... I keep forgetting to take a video, soon though, hopefully.

 

Added a fonts directory to the repository so that if anyone makes gauges they can download some cool fonts, add them to gauges and install them on the raspberry pi.
I have included two in the first commit but if I create more gauges with other fonts I'll include them too.
I think OTF and TTF fonts are supported by raspberry pi. The install_fonts.sh script copies them to the raspi's font directory for any rasbian user to use.

 

Sorry haven't pushed my gauges yet , struggling to setup git ... Also redoing the gauges since you implemented the installation of fonts hope I have everything sorted by Monday afternoon including a drive video .

 

Just wandering if you are able to have this interface setup running the datalogit software with a 98 octane tune and e85 tune saved and then switch between the 2 maps on the go. Therefore making it possible to finally run dual maps on the power fc ?

 

It should be possible , to implement switching between 2 different maps , but this means writing to the power FC . This would require someone with a good understanding of the Power FC Protocol and FC Edit Maps . At the moment the software only reads from the Power FC , which makes this software very safe to use in my view.
SonicRat is busy building his own version of FC edit for OSX, maybe he can give a comment /inisght on how difficult and safe it would be to implement such a feature .
I don't really think there is a big likelyhood of this to be implemented

 

Hi everyone

Great project, did you get anywhere with making a custom O/S for your software?

Regards!

 

Not really , I basically just created a self booting image based on the last raspbian release . Boot time is approx 40 seconds and the image runs on raspberry pi 1 and pi 2 and fits on a 4GB sd card . If anyone has good skills with Linux and building a custom fast booting kernel stripped of all unnecessary stuff that would be really cool . I need to clean it up still a little and compile the latest source before I upload it . But I wrote step by step instructions how to do it yourself ( takes about 20 mins to do that )

 

My apexi AVC-r had a Gear judge feature.
Using the Engine RPM and Speed it can determine what gear you are in.

the formula is " RPM/Speed=N " where N equals a known number relative to the gear you are in.
eg.
Gear | N=
1st | 230
2nd | 145
3rd | 94
4th | 75
5th | 50

On the AVC-r the value of N varies depending where in the rev range you are, but not by more than +/-6

Is there any way to implement this calculation as a data source in Raspexi? so you can have a logged value of what gear you are in, as well as a visual representation on the dashboard.

Here is the section from the AVC-r manual dealing with the gear judge.
Apexi AVC-r - Gear Judge

 

Sounds good , I will ad it under issues on GitHub as an enhancement request . Maybe someone wants to implement it .

 

Did a quick drive video . My headlights where not aimed and my indicators not fitted , so i had to drive slow arround the block . This is the latest Raspexi source compiled on 6th april 2015 with all new designed Dashboards .
The last dashboard has already gauges for features still to be implemented (torque , 0-100km/h , G-Force ) , the only gauge that is implemented is the Power meter in KW
The strange sound is due to the video compression ( did everything really quick as i had a bit of time pressure )

 

Ok, finally made a video of my Raspexi setup. I only filmed it while I was running some of the newer digital gauges I made, not analog style ones.

These gauges finally work because I fixed an ongoing issue with text alignment in MegaTunix, I forked the repo, made the fix and am waiting for David to accept my pull request. For the time being you can checkout my copy from here.

Also, I have some features for Raspexi R7 in the works. Will let you guys know when they're done.

 

Yeah i can build a kernel thats easy as

I will borrow a PI and start working on it, I will just need you to test that the Hako/Datalogit works - 40 seconds isn't bad for a startup time. unsure if i can get it any quicker but its worth a shot.

Once i stop spending money on getting FD parts from Japan i will buy a cable

 

My raspi boots in about 30 seconds to the gauges on a model B not overclocked and with a raspi SD.
If you do create a custom image keep in mind that some of us may need PiTFT's to work (i.e. me :p ) and so the gpio pins, framebuffers, cap touch settings etc may need to be accounted for. You can see how you go without that to begin with, I can look to add it later.

I currently use an init.d script to launch Raspexi with xinit directly after loading the kernels for the pitft.

Look forward to seeing how you go.

 

Hey guys,
Spent some time adding some extra features to Raspexi, spoke to Markus and pushed it to R7.
I will push the features to GitHub soon. So far extra features are:

+ Added acceleration datasource (how many seconds would it take to increase 100km/h)
+ Added acceleration G-Force datasource (with warning at 0.7 which is close to loss of traction)
+ Added force datasource from mass x acceleration (Newtons)
+ Added gear number indicator datasource (4speed, 5speed and added 6speed (after video))(suggested by Spud2233)
+ Added simple speed correction cfg setting via multiplier (added after video)
+ Added user tyre size speed correction cfg setting (uses original and current tyre sizes to calculate adjustment)(added after video)
+ Added some new digital gauges and dashboards as examples for the new datasources
+ Some other minor code tweaks, fixes, changes, etc

Here's a video of the four new datasources (apologies for the portrait video orientation):