ok, when i try to do this:

Almost done, now download a pyXede release from the webpage. Decompress it and look for a file called wxgui.py. Away you go! If you want to try a different version of pyXede, just download a new release file.

when i click on the pyxede-1.5.tar file it give me the "cannot find program which created" message. any idea how to fix it? i don't have winzip, do i need it?

 

also, i get this message when clicking on wxgui.py in the version 1.0

Traceback (most recent call last):
File "wxgui.py", line 39, in ?
File "arch.pyo", line 37, in ?
File "ConfigParser.pyo", line 286, in get
ConfigParser.NoSectionError: No section: 'gnuplot'
Traceback (most recent call last):
File "wxgui.py", line 39, in ?
File "arch.pyo", line 37, in ?
File "ConfigParser.pyo", line 286, in get
ConfigParser.NoSectionError: No section: 'gnuplot'
Traceback (most recent call last):
File "wxgui.py", line 39, in ?
File "arch.pyo", line 37, in ?
File "ConfigParser.pyo", line 286, in get
ConfigParser.NoSectionError: No section: 'gnuplot'
Traceback (most recent call last):
File "wxgui.py", line 39, in ?
File "arch.pyo", line 37, in ?
File "ConfigParser.pyo", line 286, in get
ConfigParser.NoSectionError: No section: 'gnuplot'

 

I'm about ready to "pay" someone to teach me how to set up and use this... not because I am lazy, but because I am just too damn far behind the curve when it comes to "key strokes".

 

also, are there any instructions on how to use this stuff once its all installed?

sorry about all the questions donour

 

I'd use WinRAR. it has support for .tar and .gz files. www.rarlab.com

 

Once you get in there, its pretty simple. the only actual menu items you have are datalogging, highspeed datalogging, and perform road dyno.

other than that, just follow along and everything is pretty easy.

setup your com port under File, configure.

Also be sure to do Port, Connect if you dont see any numbers on the main pyXede screen (with the car running and connected)

 

what im asking is:

how do i get to those options(road dyno, highspeed log, ect)

I made a folder on my desktop with all of the stuff i downloaded and installed. Which of those programs to i actually use to log and do the road dyno?

 

To clear up a whole bunch of questions:

1) winzip should probably open the tar.gz file fine. It's unix-style zipped tarball. It's a pretty standard format that's been around for many, many years. Again, I have very little experience with windows, so I'm not sure exactly what will and won't open it. As Sackett said, winrar will probably work too.

2) wxgui.py is the file you want to run to start the graphical interface. The file isn't really a program so much as the source code to a program that gets run by the python interpreter. If you've installed python as per the directions, it should automatically launch python and get pyxede started. Once running it's pretty self explanatory.

You 'connect' to start communicating with the Xede.
Under 'file' there's data capture options
Under 'view' there's an option to display the list of loaded runs. If you close this window it doesn't really go away, it just hides in the background. If you 'view' it again, all your loaded runs are still there. However if you actually exit the program, then of course the runs you didn't save are gone -- it doesn't warn the user of this.

d

 

thanks, that clears some things up.

maybe us xede users could go by this when making mod comparisons and tune comparisons instead of dynos....i mean, we all using the same program is like us all using the same dyno correct??? of course, temp and conditions would vary...but you get the point!

i gotta get a freakin wideband.....will any part of this show actual AFRs in real time? Like, no having to log the run to get it, just view it on the laptop screen in real time?

 

I guess, but more important than all those things you mentioned is the road. Everybody would need more or less the same stretch of highway.

Yah sure, right on the main screen it shows current AFR reading (as well as current rpm, timing, etc). I suppose a history graph would be useful as well. Maybe for 1.6.

d

 

Actually, I have winzip 9.0 and it will _not_ open the archive. i downloaded strait from the website and tried, no dice.

this is why i have WinRAR installed on my PC also

 

ok, just tried my first road dyno. when picking RPM start and finish, i selected 2500 to 7000.

i did it 3-4 different times, and each time i got a graph that looked more or less like a heart monitor with red and blue lines. But, after i hit that desired RPM, the road dyno screen still says running....and i cant click on anything else.

what is supposed to happen when you hit the desired RPM? What is the black python24 screen supposed to say...right now, mine has 3 lines of "missed one".

any help would be appreciated! thanks!

 

Same problem i had. glad to see it's not just me. this seems to be a bug, just wait it out until donour can take a look at it.

the high-speed logging works well, and you can then 'import' the log into the Dyno viewer to see everything.

 

well, thats cool. glad to know its not just me as well.

I really appreciate both yours and donour's help. yuz guyz are great!

 

At this point, pyxede doesn't do any postprocessing of the data before displaying it,
so the power/torque curves aren't really visible.

[quote]
But, after i hit that desired RPM, the road dyno screen still says running....and i cant click on anything else.
[/quote

Yeah, sackett informed me a little while ago that the RoadDyno is puking on windows. I need to find somebody that has a windows laptop and will let me borrow it for a few hours. If you're desparate to get dyno runs in, you can always just do a regular highspeed datalog and then import the run.

That's a debugging info screen. You don't really have to pay attention to it unless something goes wrong. It's existence is sort of a by-product of windows not being based off a terminal interface.

The 'missed one' lines are debugging info from the logging task. When the Xede is set in highspeed logging mode, it sends data whether anything is waiting for it or not. Sometimes the data comes too fast or in an unexpected order. When this happens, my software is smart enough to recover at what's called a log "marker" by chiptorque. Any data received between 'getting lost' and 'finding marker' is basically junk because there is no way to determine what the data is representing (rpm, timing, afr, etc.). So for each byte of unidentified data, I print "missed one". It's common for this to happen right when datalogging is starting because I'm too lazy implement proper parsing of the log initiation protocol. Instead I just wait for the first maker then go. As you see, you usually only miss 3-4 bytes of data. That's only about 1 sample (i.e. 1/100th second).


d