It worked!

Post Number:#1 by **Phil-T4** » February 23rd, 2014, 10:27

A while ago i made a comment that i thought i could make a T4, as a proof of concept i wrote a software package to emulate the T4, it worked reasonably well on my test bench so i took a copy of my "T4 Server" software to the Milton Keynes meeting today and tried it out :DD

If performed as well as expected on a diesel so i tried it for the first time on a V6 and it it flew through the engine management system, reading live data, reading and clearing faults without any problem at all!
The other ECU's didnt pose a problem either, so far so good, however as windows is not a real time OS its not the ideal platform so the next step is to transfer my source code over to an embedded device to test a hardware module which should give me the response times required.

Not sure when this will be started but its a very interesting project!

Post Number:#2 by **KDA4G** » February 23rd, 2014, 10:28

Congratulations, Phil - well done!

Share your views on the use of Windows for these type of projects - interested to hear how you got on with the diesel...

Post Number:#3 by **Zeb** » February 23rd, 2014, 10:30

Fantastic work Phil! :-)

That all sounds really promising! Will look forward to updates from you on this!

Post Number:#4 by **Janny** » February 23rd, 2014, 10:32

You've 'made' a T4 ! ... Well done that man :clap:

Post Number:#5 by **Phil-T4** » February 23rd, 2014, 10:47

KDA4G wrote:Congratulations, Phil - well done!

Share your views on the use of Windows for these type of projects - interested to hear how you got on with the diesel...

My test bench (on my sofa) is a diesel version and running the software on this was fine, i could reflash the ECU upto about 80% before another thread took priority, caused a delay in comms and it fails

As you probably know the T4 receives its ethernet frame, unwraps it, transmits, receives, wraps it back up and sends it out again all in a few milliseconds! I am averaging about 200 ms process time from when the frame is received, processed and transmitted back again. However some of the DDE4 responses can take 2 or 3 seconds so these have to be identified and the thread put to sleep for awhile, not a good practice!

The embedded developers kit i have should be able to handle everything, i know an embedded developer who is willing to help, he develops the firmware for electronic steering.

Post Number:#6 by **KDA4G** » February 23rd, 2014, 10:49

Sounds good... no wonder we had a bit of bother with the diesel then.

Post Number:#7 by **Phil-T4** » February 23rd, 2014, 11:01

Janny wrote:You've 'made' a T4 ! ... Well done that man

Well sort of

Its very early stages but the results were promising :-D

Post Number:#8 by **Janny** » February 23rd, 2014, 11:11

Phil-T4 wrote:
Janny wrote:You've 'made' a T4 ! ... Well done that man

Well sort of Its very early stages but the results were promising

I still say "Well done" :clap:

... to even attempt it is more than most of us could comprehend !

Brilliant job old bean. :fingers:

Sounds brilliant. What will this mean to us normal bods? Eventually will we be able to buy a 'T4ish' to play with our own cars?

Big Thumbs up old bean

Will this new T4 be able to cure HGF ? :shrug:

well done Phil, now if you replace can Windows with a Raspberry or similar, you've got it cracked!

Well Done.

Wow, with such dedication, development and devotion, it'll not be long before there is a T4 app available..... :shock:

Mofo wrote:Wow, with such dedication, development and devotion, it'll not be long before there is a T4 app available.....

Sure thing, and then people will start playing around with home-brew software, fuck up their cars, blame us Enthusiasts and/or T4 operators, and so on...