pyXede: public release
Thread Starter
Evolved Member
iTrader: (6)
Joined: May 2004
Posts: 2,502
Likes: 1
From: Tennessee, USA
pyXede: public release
A new version of pyXede is available a little earlier than expected. The new version has been significantly revamped and will progress until a stable version 2.0. This one is marked 1.5 as I feel about half of the 2.0 stuff is working the way it should. Here's the changelog:
o Most prominant is the new support for Vishnu's "SMART" information. If the hardware is available, then information like knock and wideband AFR can be viewed and logged. If not, then you just get boring flat lines.
o There's an integrated debugging and scripting console, aptly named the "Master Control Program". Yes, the MCP has returned. What am I talking about, you ask. Go watch Tron you young whipper-snapper.
o The Road dynomameter is vastly improved. First, there is now a central list of all currently loaded runs. This list also has an integrated plot of the currently selected run -- not just power/torque either. The plot displays AFR, knock, and timing info as well. Cool huh? In addition the dyno list will let you do all kind of swank analysis on your run. You can Save/Load. Import from basically any imaginable type of CSV file. You can trim data off the ends of the run. You can trim above a user-definable threshold. You can smooth power plot using a variety of different methods: SavGol, Moving window, Box, Nearest Neighbor. You can even superimpose plots, although this still requires the use of an external program, GNUPlot.
o When using the RoadDyno menu option, the generated run now gets placed in the dyno list after the run is complete rather than pop up in a new managment window. In addition to power/torque the RoadDyno dialog will now allow the user (you!) to choose other information you want logged such as AFR and knock. Here's the kicker. This information is plotted real-time when the run is in progress.
That's the big stuff. Underneath there are more changes, but people probably don't care. Just so people have an idea about what's rolling around in my head, here's what the plan has been for a release schedule. Version 1.0 was basically just the protocol work -- getting an open source library to talk to the xede. Version 2.0 is focused on data collection and analysis (stuff like SMART and Road dynos). My vision for version 3.0 is a complete mapping system. What I have in my head is not quite like anything I've seen before. I have a firm belief that closedloop/feedback systems can be smarter than they are. *sigh* If only the Xede had another 32mb of memory....ahem. Anyway, mapping is a long term goal.
The best place to get started is the website:
http://pyxede.sf.net
For you programmers out there, there's anonymous CVS access. Fix things!
Obligatory screen shots (somewhat old):
http://pyxede.sourceforge.net/screens/plot-1.1.png
http://pyxede.sourceforge.net/screen...r_knock_ts.png
http://pyxede.sourceforge.net/screens/big-1.2.png
In that last screen shot there aren't labels. Top is power/torque, green is AFR, white is knock, blue is timing shift. They data is a pretty crazy in that one, but that's the point. It's easy to _see_ that it's crazy.
d
o Most prominant is the new support for Vishnu's "SMART" information. If the hardware is available, then information like knock and wideband AFR can be viewed and logged. If not, then you just get boring flat lines.
o There's an integrated debugging and scripting console, aptly named the "Master Control Program". Yes, the MCP has returned. What am I talking about, you ask. Go watch Tron you young whipper-snapper.
o The Road dynomameter is vastly improved. First, there is now a central list of all currently loaded runs. This list also has an integrated plot of the currently selected run -- not just power/torque either. The plot displays AFR, knock, and timing info as well. Cool huh? In addition the dyno list will let you do all kind of swank analysis on your run. You can Save/Load. Import from basically any imaginable type of CSV file. You can trim data off the ends of the run. You can trim above a user-definable threshold. You can smooth power plot using a variety of different methods: SavGol, Moving window, Box, Nearest Neighbor. You can even superimpose plots, although this still requires the use of an external program, GNUPlot.
o When using the RoadDyno menu option, the generated run now gets placed in the dyno list after the run is complete rather than pop up in a new managment window. In addition to power/torque the RoadDyno dialog will now allow the user (you!) to choose other information you want logged such as AFR and knock. Here's the kicker. This information is plotted real-time when the run is in progress.
That's the big stuff. Underneath there are more changes, but people probably don't care. Just so people have an idea about what's rolling around in my head, here's what the plan has been for a release schedule. Version 1.0 was basically just the protocol work -- getting an open source library to talk to the xede. Version 2.0 is focused on data collection and analysis (stuff like SMART and Road dynos). My vision for version 3.0 is a complete mapping system. What I have in my head is not quite like anything I've seen before. I have a firm belief that closedloop/feedback systems can be smarter than they are. *sigh* If only the Xede had another 32mb of memory....ahem. Anyway, mapping is a long term goal.
The best place to get started is the website:
http://pyxede.sf.net
For you programmers out there, there's anonymous CVS access. Fix things!
Obligatory screen shots (somewhat old):
http://pyxede.sourceforge.net/screens/plot-1.1.png
http://pyxede.sourceforge.net/screen...r_knock_ts.png
http://pyxede.sourceforge.net/screens/big-1.2.png
In that last screen shot there aren't labels. Top is power/torque, green is AFR, white is knock, blue is timing shift. They data is a pretty crazy in that one, but that's the point. It's easy to _see_ that it's crazy.
d
Trending Topics
Suggestions?
File "C:\PROGRA~1\PYTHON23\lib\site-packages\Pythonwin\pywin\framework\scriptutils.py" , line 310, in RunScript
exec codeObject in __main__.__dict__
File "D:\VischnuXede\Software\pyXede\pyxede-1.5\wxgui.py", line 1194, in ?
app = MyApp(0)
File "C:\PROGRA~1\PYTHON23\Lib\site-packages\wxPython\wx.py", line 1957, in __init__
_wxStart(self.OnInit)
File "D:\VischnuXede\Software\pyXede\pyxede-1.5\wxgui.py", line 506, in OnInit
self.dynolist=wxdyno.DynoList(self.frame, "pyXede :: Dyno Runs")
File "D:\VischnuXede\Software\pyXede\pyxede-1.5\wxdyno.py", line 165, in __init__
self.Bind(wx.EVT_MENU, self.ViewDynoData, id=200)
AttributeError: DynoList instance has no attribute 'Bind'
exec codeObject in __main__.__dict__
File "D:\VischnuXede\Software\pyXede\pyxede-1.5\wxgui.py", line 1194, in ?
app = MyApp(0)
File "C:\PROGRA~1\PYTHON23\Lib\site-packages\wxPython\wx.py", line 1957, in __init__
_wxStart(self.OnInit)
File "D:\VischnuXede\Software\pyXede\pyxede-1.5\wxgui.py", line 506, in OnInit
self.dynolist=wxdyno.DynoList(self.frame, "pyXede :: Dyno Runs")
File "D:\VischnuXede\Software\pyXede\pyxede-1.5\wxdyno.py", line 165, in __init__
self.Bind(wx.EVT_MENU, self.ViewDynoData, id=200)
AttributeError: DynoList instance has no attribute 'Bind'
Thread Starter
Evolved Member
iTrader: (6)
Joined: May 2004
Posts: 2,502
Likes: 1
From: Tennessee, USA
Originally Posted by freedom
Suggestions?
EDIT: actually, the python version isn't the problem here, but i still suggest installing the latest python (2.4) and wxpython (2.6.1). It only takes like 2 minutes.
EDIT2: that error is almost certainly happening because you're using wxpython 2.4.x.
d
Last edited by donour; Aug 13, 2005 at 12:37 PM.
I didn't realize you moved to 2.4 & 2.6.1.
Originally Posted by donour
EDIT: actually, the python version isn't the problem here, but i still suggest installing the latest python (2.4) and wxpython (2.6.1). It only takes like 2 minutes.
d
d
Thread Starter
Evolved Member
iTrader: (6)
Joined: May 2004
Posts: 2,502
Likes: 1
From: Tennessee, USA
Originally Posted by freedom
I didn't realize you moved to 2.4 & 2.6.1.
Do you know anything about python? What to become the release manager.
d
Evolving Member
Joined: May 2005
Posts: 354
Likes: 0
From: NorCal
has anyone has a problem doing a dyno run on windows?
i setup everything for the run, it starts, then looks like the program freezes 200 rpm from the stop point. still says 'running...' but it never finishes, and the program locks up. all you can do is end the task.
i setup everything for the run, it starts, then looks like the program freezes 200 rpm from the stop point. still says 'running...' but it never finishes, and the program locks up. all you can do is end the task.
Thread Starter
Evolved Member
iTrader: (6)
Joined: May 2004
Posts: 2,502
Likes: 1
From: Tennessee, USA
Originally Posted by crusin_lancer
Donour you bad ***! Nice job. 
Still running 101oct?
Still running 101oct?
d