Graham Rudd

If only I could have fitted my TC from the comfort of a chair! Heaven! No such luck, hours of leaning over the side of the car bruising ribs. Smacking my head off various protrusions and fighting with the two nanometres of slack I had in the loom was my lot. Phil... I'm envious. However I'm never going through that crap again, so I want a field connector ASAP. Matt, if you intend ordering one then I'll definately go for it to share the carriage. Anytime is good for me, the sooner the better. Let me know how you want to arrange payment etc. My e-mail address is [email protected] Graham

I'm interested in getting one Matt, although I need one quite soon as I'm starting a DIY project on my Soop and need easy access to the ECU. I'm not going through the hell that was fitting RLTC again. I'm a big bloke and crouching into that tiny space was NOT a lot of fun.

That does seem a tad expensive, but I think I'm going to have to get one myself. $174 though.... Ouch. Graham

Yep, my stock turbos disintegrated running 1.25 bar. I think my front cat still might have bits of the little buggers rattling about inside it.

Don't mean to upset anyone here, but it may be worth making an enquiry on the 300zx site about a group buy for RLTC. I joined in a group deal with them, got it for £480 including delivery, the fully adjustable system with launch control.

Phil, Where did you get hold of manufacturer specific tyre data for rolling diameter? I've had a bit of a search, but its like trying to find a very small needle in a very big haystack.

Thats it, I'm going to make a conscious effort to actually read that damned manual!

Phil, Here is a copy of my active .dat file. Graham's DAT file Apologies for a mistake I made earlier, I said I had 245/45 front, they are 245/40. (However I had entered them correctly in the TC unit)

Ash, Martin Thanks for the info, certainly a good starting point. Ash what is ALLDATA ? Thanks Graham

I was wondering if any of you know where I can find some good info about the ECU connector block. A description of each pin on the connector would be fantastic, but somewhat optimistic I suspect. Any info at all would be greatly appreciated. Thanks Graham

Out of curiosity I took my car out this morning just to see if there were any adverse effects from my slight difference in front to rear wheelspeeds. Unfortunately there is, if I try pulling quite tight turns the RLTC will cut in, even thought the car is definately NOT slipping. Whats pretty irritating about this is that it would seem to indicate that the system is so sensitive, I guess a good thing, that to keep it in its best working order you're going to have to check your front and rear rolling diameters every now and then to compensate for tread wear. I was considering cheating by programming a calibration mode into the TC editor to automatically adjust either the front or rear diameter to compensate for this effect. i.e. get to a straight section of road, run the program, hit calibrate and drive down it for a few seconds. The system then comes up with revised tyre diameter parameters to bring the front and rear wheelspeeds in line with each other. On reflection, this probably isn't a good idea, more a cludge than a solution. Graham

I've double checked my tyre profiles, I've definitely entered everything correctly. Guess I'll have to actually measure them to enter the exact data.

Has anyone got a trace from the traclog.exe that they could zip up and send to me? I want to check someone else's trace to see if I can figure out whats happening. Thanks Graham

Ok, I've got the scroll and zoom feature working in the analysis window. I've examined a longer trace with a nice straight road drive section in it. The two rear wheels speeds match up with each other, as do the two front wheel speeds. So what I get on the trace is a distinct seperation between front and rear wheel speeds. On the face of it I guess this is correct, if the RL unit is just pumping out raw data.

The actual data analysis window is seperated from the main dialog. The small data display shown in the screenshot is only used during real time capture. I guess I was just designing it from the way I would personally use the system, that is capture all of the data then check it out afterwards. Would people find it preferable for the actual data acquisition to also be in a 'normal' window? I.e. one that can be resized and made full screen etc. As to the file load/save/default location/extenstion stuff, yep no problem, I will sort it out. Thanks for the feedback. Graham

Bah! I managed to miss this post last night. If you could chase this up Stu, that would be fantastic. Justin! Are you listening? Not to sure how long I can resist the urge to just buy one though. Graham aka Mr. Impulsive

Well, it would be of limited use to them as I didn't send them the source code, just the exe. I'm WAY to trusting to suspect anyone of nicking anyway.

To be honest I sent a copy of my software to RL a few weeks back. They indicated that they might be willing to buy it. I wrote back and said I wasn't doing it to make money, and (jokingly) if they really wanted to give me something for it then they could swap me for one of their products. After a couple of e-mails from them saying it looked good I heard nothing else. I take this to mean they must be doing their own in-house development and aren't interested in obtaining a copy anymore. Anyway, the point is I'm not really prepared to approach them to ask, given the above assumption then I don't want to be seen to be trying to push mine on them. I'm sure they'll come up with a better system than I have, I'm just proud mine has been used as a tool to provide us with some useful information in the mean time.

Well, my maximum price would be on a sliding scale of what features it has. Obviously the one critical thing it needs from my point of view is an RS232 interface.

Ooo nice... I don't want you to provide me with the image for that one though! :shocked: Actually, what I DO want to do is buy a cheapo GPS with an RS232 port for ~100 quid. Then I'm going to incorporate the feature into the data logging to also plot a 2D map along with the data capture. Hmmm.. the more I think about it the more I wanna do it. Thats it, I'm ordering a GPS tomorrow.

I have 285/30 18" rear, 245/45 18" front. I'm using width*aspect*2+rim diameter for the sizes, I don't have manufacturer's data.

Provide me with a nice top down picture and I'll provide you with a personal copy with it on!

Now you mention they don't, not quite anyway. I am using the the 48 pulses. Maybe this is be because I have different tyres and different wear on the front/back. I hope so anyway.

Yep, it did reach hard cut, if you check the large cyan spikes out you can clearly see the three cut levels, the two huge spikes are hard cut. This little section of data was sampled by planting my foot to the floor coming of a roundabout on a damp road. 1) Yep, there is no problem at all giving the app this. 2) The window shown is the real time capture, the Analyse button on that screen will be used to open up a new window. This window will provide the functionality to zoom, scroll, analyse etc. the data that has been captured, or a file loaded from disk. 3) Maximum time is pretty much an open issue. Assuming a sampling rate of 50Hz, thats 18000 bytes per minute to monitor all 6 channels. So for an hours worth of sampling it would be just over 1Mb. So given this data... you decide. As soon as I'm happy it isn't going to crash anyone's laptop I'll be happy to let anyone who wishes beta test it. Cheers Graham

I've recently started adding a data logging feature to my TC program. The RL unit seems to stop reporting sensible data on any given channel, if that channel's values drop below a certain threshold. I was wondering if this is normal behaviour? Has anyone who has had a play with the software provided by RL (traclog.exe) noticed a similar thing? As an example, my RPM will be flat-lined until they are over ~1100. Just curious, I'm sure it's perfectly normal but I thought I'd better check. Incidently, here's an image for anyone interested in how its going, its the prototype logging window. http://websites.cable.ntl.com/~graham.rudd/datalog.jpg BTW, the crazy cyan trace is the control signal, exaggerated so I can easily check when the TC is cutting in. Thanks Graham