Jump to content

elbekko

Settled In
  • Posts

    5,124
  • Joined

  • Last visited

  • Days Won

    38

Posts posted by elbekko

  1. 2 hours ago, dangerous doug said:

    75k

     

    workshop is in the middle of nowhere so a lot of work would need to be done

    Yikes. That'll buy you a few VFDs.

    You'd think in this age of electric cars it would be easier to bring in 3-phase, as all proper chargers need it.

  2. 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.

  3. 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?

  4. 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:

  5. 58 minutes ago, Blanco said:

    I will go back to them today, previously they have told me that it is mainly Samsung phones affected, and it is something Samsung did, which I am taking means they altered the Android OS in some way?? My phone runs fairly straight Android with very little overlay by Doogee.

    Every OEM has their own build of Android, with anything from very few to many, many changes. Samsung does quite a lot of changes. Honestly I haven't even ever heard of Doogee, and I suspect customer support heard a model with "S" in the name and thought it was some sort of Samsung phone.

    I've found this, worth a try?
    https://apn-uk.gishan.net/en/apn/tesco/doogee-s96-gt

  6. Spent a fair bit of time on this, and thought I was making good progress... but alas :( Looks like all of the actual vehicle communication logic is on the Lynx/Omitec VCI itself, not in the application, it's just a thin front-end on top of some very generic communication where it gets a list of vehicles, a list of functions that vehicle supports, etc.

    That also explains the very generic (and bad) interface in the application, as it's built around the VCI communication.

    Oh well.

  7. 54 minutes ago, JeffR said:

    Where do I start..... I've done some gems over the years.

    Latest (last week) was wasting a day of my life trying to trace a fault with brake lights. New battery fitted, Continuity was fine in all the wires, no obvious shorts, all bulbs/bulb holders swapped out with known good ones, all the earths cleaned , all multi pin connectors cleaned . Gave up . Got a mate round to give me a hand......................

    He opened the battery box and collapsed in fits of giggles, on his back unable to do anything. I'd left the effing plastic post covers on the battery.......

     

    Just remember "To err is human, to really f£$k up takes a Jeff "

    I remember once, many moons ago at @Escape's workshop, a D2 came in where the brake lights didn't work. Spent hours going over the brake switch, wiring, everything... turned out all the bulbs just went out at approximately the same time :glare:

    • Like 1
    • Haha 1
  8. 8 hours ago, ThreePointFive said:

    Has he seen the cost of copper lately?

    Don't get your exhaust fixed, I like knowing there's one that sounds rougher than mine running about. Glad you found the cause though.

    You obviously haven't listened to mine yet :ph34r:

×
×
  • Create New...

Important Information

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