DSMLink v2.5 + Map Sensor

[mnetwork]

I am trying to find a MAP sensor that would be able to read well into the 30s psi and would work with DSMLink v2.5. I have seen the Omni 4 bar and I see a lot of people using it, but I don't understand how you would log it in DSMLink as there is no option for this model... Can someone chime in here on this?

 

[gofer]

If you download/install the most recent v3 application software you should have the Omni4bar as a loggable parameter. If for whatever reason its not there because your on v2.5 then you can log it as LinBoost and change the LinBoost setting properties in your log by double clicking it and making the below changes...

0V = 0.5 psia
5V = 60.4 psia​

Hope that helps, post a log if anything and I'll take a look at things because odds are you just haven't switched to the v3 app.

 

[1992awdlaser]

I use the AEM 5-BAR sensor with mine.

 

[mnetwork]

If you download/install the most recent v3 application software you should have the Omni4bar as a loggable parameter. If for whatever reason its not there because your on v2.5 then you can log it as LinBoost and change the LinBoost setting properties in your log by double clicking it and making the below changes...

0V = 0.5 psia
5V = 60.4 psia​

Hope that helps, post a log if anything and I'll take a look at things because odds are you just haven't switched to the v3 app.

I am using the 2.5 app and there is no option for the Omni 4 Bar. I understand that the V3 app might let me log the Omni 4 Bar as the software can do the end calculations for logging, but I don't get how this would enable to the Fake MAF function to work correctly. I thought that is why there are different sensor options... because they are hard coded calculations in the chip.

So LinBoost lets you put in custom values? Where can I do that, in properties? That brings my back to my what I said above... it's my understanding that properties are just program setting (even stored locally in a settings file) that just adjust data for display and logging and have nothing to do with DSMLink (the actual chip and internal program).

These are the options I see... although LinBoost shows up the software, but not on this list: dsmlinkloggableparams [ECMTuning - wiki]

I use the AEM 5-BAR sensor with mine.

How do you like the AEM sensor, I hear "it is not as good" because the range is distributed over a 4V range. Is it accurate for you?

 

[1992awdlaser]

How do you like the AEM sensor, I hear "it is not as good" because the range is distributed over a 4V range. Is it accurate for you?

I do not have a single problem with it. It reads dead on with my boost gauge. I have not heard of anybody having problems with it either. I have heard of people having problems with the AEM wideband not logging accurate values though. Maybe that is what you are referring to.

 

[mnetwork]

I do not have a single problem with it. It reads dead on with my boost gauge. I have not heard of anybody having problems with it either. I have heard of people having problems with the AEM wideband not logging accurate values though. Maybe that is what you are referring to.

I have that issue as well, but that is a whole different thing... Which AEM sensor are you using?

This was where I read the AEM sensor information: http://www.dsmtuners.com/forums/tun...ensor-run-sd-using-ecmlink.html#post151968812

 

[snowborder714]

That is true - the AEM sensors are not the top pick because of the resolution issue. That being said though, many of us (including myself with a 5 bar) run them without any issues. Mine matched my boost gauge as well when I had the gauge installed. I personally got the AEM because of the housing and threaded section so I could screw it directly into my intake manifold. The others require a vacuum line to be ran to them.

 

[techghost]

download the v3 software, you will be pleased with its interface.
BTW this is salmaan_ali from DSMLINK

 

[mnetwork]

That is true - the AEM sensors are not the top pick because of the resolution issue. That being said though, many of us (including myself with a 5 bar) run them without any issues. Mine matched my boost gauge as well when I had the gauge installed. I personally got the AEM because of the housing and threaded section so I could screw it directly into my intake manifold. The others require a vacuum line to be ran to them.

That sounds good then... Only reason I liked the Omni more was because I could put it right in place of the stock MDP sensor and it was around $50 cheaper. I'd still like to verify that that the Omni sensor is compatible with DSMLink V2.

download the v3 software, you will be pleased with its interface.
BTW this is salmaan_ali from DSMLINK

I have used the V3 software and it i nice. I only use the V2.5 software because I am used to it.

As I posted on DSMLink, I don't understand how the software would make use of a sensor that the chip isn't programmed to accept. It is my understanding that when you change captured value properties that you are just changing the value that will be logged and displayed by the software. I do not see how the ECU can make use of this for MAF Clamp as there isn't an Omni sensor in the list.

 

[gofer]

Your nuking this stuff or just reading it incorrectly, hopefully I can clear a few things up for you. I completely understand why you don't want to run the v3 software since you feel comfortable with v2.5, it is a lot user friendly once you get used to it though I promise.

Good news for you is you can still log the Omni4Bar MAP sensor with no problems by logging LinBoost like I said in my OP. To change the parameters of LinBoost you simply capture/display it in a live datalog and then double click LinBoost . After you double click it a sub menu will pop up and allow you to change 0v and 5v, insert the values I gave you in my OP. You'll more than likely want to change the altitude as well, I'm at sea level and I have my altitude set for 750ft to get my logged boost spot on.

As I posted on DSMLink, I don't understand how the software would make use of a sensor that the chip isn't programmed to accept. It is my understanding that when you change captured value properties that you are just changing the value that will be logged and displayed by the software. I do not see how the ECU can make use of this for MAF Clamp as there isn't an Omni sensor in the list.

The software isn't "making use" of the sensor unless your running Speed Density or MAF Clamp, like you mentioned, and even then its using the parameters you've set for it from the 0v and 5v settings.

How many lbs a min. are you flowing that you need to worry about MAF Clamp anyway?!

 

[mnetwork]

Your nuking this stuff or just reading it incorrectly, hopefully I can clear a few things up for you. I completely understand why you don't want to run the v3 software since you feel comfortable with v2.5, it is a lot user friendly once you get used to it though I promise.

Good news for you is you can still log the Omni4Bar MAP sensor with no problems by logging LinBoost like I said in my OP. To change the parameters of LinBoost you simply capture/display it in a live datalog and then double click LinBoost . After you double click it a sub menu will pop up and allow you to change 0v and 5v, insert the values I gave you in my OP. You'll more than likely want to change the altitude as well, I'm at sea level and I have my altitude set for 750ft to get my logged boost spot on.

The software isn't "making use" of the sensor unless your running Speed Density or MAF Clamp, like you mentioned, and even then its using the parameters you've set for it from the 0v and 5v settings.

How many lbs a min. are you flowing that you need to worry about MAF Clamp anyway?!

I am flowing 50+ lbs/min on the 6262. It gets choppy after 50 and it will not read any higher. I am going to E85 and 30+psi after I square this away.

 

[gofer]

Yea, you'll want to run MAF Clamp then if your still on the stock MAF, like I said just apply those settings to LinBoost and everything should line up. If it doesn't post a log and let us know, we'll get you flowing 50+ lbs/min.

 

[a1320eclipse]

Forgive my ignorance, but im new with the way all this stuff works. So basicly im on a hacked maf, and tryin to run 20psi or so on the 14b. Ive read the factory MAF is overun at 2000hz. Im picking up knock after it goes into overun. So i was looking at the option of wiring in a AEM 5bar. But im not sure of how to do it, or if i can get the DSMlink to work with it. Oh yeah, i have DSMLink inthe car on V3 software. And the knock isnt related to AFR's, or bad knock. Cant find a legit reason why its nocking. I can retard or advance the timing, richen or lean it out...tried everything. Is wiring in a MAP sensor and setting it to work after the MAF a viable option. I will go speed density V3 when money allows.

 

[gofer]

To fix your PK (phantom knock)...

• Check the knock sensor, if there's black goo coming out of the back it needs replaced.
• Verify that its threaded into the block and tight, torque spec is 17 ft/lbs
• You can place a plastic washer between the knock sensor and the block to help with the PK, if you're still having issues and have done the above.

1g MAF overrun should be corrected by switching to a better MAF (2g/Evo) or going to SD. This is because the limit of the 1g MAF is too low (2000Hz as you said) and it can't produce a reliable signal for MAFClamp.

 

[a1320eclipse]

To fix your PK (phantom knock)...

• Check the knock sensor, if there's black goo coming out of the back it needs replaced.
• Verify that its threaded into the block and tight, torque spec is 17 ft/lbs
• You can place a plastic washer between the knock sensor and the block to help with the PK, if you're still having issues and have done the above.

1g MAF overrun should be corrected by switching to a better MAF (2g/Evo) or going to SD. This is because the limit of the 1g MAF is too low (2000Hz as you said) and it can't produce a reliable signal for MAFClamp.

Its not PK if your referring to me. I can audibly hear it detonating with the window down on the pull.

 

[gofer]

If you can actually hear it knocking doing a pull then odds are your stock timing map is too aggressive, typically the case on modified 1g's. What are you using to retard/advance timing, the CAS or a tuning device?

If you're tuning using the stock 1g timing map here's what you're up against...

STOCK 1g TIMING

You must be logged in to view this image or video.

STOCK 2g TIMING

You must be logged in to view this image or video.