[Success Story] 1991 Miata [Hellen]

Your chance to introduce yourself and your vehicle
fan
Posts: 46
Joined: Tue Jul 07, 2020 8:42 pm
Location: Georgia USA

Re: 1991 Miata

Post by fan »

BeerMoneyMotorsports wrote:
Sun Jun 06, 2021 7:34 pm
Going out tomorrow
OMG this new version is so cool!

---Weeping with my MRE48 sitting in the OEM ECU box with a cut-out for USB cable
BeerMoneyMotorsports
Posts: 149
Joined: Thu Jan 14, 2021 10:16 pm

Re: 1991 Miata

Post by BeerMoneyMotorsports »

Posting this here for some posterity of H64a tacho mod
Attachments
Tach h64a
Tach h64a
C3ACCE37-0D43-41E5-98EA-948B93EDACBB.jpeg (3.95 MiB) Viewed 1528 times
Keith
Posts: 26
Joined: Thu May 27, 2021 1:13 am
Github Username: Keith-N
Slack: Keith

Re: 1991 Miata

Post by Keith »

I was attempting to improve my cold starts and ran into an issue with the ECU that required re-flashing the firmware.

I started with the ECU connected to my laptop, and it remained connected until after the issue occurred. I started the car. It started to die, so I shut it off then made some adjustments to the CLT multiplier. I did the same thing a couple more times. While trying to start again, the car would not start. I couldn’t hear the fuel pump prime and it didn’t sound like it was firing while cranking. I also lost connection to the ECU from my laptop.

I checked for the ECU in the device manager and did not see it even after disconnecting and reconnecting to the laptop. I removed the cover to inspect the status LEDs and all four LEDs next to the STM were lit up solid. I attempted to get the ECU into DFU by using the boot and reset buttons. The LEDs next to the STM remained off while doing this, but still no device was found in the device manager.

I removed the ECU from the car and went to my PC. I attempted to connect it to my PC using both the same USB cable I had originally used and a second one with no success at first. I could not see the ECU in either the device manager or the STM programmer. I tried probably 10+ more times booting into DFU using the reset button, holding boot while plugging in the USB, alternating cables. After going back to the original cable, holding the boot button, plugging the cable in and making sure the connections were firmly seated, it finally showed up as STM32 Bootloader in the device manager.

I was able to connect to it with the STM32 Programmer, and flash the latest firmware build. After disconnecting and reconnecting the USB the LEDs started behaving as expected (Yellow solid, blue flashing, others off) and I was able to connect to the ECU with TunerStudio again.
User avatar
AndreyB
Site Admin
Posts: 13274
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: 1991 Miata

Post by AndreyB »

Ohh :( Glad it has worked out in the end but we clearly have two issues we have to get to the bottom of

1) issue one is either https://github.com/rusefi/rusefi/issues/3264 exactly or a variation of https://github.com/rusefi/rusefi/issues/3264

2) issue two is drama to enter DFU, no ticket for this for now but I am noting at https://github.com/rusefi/rusefi/wiki/HOWTO-DFU#q-i-am-using-the-buttons-but-it-simply-does-not-work
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Keith
Posts: 26
Joined: Thu May 27, 2021 1:13 am
Github Username: Keith-N
Slack: Keith

Re: 1991 Miata

Post by Keith »

So it turns out my USB connection isn't great, possibly due to the cable, so that likely contributed to not seeing the board in DFU during some of those initial attempts.

I did end up improving my cold starts. I referenced BeerMoneyMotorsports tune https://rusefi.com/online/index.php?vehicleName=Lemon&user_id=1408&sorts[uploadedMsq]=-1&sorts[uploadedLog]=-1 to adjust my cranking and idle settings. It may end up getting a few more tweaks, but it will start and hold idle without any throttle input, even on colder days. My tune is here with a startup log https://rusefi.com/online/view.php?msq=659.
Post Reply