What to use for DataLogging
Originally Posted by PDXEvo
Read here (http://www.innovatemotorsports.com/s...MA3_Manual.pdf) on page 18. Actually gives you a nice lesson on how to determine timing.
i think the $15.00 is only to register... the software is still free but w/o the registration fee you don't get some 'special services'. Not that I don't think anyone would pay the $15.00 fee, I know I will... I just wish it would be release already.
knowing the amount of time he's spent on the program, Its definitely worth the $15 registration just for his time, he's only looking to recoup the costs of the licensing for some of the GUI components.
I am working on the program all afternoon today, lets see if I can get a version out to you guys asap, my car still needs a new waterpump installed, I took the waterpump off yesterday, struggling to source a new one, hopefully Tuesday I will get the new waterpump on.
It would be good to get my car going to verify the AYC and ABS g-force sensor data. Maybe I can disable those loggers for an initial release.
Check back this afternoon for some new screenshots..
It would be good to get my car going to verify the AYC and ABS g-force sensor data. Maybe I can disable those loggers for an initial release.
Check back this afternoon for some new screenshots..
Evo4mad, thanks again for all your hard work!
I'm not trying to reignite the little VB vs C battle, I just wanted to add that all .NET languages (including VB.NET, which is what it seems this logger is being written in) can be assembled into MSIL, or MicroSoft Intermediate Language. This resulting file can then be run on any machine running the .NET framework (in theory). That is kind of the point of the whole .NET initiative: cross-platform code.
I guess my point is, if the whole logger is written with managed .NET code, it can potentially be ported to Linux because there DO exist various .NET Linux implementations. Evo4mad is the only one who can give us a final answer though...
Sorry if this is unclear, I'm rushing...
I'm pretty sure VB.net was chosen as the host language because it is the easiest to use and get a User interface that people won't ***** about
I guess my point is, if the whole logger is written with managed .NET code, it can potentially be ported to Linux because there DO exist various .NET Linux implementations. Evo4mad is the only one who can give us a final answer though...
Sorry if this is unclear, I'm rushing...
Originally Posted by galvitron
Evo4mad, thanks again for all your hard work!
I'm not trying to reignite the little VB vs C battle, I just wanted to add that all .NET languages (including VB.NET, which is what it seems this logger is being written in) can be assembled into MSIL, or MicroSoft Intermediate Language. This resulting file can then be run on any machine running the .NET framework (in theory). That is kind of the point of the whole .NET initiative: cross-platform code.
I guess my point is, if the whole logger is written with managed .NET code, it can potentially be ported to Linux because there DO exist various .NET Linux implementations. Evo4mad is the only one who can give us a final answer though...
Sorry if this is unclear, I'm rushing...
I'm not trying to reignite the little VB vs C battle, I just wanted to add that all .NET languages (including VB.NET, which is what it seems this logger is being written in) can be assembled into MSIL, or MicroSoft Intermediate Language. This resulting file can then be run on any machine running the .NET framework (in theory). That is kind of the point of the whole .NET initiative: cross-platform code.
I guess my point is, if the whole logger is written with managed .NET code, it can potentially be ported to Linux because there DO exist various .NET Linux implementations. Evo4mad is the only one who can give us a final answer though...
Sorry if this is unclear, I'm rushing...
Originally Posted by evo4mad
It would be good to get my car going to verify the AYC and ABS g-force sensor data. Maybe I can disable those loggers for an initial release.