AshleyR

Budding Enthusiast
  • Content Count

    13
  • Joined

  • Last visited

About AshleyR

  • Rank
    Member

Profile Information

  • First Name
    Ashley
  • Ford Model
    Focus Mk2.5 1.6 TDCi
  • Ford Year
    2009
  • UK/Ireland Location
    Hampshire
  1. I feel pretty dumb, because cruise control works. I'm not sure at which point it was enabled, because it turns out I was testing it incorrectly the whole time. On other vehicles I've driven, pressing the cruise control On button makes a sound or illuminates an indicator somewhere. Not so on my Focus - pressing the On switch seems to do absolutely nothing. It's only when you're at a suitable speed and press the Set+ button after pressing the On button that cruise control becomes active and the green lamp illuminates in the dashboard. 🤦‍♂️ I figured this out on the last day of my trip, so at least the drive back was more comfortable. Regarding the OHP adapter I bought on Amazon.co.uk, I contacted the people at https://ohptools.com/ and they confirmed that the Amazon.co.uk seller is not affiliated with them and that the adapter I got is not an official OHP adapter. They kindly sent me a genuine OHP adapter, and I'm happy to report that it works fine with ELMConfig in the testing I did. I haven't tested PCM firmware reading or writing with it as there's been no need, but I'm optimistic from what I've seen so far. I'm still at a loss as to why ELMConfig doesn't like the As Built configuration data downloaded from the internet, but I'm going to leave that issue be for now. Thanks for the help, everyone! 🙂
  2. My PCM, the Bosch EDC16C34-2, seems to allow writing of configuration data separately from the firmware, as ELMConfig presents no errors or warnings when writing configuration changes back to the PCM. In other words, the "Write to PCM" button on the PCM Configuration page works fine. Reading configuration from PCM successfully reflects newly written values, which indicates that the changes are being persisted, although there's not much there that I could use to test whether the changes are actually taking effect. Maybe I should try set the Vehicle Speed Limit down from 255kph to something I could reasonably reach to see if these changes are actually being used. When simply enabling the PCM cruise control configuration option didn't work, as Milosh experienced, I tried following the firmware read-load-write process that people with other PCMs use. I did this with both the full firmware read from my car, as well as just the calibration data read from my car using the "Read calibration data only" checkbox below the "Read firmware from PCM to BIN-file" button. ELMConfig never said anything about the VID-block being empty or non-empty or asked which one to use. Everything just writes successfully, and cruise control still won't turn on, much the same as Milosh experienced. I'm not sure what dentex's experience was, but I have sent them a message to try find out more. In Milosh's case, their PCM configuration had some invalid values, so it seemed that their PCM ignored all configuration settings until everything was valid, at which point Milosh's cruise control started working. On the PCM Configuration page in ELMConfig, there is a button to "Load from As-Built", which will use your VIN to look up your PCM's As Built configuration data from the internet (I don't know what server ELMConfig uses to retrieve this information). Again, this is configuration only, with no firmware changes. This is also the only place where ELMConfig says anything about the VID-block, in this case telling me that the As Built data it retrieves from the internet doesn't match my chosen PCM type. I'm not sure how this can be, as my PCM type is definitely set correctly.
  3. Milosh kindly shared his ELMConfig save files and firmware with me. Unfortunately, I discovered that his module number is different from mine; his is a 8M51-12A650-LG for the 90PS 1.6 TDCi, while mine is a 8M51-12A650-XE for the 110PS 1.6 TDCi. This means I can't use his firmware, which does have some differences to mine, despite being the same release version. The PCMConfig.elm save files were also handled differently. When you take an existing config, tick the cruise control box, and save it, ELMConfig changes two bytes to new values. However, the values it uses seem to be different between my config and his. It could be that I'm maybe looking at a bitfield of settings rather than individual bytes per setting, but besides that, our configs seem to be aligned. Is it possible that my 8M51-12A650-XE doesn't support cruise control at all?
  4. Sadly, I remembered incorrectly. My PCM configuration is already identical to dentex's, except for the alternator, which is 150A on my car. I'm back to not knowing what more I can try to enable cruise control. 😞
  5. The speed source is a drop-down and is indeed set to "ABS (via CAN)", both in the current PCM configuration and the downloaded As Built configuration. As I say, all the fields in my PCM configuration are filled in with the current PCM configuration, except one of the fuel-related ones, which doesn't have an option for diesel. I had the same thought and have done the GEM module test, with all the buttons being picked up. I even went as far as unplugging the cable to the GEM module and checking that the resistance between the two cruise control pins is correct, which they are (2,110Ω, dropping to 1,110Ω when the On button is pressed). Searching further, I found dentex's post that shows they have the same PCM as me in a screenshot they posted. Surprisingly, their PCM configuration has "Unleaded Petrol / Base calibration" as the fuel type, which I believe is different to mine. I'll try matching their config and seeing how that works.
  6. Well, several attempts later, and no luck. My toe is thankfully not broken, and I drove through to Amsterdam yesterday without cruise control, though I really do wish I'd had it working for the trip. ELMConfig 0.2.17c is happy to write PCM configuration changes successfully, which I tried first. When I read the configuration back from the PCM, all the changes are there. Despite this, and having enabled the options in the GEM and HEC modules, cruise control does not work. I then took the plunge, and wrote the full PCM firmware back to the car (After confirming that the 2MB firmware dumps I read on the separate two laptops were byte-identical), which took about 50 minutes with the Tunnelrat adapter. However, I didn't get any questions about which VID-block to use, no matter what I tried. As I have a TDCi, I also tried the advice in OldLen's post to read the PCM firmware with the "Read calibration data only" checkbox ticked. I once again got a 2MB file, but ELMConfig recognizes it as being calibration only as opposed to the full firmware. I wrote this to the PCM as well, which took about 20 minutes, but again, I didn't get any VID-block related questions, and despite everything being successful, cruise control still does not work. I tried searching specifically for people enabling cruise control on the same PCM as I have (EDC16C34-2), and I found Milosh's post where he details having the same problems as me. However, in my case, all the configuration fields seem to be correctly filled in already, including the Tire/Axle ratio. The only exception I've discovered is that if I load my car's As Built data from the internet, it populates most of the fields but resets a few of the drop-downs to "Base calibration". When I try to write that to the PCM (after correcting those fields), I get the error "VID-block doesn't match chosen PCM type". If I load it from the internet, immediately save to a file, and load that file back in, then writing to the PCM works fine. I suspect something not visible in the UI is being loaded from the internet As Built data, but isn't being saved to or loaded from the file. The only other result I could find for my PCM was on a non-English forum where the poster apparently managed to manually edit the relevant configuration bytes in the PCM firmware dump to enable cruise control and then wrote that back to the car. Unfortunately, they didn't seem to document how they did this, and I'd be hesitant to try the same without a very clear understanding of what I was changing.
  7. Ah, I think this is the part I hadn't seen before, as I had seen Dan P's post, though it seemed to be general instructions for enabling cruise control. By "as built" data, do you mean the stock PCM firmware for your car from civil-zz's website? (Archived copy - his site seems to be down at the moment)
  8. The OHP adapter came up as COM5 on the Windows 10 laptop, and COM4 on the Windows 7 laptop. The Tunnelrat adapter was COM3 on both before I uninstalled its drivers in an effort to get the OHP working with ELMConfig.
  9. I'm hoping to avoid spending a heap of money on a battery charger that I'm only going to use to keep the battery going while enabling cruise control. I am, after all, trying to get away with doing this cheaply. 😉 No, definitely not doing this with the engine running, but absolutely everything optional is turned off. I'm also not willing to proceed with writing until my reading times match what other people tend to experience. So, the OHP adapter arrived today, and... it doesn't work with ELMConfig. 😡 On the Windows 10 laptop, FORScan picks it up in FTDI mode and can happily read the DTC codes. On the Windows 7 laptop, FORScan picks it up in COM mode and can happily read the DTC codes. ELMConfig can't open a connection to the adapter at all, no matter which mode or laptop I try (Yes, FORScan is closed when I try to use ELMConfig). In all cases, it pops up an error saying "Correct response from adapter timed." Usually, the request and response are both empty, as in this screenshot I took: On the Windows 10 laptop, I got a slightly different error a few times, similar to this: I'm desperately trying to get cruise control working by the weekend, as I'm leaving on a long road trip on Sunday. As of this morning, it's slightly more crucial, as I managed to give myself a suspected broken toe on my right foot, so driving long distance with that foot on the accelerator the whole way is gonna suck if I can't get cruise control sorted. Any advice or leads at this point is greatly appreciated!
  10. I've read about your misfortunes, really hoping to avoid landing in the same situation. 😉 How did you manage to unbrick it in the end? I haven't found a complete post on how you fixed it
  11. Tonight I tried a fast Windows 10 laptop with the latest CH340 drivers and the same Tunnelrat adapter: 115 minutes to read the PCM firmware this time. I tried to find a way to cancel the process in ELMConfig once I realized how slow it was, but as the app warns in the pop-up at the start of the process, it disables everything in the app and the keyboard (mouse still worked, though). I was tempted to turn off the ignition or yank the cable, but decided to play it safe and let it finish. 😞 I don't have a battery charger so I'm running it off the car's battery, which has thankfully been a trooper so far. It's a big battery, but still dropped 0.4v running the electronics for so long. I've ordered an OHP adapter off Amazon, so I'll try again tomorrow after that arrives. Could it be the PCM itself, which is a EDC16C34-2? Or could it be ELMConfig 0.2.17c? I noticed it defaults to a blocksize of 128 bytes - is this normal?
  12. I've only used FORScan for reading and resetting DTC codes so far, and that worked fine. The same goes for configuring some GEM settings with ELMConfig. The main issue seems to be with reading (and presumably writing) the PCM's firmware. Maybe I missed it, but where can I do this in FORScan?
  13. I'm trying to enable cruise control on my Focus Mk2.5 1.6 TDCi, and am getting extremely slow speeds doing the initial step of "Read firmware from PCM to BIN-file". I waited until it finished reading, with ELMConfig popping up a confirmation that it took 93 minutes, at which point I decided to call it rather than risk the battery dying mid-write. I've read that this step takes other people closer to 5 minutes, once the setup is correct, so I'm trying to figure out where I went wrong. I'm using a Tunnelrat Modified ELM327 USB adapter, and happened to get one based on the CH340 chip. I tried using the latest CH340 drivers from the manufacturer's website (v3.5 from 2019-03-05), but they never installed correctly on my Windows 7 laptop despite several attempts, so I'm using an older version (v3.4 from 2016-09-27) which installed successfully. I'm using ELMConfig 0.2.17c which I downloaded directly from civil-zz's website. I've explicitly set the adapter to use 500,000bps in ELMConfig, and it confirms that setting in the window titlebar. Is there something I'm missing or doing wrong?