castillaricardo

Does the car have the stock TPS? Is it manual? 90-93 manual NA6 Miata’s have an on/off sensor instead of variable 0-5v sensor. In this case you’ll need to install a VTPS, but if it already has an aftermarket sensor then it’s not working right as Adamw said

ah, makes sense.

It seems the spike happens when the Fuel Calculation goes to ERROR_LOW, in case that helps debug.

Understood. Thank you, Vaughan

Haven't tried [email protected] yet because they ask to try the forum first. A bit more detail: Computer is a Surface Pro 8 running Windows 11. Ecu Firmware Version: 6.23.6 and BootCode: 6.21.16 I get at least 35 minutes of logs before this happens but haven't found what the limit is yet.

It stands for General Purpose.

Hi all. I'm having an issue where I'm unable to download ECU Logs after a long drive or after multiple drives. The downloads page is empty but doesn't show a no logs available message. To be able to record and download new logs I "Delete All" and reboot the ECU. Then it works for a while until it happens again. Screenshot and tune are in OneDrive: https://1drv.ms/u/s!Amu_1gWOWFlvgVrLL_OwLrcWpSz8?e=DcSzlJ

I tried something as you described but with TPS delta instead and it worked well today. Thanks for that idea.

I also like the Spartan 3 controller. If CAN is not a wanted feature 14point7 also offers the Spartan 3 Lite that only outputs voltage and the Spartan 2 is also nice. The LC2 I had prior was off by a lot as I've found out.

You can edit the post that has the attachment, and delete it. You can find the posts under Account > My Attachments

@Adamw the changes I made helped quite a bit but the issue is still here. I forgot to mention that when I notice this the most is when I don’t close the throttle fully. So for instance going from 20% to %4 then up to 10% throttle, like when throttle steering in an uphill corner. If you have any other pointers I would really appreciate it

Yes, the tune I had loaded during that log used TPS as the load axis for the trim tables with 0 and 0.5 as the first two break points. One of the changes I made was to MGP as the axis, and I also lowered the TPS delta lockout from 10 to 6.5. Do you think TPS as the load is the better choice?

Sorry to bring this thread back, but I'm experiencing an issue with CLL causing small lean spikes after a decel and was looking for minimum lockouts, negative TPS delta lockouts, or some method of fixing these with the current settings. Sometimes when getting back on the throttle after a decel that didn't engage fuel cut CLL goes to its min clamp and causes a lean spike that makes the car stumble. I do disable CLL during overrun using the 3D tables, but the transition from a disabled cell to a regular cell seem to be the issue. I've added a log and current tune to my shared drive in case you have any suggestions on how to fix these with the current settings. I had made some changes to the tune the car had before I came across this thread. I can take another log tomorrow if that's an issue. https://1drv.ms/u/s!Amu_1gWOWFlvgU7puVEb17N_nLLm?e=sc7hCW Any chance the minimum lockouts could be reconsidered? Having a negative tps delta lockout that forces CLL to wait for the reactivation delay would help with some of my events. Thank you, Ricardo

I noticed yesterday that the padding column is not present with internal ecu logs and imported into MLVHD without modification

Thank you, Adam. Adding a character as you said did the trick in my older logs as well. One more tiny thing I noticed is that Lambda 1 says Lambda1 in the exports (missing a space). Obviously not an issue, just figured I'll mention it because the other Lambda [2-8] do have a space.

I tried as you said but still get the same error. I've uploaded the new exported log to OneDrive too. It has the same units line and blank line that I have to manually remove.

I've been using Megalogviewer HD to review logs but I'm not having luck importing the logs without manually modifying the CSVs. Maybe I'm missing something, but I go to 'Logging' > 'Export', select 'Full Log' and 'File Time'. Once the file is exported it contains a blank line after the units, and I'm not able to import into MLVHD unless I remove them both. See screenshot in the link below. Am I missing something? I've contacted EFI Analytics about this but haven't gotten a response yet. Linked is a sample exported log where line 3 contains the units, and line 4 is the white line, and the same log with these lines removed that I'm able to import into MLVHD. Any ideas? https://1drv.ms/u/s!Amu_1gWOWFlvgT42-HPtrtikjpBj?e=1w9vPW

Idle ignition control does help a lot and I do use it. Thanks for the suggestion as well.

Sorry, tune file attached. Thanks for the information, sometimes I don't know what 'normal' or 'acceptable' is. I do have closed-loop idle control and I do use Engine Fan Idle Up, but because of the routing of the IACV to the vacuum block it does take sometime for the idle to increase. It is an ITB motor, so some things are unusual. I'm working on this at the moment. As for the targets, I'm personally not interested in lower voltages during idle or WOT, just thought other people might be. Thank you for the responses by the way.

Thanks for the suggestions. Currently the control responds within 0.1 seconds, and gets to target around 0.25 seconds after the fan turns on. Is this a good response time? In my case I only use Engine Fan Idle Up as my car doesn't have AC, PS and is manual. I looked at a log after you mentioned it and the dip does happen between Fan 1 turning on and idle increasing. Attached is a log with two Fan on events. 3:10 in the idling section, or 10:54 of the whole file.

Hi all. The alternator control seems to be working well on my car, but I've noticed that it has momentary errors up to 0.8v when accessories are turned on/off. Could it be possible to add load offsets similar to the idle control offsets? This way we can increase/decrease the duty cycle on expected demand? Another consideration could be adding dedicated targets for charging, overrun, idle and full throttle. Having one target and base table doesn't allow for having multiple of these at once easily.

I use a CANChecked MFA 2.0 and it has performed well so far. I have used it for 8 months, first on MS and now in Link. It doesn't offer custom warnings like the GaugeART or Perfect Tuning, it can be cumbersome to configure at first, and I've found that not all channels are showing values but that could be wrong configuration on my CAN setup. What I like about it is that it is discreet in the MX-5 dash, has a discreet shift light and it can also be set it up as an analog display to be less distracting. You can setup popup warnings or discreet warnings for each sensor. I have had to use support because I broke the rotary switch and Stephan was responsive and helpful. I don't have any direct experience with the others.