Jump to content

PeterHay205

Members
  • Posts

    45
  • Joined

  • Last visited

Posts posted by PeterHay205

  1. Hi, we run a ST205 in local tarmac rallies (with plug-in TST205 G4X).

    It has finally done a head gasket, so we are getting it checked then rebuilt with bigger cams, e-throttle, larger turbo etc. When discussing with our engine builder, he is keen to have individual cylinder EGTs. I'm thinking the easiest way is to connect the thermocouple probes into an amplifier that goes straight to Canbus (something like this maybe: https://www.ptmotorsport.com.au/product/egt-can-expander/). We can then setup protection like in this thread (\\https://forums.linkecu.com/topic/16732-can-tc-egt-safety-2jz/#comment-106946 - many thanks for the info). 

    We will also have a PowerTune dash hanging off the Canbus and I'd just like to check if there is anything I need to be aware of like:

    - should I put the PowerTune dash on a separate Canbus to the Thermocouple Canbus amplifier (I think the TST205 has more than one canbus?)

    - any other recommendations for a Thermocouple->Canbus amplifier? Given the electronics involved there are lots of things out there that seem really overpriced given what is inside them.

    I'm familiar with Canbus, given I have successfully decoded a handful of Canbus IDs on our GR Yaris (we are using the PowerTune dash to log these when racing whilst we wait for our GT4 to come back to life). 

    Any info much appreciated.

    Regards

    Peter

  2. Hi Simon, we have a ST205 GT4 Celica currently running on a G4X Extreme Plug-in (part no TST205X). The engine has developed either a crack in the block or a head gasket issue, so we are going to be putting a ST215 engine in. I have looked at all the I/O channels required and either the wire-in Extreme G4X or the plug-in TST205X has more than enough to run the engine plus any extras you might need.

  3. Ok - so with a copy of PCLink for the G4+ open on one screen (with my current map loaded) and a second copy of PCLink for the G4X open on the other, it seems I should click through all of the below config items, expand them, and copy all the config across to the G4X. Is that correct?

    image.png.c1b9739e66beb3d6eb42078c9c54a5f8.png

    Is there a quicker way of copying tables across? That looks like it may take forever.  

  4. Hi, I've upgraded from a G4+ wire-in to a G4X pnp and noticed that PCLink won't load the old G4+ map.

    Is there a 'how to' guide or an import tool or something that I can use to copy the appropriate settings across?

  5. Hi - just planning how to connect our Powertune dash to a TST205X we have just started using.

    According to the G4X Extreme quick start guide, CAN 2 is shared with DI9 and DI10. Given we have a plug-in, I'd prefer not to use CAN 2, as we then couldn't use DI9 & 10 as digital inputs (spare DIs are a bit scarse on a plug-in).

    According to the TST205X manual, we can use CAN1, but should probably chop off the Grey and Yellow RS-232 wires so they don't accidentally act as an aerial. 

    Is my understanding correct?

    image.png.1d5ecc6d00036e917a29508ecc0682fb.png

  6. Hi all, we recently got our freshly built 3S-GTE running in our ST185 caged tarmac car. To get it going, we used the two trigger signals from the stock distributor. Now that we have a much smoother idle (thanks Adam), the next step is to switch Trigger 1 to a reluctor CAS with a 36-1 tooth trigger wheel mounted on the crank (for more stable timing).

    In the Trigger 1 settings I have set 'Multi-tooth post' to 'crank' (was previously 'cam'), and set the Tooth Count to 36 (was previously 24). We have set the reluctor nice and close to the wheel, so we have a good strong signal, but we still seem to be getting Trigger errors. 

    I think it maybe just a matter increasing the Trigger Arming Threshold a bit, but not too sure.

    I have attached a copy of the tune (fuel=off deliberately), a triggerscope, and a log.

    Any comments most welcome.

    59-Shelley setup for CAS with fuel off and CAS closer - still no luck.pclr 210307-Shelley triggerscope with CAS sensor much closer still 5 errors.llg 210307-Shelley with CAS sensor much closer -full log.llg

  7. Many thanks Adam - I'll give it a go in the next couple of days.

    Regarding fuelling, the 'master fuel' in our ST205 tune (that I used as a basis for this) was set to 9msec. Given that this engine is running 720cc injectors (compared to the standard 540cc injectors in the ST205), I also reduced 'master fuel' to 6msec in an effort to compensate. I acknowledge this is a bit of a blunt instrument, but the plan is to get it properly tuned soon anyway. Let me know if you think it may be worth bumping that back up to 9msec.

  8. Hi Adam - please find attached (sorry - took me a while to get back to where the car is). It basically started, I had to keep it alive with a few well times stabs at the throttle, and then I let it conk out eventually.

    Apologies for the IAT being stuck at 50 degrees - it is a wiring error that I fixed after taking the log.

    Please let me know of any areas I should be looking at.

    Thanks

    210303-Shelley surging idle PC log.llg

  9. Hi all, we recently managed to fire up our new 3s-gte (installed in a ST185 caged tarmac car). The engine is a pretty standard Gen 2 (as installed in ST185s) engine. Standard compression, standard throttle body and air bypass valve but larger cams (272 from memory). To get it started, we took the tune from our other GT4 (a ST205 with a stock engine that had been tuned by one of the local tuners), altered the I/O to match, and got it going.

    However, the idle seems to surge a fair bit when it is cold to the point where it needs a bit of carefully timed throttle to catch it from stalling. I am no expert in tuning, so I'm not really to sure where to start to get get it to have a stable idle. I have attached the tune file - any pointers on where to look would be welcome.

    55-Shelley change to 3bar GM map sensor.pclr

  10. Possibly.

    When I wired up our 205 originally, I loaded up the Link base map, and it started straight away so I didn't bother checking anything else. We then took it to the tuner, they worked their magic, and we have been running it in events ever since then. 

    I've just loaded up the Link base map, and it shows an Offset of 1 degree. When I got our 205 back from the tuner, it had an offset of -4 degrees (not much different). Given that I had to add 360 degrees to get our new engine to run (with direct spark instead of a distributor), it looks like maybe the base map is out by 360 degrees.

    I am definitely no expert though!

  11. 14 hours ago, Adamw said:

    Try adding 360 deg to your trigger offset, with a distributor it will still run with it being 360out, but with direct spark it wont.  

    Just thinking this through, that means that our ST205 has been running all this time with the timing 360 out, but because of the distributor it will still fire. So basically when the ECU thinks it is firing #1, it actually is firing #4, #3 is firing #2, #4 is firing #1 and #2 is firing #3. I assume that also means that it will be firing the 'wrong' injector as well, but because they are port injectors, there is enough mixture in the manifold to make it all work still?

    I'm wondering if we should also fix the timing on the ST205 and send it back to the tuners to have the mixture checked (once we have the current injectors firing). 

  12. Hi all – we are having trouble getting our newly built 3s-gte running (for a caged ST-185 tarmac car). There is obviously something we have missed, and I’d appreciate any suggestions as to what we should try next. We are running a Link Storm G4+ wired into the stock Toyota loom (ie not using a plug-in).

    The engine is a relatively standard gen2 3S-GTE rebuilt with:

    -       264 degree brian crower cams with shim under bucket

    -       Forged pistons

    -       720 cc injectors

    -       Sard fuel pressure regulator

    -       Generic 3Bar MAP sensor

    -       Bosch Intake Air Temp sensor mounted just inside the manifold (in place of the old cold start injector)

    -       Still using the stock Toyota distributor for timing. The NE signal (24 tooth cam driven CAS) is connected to Trigger 1, and G1 (1 tooth cam driven signal) is connected to Trigger 2.

    -       Using 4 Yaris coilpacks for direct spark

    As a base, we have unplugged the Storm from our running ST205 (has been running fine for about the last 3 years) and used it's tune as our starting point. The ST205 is basically stock (except running 17psi boost) and was tuned by one of the local tuners. The main differences in the setups between the two engines are:

    -       ST205 Cams aren’t as big

    -       ST205 stock injectors are 540cc

    -       ST205 ignition system uses distributor and single coilpack

    We have done a TPS calibration, MAP calibration, and a trigger scope (see attached). I have looked at the trigger arming thresholds (copies from the ST205) and they seem ok (I think?).

    When we crank it over, we get RPM readings of 200 – 250 rpm in PCLink.

    I have only ever seen 1 Trigger 1 error count over the past few days, and both triggers show ‘active’ whilst cranking. So I’m assuming it is getting a correct trigger.

    We have shone a timing light at it during cranking and it is dead on 10 degrees BTDC.

    We have done an ignition test to verify all the 4 coilpacks are firing individually when put into test mode.

    The is a smell of fuel in the exhaust, so we know that we have fuel.

    A couple of days ago, the wires to the distributor were in the process of breaking, and we were getting combustion happening in the dump pipe whilst cranking (as the triggers were all over the place), however we have fixed the distributor wiring, and the attached triggerscope is from today.

    The ST205 map we started with is using ‘Traditional Mode’ for fuelling, with a ‘Master Fuel’ value of 9msec. To account for our larger injectors I have tried 8,7,6,5,4,and 3 msec with no real hint of it starting.

    Our intent is to get it started and idling, then finish the rest of the build, before taking it to our local tuner for a tune.

    I have attached the pclr file for reference.

    Any help would be appreciated, as we have hit the limit of our expertise.

    201231-Shelley Trigger scope after fix distributor plug.JPG

    53-Shelley temp b4 doing set base timing.pclr

  13. On 12/22/2020 at 3:42 PM, Adamw said:

    For basic stuff, I use a free online one called scheme-it, from Digikey.  You just need to set up a log-in.  One of my drawings as an example below.  

    DQ7ATeb.png

    Hi Adam - I have setup an account and the package looks good. You wouldn't happen to have a custom symbol for the Link A and B connectors on the G4+ Storm by any chance? That would save me a lot of time documenting my patch harness.

  14. Can anyone recommend a cheap (ie preferably free) and easy to use schematic drawing package that I can use to document the wiring I have done in our race car? I find myself rifling through scrappy drawings in my notebook trying to remember what I did when I added a fan, or an additional temp sensor etc. I also made up my own patch harness to adapt the Link to the factory wiring, so I would like to properly document that as well. Thanks, Peter

  15. Hi, we are running a Celica GT4 (ST205), that appears to have developed a crack in the block (so engine out, rebuild etc). 
    Whilst we have it in bits, I'm keen to see if we could add an electronic throttle to it. We have a Link G4+ Storm that I wired into the factory harness. As it is not a plug-in, we still have plenty of spare I/O. Adam (or others), are you able to let me know if our Storm is able to drive an e-throttle, or there is an interface box we need in order to do this?

  16. I used an illuminated push-on, push-off switch connected to a DI. When the switch is on, the DI is pulled low and logging is enabled (and the light in the switch is on), off otherwise. Very handy when you are on the start line to be able to glance down and know you have remembered in turn on logging.

×
×
  • Create New...