Pocket PC and Tactrix cable
Evolving Member
Joined: Apr 2007
Posts: 195
Likes: 1
From: Slovakia
I cant get ms work on PDA - I will try on PC - whether they are actually retrievable.
The logging speed with your PC logger is cca 9-10 rows per second. The same with PDA is cca 4-5 rows - so the FTDI driver on PDA is relatively slow.
The logging speed with your PC logger is cca 9-10 rows per second. The same with PDA is cca 4-5 rows - so the FTDI driver on PDA is relatively slow.
You need to use the QueryPerformanceCounter stuff. I beleive you need to PInvoke a few functions. Just google ".NET High Performance Timer" and you should get some info.
The Windows.Forms.Timer only has a innacurate timer.
If you need to speed it up you will want to multithread the app and possibly convert to native C.
The Windows.Forms.Timer only has a innacurate timer.
If you need to speed it up you will want to multithread the app and possibly convert to native C.
Evolving Member
Joined: Apr 2007
Posts: 195
Likes: 1
From: Slovakia
The problem with the timer is that it doesnot return any values less than one whole second (even if you ask for milliseconds) - so I do not know what is wrong.
Multithread or native C
my programming skills are not that good
Multithread or native C
my programming skills are not that good
Evolved Member
Joined: Jan 2006
Posts: 953
Likes: 2
From: Oxfordshire
The graphs display fairly reasonable valuse, but there seems to be quite a lot of "noise" in some of the traces. Some of the csv values look Ok IAT, MAP, timing, knock but TPS and RPM are whacked.
Sample rates are pretty poor as Evo828 has noted. I'll make a more coherent investigation soon.
MB
Sample rates are pretty poor as Evo828 has noted. I'll make a more coherent investigation soon.
MB
As a temporary stopgap for the timing thing (until QueryPerformanceTimer), try this:
dim dt as datetime = new datetime(datetime.now.ticks)
outp = dt.tostring("hh:mm:ss.ffff")
'ffff represents the 4 most significant digits of the fractions of a second.
Reference:http://msdn2.microsoft.com/en-us/library/8kb3ddd4.aspx
dim dt as datetime = new datetime(datetime.now.ticks)
outp = dt.tostring("hh:mm:ss.ffff")
'ffff represents the 4 most significant digits of the fractions of a second.
Reference:http://msdn2.microsoft.com/en-us/library/8kb3ddd4.aspx
I should note that for this datetime thing the fractions may be innacurate to the point of being arranged improperly. I would suggest only using hundredths of a second rather than milliseconds when using the System.Windows.Forms.Timer
Evolving Member
Joined: Apr 2007
Posts: 195
Likes: 1
From: Slovakia
As a temporary stopgap for the timing thing (until QueryPerformanceTimer), try this:
dim dt as datetime = new datetime(datetime.now.ticks)
outp = dt.tostring("hh:mm:ss.ffff")
'ffff represents the 4 most significant digits of the fractions of a second.
Reference:http://msdn2.microsoft.com/en-us/library/8kb3ddd4.aspx
dim dt as datetime = new datetime(datetime.now.ticks)
outp = dt.tostring("hh:mm:ss.ffff")
'ffff represents the 4 most significant digits of the fractions of a second.
Reference:http://msdn2.microsoft.com/en-us/library/8kb3ddd4.aspx
LogEntrySeconds
14:51.0
14:52.0
14:52.0
14:52.0
14:52.0
14:53.0
14:53.0
14:53.0
14:54.0
14:54.0
14:54.0
14:55.0
14:55.0
14:55.0
So still not getting anything smaller than a second
This whole thing has been on hold for me as I started working on my carPC, which would eliminate my need for a mobile solution. I will get back to it eventually, but in the meantime the source code is here if anyone wants to pick up and run with it...