ECU Talk Pocket PC Edition
-
MichaS14a
- Vielschreiber
- Posts: 4476
- Joined: 09.04.2004, 17:53
- Location: Südniedersachsen / Nordhessen
- Contact:
Also das ECUTalk läuft auf jedem PDA, der Windows Mobile 2003 und höher hat (bei WM2000 muss noch das .NET Compact Framework 1.0 SP3 Redistributable installiert werden, dann sollte das auch gehen).
Das Kernproblem ist: Der PDA muss eine serielle Schnittstelle anbieten, damit das Nissan-Datenkabel angeschlossen werden kann. Das bietet leider nicht jeder PDA. Meine Hardware und auch die von mir benutzten Adapter habe ich irgendwo weiter vorne gepostet.
Was ich nicht weiss ist, ob die USB-Version des Datenkabels mit einem PDA leichter zu verbinden ist. Dort muss dann ein Adapter PDA-2-USB gekauft werden.
Das Problem ist, dass die PDAs ja nur proprietäre Schnittstellen anbieten, die im Normalfall nur benutzt werden, um den PDA via Craddle mit dem PC zu verbinden um Strom aufzuladen und ein Abgleich mit Outlook zu machen.
So jetzt mache ich Feierabend und werde testen fahren.
Das Kernproblem ist: Der PDA muss eine serielle Schnittstelle anbieten, damit das Nissan-Datenkabel angeschlossen werden kann. Das bietet leider nicht jeder PDA. Meine Hardware und auch die von mir benutzten Adapter habe ich irgendwo weiter vorne gepostet.
Was ich nicht weiss ist, ob die USB-Version des Datenkabels mit einem PDA leichter zu verbinden ist. Dort muss dann ein Adapter PDA-2-USB gekauft werden.
Das Problem ist, dass die PDAs ja nur proprietäre Schnittstellen anbieten, die im Normalfall nur benutzt werden, um den PDA via Craddle mit dem PC zu verbinden um Strom aufzuladen und ein Abgleich mit Outlook zu machen.
So jetzt mache ich Feierabend und werde testen fahren.
98'er S14a, mit ein paar Modifikationen 
-
TurboGrinch
- Vielschreiber
- Posts: 5086
- Joined: 10.04.2004, 11:19
- Vorname: Martin
- Spamabfrage: ein Boot
- Location: Siegburg
- Contact:
-
MichaS14a
- Vielschreiber
- Posts: 4476
- Joined: 09.04.2004, 17:53
- Location: Südniedersachsen / Nordhessen
- Contact:
The new Version works very well.
I have only found minor issues:
- the automatic reconnect if the connection to the ECU ist lost doesn't work anytime. Sometimes the gauges are frozen like the ECUTalk versions before. If I tap on the screen and click "show gauges" again is everything okay: the gauges shows the actual sensor values. On my test drive I have this only once. When I disconnect the datacabel-to-PDA connector by myself wait 2 seconds and put the cable in the PDA, the reconnect is working very well: All gauges will prompt show the actual values. Well done!
- if the connection to the ECU is lost and an automatic reconnect applies there is a reset on the distance counter.
here is an example:
Time RPM Timing Throttle Air Flow AAC O2 Sensor Injector Battery Duty Cycle Speed kph Water Temp C Econ L/100KM Distance Fuel Used Trip L/100KM A/F Base A/F Base SL
56:28,2 5462 20 0,42 2,22 95 0 0,6 13,68 2 208 95 1,7 6,6 1,2 18,3 90 119
56:28,2 5450 20 0,4 2,2 95 0 0,6 13,68 2 208 95 1,7 0 1,2 18,2 90 119
You see: There is a reset from 6,6 driven km to zero in the next protokoll-cycle.
My suggestion ist to hold the last value from the driven distance in the memory (and write it from time to time to the ecutalk.ini e.g. every 5 seconds). Then you have to implement a reset button, like the original short distance counter on the tachometer but this will prevent the complete lost of the value of driven km if the connection to the ECU is lost.
I have append a zip-file of my log from the test drive. Please rename the attachment from .jpg to .zip as this is a restriction of this forum. Try this link: http://www.200sx.name/forum/files/ecuta ... ip_297.jpg
The test drive is done with 555 ccm Nismo-Injectors at maximum pressure of 1,1 bar. The peak value of the injector duty cycle is only 71%. I think this is a good value.
Can I make more different test for you to test something special?
Sorry for my quick and dirty writing but I am now connected only with a modem and not with a broadband connection. I think you are waiting for a replay if your new version works.
I have only found minor issues:
- the automatic reconnect if the connection to the ECU ist lost doesn't work anytime. Sometimes the gauges are frozen like the ECUTalk versions before. If I tap on the screen and click "show gauges" again is everything okay: the gauges shows the actual sensor values. On my test drive I have this only once. When I disconnect the datacabel-to-PDA connector by myself wait 2 seconds and put the cable in the PDA, the reconnect is working very well: All gauges will prompt show the actual values. Well done!
- if the connection to the ECU is lost and an automatic reconnect applies there is a reset on the distance counter.
here is an example:
Time RPM Timing Throttle Air Flow AAC O2 Sensor Injector Battery Duty Cycle Speed kph Water Temp C Econ L/100KM Distance Fuel Used Trip L/100KM A/F Base A/F Base SL
56:28,2 5462 20 0,42 2,22 95 0 0,6 13,68 2 208 95 1,7 6,6 1,2 18,3 90 119
56:28,2 5450 20 0,4 2,2 95 0 0,6 13,68 2 208 95 1,7 0 1,2 18,2 90 119
You see: There is a reset from 6,6 driven km to zero in the next protokoll-cycle.
My suggestion ist to hold the last value from the driven distance in the memory (and write it from time to time to the ecutalk.ini e.g. every 5 seconds). Then you have to implement a reset button, like the original short distance counter on the tachometer but this will prevent the complete lost of the value of driven km if the connection to the ECU is lost.
I have append a zip-file of my log from the test drive. Please rename the attachment from .jpg to .zip as this is a restriction of this forum. Try this link: http://www.200sx.name/forum/files/ecuta ... ip_297.jpg
The test drive is done with 555 ccm Nismo-Injectors at maximum pressure of 1,1 bar. The peak value of the injector duty cycle is only 71%. I think this is a good value.
Can I make more different test for you to test something special?
Sorry for my quick and dirty writing but I am now connected only with a modem and not with a broadband connection. I think you are waiting for a replay if your new version works.
You do not have the required permissions to view the files attached to this post.
98'er S14a, mit ein paar Modifikationen
thanks!
"the automatic reconnect if the connection to the ECU ist lost doesn't work anytime"
can you explain this better? are you saying it never works? the only time it is supposed to automatic reconnect is when it is showing gauges - if you turn off the car, turn it back on again, gauges should start moving again. also it should work if you pull plug while driving then put it back in. or turn off car, turn off pda, then turn pda back on and start car.
if you are not in gauges it wont reconnect itself (its only for when in gauges mode). in my testing, this feature has always worked. you might need to be disconnected for more than 5 seconds for it to always work?
6.6km reset - the problem is here that maximum value of a 16bit number is 65535 (i dont even know why im not using 32bit). divide that by 10000 (which is what i scale by) = 6.5535, ie only a bit above 6.55, which is when it starts rounding to 6.6 (rather than round down to 6.5), thats why it works at 6.6 for a few rows then goes to 0. anyway, thats easily fixed, thanks. it should go up to 6553km before it resets after i fix it
so is the distance accurate? ie how does it compare to your odometer?
assuming normal L/100KM is accurate, then it looks like trip economy is also accurate? i guess fuel used is something youd have to test by starting with a full tank then filling up at the end? but it seems to look ok also?
if you are able to test imperial option (it turn imperial on, restart ecutalk) and see if the same sensors work in miles/mpg
"the automatic reconnect if the connection to the ECU ist lost doesn't work anytime"
can you explain this better? are you saying it never works? the only time it is supposed to automatic reconnect is when it is showing gauges - if you turn off the car, turn it back on again, gauges should start moving again. also it should work if you pull plug while driving then put it back in. or turn off car, turn off pda, then turn pda back on and start car.
if you are not in gauges it wont reconnect itself (its only for when in gauges mode). in my testing, this feature has always worked. you might need to be disconnected for more than 5 seconds for it to always work?
6.6km reset - the problem is here that maximum value of a 16bit number is 65535 (i dont even know why im not using 32bit). divide that by 10000 (which is what i scale by) = 6.5535, ie only a bit above 6.55, which is when it starts rounding to 6.6 (rather than round down to 6.5), thats why it works at 6.6 for a few rows then goes to 0. anyway, thats easily fixed, thanks. it should go up to 6553km before it resets after i fix it
so is the distance accurate? ie how does it compare to your odometer?
assuming normal L/100KM is accurate, then it looks like trip economy is also accurate? i guess fuel used is something youd have to test by starting with a full tank then filling up at the end? but it seems to look ok also?
if you are able to test imperial option (it turn imperial on, restart ecutalk) and see if the same sensors work in miles/mpg
-
MichaS14a
- Vielschreiber
- Posts: 4476
- Joined: 09.04.2004, 17:53
- Location: Südniedersachsen / Nordhessen
- Contact:
No no, the reconnect works very well if I pull the cable out of the PDA, wait 1 or 2 seconds and plug it in again. In every version of ECUTalk I have an issue that sometimes there is no upate anymore on the gauges. the shown values are frozen. Then I tap on the screen to got to the main menu and the only thing I do is to tap on "show gauges". Then the gauges will show the actual values again. It is also possible that I have a loose contact in the adapter from the datacable to PDA-Converter. I will check this.NewKleer wrote:thanks!
"the automatic reconnect if the connection to the ECU ist lost doesn't work anytime"
can you explain this better? are you saying it never works? the only time it is supposed to automatic reconnect is when it is showing gauges - if you turn off the car, turn it back on again, gauges should start moving again. also it should work if you pull plug while driving then put it back in. or turn off car, turn off pda, then turn pda back on and start car.
if you are not in gauges it wont reconnect itself (its only for when in gauges mode). in my testing, this feature has always worked. you might need to be disconnected for more than 5 seconds for it to always work?
Oh okay. I have thought that this will be triggered by loosing contact to the ECU. I don't know that this will be induced by an overflow of a variable. Fine if I can help to find the reason.NewKleer wrote:6.6km reset - the problem is here that maximum value of a 16bit number is 65535 (i dont even know why im not using 32bit). divide that by 10000 (which is what i scale by) = 6.5535, ie only a bit above 6.55, which is when it starts rounding to 6.6 (rather than round down to 6.5), thats why it works at 6.6 for a few rows then goes to 0. anyway, thats easily fixed, thanks. it should go up to 6553km before it resets after i fix it
I the next few days I will test if the calculated values are ok. At the first test I not have payed attention to this. Then I can compare it exactly as I always note my driven km during the tank stops.NewKleer wrote:so is the distance accurate? ie how does it compare to your odometer?
assuming normal L/100KM is accurate, then it looks like trip economy is also accurate? i guess fuel used is something youd have to test by starting with a full tank then filling up at the end? but it seems to look ok also?
NewKleer wrote:if you are able to test imperial option (it turn imperial on, restart ecutalk) and see if the same sensors work in miles/mpg
This I can test very quick. Do you want photos of the screen with imperial gauges?
Bye
98'er S14a, mit ein paar Modifikationen
no photos are needed, just logs are fine
were you saying the no more update on gauges still happened with beta2? let me know if it happens with beta3
-------
http://www.ecutalk.com/downloads/ECUTal ... _beta3.exe
New features in beta3 below, along with a fix for distance sensor resetting after 6.6km.
#14 Add offset option timing so US users can get correct timing readings
#24 Derived sensors should select dependent sensors automatically
#26 Priority option for ECUTalk (eg so mp3 etc play fine)
Also minor change to delays in between commands, may help people who dont always get all sensors detected? Also minor change to consult reading for gauges, to reduce chances of corrupt data being accepted, eg you see all gauges flick to weird values for a second
were you saying the no more update on gauges still happened with beta2? let me know if it happens with beta3
-------
http://www.ecutalk.com/downloads/ECUTal ... _beta3.exe
New features in beta3 below, along with a fix for distance sensor resetting after 6.6km.
#14 Add offset option timing so US users can get correct timing readings
#24 Derived sensors should select dependent sensors automatically
#26 Priority option for ECUTalk (eg so mp3 etc play fine)
Also minor change to delays in between commands, may help people who dont always get all sensors detected? Also minor change to consult reading for gauges, to reduce chances of corrupt data being accepted, eg you see all gauges flick to weird values for a second
-
MichaS14a
- Vielschreiber
- Posts: 4476
- Joined: 09.04.2004, 17:53
- Location: Südniedersachsen / Nordhessen
- Contact:
New Upate with version 1.3.3 beta2 from yesterday:
If I want change from km to miles I have to close ECUTalk and open it again. Then the sensors will be shown in imperial style. I have the assumption that the "Trip MPG"-Value is not calculated correctly. I have append a log file for you: http://www.200sx.name/forum/files/ecuta ... ip_199.jpg Please rename it to .zip.
The logfile itself is a little bit boring as I only jaunted and not drive hard.
I will test the new version 1.3.3 beta3 today and give tomorrow a report.
If I want change from km to miles I have to close ECUTalk and open it again. Then the sensors will be shown in imperial style. I have the assumption that the "Trip MPG"-Value is not calculated correctly. I have append a log file for you: http://www.200sx.name/forum/files/ecuta ... ip_199.jpg Please rename it to .zip.
The logfile itself is a little bit boring as I only jaunted and not drive hard.
I will test the new version 1.3.3 beta3 today and give tomorrow a report.
You do not have the required permissions to view the files attached to this post.
98'er S14a, mit ein paar Modifikationen
yeh it says "restart" in brackets for imperial option because ecutalk needs to be restarted if u change it.
15mpg = ~15.5L/100km, which sounds about right? log file seems to look ok. i should probably change headings to Fuel Used L/Gal so u can see what units it is in log files.
beta3 should be a bit better for fuel used as it shows 2 dec places
15mpg = ~15.5L/100km, which sounds about right? log file seems to look ok. i should probably change headings to Fuel Used L/Gal so u can see what units it is in log files.
beta3 should be a bit better for fuel used as it shows 2 dec places
@NewKleer: @MichS14a is trying to repair his Notebook, so i have the order to post the results for him (f**k Vista 
).
The drivenkilometer-display works good.
The fuel-consumption-display also works good.
The logfiles will be uploaded as soon as possible.
If the gauges are "freezed" the actual sensor-values are written into the logfiles. so if you go to the mainmenue and tap on "show gauges" then the right values are showen again. he see it on the drivenkilometer-display, it is showen the correct value of the driven kilometers.
@MichaS14a is very happy about your program-update.
greetings from
MichaS14a + X-Ray
).The drivenkilometer-display works good.
The fuel-consumption-display also works good.
The logfiles will be uploaded as soon as possible.
If the gauges are "freezed" the actual sensor-values are written into the logfiles. so if you go to the mainmenue and tap on "show gauges" then the right values are showen again. he see it on the drivenkilometer-display, it is showen the correct value of the driven kilometers.
@MichaS14a is very happy about your program-update.
greetings from
MichaS14a + X-Ray
thanks for update
"If the gauges are "freezed" the actual sensor-values are written into the logfiles"
do you mean that when gauges are frozen, the log will still be written to with new values? (but these values arent being shown on gauges?) so the program is still reading data from ecu, just the gauges wont update?
"If the gauges are "freezed" the actual sensor-values are written into the logfiles"
do you mean that when gauges are frozen, the log will still be written to with new values? (but these values arent being shown on gauges?) so the program is still reading data from ecu, just the gauges wont update?