HE351 code for me78569

Rx7man · November 09, 2015, 08:22:29 AM

I'm not sure, Hard to know if it's a hardware or software issue... a scope on it would help.. since it's jumping UP, I have a hard time imagining a sensor issue.. more likely a software thing...

me78569 · November 09, 2015, 08:28:01 AM

I would imagine that if I had the issue so would other tho if it was software.

Also since it is worse on some days than others leads me away from code. Working in a software company it is rare to see a dynamic issue like this that is code related. Much more often hardware is the issue.

It's a strange issue Maybe I should twist the wires and see if the issue gets better.

Rx7man · November 09, 2015, 10:20:47 AM

I would think it's more likely it would MISS count pulses at high speed than get extra ones!...

if weather plays a role it certainly pretty much eliminates software...

Perhaps a bad cap somewhere?

me78569 · November 09, 2015, 01:26:51 PM

Could be.

I need to spend some time digging I guess.

Rx7man · November 09, 2015, 02:43:03 PM

Once I get my 'version' of the software tested, I might be of more help... I don't plan on using freqmeasure at all.

hakcenter · November 09, 2015, 02:45:51 PM

Check your shield for cold solder joints. If nothing I would start with the ceramic cap first, replace it. Then the 2 resistors, before digging into the power circuit on the max chip.

You don't need to twist the wires! It has a cap

At worst you can swap the pins, but I doubt it will do anything.

me78569 · November 09, 2015, 04:10:58 PM

Remember way back when I started I got the 9924 put in backwards. I wonder if that if what caused it.

I am no electrical engineer so I will take your word that it having a cap prevent any issues needing to twist the cable

I will look deeper, however on my way home, it read fine....

hakcenter · November 09, 2015, 05:37:22 PM

the VR sensor wires are coupled via the capacitor any interference bleed over would make it count less not more, at least that's what I get by looking at it.

I would just go through your shield, and re-solder all your joints.

If it still does it after re-soldering, I would replace the ceramic capacitor. Then check your alternator for AC current. Then check your arduino power supplies, then maybe / maybe replace the max.

me78569 · November 10, 2015, 09:40:26 AM

Cool thanks,

Again it was fine this morning. I am needing to check the alternator so I will start there haha.

Thanks!

me78569 · November 10, 2015, 03:47:31 PM

Alright,

another thought I have been having is that I would really like to start reading the canbus data from the truck. things like RPM, APPS and so forth would be VERY handy when it comes to controlling the turbo, mostly rpm, but rather than run a bunch of wires under the hood I might as well use what is there.

Am I off base in thinking that I could use the uno to read canbus data and send canbus to the turbo at the same time with the same canbus shield? or would I run into issues trying to send a canbus message to the turbo over the same can network that ecm is running on?

Thoughts on this? I have example code to get this going, but I am no buff in terms of how the canbus network works. I am worried that the canbus network protocol for the turbo won't work with the old canbus j1939 that the rest of the truck uses.

Rx7man · November 11, 2015, 02:17:59 AM

I think it should be possible.. CAN can have several slave devices, as long as they have unique ID's.. only the unit with the correct ID will respond to the command, so it should work... I don't have that luxury I don't think.. my truck is OBD1 (1994)

me78569 · November 11, 2015, 06:35:28 AM

Issue I am thinking is that the turbo more than likely uses a different can protocol to talk than my truck does. More I think about it the more I think I will need another can bus shield.

Rx7man · November 11, 2015, 07:08:15 AM

One way to find out!!

me78569 · November 13, 2015, 09:06:02 AM

http://freematics.com/store/index.php?route=product/product&product_id=30

$39 shipped to port OBD data into the arduino via serial. Gonna open up a whole new world in terms of tuning the turbo. I have always felt that engine RPM is HUGE when it comes to tuning the turbo. pretty excited to get this in and working on it.

This will open up a pin on the arduino as I won't need to read TPS VIA voltage input on the pin.

Rx7man · November 13, 2015, 04:21:06 PM

I just hacked my wiring harness and used an arduino for an oscilloscope (I ran 4 channels at 500 samples per second.. and I think I can do better) I think it's Gray/light blue, and it outputs a 5v square wave, but with a very short pulse... I'm sending that to an interrrupt enabled pin to do the counting... I'll be able to tell you how it works tomorrow I think.

I do think that if I had the option of using OBD2 (perhaps OBD1 would have enough info?) I could save myself some CPU cycles and have access to more info... I have to make do with what I have.

I totally agree though, engine RPM is essential for turbo tuning!