i'm using tunerpro for aldl and i want to work out duty cycle
i have the pulse width in the stream and i can use the formula
dutycycle= pulsewidth x rpm /600

but i can't work out if i can use an equation like that in the aldl setup
any ideas?

 

The current tunerpro version can't do math on 2 different ALDL values which is what you are wanting to do.

I have heard in the future it might be able to.

 

Indeed, it's coming. I've even got a "fuel economy" item working great in my test application (dependent on PW, RPM, MPH, and injector constant). =)

 

Thats so cool!
Tunerpro is a great application. Once I make some more money I'm buying the ostrich and registering it.

 

Oohs and Ahhhs..
And the crowd goes wild !!

 

Here's an image (a peak of sorts) of the test app, which will be released as a stand-alone datalogging and monitoring application. After I release it, I'll integrate all features into TunerPro v5.

In this screenshot, you can see how a fuel economy item is defined (i.e. how output from items are linked to create a new item) and the results as outputted in a new analog gauge control I just finished yesterday.

This gives you a hint of some of the cool features of the new ADX ALDL definition format. It's as powerful as the XDF format is, if not more.

M

 

Now that's really cool, Mark!!!!

 

Looks good. New file format???? ADX???

 

;-) Think XDF, but for data acquisition. (Yes, there is an ADS importer).

- new command types (listen for silence, listen for chatter, etc)
- command macros (link commands to other commands, etc)
- Item output linking (like the above example)
- constants (like the injector constant in the above example)
- calculated output can be passed to a lookup table
- string lookup tables supported (for things like outputting "High" if value > X)
- completely configurable histograms
- completely configurable dashboard
- completely configurable "list views" where defined items get added to a list view, bolded, colored, etc.

and more over time (I have lots of item types that I plan to add post-release, such as "state" items, where you can specify that a state is TRUE if MPH > X, load < Y, and overdrive == true).

Good stuff, and all working. I'll let you know when ScannerPro is ready for alpha testing.

M

 

I'm willing to help Beta that....

 

Looks excellent! If you need public testers, i'll be willing to help (maybe testing the 160 baud support? )

 

ScannerPro ?, kind of plain ya know.
Why not "MagnuScan Pro" !!!

Yea, I know

 

Mark, Vern is an excellent tester.
He can be very helpful for filling in the holes in your info and help files.
I think he helped on about 25% of the WB patch info file.
I mean that in a good way Vern...

 

I don't doubt it. I'll make an announcement when I'm ready for testing. =)

 

Mark, any esimate on the release date? I am interested and will test also.

 

I know you do, Scott - and thanks!!!

 

Yah Mark has some killer stuff coming that is for sure. I checked out a version to see if I could get it to connect to the 749 (code 58/59).

I was playing with this nice little historgram I made when I got it to connect.

 

We've pretty much hijacked the thread. Sorry!

No ETA. My ETAs are almost always way too optimistic anyway.

I've got 3 major work items left, each will cost about a full week of dev time (meaning 40 hours each). They are:

- writing the new datalogging engine
- writing the new monitor visualization (multiple items on one chart, range selection, log markers, etc)
- finish the dash (2 more controls to write, plus the dash itself)

Then I have to integrate everything and hook up the logging, write a UI for the logging (with features like search for min, max, XXX, jump to marker, etc).

So it's a bit out. I'd *like* to have something before the end of the summer, but we'll see.

 

You've got to fix your axes, man! =) Also, I've since added 3D graphing for the histos.

 

So, is ScannerPro going to be just a stand-alone scanning software, or will it also be a tuning tool like TunerPro/replacement for TunerPro?

 

HTH

Teeleton

 

Real time 3D graphs? As in 4D. That is looking nice and I like the ADX features. It seems to have it's own programming language built in.

Can the ALDL stream definition be defined in the file? So new ALDL modes could be added. I would like to try making a new mode to report a different set of 63 bytes. With the compiled modes I can't command the new modes right now with TP.

 

I made that before you told me how to fix it and that was the only screen shot I made.

 

Yes, macros will allow mode 4, etc. That isn't yet functional, but it will be.