ECU Talk Pocket PC Edition
im not sure - i dont have a s14a to test on personally
ECUTalk v1.3 Released - http://www.ecutalk.com
ECUTalk v1.3 Released - http://www.ecutalk.com
- Added ability to log sensors without showing them on gauges (when logging is enabled, checkboxes have a greyed out checkstate, indicated logging only)
- Logging changed so it logs all packets (only gauges will drop packets/not update when cpu is falling behind, but all packets will be logged)
- Colour setup for gauges added. Hard bit for you is coming up with a colour theme that looks ok!
- Added Instant Fuel Economy Sensor - requires RPM, Injector and Speed kph selected to work
- Changed DutyCycle/RH Sensors to calculate values from RPM and Injector/RH sensors (therefore requires them to be logged at least to work)
- Fixed Timestamps when milliseconds are less than 100 (3 digits). Previously they would not have leading zeroes
- Simplified gauges such that they will only display values within their range (however, logging will show the calculated value) and will no longer auto change their range to suit the values (as occasionally a weird value may be read which causes a unco gauge to be drawn).
- Added an option to allow the full-screen mode to only use the "working area" of the screen. Eg, it wont cover taskbar in a normal windows desktop, and for carpc users with special frontends, it may mean gauges display properly if running ECUTalk from within your frontend.
- Improved the saving of settings to .ini file. Note that the order of items in this .ini file matters - their names (what is shown before the ":") does not. Eg autoconnect, logging, selected sensors, working area option, injector size, gauge colours, etc are all stored in here.
- Removed EGT sensor (it's useless, only ever reads 4.98v)
bad translation 
ECUTalk v1.3 - http://www.ecutalk.com
ECUTalk v1.3 - http://www.ecutalk.com
- kann Sensoren loggen, ohne auf Lehre darzustellen
- vermißt die Protokollierung nicht Daten mit langsamer CPU (z.B. Pocket PC)
- deine eigenen Lehre Farben verursachen.
- addierter sofortiger Brennstoffersparnis-Sensor - erfordert U/min, Injektor und Geschwindigkeit das kph, das vorgewählt wird, um zu arbeiten
- errechnen DutyCycle/RH Sensoren Werte von U/min und von den Injector/RH Sensoren (also von ihnen für die Protokollierung oder die Lehren vorgewählt werden müssen, damit es arbeitet)
- reparierte Zeitstempel in den Maschinenbordbüchern, wenn Millisekunden kleiner als 100 sind (3 Stellen). Vorher würden sie nicht führende null haben
- zeigen vereinfachte Lehren also sie nur Werte innerhalb ihres Bereiches (jedoch, zeigt die Protokollierung den errechneten Wert) an und nicht mehr ändern automatisch ihre Strecke, um den Werten zu entsprechen (manchmal verursacht ein ungewöhnlicher Wert falsche Lehre Zeichnung).
- Wahl, damit auf dem ganzen Bildschirmmodus den „Funktion Bereich“ des Schirmes verwendet (anstatt des vollständigen Schirmes)
- verbesserte die Einsparung der Einstellungen zur .ini Akte.
- entfernter Abgastemperatur Sensor (es ist unbrauchbar, nur überhaupt 4.98v anzeigt)
ECUTalk v1.3.2 Released - http://www.ecutalk.com
This version fixes a few bugs and has some pretty big performance improvements.
Users of v1.3 and v1.3.1 should update to this version.
v.1.3.1 added a MPG sensor for Imperial users (and an option to switch between Imperial/Metric sensors).
Dieses ist die beste Version, erhalten sie!
Frequenz der Protokollierung groß verbessert
Die addierte Gauge "Minimum erneuert Ms" Wahl
This version fixes a few bugs and has some pretty big performance improvements.
Users of v1.3 and v1.3.1 should update to this version.
v.1.3.1 added a MPG sensor for Imperial users (and an option to switch between Imperial/Metric sensors).
- Fixed issue in v1.3 and v1.3.1 which meant data packets weren't being dropped when CPU couldn't keep up
- Increased performance of gauge drawing by ~250% (on my PPC, time to draw a gauge went from ~30ms down to around ~12ms).
- Changed code to always draw gauges (even if data hasnt changed) in order to result in consistent amount of packets being logged per second.
- Added option to specify minimum gauge update speed - higher value means more packets are logged due to less gauge updates (and hence more time for logging). Eg on my 568 Jornada PocketPC 2002, 10ms = ~5 packets logged/second, whereas 1000ms = close to full 50 packets). The setting ignored when not logging (it will just update as quickly as possible).
- Improved consult streaming to allow more data to be read in and processed (rather than lost). Probably the best program for data logging due to the sheer amount of data able to be read in. On my desktop PC, setting minimum gauge refresh to 0ms (ie never skip a gauge redraw, hence uses most CPU), can log 35 packets/second of all sensors. Setting minimum refresh to just 50ms gives the full 50 packets/second. I compared this to Nissan Datascan, which can only log 16 packets/second on the same PC (and thats without gauges shown at all) with the same sensors.
- Changed options controls to dropdowns rather than textboxes (i didnt realise id disabled the use of the soft input panel on PPC, so you couldnt change settings). If you want to enter a value other than shown, edit the .ini file.
- Fixed logging time output, both to add in the missing leading zeros (eg it would show 7:5:7 for 7:05:07), and also added in a interpolated millisecond value for PPC users (which doesnt have a millisecond capability in standard time object).
- Minor changes to individual sensors to better display on gauges, and slight changes to change config (units shown next to sensor rather than down bottom as often the units would overlap gauge).
- Added a hidden option for CarPC users with frontends (eg Centrafuse) to manually edit .ini file to set custom top/bottom/left/right co-ordinates for full-screen mode. Example: FullScreenBounds_L|T|R|B:10|20|1000|900. Setting all to 0 will use default method.
Dieses ist die beste Version, erhalten sie!
Frequenz der Protokollierung groß verbessert
Die addierte Gauge "Minimum erneuert Ms" Wahl
-
MichaS14a
- Vielschreiber
- Posts: 4476
- Joined: 09.04.2004, 17:53
- Location: Südniedersachsen / Nordhessen
- Contact:
Very nice! :heiss: :respekt:
It's sounds like the version 1.3.x is a real major release update.
I will test the new version today on my PDA. The only problem is that my car is in winter sleep but I think ECUTalk will log the sensor values if the ecu has power wether the motor is running or not. The only thing is that the log-file will be very boring.
It's sounds like the version 1.3.x is a real major release update.
I will test the new version today on my PDA. The only problem is that my car is in winter sleep but I think ECUTalk will log the sensor values if the ecu has power wether the motor is running or not. The only thing is that the log-file will be very boring.
98'er S14a, mit ein paar Modifikationen
yeh it just needs ign power on. you can use accelerator pedal (and that might change some of the other sensor values) but not that exciting. will be good to know how many packets of data per second it can log too.
and i dont know why ive been using this old jornada 568 for so long...just tried some performance tests with H2210:
568 Jornada, 100ms refresh
5 packets/second
568 Jornada, 150ms refresh
17 packets/second
568 Jornada, 250ms refresh
31 packets/second
iPAQ H2210, 0ms refresh
20 packets/second
iPAQ H2210, 100ms refresh
48 packets/second
the big difference is probably the .net compact framework installed in the ROM (rather than in RAM on PPC 2002)
that was with 6 sensors on gauges (afm, batt, duty cycle, o2, water temp, economy) and 4 others (afm, inj, speed, timing) on logging only.
48 packets/second is the maximum amount of data sent for those sensors on this ecu, so the fact a H2210 can max it out with gauges updating 10 times/second is pretty good
and i dont know why ive been using this old jornada 568 for so long...just tried some performance tests with H2210:
568 Jornada, 100ms refresh
5 packets/second
568 Jornada, 150ms refresh
17 packets/second
568 Jornada, 250ms refresh
31 packets/second
iPAQ H2210, 0ms refresh
20 packets/second
iPAQ H2210, 100ms refresh
48 packets/second
the big difference is probably the .net compact framework installed in the ROM (rather than in RAM on PPC 2002)
that was with 6 sensors on gauges (afm, batt, duty cycle, o2, water temp, economy) and 4 others (afm, inj, speed, timing) on logging only.
48 packets/second is the maximum amount of data sent for those sensors on this ecu, so the fact a H2210 can max it out with gauges updating 10 times/second is pretty good
-
MichaS14a
- Vielschreiber
- Posts: 4476
- Joined: 09.04.2004, 17:53
- Location: Südniedersachsen / Nordhessen
- Contact:
Code: Select all
that was with 6 sensors on gauges (afm, batt, duty cycle, o2, water temp, economy) and 4 others (afm, inj, speed, timing) on logging only. One question: How you have measured the "packets per second-value"? Have you count the entries in the log-file with excel?
98'er S14a, mit ein paar Modifikationen
yep exactly - just the average number of packets in a given second. ie count all the packets for a random second. eg:
in this case there is 43 (this is H2210, 100ms i just tried in my car then). one thing to note (you may have already noticed this before) is that the ECU doesnt update the speed reading too often - sometimes it takes half a second or so to update
Time, RPM, Timing, Air Flow, O2 Sensor, Injector, Battery, Duty Cycle, Speed kph, Water Temp C, Econ L/100km
08:31:43.000, 4162, 4, 3.92, 0.89, 19.03, 13.68, 66, 46, 73, 86
08:31:43.020, 4212, 4, 3.94, 0.89, 18.93, 13.68, 66, 46, 73, 86.6
08:31:43.040, 4288, 4, 3.98, 0.9, 18.93, 13.76, 67, 46, 73, 88.2
08:31:43.060, 4375, 5, 3.99, 0.9, 18.97, 13.68, 69, 56, 73, 74.1
08:31:43.080, 4412, 5, 4.01, 0.9, 19.07, 13.68, 70, 56, 73, 75.1
08:31:43.100, 4412, 5, 4.03, 0.9, 19.22, 13.68, 70, 56, 73, 75.7
08:31:43.120, 4438, 5, 4.04, 0.9, 19.15, 13.68, 70, 56, 73, 75.8
08:31:43.140, 4475, 5, 4.04, 0.9, 19.17, 13.68, 71, 56, 73, 76.5
08:31:43.160, 4512, 6, 4.04, 0.9, 19.43, 13.6, 73, 56, 73, 78.2
08:31:43.180, 4488, 6, 4.05, 0.9, 19.48, 13.68, 72, 56, 73, 78
08:31:43.200, 4525, 6, 4.06, 0.9, 19.4, 13.68, 73, 56, 73, 78.3
08:31:43.220, 4562, 7, 4.07, 0.9, 19.74, 13.68, 75, 56, 73, 80.4
08:31:43.240, 4600, 7, 4.08, 0.9, 19.87, 13.68, 76, 56, 73, 81.6
08:31:43.260, 4575, 7, 4.11, 0.9, 19.93, 13.68, 75, 56, 73, 81.4
08:31:43.280, 4600, 7, 4.11, 0.89, 20.31, 13.68, 77, 56, 73, 83.4
08:31:43.300, 4612, 7, 4.11, 0.9, 20.45, 13.68, 78, 56, 73, 84.2
08:31:43.320, 4662, 7, 4.12, 0.9, 20.77, 13.68, 80, 56, 73, 86.4
08:31:43.340, 4662, 7, 4.12, 0.9, 21.39, 13.68, 83, 56, 73, 89
08:31:43.360, 4662, 7, 4.12, 0.9, 21.25, 13.68, 82, 56, 73, 88.4
08:31:43.380, 4675, 7, 4.12, 0.9, 21.26, 13.68, 82, 56, 73, 88.7
08:31:43.400, 4700, 7, 4.12, 0.9, 21.36, 13.68, 83, 56, 73, 89.6
08:31:43.420, 4738, 7, 4.11, 0.9, 20.92, 13.68, 82, 56, 73, 88.4
08:31:43.440, 4738, 7, 4.1, 0.9, 20.87, 13.68, 82, 56, 73, 88.2
08:31:43.460, 4712, 8, 4.08, 0.91, 20.16, 13.68, 79, 56, 73, 84.8
08:31:43.480, 4762, 9, 4, 0.91, 19.44, 13.68, 77, 56, 73, 82.6
08:31:43.500, 4788, 9, 3.88, 0.91, 18.13, 13.68, 72, 56, 73, 77.5
08:31:43.520, 4512, 13, 3.3, 0.82, 12.61, 13.68, 47, 56, 73, 50.8
08:31:43.540, 4438, 20, 2.87, 0.74, 7.06, 13.68, 26, 56, 73, 27.9
08:31:43.560, 4412, 26, 2.6, 0.67, 4.19, 13.76, 15, 56, 73, 16.5
08:31:43.580, 4388, 30, 2.48, 0.65, 3.39, 13.76, 12, 56, 73, 13.2
08:31:43.600, 4338, 30, 2.33, 0.64, 2.84, 13.76, 10, 56, 73, 10.9
08:31:43.620, 4275, 30, 2.58, 0.64, 3.15, 13.84, 11, 56, 73, 12
08:31:43.640, 4225, 30, 2.33, 0.64, 3.34, 13.84, 11, 56, 73, 12.5
08:31:43.660, 4175, 30, 2.44, 0.64, 2.67, 13.84, 9, 56, 73, 9.9
08:31:43.680, 4125, 30, 2.63, 0.65, 2.75, 13.84, 9, 56, 73, 10.1
08:31:43.700, 4100, 30, 2.72, 0.68, 2.99, 13.84, 10, 56, 73, 10.9
08:31:43.720, 4038, 30, 2.33, 0.69, 3.12, 13.84, 10, 66, 73, 9.5
08:31:43.740, 3988, 30, 2.31, 0.7, 2.97, 13.84, 9, 66, 73, 8.9
08:31:43.760, 3950, 30, 2.52, 0.7, 2.9, 13.92, 9, 66, 72, 8.6
08:31:43.780, 3912, 30, 2.58, 0.7, 3, 13.92, 9, 66, 72, 8.8
08:31:43.800, 3862, 30, 2.22, 0.71, 3.07, 13.92, 9, 66, 72, 8.9
08:31:43.820, 3825, 30, 1.92, 0.71, 2.84, 13.92, 9, 66, 72, 8.2
08:31:43.840, 3775, 30, 2.11, 0.71, 2.55, 13.92, 8, 66, 72, 7.2
08:31:44.000, 3725, 30, 2.4, 0.7, 2.51, 13.92, 7, 66, 72, 7
or count lines for a whole minute and divide by 60. for me, i did 2861 lines in a minute, = 47.7 packets/second average.
you can also see the "guess" at the milliseconds - in this case it was guessing 50 packets/sec = 20ms increment, but it only got up to 840 before the next second started (it will continually adjust the increment so its "roughly" right, or close enough to it.
in this case there is 43 (this is H2210, 100ms i just tried in my car then). one thing to note (you may have already noticed this before) is that the ECU doesnt update the speed reading too often - sometimes it takes half a second or so to update
Time, RPM, Timing, Air Flow, O2 Sensor, Injector, Battery, Duty Cycle, Speed kph, Water Temp C, Econ L/100km
08:31:43.000, 4162, 4, 3.92, 0.89, 19.03, 13.68, 66, 46, 73, 86
08:31:43.020, 4212, 4, 3.94, 0.89, 18.93, 13.68, 66, 46, 73, 86.6
08:31:43.040, 4288, 4, 3.98, 0.9, 18.93, 13.76, 67, 46, 73, 88.2
08:31:43.060, 4375, 5, 3.99, 0.9, 18.97, 13.68, 69, 56, 73, 74.1
08:31:43.080, 4412, 5, 4.01, 0.9, 19.07, 13.68, 70, 56, 73, 75.1
08:31:43.100, 4412, 5, 4.03, 0.9, 19.22, 13.68, 70, 56, 73, 75.7
08:31:43.120, 4438, 5, 4.04, 0.9, 19.15, 13.68, 70, 56, 73, 75.8
08:31:43.140, 4475, 5, 4.04, 0.9, 19.17, 13.68, 71, 56, 73, 76.5
08:31:43.160, 4512, 6, 4.04, 0.9, 19.43, 13.6, 73, 56, 73, 78.2
08:31:43.180, 4488, 6, 4.05, 0.9, 19.48, 13.68, 72, 56, 73, 78
08:31:43.200, 4525, 6, 4.06, 0.9, 19.4, 13.68, 73, 56, 73, 78.3
08:31:43.220, 4562, 7, 4.07, 0.9, 19.74, 13.68, 75, 56, 73, 80.4
08:31:43.240, 4600, 7, 4.08, 0.9, 19.87, 13.68, 76, 56, 73, 81.6
08:31:43.260, 4575, 7, 4.11, 0.9, 19.93, 13.68, 75, 56, 73, 81.4
08:31:43.280, 4600, 7, 4.11, 0.89, 20.31, 13.68, 77, 56, 73, 83.4
08:31:43.300, 4612, 7, 4.11, 0.9, 20.45, 13.68, 78, 56, 73, 84.2
08:31:43.320, 4662, 7, 4.12, 0.9, 20.77, 13.68, 80, 56, 73, 86.4
08:31:43.340, 4662, 7, 4.12, 0.9, 21.39, 13.68, 83, 56, 73, 89
08:31:43.360, 4662, 7, 4.12, 0.9, 21.25, 13.68, 82, 56, 73, 88.4
08:31:43.380, 4675, 7, 4.12, 0.9, 21.26, 13.68, 82, 56, 73, 88.7
08:31:43.400, 4700, 7, 4.12, 0.9, 21.36, 13.68, 83, 56, 73, 89.6
08:31:43.420, 4738, 7, 4.11, 0.9, 20.92, 13.68, 82, 56, 73, 88.4
08:31:43.440, 4738, 7, 4.1, 0.9, 20.87, 13.68, 82, 56, 73, 88.2
08:31:43.460, 4712, 8, 4.08, 0.91, 20.16, 13.68, 79, 56, 73, 84.8
08:31:43.480, 4762, 9, 4, 0.91, 19.44, 13.68, 77, 56, 73, 82.6
08:31:43.500, 4788, 9, 3.88, 0.91, 18.13, 13.68, 72, 56, 73, 77.5
08:31:43.520, 4512, 13, 3.3, 0.82, 12.61, 13.68, 47, 56, 73, 50.8
08:31:43.540, 4438, 20, 2.87, 0.74, 7.06, 13.68, 26, 56, 73, 27.9
08:31:43.560, 4412, 26, 2.6, 0.67, 4.19, 13.76, 15, 56, 73, 16.5
08:31:43.580, 4388, 30, 2.48, 0.65, 3.39, 13.76, 12, 56, 73, 13.2
08:31:43.600, 4338, 30, 2.33, 0.64, 2.84, 13.76, 10, 56, 73, 10.9
08:31:43.620, 4275, 30, 2.58, 0.64, 3.15, 13.84, 11, 56, 73, 12
08:31:43.640, 4225, 30, 2.33, 0.64, 3.34, 13.84, 11, 56, 73, 12.5
08:31:43.660, 4175, 30, 2.44, 0.64, 2.67, 13.84, 9, 56, 73, 9.9
08:31:43.680, 4125, 30, 2.63, 0.65, 2.75, 13.84, 9, 56, 73, 10.1
08:31:43.700, 4100, 30, 2.72, 0.68, 2.99, 13.84, 10, 56, 73, 10.9
08:31:43.720, 4038, 30, 2.33, 0.69, 3.12, 13.84, 10, 66, 73, 9.5
08:31:43.740, 3988, 30, 2.31, 0.7, 2.97, 13.84, 9, 66, 73, 8.9
08:31:43.760, 3950, 30, 2.52, 0.7, 2.9, 13.92, 9, 66, 72, 8.6
08:31:43.780, 3912, 30, 2.58, 0.7, 3, 13.92, 9, 66, 72, 8.8
08:31:43.800, 3862, 30, 2.22, 0.71, 3.07, 13.92, 9, 66, 72, 8.9
08:31:43.820, 3825, 30, 1.92, 0.71, 2.84, 13.92, 9, 66, 72, 8.2
08:31:43.840, 3775, 30, 2.11, 0.71, 2.55, 13.92, 8, 66, 72, 7.2
08:31:44.000, 3725, 30, 2.4, 0.7, 2.51, 13.92, 7, 66, 72, 7
or count lines for a whole minute and divide by 60. for me, i did 2861 lines in a minute, = 47.7 packets/second average.
you can also see the "guess" at the milliseconds - in this case it was guessing 50 packets/sec = 20ms increment, but it only got up to 840 before the next second started (it will continually adjust the increment so its "roughly" right, or close enough to it.
-
MichaS14a
- Vielschreiber
- Posts: 4476
- Joined: 09.04.2004, 17:53
- Location: Südniedersachsen / Nordhessen
- Contact:
Hello @Newkleer!
Here are my results:
HP iPAQ 5550, 0ms refresh
14,7 packets/second
HP iPAQ 5550, 100ms refresh
57,8 packets/second
HP iPAQ 5550, 150ms refresh
63,8 packets/second
HP iPAQ 5550, 250ms refresh
63,9 packets/second
HP iPAQ 5550, 500ms refresh
64,2 packets/second
I have logged the same sensors as you have posted (Timing, Air Flow, O2 Sensor, Injector, Battery, Duty Cycle, Speed kph, Water, Temp C, Econ L/100km) and have shown these 6 sensors: Air Flow, Battery, O2 Sensor, Duty Cycle, Water Temp and Econ.
So I think my PDA is not the slowest one.
You can see that there is no sense to set a higher refresh rate than 150ms with my PDA.
The new version works very well. The only issue I have found was that sometimes ECUTalk does not find all available sensors (mostly the rpm-sensor). In this case I have to close ECUTalk and start it again (without power off/on the ECU!). This is no real problem as I know which sensors are available and must find by ECUTalk.
I am not able to make other tests as I have not started the engine or even drive. This is too bad as I want to test the new economy-function and the new calculation for the duty-cycle-funtion.
I have made the calculations with Excel. I have count the log-entries from 1 minute and devided this by 60. I think this gives the best comparable results.
I can send you the log-files per mail if you wish. They are to big to post it here.
...and they are really boring.
The appended screenshot shows the settings I use to make the log-files for the PDA-speed-calculation.
Greets
Michael
Here are my results:
HP iPAQ 5550, 0ms refresh
14,7 packets/second
HP iPAQ 5550, 100ms refresh
57,8 packets/second
HP iPAQ 5550, 150ms refresh
63,8 packets/second
HP iPAQ 5550, 250ms refresh
63,9 packets/second
HP iPAQ 5550, 500ms refresh
64,2 packets/second
I have logged the same sensors as you have posted (Timing, Air Flow, O2 Sensor, Injector, Battery, Duty Cycle, Speed kph, Water, Temp C, Econ L/100km) and have shown these 6 sensors: Air Flow, Battery, O2 Sensor, Duty Cycle, Water Temp and Econ.
So I think my PDA is not the slowest one.
You can see that there is no sense to set a higher refresh rate than 150ms with my PDA.
The new version works very well. The only issue I have found was that sometimes ECUTalk does not find all available sensors (mostly the rpm-sensor). In this case I have to close ECUTalk and start it again (without power off/on the ECU!). This is no real problem as I know which sensors are available and must find by ECUTalk.
I am not able to make other tests as I have not started the engine or even drive. This is too bad as I want to test the new economy-function and the new calculation for the duty-cycle-funtion.
I have made the calculations with Excel. I have count the log-entries from 1 minute and devided this by 60. I think this gives the best comparable results.
I can send you the log-files per mail if you wish. They are to big to post it here.
...and they are really boring.
The appended screenshot shows the settings I use to make the log-files for the PDA-speed-calculation.
Greets
Michael
You do not have the required permissions to view the files attached to this post.
98'er S14a, mit ein paar Modifikationen