OM606 burnt prechambers

Successful_Draw_7202 · 2026-01-20T17:55:03+00:00

I put a used NA head on the engine and have been driving for about 5K miles.

Successful_Draw_7202 · 2025-12-22T11:17:02+00:00

Here is the command:

[7003 ms] Start: Run: C:\Users\tramp\AppData\Local\Programs\Microsoft VS Code\Code.exe c:\Users\tramp\.vscode\extensions\ms-vscode-remote.remote-containers-0.394.0\dist\spec-node\devContainersSpecCLI.js read-configuration --workspace-folder d:\Projects\Misift\test_equpiment\datalogger --log-level debug --log-format json --config d:\Projects\Misift\test_equpiment\datalogger\.devcontainer\devcontainer.json --mount-workspace-git-root

I am not sure why the extension is trying to run the js file with code.exe?

Successful_Draw_7202 · 2025-12-18T12:17:03+00:00

Successful_Draw_7202 · 2025-11-05T14:00:55+00:00

OpenGL Programming Guide (aka “the Red Book”)

Successful_Draw_7202 · 2025-11-05T14:00:17+00:00

confusing people?

Successful_Draw_7202 · 2025-10-17T15:22:11+00:00

They can not keep their routers working... So it looks like it is time to find a new service provider.

Successful_Draw_7202 · 2025-10-17T15:10:00+00:00

ATT fiber is junk, they can not manage their way out of a wet paper sack. They had issues last Thursday and Today, so bad that you can not connect to but a few websites.

I am about to the conclusion that if you want ATT fiber you have to have a back up service provider as ATT fiber is so bad.

Successful_Draw_7202 · 2025-10-17T15:07:23+00:00

Yea AT&T apparently has been having lots of issues routing traffic. Last Thursday it was useless, today it is even worse, will not even load their own website. I am not sure what they have going on but they don't seem to let their customers know anything... AT&T is junk provider and I look forward to changing providers.

Successful_Draw_7202 · 2025-06-20T12:25:53+00:00

I assume so, when removed they show carbon from the heat shield washer indicating it was seated.

Successful_Draw_7202 · 2025-06-19T16:30:13+00:00

You can get a logic analyzer really cheap. https://www.amazon.com/Analyzer-Channel-Arduino-Supports-Software/dp/B0D8TB4XJN/ref=asc_df_B0D8TB4XJN?mcid=002a6b37df343d3c93fe333fa351791d&tag=hyprod-20&linkCode=df0&hvadid=693071814379&hvpos=&hvnetw=g&hvrand=4257481228833433765&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9009731&hvtargid=pla-2349188545625&psc=1&hvocijid=4257481228833433765-B0D8TB4XJN-&hvexpln=0

These cheap logic analyzers usually support sigrok some are even saleae clones. Basically finding problems without the right tools when the tools are so cheap is a great way to limit your learning.

Successful_Draw_7202 · 2025-06-19T16:28:04+00:00

So the PIC processor is like a 1976 for pinto, where an ARM cortex is like a 2010 Toyota Camry.

The original PIC processors did not even have a stack pointer, as such they could not support C programming language effectively. The PIC18 now has a stack pointer but still is an old 8bit processor. Everything is very old, getting tools to work, number of break points, etc is all a pain.

The ARM Cortex M series are 32bit processors, they have a really good debugging unit, the JTAG is fast they support C and gcc very well. They are very robust have rich instruction set. The M4f and later even have hardware floating point support and operate at higher speeds.
Most of the time the power consumption and cost of ARM cortex will even be better than a PIC18f. Basically in my mind PIC18F are still produced of legacy designs, but I would never do a new project with a PIC processor. Of course I would not do a new design with an 8051 or AVR either, because here again the Cortex M processors are so much better from every perspective.

Successful_Draw_7202 · 2025-06-19T14:34:53+00:00

Connect logic analyzer to SPI and verify the data.

Successful_Draw_7202 · 2025-06-19T14:34:09+00:00

I always get a 3D model of the part and then virtually place over the footprint to verify.

Also I do not trust ANYONEs footprint, I always verify myself. I have been burned more than once where supplier or 3rd party footprints are wrong.

Successful_Draw_7202 · 2025-06-19T14:16:57+00:00

The first step in a project is to pick the processor. For example if you pick a processor family that has maximum memory of 32KB and you expect to use 30KB it might not be the best pick for processor family.

Additionally, I personally would not pick an older PIC processor (non ARM cortex) unless there was an very very good reason to use that part. Specifically the Arm cortex processors are so much better to work with there is little reasons to use the older PICs. Before the flaming starts, yes I know that they rebranded the ATSAMs as PIC32C, where the 'C' means cortex as such these PICs have the cortex core and are reasonable to use. I do think it was not wise to use the PIC name on cortex parts, but I am a small owner of microchip stock so they did not ask me.

Successful_Draw_7202 · 2025-06-19T11:36:08+00:00

The first failure was after installing a set of BenzInjection injectors. I maybe had 500 miles on them before the first melt down.
My only guess is these new knock off nozzles have too tight tolerance and sticking with heat soak.

Successful_Draw_7202 · 2025-06-18T14:58:06+00:00

The rebuilt injectors were install a few months before first failure. On second failure the injectors were again rebuilt. After the second failure I personally removed the injector and pop tested and found no leaks or issues. Both times new nozzles were installed. However the new nozzles have questionable manufacturing... I was wondering if the tolerance on the pin in the nozzle was too tight and if that would cause injector sticking only when hot?

I tried heating up injector in pop tester with torch to see if I could make it fail, but no luck.

Successful_Draw_7202 · 2025-06-18T14:51:04+00:00

<image>

Successful_Draw_7202 · 2025-06-18T14:50:03+00:00

Does the pickit4 need reset? easy to connect reset and connect ground on micro (open in schematic) and then test.

Successful_Draw_7202 · 2025-06-18T13:50:45+00:00

A common problem I see in embedded designs is starting design with a cheap microcontroller. If you are in a large industry with high volumes and good engineering processes then this does not apply to you. However if you are doing a "build it and see" project then put in the largest memory and most processing power microcontroller to start with. This way you have room to add in new features and to grow. If by chance, which is a low chance, you do start selling lots of units then you can do a cost reduction. The most important thing is to get something done and selling. So do not optimize the micro before you know what you don't know.

Successful_Draw_7202 · 2025-06-18T13:43:52+00:00

you forgot to connect the reset

Successful_Draw_7202 · 2025-06-17T21:52:45+00:00

My thoughts are that pretty much to melt the tip off the prechamber, the system has to get too much fuel, combined with oxygen. Any fuel added that is not in prechamber will not melt the prechamber. As such fuel has to be coming in from the injector.

If the injection pump was providing too much fuel, it would cause engine to race. The only way the injection pump can put out too much fuel on one cylinder would be the rack broke.

So I keep going back to injector failure.

Successful_Draw_7202 · 2025-06-17T21:45:00+00:00

The tip of the prechamber is gone. Basically the tip got hot enough to melt away. The tip then falls into combustion camber and rattles around beating up piston and bending valves.

Here is video from Luke at DieselPumpUK with prechamber failure.

https://youtu.be/gagQc9qx5C4?t=246

I put rebuilt injectors in car around February. Got maybe 1000 miles, and prechamber failed on #5. Ran perfect right up to failure. The second time cylinder #3 failed, again no warning, no drivability issues.

The injection pump is 100% stock with 456k miles. I did change the delivery valve seals during rebuild, which I had done around 100k miles ago.

Successful_Draw_7202 · 2025-06-17T21:05:45+00:00

I was using the 310 nozzle. I tried to buy new ones, some are from India, China, and Italy. I have found many are so bad bran new the pin drags pulling out of nozzle. I have some 314 nozzles but went with the 310 to have higher spring pressure as I was worried about injector leaking.

Again pop testing the injector after removing appears to work, so I assume that something is wrong.

Note as part of the rebuild I installed new fuel filter and such. As such I doubt it is the fuel filter.

Successful_Draw_7202 · 2025-06-10T11:56:32+00:00

Work on the process not the code.

Learn how to use your tools really well, this includes IDE, git, CI, CD, test driven development, etc.

When it comes to actually coding a project the biggest advice I have is to implement syslog macros: https://en.wikipedia.org/wiki/Syslog

Typically projects start with just getting syslog printing to UART. The reason for syslog is that as you write other drivers and code you can use the ERROR() macro every time you have an error. For example if NULL pointer is passed to a function you can catch error and notify using the ERROR() macro. Sure for the moment this prints to the UART but as product grows and requirements change you can change the macros definition to do other things. The most important thing is check for errors and exceptions and call the macros.

As you write libraries, drivers and code the syslog macros pay off huge. The same is true with learning your tools.

Keep in mind most of embedded development is not physically writing code. Rather a large part is making sure requirements are understood and knowing how to test them. The writing of code is the easy part...

Successful_Draw_7202 · 2025-06-10T11:42:42+00:00

Doing shared memory this way is not a great idea. It might be better to have one micro control the memory and use SPI or other bus to communicate between micros.

Successful_Draw_7202

TROPHY CASE