pyXede: public release
Originally Posted by donour
Those numbers are fine, except they aren't in any unit that most people would recognize. If you didn't notice, all the torque/power calibration code is completely disabled. The torque values you see are in the unit RPM/second or more correctly 1/seconds -- useful for tuning, useless for bragging. 
Originally Posted by donour
The value you see under "timing" is "Tuned timing out". It's value ranges from -128 to 128. In other words, it's the ouput crank angle sensor.
EDIT: I'm not sure how you could get all zeros unless your timing table is empty. Are you running a map with a zero'd timing table?
d
EDIT: I'm not sure how you could get all zeros unless your timing table is empty. Are you running a map with a zero'd timing table?
d
Thread Starter
Evolved Member
iTrader: (6)
Joined: May 2004
Posts: 2,502
Likes: 1
From: Tennessee, USA
Originally Posted by gsujeff55
yes, i am. i thought this program showed actual degrees of timing the ECU was seeing???
EDIT: On a side note, this is the same thing that Xmap does. My software was never intended to replace xmap or xupdate, but some of us can't run xmap. This is an alternative.
d
oh, so the timing log just tells us what the xede is seeing? Therefore, just tells us what we put in our table?
The xede doesn't pull timing when a knock condition occurs, the ECU does, so what does the timing sample actually tell us?
The xede doesn't pull timing when a knock condition occurs, the ECU does, so what does the timing sample actually tell us?
Thread Starter
Evolved Member
iTrader: (6)
Joined: May 2004
Posts: 2,502
Likes: 1
From: Tennessee, USA
Originally Posted by gsujeff55
oh, so the timing log just tells us what the xede is seeing? Therefore, just tells us what we put in our table?
The xede doesn't pull timing when a knock condition occurs, the ECU does, so what does the timing sample actually tell us?
The xede doesn't pull timing when a knock condition occurs, the ECU does, so what does the timing sample actually tell us?
d
o, im not taking anything the wrong way....
i don't understand what there is to explain i guess, i mean, what im asking is if the timing log shows what is in our xede table at a given RPM? nothing more, nothing less?
i don't understand what there is to explain i guess, i mean, what im asking is if the timing log shows what is in our xede table at a given RPM? nothing more, nothing less?
Thread Starter
Evolved Member
iTrader: (6)
Joined: May 2004
Posts: 2,502
Likes: 1
From: Tennessee, USA
Originally Posted by gsujeff55
o, im not taking anything the wrong way....
i don't understand what there is to explain i guess, i mean, what im asking is if the timing log shows what is in our xede table at a given RPM? nothing more, nothing less?
i don't understand what there is to explain i guess, i mean, what im asking is if the timing log shows what is in our xede table at a given RPM? nothing more, nothing less?
EDIT: ack. I said freq0. Actually it's CAS. freq0 is the maf signal
The original value is 0-255, but that get's shifted to -128:127. At no point does it actually access the table. What you're really asking is how that signal is generated. Ask shiv.
d
Last edited by donour; Aug 15, 2005 at 10:16 AM.
Thread Starter
Evolved Member
iTrader: (6)
Joined: May 2004
Posts: 2,502
Likes: 1
From: Tennessee, USA
Originally Posted by gsujeff55
ok, this may have been stated...but if it was, it wasn't in my language..LOL
once i import the log to wxdyno how do i plot the graph to look like actual tq and hp curves???
once i import the log to wxdyno how do i plot the graph to look like actual tq and hp curves???
EDIT: that window is illustrated in this screenshot:
http://pyxede.sourceforge.net/screens/big-1.2.png
Here you see run #5 in one window and run #2 in another. Notice that run #2 and #5 are actually the same -- only some smoothing has been done.
d
Last edited by donour; Aug 15, 2005 at 06:00 PM.
Thread Starter
Evolved Member
iTrader: (6)
Joined: May 2004
Posts: 2,502
Likes: 1
From: Tennessee, USA
Originally Posted by gsujeff55
LOL, this is what mine looks like
d
Originally Posted by donour
Um, that wasn't a very clean run. You have to stay WOT for the entire run or the data doesn't make any sense. If you drop to partial throttle at any point, the run is bogus. You also seem to have loaded the wrong data to AFR and knock.
d
d
also, i dunno how to stop it without getting off the throttle. I mean, you do have to hit "stop"(or something similar). Can't really do that pulling 3gs of acceleration!
Newbie
Joined: Aug 2005
Posts: 24
Likes: 0
From: Chicago
Modify Xede map through pyXede?
Is it possible to program pyXede so that it could adjust the values of individual cells in the tuning maps in the Xede, through the comm port? In XMap you can change a value and it takes effect right away, so obviously the value is passed through the serial port to the Xede in real time, right? So here's where I'm going with this. Imagine doing a DynoRun in pyXede and then have it compared to a "base" run. pyXede would then compare the 2 runs to see if the HP/Torque increased or decreased. It could then send some map changes (like leaning the fuel map, for instance) and then pull another Dyno run to see if the changes made things better or worse. If the HP increased, this would become your new "base" run and the next run would be compared to it. If the HP was less, then it would discard that run and make make fuel adjustments in the opposite (richer) direction. So as a user, all you would do is keep doing full throttle 3rd gear runs from 2,000 ish rpm over and over again untill pyXede had found the maximum HP settings, that now becomes your new fuel map!. I know it's not that simple, but in theory it might work? It's no different than multiple dyno runs except you can do it on the street and it makes adjustments automatically. Obviously you'd have to set some parameters so it didn't go too lean or advance timing too much. Any thoughts, anyone?