Recent Posts

Pages: [1] 2 3 ... 10
1
URGENT / Re: Closing down
« Last post by steelcurtaindsm on April 11, 2018, 05:54:55 PM »
Mabye a farewell werewolf upgrade??...hey had to ask..
2
URGENT / Re: Closing down
« Last post by Warlord on March 16, 2018, 06:58:16 AM »
 :crywave
3
JACKAL / Re: Can I use 2 different laptops for the same ostrich 2.0
« Last post by hakcenter on March 06, 2018, 09:04:34 AM »
Yes, the key file is per ostrich not per computer.
4
JACKAL / Can I use 2 different laptops for the same ostrich 2.0
« Last post by steelcurtaindsm on March 04, 2018, 02:55:48 PM »
Can I use multiple PC's to tune on the same car ..for instance like my laptop and wife's laptop as mine is problem dead.???
5
URGENT / Closing down
« Last post by hakcenter on February 27, 2018, 10:54:43 AM »
I'll be closing down ds-map near or during March.

Life is changing and I simply don't have time to dedictate to this site, or tech, or simple problems and solutions. It's been a great run guys and I appreciate everyone who has been apart of this place, and cheered others and myself onward.

I will leave the wiki up for a bit, and everything will point over to it, and when the domain expires, it'll be over I won't be renewing. If anyone needs anything specific, no question is beyond asking.. you know how to contact me  8;)
6
JACKAL / Columns 1-12 actual value
« Last post by [email protected] on January 10, 2018, 04:22:38 AM »
Can anyone tell me if there is an approximated value for the load index on columns 1 through 12?
7
WEREWOLF / Re: Aem wideband don't match
« Last post by hakcenter on December 18, 2017, 10:48:51 PM »
That guys was always off by 0.6, if this remains true to yours, you can setup a programmable, and make it match your gauge output, by varying the low / high until you reach a good linear line.
8
WEREWOLF / Re: Aem wideband don't match
« Last post by eclipsegst1990 on December 17, 2017, 08:12:02 PM »
Thought this article on the AEM site might help a little.

http://aemelectronics.com/?q=forum/aemtuner-and-guage-not-reading-same
9
WEREWOLF / Re: Aem wideband don't match
« Last post by eclipsegst1990 on December 17, 2017, 03:54:46 PM »
I am grounded to the ECU ground.  I tried that a while ago, but didn't fix the problem.  I will try to get a few more points.  Now the voltage readings are coming from the Werewolf logger.  If the analog gauge output is wrong with the AFR values, wouldn't the voltages be wrong too? 
10
WEREWOLF / Re: Aem wideband don't match
« Last post by hakcenter on December 17, 2017, 02:02:09 PM »
I need to find the super super old old aem pdf, cause those linear values don't cut it.

It is just (2 * x) + 10 for p0 / p1, which we all know is wrong.

Using 1.15 / 2.46 really makes it like,
(4.86586386*ln(x))+10.31993741

I have some old mmSD code that I used from the super old pdf and inputted everything by hand, in a 256 byte array from 0v to 5v.
Basically 0.01953125v per 1 unit, starting at 0
Code: [Select]
//AEM UEGO Unlinear
if(WB02Unit == PREFS_WB02_AEM) {
static const UInt32 interp[256] = {
8410,  8423,  8437,  8451,  8465,  8479,  8492,  8506,  8520,  8535,
8550,  8565,  8580,  8596,  8611,  8626,  8641,  8663,  8684,  8705,
8727,  8748,  8769,  8791,  8812,  8834,  8855,  8876,  8898,  8919,
8940,  8962,  8982,  8996,  9009,  9023,  9037,  9051,  9065,  9079,
9094,  9115,  9137,  9158,  9179,  9201,  9222,  9243,  9265,  9288,
9310,  9333,  9356,  9378,  9401,  9423,  9446,  9467,  9488,  9510,
9531,  9552,  9574,  9595,  9617,  9638,  9659,  9681,  9702,  9723,
9745,  9766,  9787,  9809,  9830,  9851,  9873,  9894,  9916,  9937,
9958,  9980, 10001, 10022, 10044, 10065, 10086, 10108, 10129, 10150,
10172, 10193, 10215, 10236, 10257, 10279, 10301, 10323, 10346, 10368,
10391, 10414, 10436, 10459, 10484, 10512, 10539, 10567, 10595, 10622,
10650, 10678, 10706, 10735, 10764, 10793, 10822, 10851, 10879, 10908,
10937, 10966, 10995, 11024, 11053, 11082, 11111, 11140, 11168, 11197,
11226, 11255, 11284, 11313, 11342, 11371, 11405, 11441, 11478, 11514,
11551, 11587, 11623, 11660, 11695, 11731, 11766, 11801, 11836, 11871,
11906, 11942, 11978, 12014, 12051, 12087, 12124, 12160, 12196, 12233,
12274, 12317, 12360, 12403, 12445, 12488, 12531, 12573, 12616, 12659,
12702, 12744, 12787, 12830, 12872, 12915, 12959, 13003, 13047, 13091,
13135, 13179, 13223, 13267, 13317, 13367, 13417, 13467, 13518, 13568,
13618, 13669, 13726, 13784, 13842, 13900, 13957, 14015, 14073, 14131,
14195, 14259, 14323, 14387, 14451, 14515, 14579, 14644, 14716, 14787,
14859, 14930, 15002, 15074, 15145, 15218, 15297, 15376, 15455, 15534,
15613, 15693, 15772, 15852, 15939, 16025, 16112, 16199, 16285, 16372,
16459, 16547, 16640, 16733, 16826, 16919, 17011, 17104, 17197, 17295,
17411, 17527, 17642, 17758, 17873, 17989, 18105, 18231, 18388, 18545,
18702, 18859, 19016, 19174, 19331, 20430
};
UInt32 v = (interp[d]) / 100;
return StrPrintF(s, "%d.%02d", (UInt16)v, (UInt16)(v % 10000));
}

I'll try to convert it today and see what I can come up with.

Basically unit, 58.88 which lands at 9.51:1, don't think that matches up to the gauge :/

V * 2 + 9.3 is closer but also not it. If you can... get more points so I can plot it out, it should start to match up with some equation.

Also something quite important about matching gauges, they must share the same ground as the ecu. So I would highly suggest grounding the gauge to the ECU ground, and not any random frame ground to help get consistency between the 2. The same goes for measuring voltage output from the gauge itself, make sure your ground on your voltage reader is to the ECU ground

I can tell you from personal experience working with my he351ve turbo controller, when I am programming and monitoring the device through the USB connection, my ISR for counting engine rpm, is different, when I am just connected through bluetooth (not using a different ground ie PC), so sources and grounds really matter in this type of stuff.
Pages: [1] 2 3 ... 10