hjtrbo

I understand how it's done, just need to know how the dyno output on CAN is to be interpreted by my tool... Can also get close to MBT watching fuel trims if you are doing it on the road using cruise control and a mate in the car . But, doing some reading I think I've got the gist. I'm basically just acting as a CAN pass thru to the rear O2 sensor. I'm hunting around for a better chip. Found a couple of candidates with on board CAN that are automotive rated. It's just the models aren't available in Proteus, which makes debugging more time consuming using an in circuit debugger.

@Roland@pcmtec, is this what you were saying? ... For the CAN feature I presume I'd bring in from the dyno: Ignition Trim Lambda Trim Inlet Cam Trim Exhaust Cam Trim Basically using my tool as a pass through to the rear o2 sensor, I.e. the dyno would control the sweep. The user would then set up the flex fuel OS respective map pair in PCMTEC and then run the dyno sweep?

Thanks for the links. Chip is a 8k word 8 bit PIC micro running at 16MHz. It doesn't have native CAN support but I have in a past project bit bashed a CAN MCP2515 transceiver using SPI to communicate with a LINK ECU to pull data out for a custom dash which went really well. If I get bored I can bring those source files into the project and integrate. Chip memory usage is at 82% 😬, but I know I could get that down with some optimisation and compiler tweaks.

Hey all, one for the home brew guys. Making a little tool that connects up to your rear o2 sensor and sweeps 0-1V over 256 DAC steps (resolution 4mV ). The idea is you set up a flex fuel OS, set up a map pair you’d like to dial in. A good example is cam shafts. In 98 fuel intake cam, set all -10°, E85 set all to 50°, then load the engine up and sweep from 0 to 1V to find the optimal angle for the map cell you’re working in. Sweep time is adjustable and there is a manual mode. All settings are saved to flash so you’re not having to re-set up the tool every power cycle. The code is written in C using Microchips MPLAB X IDE. Definitely possible to port to Arduino with a little bit of effort and care. Project folder attached. Handy little bit of gold in the LCD code, made a function that scrolls 1 line of text whilst keeping the other line fixed. Software is done and tested on a development board. The final board layout and component BOM are the next steps. Downloads if you want to play along… IDE https://ww1.microchip.com/downloads/en/DeviceDoc/MPLABX-v5.35-windows-installer.exe Compiler https://ww1.microchip.com/downloads/aemDocuments/documents/DEV/ProductDocuments/SoftwareTools/xc8-v2.41-full-install-windows-x64-installer.exe MCC Plugin https://ww1.microchip.com/downloads/en/DeviceDoc/com-microchip-mcc-4.0.2.zip Source code (spacing weird, tabs vs spaces interpretation issues when github gets it, looks fine on my machine) hjtrbo/Map-Sweeper (github.com)

Will do. Will check all the others too. Cheers man.

Hmmm, same shit happening here. Cant get a stable RPM signal. V3 Pro. Tried your suggestion @Puffwagon, no bueno. Have reached out to customer support. Will see what I get back. For reference I have tried injector #1 and coil pack #1. For both cases I tried at the PCM connector and at the injector / coil itself. Verified the appropriate settings selected in software for injector or coil rpm method. Swapped those 2 probes around for good measure as well. For the ground side I have tried engine block, PCM case ground, PCM sig ground, chassis ground. Have also kept all TN wiring away from all other wiring. Have tried the knock box inside and outside the car. Laptop is on battery so no AC connected. Nothing makes a difference. Unable to do a firmware update as I have an older version that does not have the lock icon on the microcontroller.

Might as well port it while you're in there

Ooh, like it very much. Cheers 🤙

All good. Looking forward to seeing the end result. The can interface is very nice. Would be neat if you could sell me the hardware and open source the code so I can config my own logic. Thinking out loud, I'd like to add in a 20A solid state relay output that can open up the coil and injector power feed in the event of a serious problem. The override switch is a nice idea also. In the event of a 'trip' would be good to have a LED flashing in certain sequences so you know which input or logic combination took it out without having to bust out the laptop.

I'll go you one better. Starts at $88. Write all the custom code you want in easy to learn ladder logic. Analog modules add $130. Industrial rated. Not for running an engine obviously, but for a box that acts on inputs to provide engine safety, this is about as cheap as it gets. CLICK PLCs (Stackable Micro Brick) | Programmable Controllers | Products | AutomationDirect

Way to slow to respond and had a 10deg offset from my previous logs. Calling it a fail. Have relocated to the turbo feed and put temp sensor back to where it was in live oil flow. Just made a npt fitting in the lathe and tigged it onto the banjo nut.

I don't think this makes it any clearer as to which adapt procedure to use. FG-X is the only one that lines up... FG Mk1 AR29-7J105-GB Software Version 24.09 FG-X ER2G-7J105 Software Version 19.11 BF F6 5R29-7J105-DG Software Version 17.13

Having a read of the adaption procedures. Do we know what software version we are? Stuck on night shift so cant go through the tune. Software P says 6HP19 which leaves us 19.02 (A), 19.04 (N), 19.11 (T)

If you have a trans cooler without a thermostat there is a scalar that can be lowered to enable adapts at a lower temperature. I'm away from my pc to get you the scalar ID. edit: ID ZF00027

Put back in a good known tune. Forscan DTC read. Go from there.

Its coming from your commanded fuel table. A normal O2 sensor can't read anything other that stoich (lambda 1). The O2 sensor is only used for closed loop fuel corrections.

Presuming you mean closed loop? You'll get a DTC if the O2 sensor has died. Stuck rich or lean from memory. The O2 switching volts in closed loop looks something like this when all is well (V8, not a Barra but same same)...

ooh. I presume just the calibration segment(s) goes across? Or the OS as well?

Presume so. There is some docs I posted in another ZF thread somewhere here. One of them was out of a ZF training seminar where they listed the range of acceptable adapt values.

yes

Of course. The adaption values change over time that is for sure. I've been keeping an eye on mine. Some have improved with increased pressure but alas my E clutch adapts are getting worse. It's just a matter of time before the box comes out.

No, it's been covered before, resets pcm stuff. From memory idle learn values and fuel trims??? If you search you'll find the thread where Roland give us the run down. The ZF adapt reset is a bit of a mystery. Some say the procedure available on this forum works, others say it doesn't. There is some bench flash software starting to make its way out to the public which is used for OS swaps. If that writes to the adapt area and resets it back to 0 would be awesome. No idea if it does.

A lot of good info. Thanks for sharing! What's next? Big HP build? Drive and enjoy?

It sure does kill torque. From my experience it used ETC which is a slow acting actuator, not sure if that will be as fast and precise as you want. From memory auF0072 is in play.

Clean engine is good. Wasn't so clean a while ago, was like yours I imagine, oil leaking out the front cover making a mess of the driveway. No experience with EOT. Yes, it will be slower to respond but I don't envisage that causing any issues in this case. The oil and block have a long thermal time constant as it is.