Power FC New Power FC Software RasPexi Viewer
Hi Guys,
Came across this randomly while researching some PFC stuff. This looks absolutely brilliant and I am/was pretty keen to get a Pi and give this a go, the only issue being I want to use it with my Evo. I followed the link to the Kashima page but it does not have any info listed for Mitsi so no idea what the offsets for the data is. If anybody has any info on how to get the correct data and get this working for the Evo would love to try it out. Cheers.
Came across this randomly while researching some PFC stuff. This looks absolutely brilliant and I am/was pretty keen to get a Pi and give this a go, the only issue being I want to use it with my Evo. I followed the link to the Kashima page but it does not have any info listed for Mitsi so no idea what the offsets for the data is. If anybody has any info on how to get the correct data and get this working for the Evo would love to try it out. Cheers.
Hi guys, I've come across this thread looking for a way to read diagnostics from my Power FC, installed in my R33 GTS-t, without the need for a hand controller.
I have a Raspberry Pi and have used it before to communicate to ECU's via OBD style protocols.
I am super interested in the work Markus has done here and would be quite interested in implementing this.
I have literally everything to complete this project except the FC Hako (or similar) and I have plenty of experience do get this done.
Considering I was thinking of spending some time implementing something, much like what has been done here, from scratch, I might look at getting the Raspberry PI to communicate directly with Power FC. Effectively meaning this project could be done very cheap.
Does anyone here know if this can be done?
I have only had a brief look though here so far.
I have a Raspberry Pi and have used it before to communicate to ECU's via OBD style protocols.
I am super interested in the work Markus has done here and would be quite interested in implementing this.
I have literally everything to complete this project except the FC Hako (or similar) and I have plenty of experience do get this done.
Considering I was thinking of spending some time implementing something, much like what has been done here, from scratch, I might look at getting the Raspberry PI to communicate directly with Power FC. Effectively meaning this project could be done very cheap.
Does anyone here know if this can be done?
I have only had a brief look though here so far.
and now I have found this thread .. hmmm
FC Tune preview - RX7Club.com
FC Tune preview - RX7Club.com
The Power FC may not follow the I2C protocol but it still appears to have a serial style transmit and receive line. A protocol could be written for the Raspberry Pi to communicate directly with it assuming the Power FC's clock speed was not too fast (and a few other limiting factors).
After a little bit of a read it looks like the guys here looked into what the protocol needed to be, although I havent read the whole thread and it looks like they stopped working on it quite some time ago (I think I may have read somewhere that it is them who make the FC-Hako??)
Anyway, I think the RasPi could do it, it's just a matter of working out how the Power FC will communicate with its TxD and RxD.
After a little bit of a read it looks like the guys here looked into what the protocol needed to be, although I havent read the whole thread and it looks like they stopped working on it quite some time ago (I think I may have read somewhere that it is them who make the FC-Hako??)
Anyway, I think the RasPi could do it, it's just a matter of working out how the Power FC will communicate with its TxD and RxD.
Alright, I've got everything working, installed and can run raspexi and have the source code as well should I need to change anything.
Thinking of getting one of these and can then just swipe between guages:
PiTFT 2.8" Capacitive Touchscreen
I might end up getting an FC Hako after all, probably will be much cheaper in the long run.
Then I can work on getting the boot time down (hopefully less than 10s) and creating some nice guages etc.
Thinking of getting one of these and can then just swipe between guages:
PiTFT 2.8" Capacitive Touchscreen
I might end up getting an FC Hako after all, probably will be much cheaper in the long run.
Then I can work on getting the boot time down (hopefully less than 10s) and creating some nice guages etc.
As the source is made available as open source I would like to ask you to also submit the changes you make so we can ad more cars . The r33 would be a awesome ad on. Pm me and I ad you to the submitters on google code . Thank you
Joined: Dec 2001
Posts: 10,630
Likes: 3
From: NY, MA, MI, OR, TX, and now LA or AZ!
Adding more vehicles wouldn't be terribly difficult. It would just take someone motivated with FC-Edit and a target ECU to generate a few dumps.
As for the Pi -- it would be generally cumbersome and difficult to add direct communication support, and you'd end up doing bit-bang, which can be annoying without a realtime kernel.
As for the Pi -- it would be generally cumbersome and difficult to add direct communication support, and you'd end up doing bit-bang, which can be annoying without a realtime kernel.
Adding more vehicles wouldn't be terribly difficult. It would just take someone motivated with FC-Edit and a target ECU to generate a few dumps.
As for the Pi -- it would be generally cumbersome and difficult to add direct communication support, and you'd end up doing bit-bang, which can be annoying without a realtime kernel.
As for the Pi -- it would be generally cumbersome and difficult to add direct communication support, and you'd end up doing bit-bang, which can be annoying without a realtime kernel.

It looks very easy to do after having a look at the source code.
I ordered an FC Hako because I'd rather get this working than farting around bit banging like you said. I knew that that is what it would take and I know that it would be a headache, however, it would make for a real easy and cheap setup should people be interested.
Perhaps if this project turns into something bigger and with enough support I'll then look at trying to implement direct communication, probably with help.
Anyone keen to see if they can get raspexi running on this Buildroot for the raspberry pi?
https://github.com/gamaral/rpi-buildroot
https://github.com/gamaral/rpi-buildroot
Not too good on build root , started working now on the latest wheezy image from February . Got the auto login sorted last night . Also installed a window manager (matchbox) to handle the mouse and keyboard .Wrote a script to tell matchbox what to do with Raspexi . I can start the app now directly from the console without starting x desktop by typing xinit "scriptname" . Still trying to find a way to autostart the script at boot . If I ad it at the end of bash.rc it autostarts at boot but it's not ideal . Still need to read on a better way of doing it . Also managed to get the bootsplash via FBI running but the problem is that you have to change to tty2 to work as the bootsplash stays visible in the console
So , finally some more success . I found a way to launch Raspexi during the boot process . Instead of loading the splash screen as a boot logo . I directly load Raspexi while the pi keeps on booting in the backround . This brings the startup time down from about 45 seconds to only 25 seconds . I just have to test out if the serial drivers are already loaded by that time in order for Raspexi to display the cars sensor values already at that point . I will test this on Wednesday and hope I can upload the image before Friday . It uses the latest available raspbian image . I will try to see if there are any more ways to improve the boot time , but I am pretty happy with the results so far
starting to get the hang of Linux slowly but Shurely . This will make it easier for everybody without Linux knowledge to use my software
starting to get the hang of Linux slowly but Shurely . This will make it easier for everybody without Linux knowledge to use my software
Do you mean the analogue inputs for example wide band ? They currently only display voltage 0-5 volts . They are called AN1 to AN8 for gauge sources . For the sensors just connect the data cable to the bottom USB of the pi
After a lot of try and error i saw that my autoboot hack is not working properly with the latest raspbian image . so i used the one from 09 2014 . Boot time is approx 25 seconds.
I used the latest raspexi source code for this image . The USB port is configured as in the cfg file as /dev/ttyUSB0 So Plug your Datalogit into the bottom USB port (Raspberry Pi model b)
If you want to change anything , you can quit raspexi by pressing "q" or right click and select quit from the dropdown . It might take a few seconds till you see the console after quitting .
at prompt type : Startx to get to the LXDE desktop
The source code for Megatunix is under /home/pi/compile raspexi/MegaTunix/
raspexi is installed in /home/pi/raspexi
to start raspexi while in Desktop mode , open terminal and type
./launchraspexi
if you want to start raspexi from console ( without booting into terminal ) type :
xinit /home/pi/launchraspexi
The image is unfortunately made for a SD card with minimum 16 GB
I haven't had time to check if serial drivers are already loaded by the time the raspexi starts at boot , but will test over the weekend . Should it not work for you , quit raspexi at by pressing q and start after the boot sequence is finished by typing :
xinit /home/pi/launchraspexi
Enjoy playing arround with it on the weekend .
PS please be aware that the dashboard will show incorrect boost ( as i configured the source code to show kg/cm2 but the gauge is still PSI )
Will update the dashboards next week and make them also neater
I used the latest raspexi source code for this image . The USB port is configured as in the cfg file as /dev/ttyUSB0 So Plug your Datalogit into the bottom USB port (Raspberry Pi model b)
If you want to change anything , you can quit raspexi by pressing "q" or right click and select quit from the dropdown . It might take a few seconds till you see the console after quitting .
at prompt type : Startx to get to the LXDE desktop
The source code for Megatunix is under /home/pi/compile raspexi/MegaTunix/
raspexi is installed in /home/pi/raspexi
to start raspexi while in Desktop mode , open terminal and type
./launchraspexi
if you want to start raspexi from console ( without booting into terminal ) type :
xinit /home/pi/launchraspexi
The image is unfortunately made for a SD card with minimum 16 GB
I haven't had time to check if serial drivers are already loaded by the time the raspexi starts at boot , but will test over the weekend . Should it not work for you , quit raspexi at by pressing q and start after the boot sequence is finished by typing :
xinit /home/pi/launchraspexi
Enjoy playing arround with it on the weekend .
PS please be aware that the dashboard will show incorrect boost ( as i configured the source code to show kg/cm2 but the gauge is still PSI )
Will update the dashboards next week and make them also neater
Last edited by Markus1981; Mar 6, 2015 at 02:19 AM. Reason: added how to connect Datalogit




