Jump to content
SAU Community

Recommended Posts

  • Replies 149
  • Created
  • Last Reply

Top Posters In This Topic

it will be no larger than DIN (ie youll be able to fit in DIN, and may even come with DIN bracket, not sure yet)...around 130x40mm + enclosure size (so maybe add a few mm to each dimension)

20x4 instead of 40x2 (as previous one was too long to fit DIN)...same number of characters

trip meter screen (probably be able to provide this on current displays also via firmware update, but v1 displays need to be sent back for that)

buttons on front rather than top (since front is only side u always want to see, means more mounting positions possible). only 2 buttons (as all menus wrap around, so only need "move cursor right" button

using a switching power supply (more efficient, virtually no heat) so no need for the "blob" in cable like last time

probably (wont know till i do it and if it works):

1) logging to sdcard (read via usb)...this will be tricky though

2) firmware updateable via usb (ie download off net like you would modem/bios etc firmware updates)

3) maybe buzzer or something which could eventually be used for alerts/warnings etc.

4) user control of contrast/brightness

  • 8 months later...

sorry anyone who downloaded it before 5:10pm (GMT+10) today would have got a broken file. should be working now

ECUTalk v1.3.3 - Changes from v1.3.3 beta4 below:

  • #42 Removed console output for few users who have a console setup on their PPC
  • #55 Trip meter sensors shouldn't keep 'counting' while car is turned off
  • #58 Prevent 'clicking' show gauges button with keyboard when gauges already shown
  • #69 PPC users can now utilise the 'working area' option and the LTRB option (ini setting)
  • #70 Changed default 100ms max refresh to 40ms (equivalent of 25fps)

Complete list of changes from v1.3.2 on the Version History page.

this looks great, i've never heard of this free consult software

i only know of PLMS and its $200 (laptop)

how do you suggest we make the required cable as shown here?

http://www.ecutalk.com/diyconsult/

Edited by InterCooL

all you need is a usb/serial consult interface (depending on whether ur laptop has serial port or only usb).

plmsdevelopments.com and blazt.biz both have them

also on ebay there's a blazt one:

http://cgi.ebay.com.au/ws/eBayISAPI.dll?Vi...A:IT&ih=008

all you do is turn car on, plug the cable in (make sure u know what com port its using, check out port section in start-run-devmgmt.msc) and then choose the com port in the software and rest should be easy.

the diy cable could only really be made with the diy kit (which ive run out of ages ago), since it has a custom pcb. ill probably get a batch of usb cables done at some point after i finish the consult lcd displays (see group buy forum), probably towards end of year.

  • 1 year later...

ECUTalk v1.3.4 - Changes from v1.3.3 below:

  • #90 Allow user to edit ECU ID for initialisation
  • #93 COM10 and above dont work in ECUTalk

ECUTalk v1.3.5 beta - Changes from v1.3.4 below:

  • #3 User definable warning levels for sensors
  • #99 TB45E engine does not have bank1 injectors, swap with bank2

v1.3.5 beta can be downloaded here: http://www.ecutalk.com/downloads/ECUTalk_v1.3.5_beta.exe

no, pocket pc only. apple are too greedy, they make it far too hard to do something like this on the iphone without paying them a lot of money for the 'priviledge'. if apple dont make money from it they arent interested in allowing it to happen.

unfortuately the newer PPC devices with only a USB connector wont work (need access to actual serial port on it to hook up to consult cable via null modem adaptor).

ones which have a USB host port (which would allow it to host peripheral devices like usb consult cable, keyboards, etc) may work with usb consult cable, but majority of newer devices with mini-usb only dont have this

i think something like toshiba portege g900 has usb host (and found forum post explaining how to install USB drivers for FTDI chip which is used in the ecutalk usb cables)

  • 2 months later...

ECUTalk v1.3.5 beta3 which adds proper support for diesel engines, including diesel specific sensors, also update to error codes.

ECUTalk v1.3.5 beta3 - Changes from v1.3.5 beta1 below:

  • #105 Add extra sequential index column to logging
  • #108 Russian language has trouble changing alert values
  • #109 Add basic compatibility for diesels
  • #110 Differentiate between petrol/diesel (as some sensors are shared)
  • #111 Russian Update error codes (for both petrol and diesel)

v1.3.5 beta3 can be downloaded from latest news post here: http://www.ecutalk.com

hey peter i had a bit of an idea the other day. with the performance tests that you can do, could you set it up so that when you hit the start button, instead of it having a count down timer or whatever it does (been a while since i used it), could you just have it go into a prestage type thing and then have the timer start as soon as you start moving? so just have the timer triggered by the speedo

ecutalk software doesnt have performance tests, you're probably mixing it up with something else.

ecutalk display does, and it works as you describe. you hit start, and once car speed is greater than 0, starts timer till you hit the target. once speed drops to 0 it waits again for next time. i imagine this is how i would do it if i add speed test to the software in future

  • 1 month later...

ECUTalk v1.3.5 beta6 has been released, which heaps of switch/solenoid sensors.

ECUTalk v1.3.5 beta6 - Changes from v1.3.5 beta3 below:

  • #18 Display switch/solenoid etc sensors

Of the added switch sensors, 8 are common to petrol/diesel engines, 39 specific to diesel engines, and 39 specific to petrol engines. Each individual engine only supports a subset of these though, around 10-20 on average. ECUTalk v1.3.5 beta6 can be downloaded from latest news post here: ECUTalk

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

    • As I've said elsewhere, I am using the stock intercooler piping path in the engine bay, and a return flow cooler, and making ~250 rwkW (without any effort put into trying to turn it up past there just yet) and expect to be able to make some more, and frankly, I would be perfectly happy with 260-270rwKW. This is peak road Skyline usability territory. You go past there and, sure, the car will snap necks more when it's on boost, but it will also break shit all the time, cost a (even larger) fortune in tyres, etc etc. Anyway, I also do not like the over-the-fan pipe path, and you don't have to do it.
    • I see, honestly I’m not too fussed about the looks. The only reason to go plenum is to make the piping easier instead of the classic over the rad etc. 
    • Not easy to quantify wrt something like how many fractions of a second slower it would be over 0-100. But given that a 250-300rwkW car is able to do that launch sprint in 5-6 sec (and faster with appropriate tyres, and surface)..... giving up as much as a second would feel like torture. A ~450HP capable turbo is not going to make lots of boost in the 2000-3000 rpm range. So, whilst with some boost on hand it will be faster accelerating in that rev range than your engine currently is NA, it will not feel like a fast car until the boost is solidly in. You know what your car feels like right now when you open it up at 2000rpm. if you've ever been in an actual fast car, you will appreciate that the NARB25 is.... not exciting. Well, add some boost and it will be better. But shorten the intake runners and it might not be better at all. It might come out better, but it could end up feeling the same. For me, it's not the 0-X km/h sprints that matter. It is easy to fry the tyres with anything over 200 rwkW. You can't use all the power available in 1st and 2nd anyway, you have to modulate the throttle. What matters is how the car reacts when you're driving in traffic in 4th or 5th and have maybe 2000 rpm on board, and you want/need to add some speed quickly, and don't have time for the downshift. It won't make boost, it will be all NA (at the speeds we're talking about - remember how fast you're going at 2000 in 4th! and don't plan on breaking the limit by too much.) So giving away NA torque is not what I would consider practical for a street car. And retaining that NA torque builds boost faster which makes the car faster. The flashy plenum is not actually better, unless you're looking at a track car where you can keep it on the boil all the time.  
    • So how much difference does it make you think? Like 1 second in the 0-100?  I was have smaller turbo so hopefully that spools quick GTX2871.  currently it’s NA so you can imagine pretty slow, but I do want fast accusation a little as there’s not many places I’ll be driving where I go over 80 even near me. So 0-60 and 0-80 targets   
    • Short inlet runners cost quite a bit. Dulls off the off-boost torque, and delays boost onset, because arrival of boost is driven by gas flow is a product of the ability to flow air which is torque. This is the reason that the stock manifolds have longer runners. On a 3L, or bigger, you can usually accept the compromise of giving away some torque because the extra capacity gives you a little extra to waste. But on a smaller motor, there's not a lot there to start with. Example, I swapped RB20 out of my R32, 25NeoDET in its place. The "wall of torque" that I experienced afterwards made it all worthwhile. That's because I came from RB20 land where torque is not a thing. But I would not do anything, anything at all, to reduce the low/mid torque I have now, because I remember what it is like to not have it!
×
×
  • Create New...