[MasterWang]

http://www.n54tech.com/forums/showthread.php?t=25659

For all the JB4 users out there, looks like Terry figure out how to get the JB4 to log timing advance & ignition corrections on all cylinders.

"I also expect this will lead to back end flash map improvements, smarter auto tuning algorithms, a meaningful knock light in dash, etc."

[pwr hungry]

Very nice!

[135Pats]

Very impressive. The thought of tuning a single with only one cylinder available to log...not cool.

This on the other hand is very cool.

[pwr hungry]

This could actually give the jb a real edge over process for the first time....ever. Good job Terry!!

[135Pats]

Originally Posted by pwr hungry

This could actually give the jb a real edge over process for the first time....ever. Good job Terry!!

I still don't like how it reports load (blindfolds the DME), but agreed this is huge. That was easily my biggest reason for not stacking. At this point I really don't see a reason to not stack, you get the outstanding direct boost control of the piggyback, then let the flash handle timing, fuel, VANOS, etc etc. I just wonder how the 6AT deals with factory load values on an obviously non-factory setup.

[Jeff@TopGearSolutions]

Now if he could just figure out a way to make a log that utilizes 3-4 different graphs that showw 3-4 different sensors at a time so people can actually read what is going on! LOL

[pwr hungry]

Originally Posted by Jeff@TopGearSolutions

Now if he could just figure out a way to make a log that utilizes 3-4 different graphs that showw 3-4 different sensors at a time so people can actually read what is going on! LOL

Can't the log just be imputed into datazap and then no more issues?

[Jeff@TopGearSolutions]

Originally Posted by pwr hungry

Can't the log just be imputed into datazap and then no more issues?

Of course. That's just another step though.

All other tuners software on other platforms comes complete with 3-4 built in graphs and you can enable or disable your sensors to your liking. Not only is it easier on the eyes but it really helps pinpoint any flaws.

Reading these mickey mouse logs is exhausting, especially with the thin lines and similar colors and low resolution.

Here is an example of what I think they should look into:



Even PROcede had multiple graphs but that still needed some work too.

[Miller335]

Originally Posted by Jeff@TopGearSolutions

Now if he could just figure out a way to make a log that utilizes 3-4 different graphs that showw 3-4 different sensors at a time so people can actually read what is going on! LOL

The graphs yes but the csv logs it shouldnt be an issue.

[j1gilles]

Originally Posted by Jeff@TopGearSolutions

Of course. That's just another step though.

All other tuners software on other platforms comes complete with 3-4 built in graphs and you can enable or disable your sensors to your liking. Not only is it easier on the eyes but it really helps pinpoint any flaws.

Reading these mickey mouse logs is exhausting, especially with the thin lines and similar colors and low resolution.

Here is an example of what I think they should look into:



Even PROcede had multiple graphs but that still needed some work too.

Using the graph for "fine tuning" is a bad idea anyway... CSV is perfect and is a breeze to use. I agree the graph can look a little drunk if you have too many values selected but the JB4 is still by far your best option for a stand alone piggy or stacked

[Jeff@TopGearSolutions]

Originally Posted by j1gilles

Using the graph for "fine tuning" is a bad idea anyway... CSV is perfect and is a breeze to use. I agree the graph can look a little drunk if you have too many values selected but the JB4 is still by far your best option for a stand alone piggy or stacked

I never bothered with CSV, graphs are much more user friendly.

I'm not debating if JB4 is a good tune. I personally like PROcede but that is not the point. I'm just referring to the graphing and logging capabilities or lack thereof. It's something that has been bothering me since nearly 2007 with the JB stuff.

[Blaster400]

One more reason (actually 5 more reasons) to go with JB4.

[j1gilles]

Originally Posted by Jeff@TopGearSolutions

I never bothered with CSV, graphs are much more user friendly.

I'm not debating if JB4 is a good tune. I personally like PROcede but that is not the point. I'm just referring to the graphing and logging capabilities or lack thereof. It's something that has been bothering me since nearly 2007 with the JB stuff.

Graphs are good for obvious fluctuations but for subtle stuff direct values are the way to go (in my opinion). Any sales on IC's for the 4th Jeff?

[Jeff@TopGearSolutions]

Originally Posted by j1gilles

Graphs are good for obvious fluctuations but for subtle stuff direct values are the way to go (in my opinion). Any sales on IC's for the 4th Jeff?

No sales on FMIC for July 4th. We actually charge more because Murica! (JK, PM me) It's not appropriate for me to derail this thread with promotions, especially outside of a classified section, against forum rules.

I see what your saying but I've been tuning my own vehicles and E tuning for the past decade and never really had to dive into a CSV file for any car.

[pwr hungry]

Originally Posted by Jeff@TopGearSolutions

No sales on FMIC for July 4th. We actually charge more because Murica! (JK, PM me) It's not appropriate for me to derail this thread with promotions, especially outside of a classified section, against forum rules.

I see what your saying but I've been tuning my own vehicles and E tuning for the past decade and never really had to dive into a CSV file for any car.

I agree with you. if your tuning anything so close to the limit that you HAVE to go off of the csv and not the graph, you're gonna have a bad time anyway. Now if you just wanna be extremely anal and put in that non value added cost/time, so be it, but if you scale the graph resolution correctly, there is no reason the graph isn't good enough.

[j1gilles]

Originally Posted by pwr hungry

I agree with you. if your tuning anything so close to the limit that you HAVE to go off of the csv and not the graph, you're gonna have a bad time anyway. Now if you just wanna be extremely anal and put in that non value added cost/time, so be it, but if you scale the graph resolution correctly, there is no reason the graph isn't good enough.

Looking a squiggly lines hurts my eyes...

[V8bait]

Datazap is awesome. Csv is great but sometimes you get so focused on the tree you miss the forest, the graphs (namely datazap) are great.

I like the csv for non wot tuning stuff personally where the graphs are less useful.

Anyway this is a huge step, looking forward to it!

[Cloud9blue]

I am all up for the UI update on the JB4 software. Current one does the job, but it is just so hard to read if you are logging multiple values.

[Ingeniator]

I would love touch screen support. Most car software has this issue. My tablet works awesome as a platform except most of the programs I need a stylus to get the precision for most of the menus and options.

[cwarren]

anal...........csv