working on learning how to datalog with the pyxede and seems to be a very easy program to use so far. question is, where is timing watched? don't see a box to check or what value to look for on timing...

anyone has any time, check out the logs below and let me know what you think?
it only has rpm, boost solenoid duty, smart knock, afr.

it's in excel comma separated value format zipped

look forward to your thoughts.....

 

Timing or time?

Time is sampled two ways -- either by the system clock or from the timestamps from the Xede unit.

Timing can come from either CAS in/out or Timing shift out. The Crank angle sensor is what the Xede modifies directly.

EDIT: CAS = crank angle sensor
("Crank timing out (tuned timing shift)","0 = -max; 128 = 0; 255 = +max"), However, I can't remember what max is off the top of my head.

Looks fine to me, although a bit noisy at the top of 3rd. Is your engine stock? I don't ever see knock levels that high with a vishnu map.

d

ps - I'm the author. Feel free to email me directly if you have other questions, but it's also good to discuss them in a public forum.

 

Yea, I have seen that you are the author of the program. it is an awesome program and your work on it should be commended. hopefully at some point in the future, chiptorque gives you the info that you have been looking for

in regards to timing/time, I am looking for timing and how to see what the engine has going on with timing. curious to see what it is running.

I have an 03 w/ 10.5/ebay o2 housing, helix dp/hf cat, rnr exhaust, fidanza cam gears on hks 272's, buschur intake, helix i/c piping, ams front mount, walbro..think that's all..
some of the noise, and I am not sure if this would cause it has to do with the downpipe hitting the 2 factory crossbars under the motor. seems that since I installed the hotside/o2 housing there is some noise coming from that area. I am crawling under the car this saturday to space them out and install kartboy downpipe bushings. maybe I need to scale the boost down a few? currently running 93oct. and run 21psi falling to 18.

so i need to check the boxes for cas in/out and the timing shift?

also, am currently searching for how to turn the dyno info into a useful chart to look at. I have seen how it datalogs, just not sure how to the the normal looking dyno chart. as stated, i am currently searching the threads for this.

 

Apparantly cam'd cars are quite a bit noisier than the stock engine. That's probably the cause right there. Any other people with 272s have info about your noise threshold?

Yup

The dyno function isn't the most...um...reliable code on the planet. I mean, it works fine for me, but folks on windows are always reporting that it doesn't work very well. It also isn't very forgiving of anomalies in the recorded data. For example, the Xede will occasionly throw out a crazy, and completely bogus, log point. It can really mess up your dyno pull if you don't notice and remove it.

If you want to email me a dyno pull, I can try to clean the data up a little an send it back.

d

 

will send one later tonight. I am stuck at work for another 2 hours, then a 20 minute drive home, but plan on logging a few runs on the way home. this is a cool new toy to play with

if shiv hasn't put you on the payroll yet, he should, and this program should be put on disc and sold with every xede. it is a cool datalogger that is very easy to use. much more data points than my old pocketlogger for my eclipse gst.....

 

ok, logged a dyno run. it allowed me to set it up and press log. it tracked the data and automatically stopped as I hit 7200 rpm's. then the only option was to cancel and the "x" to close the window. it froze as I tried to do either and pyxede shut down with a problem. any ideas?

 

Thats one of the windows bugs with the program. Mine does the same thing.

 

how do you get around it?

 

Can you post your version numbers from the about box?

d

 

yeah I can't get past this point either.

It looks like its a problem with the graphing engine, not donour's code.

I have continuous problems importing previous dyno runs to the point where I have not been able to take advantage of this program.

 

gnuplot shouldn't be getting called there. The all the other drawing code is mine as well.

That's unfortunate. I would really like to improve the stability, but unfortunately I don't have access to windows machine to do development. Maybe the next version of virtual pc will support my macbook. *shrug*

Here's another help request: any windows programmers out there want to take over the windows releases?

d

 

what about box are you talking about?

 

never mind....
wx.gui version 1.13
pyxede version 1.11
dyno.py version 1.10
gnuplot.py version 1.1.1.1
rpmplot.py version 1.5
authors:
c.donour sizemore