Jump to content
SAU Community

Recommended Posts

ive released an update to the pocket pc edition which fixes the logging frequency (now its as often as pda can handle, ie as many log packets as sensor updates on screen, depends on speed of ur pda), and also creates seperate file each time for logging)

http://www.ecutalk.com

  • Replies 149
  • Created
  • Last Reply

Top Posters In This Topic

  • 1 month later...

ECUTalk v1.2 - http://www.ecutalk.com/

Combined Standard and Pocket PC versions into the single unified executable (single .exe also), based off the last Pocket PC release.

Added auto connect back in - it will connect on the given com port, select the sensors, and view gauges fullscreen on startup (after its set up).

Added in injector duty cycle % sensors, and added MPH and degrees F sensors (for speed/temp).

Left: Running on PC/Laptop

Right: Running on Pocket PC

ecutalk_v1.2_sensors.jpg

More screenshots: http://www.ecutalk.com/screenshots.aspx

nah, you'll need a pocket pc. palms are the poor mans pocket pc :spank:

i think theres some software written for a palm out there somewhere called "palmz" this guy wrote it: http://ecu2.forumwise.com/profile.php?mode...ofile&u=440

on that note, i picked up a h2210 on ebay for $40 :dry: (though it has nearly all non-essential bits missing and bluetack/tape needed to hold battery in, but it works!)

rz1710 ipaqs can be found a bit over 100$, might be a reasonable upgrade

Edited by NewKleer

NewKleer, i need to get a new boost controller, and some other bits first, plus i am running out of places to mount this stuff. LOL. I think a lappy will do for now, the wife is riding my nuts cos i spend too much money, Blody women, you can't live with them and you can't shoot them.

a silly question, i take it this does not work on a Palm such as an m515???

if so how, cos i can't get it tp work

what about this?

http://eccs.hybridka.com/viewtopic.php?t=105

  • 3 months later...

ECUTalk v1.3 Released - http://www.ecutalk.com

1) Added ability to log sensors without showing them on gauges (when logging is enabled, checkboxes have a greyed out checkstate, indicated logging only)

2) 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)

3) Colour setup for gauges added. Hard bit for you is coming up with a colour theme that looks ok!

4) Added Instant Fuel Economy Sensor - requires RPM, Injector and Speed kph selected to work

5) Changed DutyCycle/RH Sensors to calculate values from RPM and Injector/RH sensors (therefore requires them to be logged at least to work)

6) Fixed Timestamps when milliseconds are less than 100 (3 digits). Previously they would not have leading zeroes

7) 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).

8) 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.

9) 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.

10) Removed EGT sensor (it's useless, only ever reads 4.98v)

See screenshots below to better understand difference between selecting sensors for gauges (batt, duty, econ, temp) which you check once, and for logging (rpm, injector, speed) which are checked a second time to make them grey. Also shown is how you can set the colour of the gauges yourself.

ecutalk_v1.3_sensors.jpgecutalk_v1.3_coloursetup.jpg

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).

1) Fixed issue in v1.3 and v1.3.1 which meant data packets weren't being dropped when CPU couldn't keep up

2) Increased performance of gauge drawing by ~250% (on my PPC, time to draw a gauge went from ~30ms down to around ~12ms).

3) Changed code to always draw gauges (even if data hasnt changed) in order to result in consistent amount of packets being logged per second.

4) 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).

5) 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.

6) 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.

7) 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).

8) 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).

9) 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.

If I was to have a PDA with the only connection being via USB, would this program still be able to work on the PDA providing I have the following cable:

http://www.blazt.biz/products/images/usblarge.JPG

I've read all 5 pages of this thread, but it's still all a bit confusing. I can't see why this wouldn't work?

Please let me know.

Thanks,

Richard.

i can see two reasons:

1) your PDA most likely does not have USB host capabilities (ie, its not able to have usb devices connect to it - its only able to act as a usb device to a PC)

2) the current usb blazt cable is based off a usb/serial converter which has no virtual com port drivers for windows ce (ie pocket pc/windows mobile)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Similar Content

  • Latest Posts

    • Did this end up working? Did you take some pictures?
    • And finally, the front lower mount. It was doubly weird. Firstly, the lower mount is held in with a bracket that has 3 bolts (it also acts as the steering lock stop), and then a nut on the shock lower mount itself. So, remove the 3x 14mm head bolts , then the 17mm nut that holds the shock in. From there, you can't actually remove the shock from the lower mount bolt (took me a while to work that out....) Sadly I don't have a pic of the other side, but the swaybar mounts to the same bolt that holds the shock in. You need to push that swaybar mount/bolt back so the shock can be pulled out past the lower control arm.  In this pic you can see the bolt partly pushed back, but it had to go further than that to release the shock. Once the shock is out, putting the new one in is "reverse of disassembly". Put the top of the shock through at least one hole and put a nut on loosely to hold it in place. Put the lower end in place and push the swaybar mount / shock bolt back in place, then loosely attach the other 2 top nuts. Bolt the bracket back in place with the 14mm head bolts and finally put the nut onto the lower bolt. Done....you have new suspension on your v37!
    • And now to the front.  No pics of the 3 nuts holding the front struts on, they are easy to spot. Undo 2 and leave the closest one on loosely. Underneath we have to deal with the wiring again, but this time its worse because the plug is behind the guard liner. You'll have to decide how much of the guard liner to remove, I undid the lower liner's top, inside and lower clips, but didn't pull it full off the guard. Same issue undoing the plug as at the rear, you need to firmly push the release clip from below while equally firmly gripping the plug body and pulling it out of  the socket. I used my fancy electrical disconnect pliers to get in there There is also one clip for the wiring, unlike at the rear I could not get behind it so just had to lever it up and out.....not in great condition to re-use in future.
    • Onto the rear lower shock mount. It's worth starting with a decent degrease to remove 10+ years of road grime, and perhaps also spray a penetrating oil on the shock lower nut. Don't forget to include the shock wiring and plug in the clean.... Deal with the wiring first; you need to release 2 clips where the wiring goes into the bracket (use long nose pliers behind the bracket to compress the clip so you can reuse it), and the rubber mount slides out, then release the plug.  I found it very hard to unplug, from underneath you can compress the tab with a screwdriver or similar, and gently but firmly pull the plug out of the socket (regular pliers may help but don't put too much pressure on the plastic. The lower mount is straightforward, 17mm nut and you can pull the shock out. As I wasn't putting a standard shock back in, I gave the car side wiring socket a generous gob of dialectric grease to keep crap out in the future. Putting the new shock in is straightforward, feed it into at least 1 of the bolt holes at the top and reach around to put a nut on it to hold it up. Then put on the other 2 top nuts loosely and put the shock onto the lower mounting bolt (you may need to lift the hub a little if the new shock is shorter). Tighten the lower nut and 3 upper nuts and you are done. In my case the BC Racing shocks came assembled for the fronts, but the rears needed to re-use the factory strut tops. For that you need spring compressors to take the pressure off the top nut (they are compressed enough when the spring can move between the top and bottom spring seats. Then a 17mm ring spanner to undo the nut while using an 8mm open spanner to stop the shaft turning (or, if you are really lucky you might get it off with a rattle gun).
    • You will now be able to lift the parcel shelf trim enough to get to the shock cover bolts; if you need to full remove the parcel shelf trim for some reason you also remove the escutcheons around the rear seat release and you will have to unplug the high stop light wiring from the boot. Next up is removal of the bracket; 6 nuts and a bolt Good news, you've finally got to the strut top! Remove the dust cover and the 3 shock mount nuts (perhaps leave 1 on lightly for now....) Same on the other side, but easier now you've done it all before
×
×
  • Create New...