Ghostchips

Swapping 'int' to 'int volatile' would compile but did the same refusal to read & print temp unless something else in the system changed. As for the coils getting pos+ feed in that last diagram. That's a legacy of when i tried coil on plug igniter things (which worked) but for some reason when i swapped those out for soemthing else, it wouldn't spark if the igbt were on the low side. Not enough volts to trip them maybe? Seems i fixed the thermal reading code by added a random "Serial.print ( C = ) at the end of the loop for the resetting thermal value & add a 0.5 second delay (i hate that, it seems noobsh but then i am new...).

Shares earth via 330ohm resistor. Much less it doeens't function right.

Still curious why that code isn't reading-writing in the temp sensor department when the other switch code is in it.

Many cars are bare metal. They don't always stay that way & have to be rego'd as brown within a year.

Don't fall into the trap of thinking you need perfection if you know it ran well before. Some engines builders scoff at me for saying this but... There have been many people who build engines with pitting in the bore. One guy bored 90 thou' oversize and still had some pitting. He calls those pits "oil retention dimples" now. 1 mm oversize should cure the worst of it. (This is only my advice and i cannot recommend pistons to fit as i know nothing of the pin height ect of said engine)

Also. Is the reason this works with a pair of double A batteries but the arduino fires all the coils at once something to do with ground float? And how would i fix it? Forgot to say the arduino has 'fast shitty diodes' on the output pins. Think i toyed with a heavy resistor from the arduino ground to main ground in the past but it wasn't happy? can't remember.

And now for combining it with something that doesn't work well when i added that code Ned helped with.

Not a snowballs change in hell of me figuring out how to use google drive. Google really does need to be dragged outside, beaten & shot. And the corpse thrown in a volcano while people chant & beat drums. How they can make something that unintuitive i don't know. Who thought having buttons that aren't visible & don't have any known function was a good idea? It's like point & click lucky dip & not every action is repeatable. Just like things i build in real life.... Ok the thing in the spoiler should be code that worked.

Wanted to re-use some expensive gear oil with less than 100KM on it. Was full of glitter. Tried running it through a funnel on top of a pipe filled with rope. No luck. Cut the top off an oil filter and put it in a funnel with a magnet on the bottom, that caught the big chunks but there's fine bronze glitter oozing through the filter. (repco brand) Aside from tell me that engine oil filters aren't that picky & let through some stuff i wouldn't want in my engine, what else should i strain the oil through? Doesn't seem to wick uphill and back down into a container through a rope. Appears too thick for that.

OK, so i have started to blend 2 codes together and found something odd. The temp' reading won't update-read a new value unless one of the other input pins is changing state & performing an action based on it. May i send someone the code for them to see what's going on & tell me what i did wrong? I suspect it's something to do with needing brackets or a "while run" type thing. But i really don't know.

I recall someone saying they did that. Registered as a commercial vehicle and was allowed to black out the back. The penalty was something like $550 a year rego'. This is third hand info' and may be out dated.

Tested it. Way less buggy than the stuff i was using. Not always as fast to respond but tht's not always a bad thing. Cheers Ned.

One of those gives me looping readouts of the temp falling warnings, Neds one looks good but i wasn't sure where to put the defines. No matter where they go, i get this "thermo_Neds_code:47:2: error: invalid preprocessing directive #ï #define TEMP_BAND 2 ^ exit status 1 invalid preprocessing directive #ï" am i missing a library or something?

That sort of worked, it's now triggering them every time it goes past the deadband range but that's ok, i just opened it up a bit (like 10 degrees. Man this thing is crude). Added serial write for testing. It gives the same warnings s the temp' falls. I don't want to sound like a spoonfeed bludger but what could i do to give different warnings as the temp falls compared to rises?

void loop() { Serial.print(" C = "); Serial.print(thermoSensor.readCelsius()); delay (1000); thermoSensorNewVal = (thermoSensor.readCelsius()); if (thermoSensorNewVal < (thermoSensorOldVal-1) || thermoSensorNewVal > (thermoSensorOldVal+1)) //dead band { if(thermoSensorNewVal >= 24.00) { tempWarningMinor(); } if(thermoSensorNewVal >= 28.00) { tempWarningGeneral(); } if(thermoSensorNewVal >= 32.00) { tempWarningDire(); } } thermoSensorOldVal = thermoSensorNewVal; } This activates warning when the temp rises or falls by 4 degrees in one second. But that's not what i was aiming for. I wanted a warning when it was between a certain range of degrees, but not to give that warning over & over, say if the temp rose by one degree but was still in the range of that same warning. What am i doing wrong, and how would i fix it? I suspect the warnings would have to be replaced with some kind of variable? And that would have to run once every time it was selected instead of every loop. Or maybe i'm going about this all wrong. Or in short "temp zone, do nothing until reading reaches value 80 plus or minus 10 degrees is temp exceeds or drops beyond 80, adjust to a value of 6, plus or minus 10 degrees and give warning" But i don't know how to write that in code..

I think it's about as flammable as fish oil.

Aww man this must be so postponed.

So how sensitive are these things? I tried electrically isolating them from a system by using LEDs and LDRs. Worked fine at first but then the LDRs decided they'd change their sensitivity base on temp' and battery level ect. But today. I hooked up one to my ignition. The earth wire wasn't connected. It wouldn't turn on without positive & negative obviously. But the other arduino for the dash decided that i was turning on my lights, engine & everything else. When i connected the neg' wire. All went quiet. That was until i turned on one sensor for a coil. The coils weren't connected as i was using test lights to see if they were working the way i wanted. But even with the test lights off that was enough to start giving false readings on the dashboard arduino/making it think it was receiving power to pins connected via leadlights ect. What would cause that?

Rust inhibiting protective oil. Seems to protect the undersides of cars ok. Not a miracle cure not every bit helps.

Have you considered spraying the underside with R.I.P.O. and black paint or you did that & it just looks like that somehow?

Already did. Now to wait for their response.

They'll tell me it's not finished & spurious, and that i'm an idiot & attention whore. And probably many other things.

Can't decide if i should have put this in the wombling thread lol. It's an oil can by the way.

Technically the engine is a 12 A soo...