Jump to content

P38a (re)build


Escape

Recommended Posts

16 hours ago, Bowie69 said:

Even with the mid-engine goodness of the Espirit?

Have we drifted off topic enough yet? 

I certainly don't mind talk about TVR and Lotus. 🙂

Link to comment
Share on other sites

3 hours ago, elbekko said:

Don't remind him of the to-do list, it causes some mild depression :D

I'm way past mild depression!
2 other projects to finish (Phoenix and Emma) and then I'll try and sort the Elan...

And talking about using a Lotus off road, I clearly remember a few of you preventing me from driving that JPS Elan across a muddy parking lot when we needed to empty the trailer for @elbekko's P38. :ph34r:
 

Link to comment
Share on other sites

  • 1 year later...

My god, has it really been a whole year since my last update? Shame on me...

However, some good news! 😎

The Elan was bumped up in the list and is running again after an engine and gearbox rebuild. Running end of December, properly tuned only by early May, due to a new but faulty set of breaker points. And then she was driven to France, where she met her twin: ElanLaon1.thumb.jpg.7a0c179cf853982e1c5a4801e42ae231.jpg

Next month we will be taking her to Silverstone Classic, hope to meet some of you there!

Phoenix is now at the head of the queue, by some margin. And there is actual progress. Thanks in no small part to @elbekko, for his help and especially for making a list of things to do. 🙂 

The engine is almost ready to fire up, just need to sort a weird issue with the firing sequence of the coils. It's MS direct drive to standard RR Bosch coilpacks, I wanted to use GEMS coils but found those difficult to mount on the Bosch inlet. Making an adapter for the wiring loom was less effort than designing and building a decent bracket.

Elektrickery is also almost done, last test this morning showed all lights coming on when they're supposed to and all switches doing what I want (a few I couldn't yet check at this point, for example the EAS). It did take longer than expected, due in no small part to Carling providing identical switches that in fact have different internal wiring for the tell tale lights. Hard to see in the picture, but the one has separate wiring for each LED, the other has both sharing a common ground. Which of course will not work if the switch is used to switch a ground signal! But I had to physically open each switch (so removing all the wiring already installed for a previous test!) to verify. 😟2023-07-1310_49_29.thumb.jpg.5425a5f1e0e7dcb843ee954c39c54faf.jpg2023-07-1310_49_38.thumb.jpg.2a62ca72f94cfd7c75516b74fd239ee7.jpg

By using 2 multi pin connectors it is now also physically possible to get the panel installed in the car. Over 100 connections in total, above shows the last ones that needed to be connected. Very happy to see everything working, not all lights display properly in the picture but they are on. Now just some tidying up to do.2023-07-1117_38_34.thumb.jpg.37eb0683097db2e756ca3dab804f7bc9.jpg

A deadline might have been set for September... Off road camping with 2 good mates.

On to the next item on the list! 🙂

Filip

  • Like 3
Link to comment
Share on other sites

2 hours ago, Escape said:

That's the Silverstone Golf Club camping site, right? We'll be staying in the hotel (don't fancy camping in the Elan!). 🙂

Correct, I'm sure you're welcome to wander over for a poke about in Mike's creation though... unless he's going to drag it into the circuit and put it on the club stand? :ph34r:

  • Like 1
Link to comment
Share on other sites

  • 5 months later...
  • 5 weeks later...
On 1/6/2024 at 11:59 PM, Bowie69 said:

So.... How's progress these days? 

:)

 

Slow, but sometimes occurring :D

Yesterday we spent a bit more time fighting the Megasquirt. Once again trying to map out what the ignition is doing. There was a small build error in the ECU (coils B & C were swapped), that's been rectified in the wiring. But there is more going on :(

Test procedure (ideally for a better test procedure we'd just hook a 4-channel oscilloscope to the coil outputs (and maybe a 5th channel to the VR), but we don't have one of those kicking around at the moment, sadly):

  • Marked TDC on the block
  • Marked TDC on the crank pulley
  • One by one, plug in a spark plug connected to a jump lead for ground
  • With the strobe, check which quadrant that plug is firing in

The test procedure works fine, but we're seeing weird results still. For example #5 firing in multiple quadrants.

In TunerStudioMS we did some logging of the tooth signal, initially this was very inconsistent, and then we found a misconfiguration in the wheel decoder settings, where the B & C trigger points were swapped (probably from experiments a few months ago trying to fix the build error in the software). No bueno because these need to be in order. Rectified this, and got a cleaner signal, but still inconsistent firing.
When exporting the log to CSV, it seems to show (usually) 34 teeth between the missing tooth, which is one too few for 36-1?! And can also only get 2-3 revolutions of a clean 0-34 run, otherwise there's a lot of missing teeth detected and such. Maybe @Escape can attach the CSV logs we took, I don't have them with me.

We also tried modifying the wheel decoder settings to be exactly like the calculator. After fixing the misconfiguration we had these settings:

IMG-20240204-WA0005.thumb.jpg.636ad27c83186e334442e66b32442de9.jpg

We then tried also filling in the return positions, but that seemed worse, barely picking up any teeth at all... so I'm guessing these should just be set to 0?

Not sure where to go from here yet. The VR sensor used is the stock GEMS one. We could try swapping the wires around, but not sure if that would cause this issue?

Help please :rofl:

Link to comment
Share on other sites

19 minutes ago, elbekko said:

When exporting the log to CSV, it seems to show (usually) 34 teeth between the missing tooth, which is one too few for 36-1?! And can also only get 2-3 revolutions of a clean 0-34 run, otherwise there's a lot of missing teeth detected and such. Maybe @Escape can attach the CSV logs we took, I don't have them with me.

We also tried modifying the wheel decoder settings to be exactly like the calculator. After fixing the misconfiguration we had these settings:

Only just started messing about with petrol EFI stuff as Pete knows but electronics I do understand (hence designing my own Speeduino board).

You say you don't have a 4 channel scope on hand - does that imply you have an oscilloscope to hand? If so can you attach it to the VR sensor output and see what that's doing? If the sensor is producing garbage then my guessing is it's game over for MS to try and figure out what's going on (hence the unreliable results).

On Speeduino there's a VR conditioner which cleans up the signal before sending it into the processor, I'm guessing this is built into the MS hardware, if you can figure out where it is then scoping the output of that if the input looks good would also see whether that's behaving itself.

Link to comment
Share on other sites

No, we don't have an oscilloscope in the Workshop. But I'm working on borrowing one. 😉

As for the VR sensor, it was working in the donor vehicle and we also had this MS unit running a similar engine in another P38. But just as a proof of concept, we never analysed the data while running, just happy she started. The sensor we're now using is the same type, but a different item. Wiring loom is the same (bar some different connectors for temperature sensor etc) but coil packs are different (tested with GEMS, now running Bosch because of mounting issues).

Part of me is saying just add fuel and give it a go, it's a Rover V8, it will fire up. But being a new and not so cheap engine, I don't really want to take the risk and make sure it will fire and run as intended so we can immediately do the 20 minute run in for the cam. At least all this testing has proven the oil is up to pressure after just a few revolutions.

  • Like 2
Link to comment
Share on other sites

1 hour ago, Ed Poore said:

If the sensor is producing garbage then my guessing is it's game over for MS to try and figure out what's going on (hence the unreliable results).

That is my feeling as well. Sadly no scope of any kind to hand, no, but should be able to borrow one at some point.

I guess easy thing to try next (after putting the wheel decoder settings back to no return position) is swapping the pins in the VR connector. And/or try to figure out what is going on with the VR signal. Maybe pop it off and double check it hasn't been hitting the flywheel prongs?

Link to comment
Share on other sites

Glad to hear this:

2 hours ago, elbekko said:

 

Slow, but sometimes occurring :D

Not so much this: 

1 hour ago, Escape said:

The sensor we're now using is the same type, but a different item.

This one could have failed of course....

What trigger wheel are you using, the one on the flexplate or one on the crank pulley? I assume flexplate if you are using the GEMs VR sensor. I also assume it is running without EDIS given all the messing with trims etc?

2 hours ago, elbekko said:

For example #5 firing in multiple quadrants.

You could be getting cross-talk from another HT lead. I would be wary of relying on this as a way to confirm when something is firing or not.

2 hours ago, elbekko said:

When exporting the log to CSV, it seems to show (usually) 34 teeth between the missing tooth, which is one too few for 36-1?! And can also only get 2-3 revolutions of a clean 0-34 run, otherwise there's a lot of missing teeth detected and such.

This is classic failed or backwards VR IMHO, that or too big of a gap between VR and trigger wheel, or not enough steel in the teeth. I don't suppose it is too easy to measure the gap if you are using the flexplate?

 

My final thought is if you have a spare EDIS8 kicking about, give it power and ground and jerry rig it to the coil packs and see what it does spark wise? it will be a fixed 10 degrees without a SAW, but that doesn't matter. Would eliminate the ECU from all this.

 

Link to comment
Share on other sites

Flywheel teeth indeed, with stock VR sensor.

No EDIS, DCD with the stock coil packs.

The missing tooth is in the wrong spot for EDIS, the last car we tried this on drove us mad and never ran (then was lost in the workshop fire), so went for DCD this time.

19 minutes ago, Bowie69 said:

This is classic failed or backwards VR IMHO, that or too big of a gap between VR and trigger wheel, or not enough steel in the teeth. I don't suppose it is too easy to measure the gap if you are using the flexplate?

Swapping the pins on the VR seems like a good first call then.

Link to comment
Share on other sites

7 hours ago, elbekko said:

We could try swapping the wires around, but not sure if that would cause this issue?

Swapped wires would cause a false "double-gap" situation yes.

You shouldn't need to mess with the VR settings, I'd suggest trying to start from the defaults / whatever Nige uses by default and not get too far into the weeds from there as there's 100 ways to confuse the issue with this stuff.

Link to comment
Share on other sites

  • 2 weeks later...
2 hours ago, elbekko said:

Made some progress yesterday :)

Solved that issue :ph34r:

received_732002012247306.thumb.jpeg.bbfc514e6f0e7809581da72c566df1ab.jpeg

 

That’s looks to be a useful piece of kit Ben. Just looked it up and I see it does Canbus decoding too. That could be handy, along with verifying sensors. 👍

Link to comment
Share on other sites

24 minutes ago, SteveG said:

That’s looks to be a useful piece of kit Ben. Just looked it up and I see it does Canbus decoding too. That could be handy, along with verifying sensors. 👍

Indeed. And surprisingly cheap at Farnell, should've gotten it ages ago! Takes a bit of a learning curve though.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We use cookies to ensure you get the best experience. By using our website you agree to our Cookie Policy