claude

Do you really want the Megasquirt ECU to control the fuel pump? AKAIK the stock wiring turns on the pump when the ignition is on without any input from the ECU. If you turn the ignition off whenever the engine isn't running you would be manually controlling the fuel pump just the same as the Megasquirt does. If you want to find the fuel pump wire without the wiring diagram, start looking at the fuel pump for one end of it and trace it back. Here is what I would expect based on my Australian delivered 260Z. There would be two wires connected to the fuel pump. One wire would go to earth which you can test for continuity to the body using a multimeter (best done with the ignition off). Its most likely black. Talking about the wiring harness side, might be another colour on the pump side of the connector. The earth wire probably splices to a few other earths and is bolted to the body somewhere in the rear hatch area near the taillights. The other wire is your positive wire which runs up into the cabin, under the right front seat and splices to the main ignition power wire somewhere near the fusebox. Hope that helps.

This engine swap is to peg one back for Nissan. Before: 400 SB Chev After: L24

I don't know how to check if the code is scrambled but loading the firmware again will overwrite a mistake if there is one. Have you started tuning at all because you would lose your settings when you reflash the code and have to start from scratch. When you connect to the ecu with TunerStudio after upgrading the code I think it prompts you to load your offline settings which could be the old code's msq. Maybe you loaded a msq from an older firmware version without realising it this way. TunerStudio saves your MSQ whenever you close tunerstudio and checks it next time you connect to an ecu. I start a new project in tunerstudio when I upgrade the code and start from the default msq in the zip folder you download with the code in it. That way you can still open the older project in offline mode to look at your previous settings and in the new project you won't need to worry if the old msq is compatible between the new and old code versions. I just input all the settings manually in the new project. You can use table export and import between code versions with the VE & spark tables etc. If you're using megatune, manually save your msq before loading the firmware because it doesn't save it for you automatically like tunerstudio.