Power FC New Power FC Software RasPexi Viewer
04-10-15, 07:14 AM
#201
Super Raterhater
iTrader: (6)
Join Date: Dec 2001
Location: NY, MA, MI, OR, TX, and now LA or AZ!
Posts: 10,624
Likes: 0
Received 2 Likes
on
2 Posts
It would be doable -- the save formats are extremely easy to work with. You would just need to query the device to get the hardware ID and software ID's to make sure it matches the save. I believe the save nukes the checksum, so you'll have to generate those for each command. Then, you more or less "replay" the save file to the device, checking for the flag 0xF2 after each write.
04-10-15, 11:12 AM
#202
Senior Member
Thread Starter
It would be doable -- the save formats are extremely easy to work with. You would just need to query the device to get the hardware ID and software ID's to make sure it matches the save. I believe the save nukes the checksum, so you'll have to generate those for each command. Then, you more or less "replay" the save file to the device, checking for the flag 0xF2 after each write.
04-10-15, 11:21 AM
#203
Senior Member
Thread Starter
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
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
04-10-15, 11:22 AM
#204
Senior Member
Thread Starter
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):
Raspexi R7
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):
Raspexi R7
04-11-15, 01:48 AM
#205
Junior Member
Join Date: Feb 2015
Location: Sydney, Australia
Posts: 26
Likes: 0
Received 0 Likes
on
0 Posts
haha thanks 
I have pushed another datasource (for release with the next version) for injector duty cycle in percentage. I couldn't find it in the adv_info group or elsewhere so I just calculated it and created the new datasource. It is only for primary injector at the moment and is called `PrimaryInjD`. It's defined as the percentage of ON time which is the millisecond value from `Primaryinp` and one cycle of a four stroke engine calculated from `RPM`.
Let me know if this is suitable for rotary engines or other engines because I'm not sure but can add support if need be.
I have pushed another datasource (for release with the next version) for injector duty cycle in percentage. I couldn't find it in the adv_info group or elsewhere so I just calculated it and created the new datasource. It is only for primary injector at the moment and is called `PrimaryInjD`. It's defined as the percentage of ON time which is the millisecond value from `Primaryinp` and one cycle of a four stroke engine calculated from `RPM`.
Let me know if this is suitable for rotary engines or other engines because I'm not sure but can add support if need be.
04-15-15, 04:35 PM
#206
Very cool project and I (surprisingly) got it up and running without too much trouble once I imaged my Pi2.
While the gauges are nice I've been wanting to use the Pi as more of a DAU (data acquisition unit). Long term I'll be working on taking the datalogit packets and adding a CAN bus wrapper so my RaceCapture Pro can consume the PFC data and I should have everything time-synced.
In the meantime I hacked together a small script to add a timestamp to the CSV log and tried to capture some runs from the SCCA Texas Natl. Tour last weekend, haven't gotten a chance to take a look at them yet.
If anyone's interested I can share the script (super simple though). One issue I know of is that if you don't have an internet connection (or realtime expansion) the timestamp won't be correct, but I should still have a unique log name for each run at the autox.
While the gauges are nice I've been wanting to use the Pi as more of a DAU (data acquisition unit). Long term I'll be working on taking the datalogit packets and adding a CAN bus wrapper so my RaceCapture Pro can consume the PFC data and I should have everything time-synced.
In the meantime I hacked together a small script to add a timestamp to the CSV log and tried to capture some runs from the SCCA Texas Natl. Tour last weekend, haven't gotten a chance to take a look at them yet.
If anyone's interested I can share the script (super simple though). One issue I know of is that if you don't have an internet connection (or realtime expansion) the timestamp won't be correct, but I should still have a unique log name for each run at the autox.
04-15-15, 06:10 PM
#207
Very cool project and I (surprisingly) got it up and running without too much trouble once I imaged my Pi2.
While the gauges are nice I've been wanting to use the Pi as more of a DAU (data acquisition unit). Long term I'll be working on taking the datalogit packets and adding a CAN bus wrapper so my RaceCapture Pro can consume the PFC data and I should have everything time-synced.
In the meantime I hacked together a small script to add a timestamp to the CSV log and tried to capture some runs from the SCCA Texas Natl. Tour last weekend, haven't gotten a chance to take a look at them yet.
If anyone's interested I can share the script (super simple though). One issue I know of is that if you don't have an internet connection (or realtime expansion) the timestamp won't be correct, but I should still have a unique log name for each run at the autox.
While the gauges are nice I've been wanting to use the Pi as more of a DAU (data acquisition unit). Long term I'll be working on taking the datalogit packets and adding a CAN bus wrapper so my RaceCapture Pro can consume the PFC data and I should have everything time-synced.
In the meantime I hacked together a small script to add a timestamp to the CSV log and tried to capture some runs from the SCCA Texas Natl. Tour last weekend, haven't gotten a chance to take a look at them yet.
If anyone's interested I can share the script (super simple though). One issue I know of is that if you don't have an internet connection (or realtime expansion) the timestamp won't be correct, but I should still have a unique log name for each run at the autox.
04-15-15, 07:59 PM
#208
Junior Member
Join Date: Feb 2015
Location: Sydney, Australia
Posts: 26
Likes: 0
Received 0 Likes
on
0 Posts
Perhaps a user defined size in terms of time (e.g. 30mins) in the config file would be good. I might look into it when I next get time.
In regards to X.ProphetEzra.X's script with the time stamp, I believe that Raspexi already adds a formatted time stamp accurate to a thousandth of a second?
The time and date may not be accurate unless you have an internet connection and the raspi's date/time set. Although, it wouldn't be hard to alter the code so the header gets written to the CSV each time Raspexi starts so you can tell when a log was started... (It might even be doing this now, I would have to check, not sure)
04-16-15, 02:04 AM
#209
Senior Member
Thread Starter
This was something I was thinking of as well, otherwise the log file gets too large.
Perhaps a user defined size in terms of time (e.g. 30mins) in the config file would be good. I might look into it when I next get time.
In regards to X.ProphetEzra.X's script with the time stamp, I believe that Raspexi already adds a formatted time stamp accurate to a thousandth of a second?
The time and date may not be accurate unless you have an internet connection and the raspi's date/time set. Although, it wouldn't be hard to alter the code so the header gets written to the CSV each time Raspexi starts so you can tell when a log was started... (It might even be doing this now, I would have to check, not sure)
Perhaps a user defined size in terms of time (e.g. 30mins) in the config file would be good. I might look into it when I next get time.
In regards to X.ProphetEzra.X's script with the time stamp, I believe that Raspexi already adds a formatted time stamp accurate to a thousandth of a second?
The time and date may not be accurate unless you have an internet connection and the raspi's date/time set. Although, it wouldn't be hard to alter the code so the header gets written to the CSV each time Raspexi starts so you can tell when a log was started... (It might even be doing this now, I would have to check, not sure)
They cheap and come are equipped with a battery , much like your PC at home . A Example can be found here
Mini RTC Module for Raspberry Pi | The Pi Hut
https://www.abelectronics.co.uk/prod...y-Pi/15/RTC-Pi
Raspexi already puts a time stamp on the log and each line contains date and time . I agree with you that it would make sense to somehow be more in control of how big the file should be or how long the logging window should be .
A aditional idea would be that raspexi looks at startup , if there is already a existing file in the logging folder eg *.csv and if yes creates a new one and calls it "name_defined_in_CFG_"_"Date&starttime".csv
This would prevent that the log file grows each time you startup raspexi and drive , it would also make it easier for the user to navigate in the logs .
Alternatively it would also make sense to assign a key to start and stop logging .
It could be linked to a new datasource called log and display a 1 for active and a 0 for not active . Therefore the user can start and stop his logs whenever he wants and also have a visual confirmation on the screen if logging is active or not.
Just my thoughts on this :-)
04-20-15, 12:55 PM
#210
A aditional idea would be that raspexi looks at startup , if there is already a existing file in the logging folder eg *.csv and if yes creates a new one and calls it "name_defined_in_CFG_"_"Date&starttime".csv
This would prevent that the log file grows each time you startup raspexi and drive , it would also make it easier for the user to navigate in the logs .
Alternatively it would also make sense to assign a key to start and stop logging .
It could be linked to a new datasource called log and display a 1 for active and a 0 for not active . Therefore the user can start and stop his logs whenever he wants and also have a visual confirmation on the screen if logging is active or not.
Just my thoughts on this :-)
This would prevent that the log file grows each time you startup raspexi and drive , it would also make it easier for the user to navigate in the logs .
Alternatively it would also make sense to assign a key to start and stop logging .
It could be linked to a new datasource called log and display a 1 for active and a 0 for not active . Therefore the user can start and stop his logs whenever he wants and also have a visual confirmation on the screen if logging is active or not.
Just my thoughts on this :-)
I have a 32Gb sd card for my Pi right now so I'm not terribly worried about log bloat, and I power cycle the Pi before after each autox run in an attempt to limit log size.
Hopefully this week I can take a look at the logs and start correlating them with the GPS/IMU data.
In the future I'd like to use a GPIO pin to start/stop caputure, likely before I get to work on the CAN message part.
Last edited by X.ProphetEzra.X; 04-20-15 at 12:57 PM.
04-21-15, 02:09 AM
#211
Senior Member
Thread Starter
This is basically what I did, I have a small python script that edits the cfg file and changes the last line to add a timestamp to the csv filename.
I have a 32Gb sd card for my Pi right now so I'm not terribly worried about log bloat, and I power cycle the Pi before after each autox run in an attempt to limit log size.
Hopefully this week I can take a look at the logs and start correlating them with the GPS/IMU data.
In the future I'd like to use a GPIO pin to start/stop caputure, likely before I get to work on the CAN message part.
I have a 32Gb sd card for my Pi right now so I'm not terribly worried about log bloat, and I power cycle the Pi before after each autox run in an attempt to limit log size.
Hopefully this week I can take a look at the logs and start correlating them with the GPS/IMU data.
In the future I'd like to use a GPIO pin to start/stop caputure, likely before I get to work on the CAN message part.
You can drop me a PM if you want to be added to the commiters on github . Then you can implement it directly in the source for everyone
04-21-15, 02:47 AM
#212
Senior Member
Thread Starter
Has anyone already worked out the gear judge numbers for the FD ?
I haven't really had time to drive yet , or logs that would be of much use .
If yes , please post your results . Haven't finished my headlights yet so i can't really drive at night at the moment
I haven't really had time to drive yet , or logs that would be of much use .
If yes , please post your results . Haven't finished my headlights yet so i can't really drive at night at the moment
04-25-15, 07:16 AM
#213
Junior Member
Join Date: Aug 2014
Location: Sydney
Posts: 7
Likes: 0
Received 0 Likes
on
0 Posts
The gear judge data source works perfectly with the provided values for my R34 GTT.
For everyone else here is a quick guide that should give you working values.
To calculate your values for the gear data source you can use this program Gearcalc
1Insert all your specs into the top section.
2Make sure metric units are selected.
3Then click calculate.
You should end up with a result like the second picture.
4The only important numbers are the ones in this box
5 Divide the RPM by each of the speeds this will give you the values you need to put in to the gear_judge_nums line.
In my case this was.
Gear| Calculated value | pre programmed values
1st |8000/71 = 113 | 120
2nd |8000/118 = 68 | 70
3rd |8000/175 = 46 | 45
4th |8000/228 = 35 | 35
5th |8000/303 = 26 | 26
As you can see as in the case of my first gear the numbers don't have to be exact to work but the closer the better.
For everyone else here is a quick guide that should give you working values.
To calculate your values for the gear data source you can use this program Gearcalc
1Insert all your specs into the top section.
2Make sure metric units are selected.
3Then click calculate.
You should end up with a result like the second picture.
4The only important numbers are the ones in this box
5 Divide the RPM by each of the speeds this will give you the values you need to put in to the gear_judge_nums line.
In my case this was.
Gear| Calculated value | pre programmed values
1st |8000/71 = 113 | 120
2nd |8000/118 = 68 | 70
3rd |8000/175 = 46 | 45
4th |8000/228 = 35 | 35
5th |8000/303 = 26 | 26
As you can see as in the case of my first gear the numbers don't have to be exact to work but the closer the better.
Last edited by Spud2233; 04-25-15 at 07:23 AM.
04-25-15, 08:38 AM
#214
Junior Member
Join Date: Feb 2015
Location: Sydney, Australia
Posts: 26
Likes: 0
Received 0 Likes
on
0 Posts
The gear judge data source works perfectly with the provided values for my R34 GTT.
For everyone else here is a quick guide that should give you working values.
To calculate your values for the gear data source you can use this program Gearcalc
1Insert all your specs into the top section.
2Make sure metric units are selected.
3Then click calculate.
You should end up with a result like the second picture.
4The only important numbers are the ones in this box
5 Divide the RPM by each of the speeds this will give you the values you need to put in to the gear_judge_nums line.
In my case this was.
Gear| Calculated value | pre programmed values
1st |8000/71 = 113 | 120
2nd |8000/118 = 68 | 70
3rd |8000/175 = 46 | 45
4th |8000/228 = 35 | 35
5th |8000/303 = 26 | 26
As you can see as in the case of my first gear the numbers don't have to be exact to work but the closer the better.
For everyone else here is a quick guide that should give you working values.
To calculate your values for the gear data source you can use this program Gearcalc
1Insert all your specs into the top section.
2Make sure metric units are selected.
3Then click calculate.
You should end up with a result like the second picture.
4The only important numbers are the ones in this box
5 Divide the RPM by each of the speeds this will give you the values you need to put in to the gear_judge_nums line.
In my case this was.
Gear| Calculated value | pre programmed values
1st |8000/71 = 113 | 120
2nd |8000/118 = 68 | 70
3rd |8000/175 = 46 | 45
4th |8000/228 = 35 | 35
5th |8000/303 = 26 | 26
As you can see as in the case of my first gear the numbers don't have to be exact to work but the closer the better.
I feel I should add a few things to this.
The way I calculated the values for my R33 GTSt (which are now the default values in the repo's example config file) were by using the log file, after having been for a drive through all gears, and then dividing the "Engine Speed (RPM)" column by the "Speed (km/h)" column.
If you graph the result it should show flat lines around the value for each gear where you can then pick an average value for each "flat" section.
If people would like to post their logs for different stock vehicles after they've been for a drive through all gears, I can add the values to the config files in the repo for the models.
Now, when I programmed it I made it so that it will use the values in the config file as the "centre" of the region to check. That is to say that if the actual RPM/Speed fluctuates a little it will not be apparent in the Gear datasource as the threshold to change is midway between the values for each gear.
For instance, if RPM / Speed resulted in a value of 60 and the config file was setup as follows:
<table style="border-collapse:collapse;border-spacing:0"><tr><th style="font-family:Arial, sans-serif;font-size:medium;font-weight:bold;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center">Gear</th><th style="font-family:Arial, sans-serif;font-size:medium;font-weight:bold;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center">N</th></tr><tr><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">1st</td><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">120</td></tr><tr></tr><tr><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">2nd</td><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">70</td></tr><tr></tr><tr><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">3rd</td><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">45</td></tr><tr></tr><tr><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">4th</td><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">35</td></tr><tr></tr><tr><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">5th</td><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">26</td></tr><tr></tr></table>
Then the program will check,
Is 60 less than 95 and also is 60 greater than 57.5
if yes then Gear is 2nd
or
if 57.5 < (RPM/Speed) < 95
Gear = 2
95 is half way between N for 1st and 2nd gear from the config file and
57.5 is half way between N for 2nd and 3rd gear from the config file.
I also made it so that if RPM/Speed is less than (for this example) 26/2 then the Gear will be "neutral", which I made equal to zero (0).
Gear will also be "neutral" (for this example) if RPM/Speed is greater than 1.5 x 120.
These would be the numbers the program uses for this example:
<table style="border-collapse:collapse;border-spacing:0"><tr><th style="font-family:Arial, sans-serif;font-size:medium;font-weight:bold;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center">Gear</th><th style="font-family:Arial, sans-serif;font-size:medium;font-weight:bold;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center">N</th><th style="font-family:Arial, sans-serif;font-size:14px;font-weight:normal;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">120 x 1.5</th><th style="font-family:Arial, sans-serif;font-size:14px;font-weight:normal;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">180</th></tr><tr><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">1st</td><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">120</td></tr><tr><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">(120+70)/2</td><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">95</td></tr><tr><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">2nd</td><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">70</td></tr><tr><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">(70+45)/2</td><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">57.5</td></tr><tr><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">3rd</td><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">45</td></tr><tr><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">(45+35)/2</td><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">40</td></tr><tr><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">4th</td><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">35</td></tr><tr><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">(35+26)/2</td><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">30.5</td></tr><tr><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">5th</td><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">26</td></tr><tr><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">26/2</td><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;text-align:center" rowspan="2">13</td></tr><tr><td style="font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal" colspan="2"></td></tr></table>
Last edited by JacobD; 04-25-15 at 08:57 AM.
05-11-15, 08:48 AM
#215
Senior Member
Thread Starter
I was wondering about FC Edit's feature with regards to Anti Lag . My power FC is quite old (version 4.11) and still supports Anti Lag . Does anyone know what command FC Edit sends when anti lag has been enabled and the SW3 is switched on ? Would love to implement this as software switch for people that have a non Datalogit cable with no switch inputs .
05-15-15, 11:50 AM
#216
Senior Member
Thread Starter
Raspexi 7" Touch commander
Sorry for beeing so quiet lately . My old screen quit on me , so i had to order a new one . Decided to go the Touch screen route this time . Ordered me a 7" touch screen from Ebay . It arrived yesterday , so i decided to build me a 7" Touch commander .
First bought a picture frame and cut it to size . Then i made a quick mould of the commander handle and filled it with smooth cast 65D .
I haven't finished it yet , still need to sand it and paint it black , but quite pleased with the result of 1 hour work so far :-) Thought i share my current progress . Will try and set up the touch screen with raspexi and figure out a nice way to run the wires .
First bought a picture frame and cut it to size . Then i made a quick mould of the commander handle and filled it with smooth cast 65D .
I haven't finished it yet , still need to sand it and paint it black , but quite pleased with the result of 1 hour work so far :-) Thought i share my current progress . Will try and set up the touch screen with raspexi and figure out a nice way to run the wires .
05-17-15, 09:36 AM
#217
Senior Member
Thread Starter
Tested my touch commander today stationary .
Will clean up the frame and paint it black next week as well as sorting the routing of the cabling out
Will clean up the frame and paint it black next week as well as sorting the routing of the cabling out
05-22-15, 08:25 PM
#219
i forgot i own an FD
THANK YOU for this awesome project!!!! I finally got it all working for the first time.
Still need to decide on a more permanent display. Also just ordered an accelerometer, and GPS hat w/ RPC from Adafruit.
Still need to decide on a more permanent display. Also just ordered an accelerometer, and GPS hat w/ RPC from Adafruit.
Last edited by namasan; 05-22-15 at 08:30 PM. Reason: fixing url for video...not sure how to embed it
05-24-15, 06:39 AM
#220
Senior Member
Thread Starter
THANK YOU for this awesome project!!!! I finally got it all working for the first time.
Still need to decide on a more permanent display. Also just ordered an accelerometer, and GPS hat w/ RPC from Adafruit.
hello raspexi - YouTube
Still need to decide on a more permanent display. Also just ordered an accelerometer, and GPS hat w/ RPC from Adafruit.
hello raspexi - YouTube
Are you using VNC viewer to show the software on the Ipad ?
I also wanted to do that at one stage , but i see now from your video that there is quite some lag
05-26-15, 10:50 AM
#222
Super Raterhater
iTrader: (6)
Join Date: Dec 2001
Location: NY, MA, MI, OR, TX, and now LA or AZ!
Posts: 10,624
Likes: 0
Received 2 Likes
on
2 Posts
It would be much, much faster to write a dashboard in HTML or native iOS, and then feed the data from the raspberry pi over a web socket or UDP rather than trying something like VNC.
11-03-15, 02:30 PM
#223
Junior Member
iTrader: (1)
Join Date: Jun 2015
Location: Paris
Posts: 8
Likes: 0
Received 0 Likes
on
0 Posts
Hi Markus,
really good job on Raspexi! Can't wait to finally get a PowerFC in my FD to try it for real!
I'm planning on using this touchscreen :
1024 x 600 7 Inch Digital LCD Touch Display Screen With Driver Board Kit For Raspberry Pi Sale-Banggood.com
in a custom single din mount wich allows to put the screen back in in order to get the cleanest interior possible!
i'll keep you updated
thank you,
Nick
really good job on Raspexi! Can't wait to finally get a PowerFC in my FD to try it for real!
I'm planning on using this touchscreen :
1024 x 600 7 Inch Digital LCD Touch Display Screen With Driver Board Kit For Raspberry Pi Sale-Banggood.com
in a custom single din mount wich allows to put the screen back in in order to get the cleanest interior possible!
i'll keep you updated
thank you,
Nick
11-04-15, 10:36 AM
#224
Senior Member
Thread Starter
Originally Posted by ncx94
Hi Markus,
really good job on Raspexi! Can't wait to finally get a PowerFC in my FD to try it for real!
I'm planning on using this touchscreen :
1024 x 600 7 Inch Digital LCD Touch Display Screen With Driver Board Kit For Raspberry Pi Sale-Banggood.com
in a custom single din mount wich allows to put the screen back in in order to get the cleanest interior possible!
i'll keep you updated
thank you,
Nick
really good job on Raspexi! Can't wait to finally get a PowerFC in my FD to try it for real!
I'm planning on using this touchscreen :
1024 x 600 7 Inch Digital LCD Touch Display Screen With Driver Board Kit For Raspberry Pi Sale-Banggood.com
in a custom single din mount wich allows to put the screen back in in order to get the cleanest interior possible!
i'll keep you updated
thank you,
Nick
11-04-15, 12:16 PM
#225
Junior Member
iTrader: (1)
Join Date: Jun 2015
Location: Paris
Posts: 8
Likes: 0
Received 0 Likes
on
0 Posts
Well, unfortunately there's no rush at the moment because i still need to sell my actual HKS Ecu to be able to buy a pfc and datalogit... so it won't be until a few weeks i think ...