[pheno]

Installed TestO on Linx7 Win8.1 tablet, 1GB RAM, 32GB flash, quad-core 1.83Ghz. Only for 79€. FTDI Drivers also installed easily. Seems to be working OK! It works great!.

Also updated TestO (05-Mar-2015). You can set update speed for graph from context menu. So it's lighter on CPU when logging.

[DWR]

Nice work Pheno.
I'm going to sing your praises for a bit here. Pheno has been working on a number of things lately that will improve the Testo experience. As you can see, getting it on a touch screen. I'm sure nice big buttons will be in the future.

He has also found some improvements to the logging speed. That's important because the horsepower and torque gauges we are developing need speed to work properly. In order to make these gauges, Pheno has included facility for calculated parameters, essentially formulas.

Being able to review a log without importing a file to Excel is something in the works. The goal is to be able to 'playback' a log within Testo.

Custom jobs are easy now with double click loading of jobs. Something I just learned, you can log more than one control unit at a time. I recently logged EGS and DDE jobs in same session - very cool.

For my part, I keep finding ways to screw these things up and Pheno keeps finding ways to mistake proof. So a along the way, subtle changes are being made that you may not have noticed.

I want to end this post with a question. Do you think many folks would be interested in a 'complete package'. A tablet, cable and software, everything installed ready to go?

[TDIwyse]

Originally Posted by DWR

Nice work Pheno.
I'm going to sing your praises for a bit here.

[Angel choir joines in]

Originally Posted by DWR

Pheno has been working on a number of things lately that will improve the Testo experience. As you can see, getting it on a touch screen. I'm sure nice big buttons will be in the future.

This would be nice. I get frustrated with my touchscreen trying to touch the little text/boxes ...

[pheno]

Thanks DWR and TDIwyse !

Yes, I have to make buttons and fonts bigger or configurable. It helps if you set DPI value from Windows. I mean the scaling of icons and fonts. I have set it to 150% and it's much better.

In testo.ini there is added section [graph] with one item: FPS. There you can permanently set it to either 'realtime' or some number. When logging I advice to set it to some value like 5 to save some CPU cycles...

[iaknown]

Originally Posted by DWR

Nice work Pheno.
I want to end this post with a question. Do you think many folks would be interested in a 'complete package'. A tablet, cable and software, everything installed ready to go?

Now that would be awesome. How much interest though I'm not too sure.

And Pheno, you are the man.

[pheno]

I've made minimum Ediabas installation package that contains prg files for DDE 7.3 US. The ZIP file is roughly 10MB and installation is easy. In case someone's interested I can upload it somewhere. For TestO you only need Ediabas.

[TorqueAddict]

Originally Posted by pheno

I've made minimum Ediabas installation package that contains prg files for DDE 7.3 US. The ZIP file is roughly 10MB and installation is easy. In case someone's interested I can upload it somewhere. For TestO you only need Ediabas.

That will be great! I am willing to test it out!

[pheno]

Originally Posted by TorqueAddict

That will be great! I am willing to test it out!

There you go:

http://phenoboy.kapsi.fi/testo/EDIAB...6-Feb-2015.zip

unzip into c:\ and rename EDIABAS_min --> c:\EDIABAS

Here's what I did for the tablet:

-Install ftdi drivers.
-Extract Ediabas zip into c:\ folder and rename to EDIABAS.
- attach OBD cable. It should be detected. Verify com port number from
control panel-> devices
- check driver properties. Set latency to minimum 1 ms and both buffers
value to 64.
- modify c:\ediabas\bin\obd.ini and change com port accordingly
- copy obd.ini into c:\windows
- add c:\ediabas\bin into environment path <-- this is important!

'Environment Variables' dialog is under:

Control panel->System and Security->System Properties->Advanced-> and click on Environment Variables.

- extract latest testo from http://phenoboy.kapsi.fi/testo and copy msvcp100.dll and mscvr100.dll in the same folder OR
install full MS Visual Studio VC++ 10 runtime setup exe. http://www.microsoft.com/en-us/downl...s.aspx?id=5555
- start TestO and enjoy

This contains .prg files for US 335D only and gearbox. I can add more if needed.

[DWR]

Originally Posted by pheno

- add c:\ediabas\bin into environment path <-- this is important!

'Environment Variables' dialog is under:

Control panel->System and Security->System Properties->Advanced-> and click on Environment Variables.
.

It looks like this:

[TorqueAddict]

Pheno, first, thank you for this fantastic tool. I was able to get it to work, but i couldn't find
"ABTRIEBSDREHZAHL = output speed
TURBINENDREHZAHL = turbine speed"

these values. Perhaps they need to be included in the ediabas folder?

[pheno]

Originally Posted by TorqueAddict

Pheno, first, thank you for this fantastic tool. I was able to get it to work, but i couldn't find
"ABTRIEBSDREHZAHL = output speed
TURBINENDREHZAHL = turbine speed"

these values. Perhaps they need to be included in the ediabas folder?

Please check the attachment. So you'll have to select ecu: GS19D and job 'STATUS_ABTRIEBSDREHZAHL'. Translations are taken straight from the .prg file so they are quite often in german language. I really should start focus more on the translation part of TestO

Similarly there is job for turbinespeed:

STATUS_TURBINENDREHZAHL.

When you run the job you should see results like:

STAT_ABTRIEBSDREHZAH_WERT -> output speed
STAT_TURBINENDREHZAH_WERT -> turbine speed

[pheno]

basic playback functionally with gauges introduced in latest version. Next there will be graph window too.
This will work with existing .cvs files also. For new logs an additional .info file is saved to make playback know about exact jobs/results that were saved. If there's .info it can utilize gauge definitions

[TDIwyse]

Cool. I'm several generations behind on this tool now. It's been a few weeks since I last updated :-)

[pheno]

Originally Posted by TDIwyse

Cool. I'm several generations behind on this tool now. It's been a few weeks since I last updated :-)

Yes, well.. new features might introduce new bugs so it's good to keep a working version in the back pocket :-)

EDIT: let me know if you find something strange. UI for playback is quite rough though

[iaknown]

Do you guys notice a problem with multiple graphs up? I am using the newest version and if I stretch the window out to show multiple graphs logging at the same time within a job things get really really slow. Had to close Testo a few times to recover it was so bad. Interestingly, when I close the same window to only allow 1 or 2 graphs showing it seems much better.

[pheno]

Originally Posted by iaknown

Do you guys notice a problem with multiple graphs up? I am using the newest version and if I stretch the window out to show multiple graphs logging at the same time within a job things get really really slow. Had to close Testo a few times to recover it was so bad. Interestingly, when I close the same window to only allow 1 or 2 graphs showing it seems much better.

I've added refresh rate option which might trigger slower update rate if it finds that UI is not responsive. I guess it does not work as expected

When it seems slow could you try putting refresh->real time from context menu. Is it still slow?

[pheno]

I can confirm that the UI update is *very* slow. Seems that version 05-Mar-2015 works normally. Thanks iaknown for finding this out!

http://phenoboy.kapsi.fi/testo/testo-05-Mar-2015.zip

[pheno]

Two things found:

Version from 05-mar used faster windows style.
Curve tracker had to go for now.

[TDIwyse]

Ha! Sounds like some design reviews around here ...

[pheno]

Originally Posted by TDIwyse

Ha! Sounds like some design reviews around here ...

Yep, doing code review with myself

New version uploaded.

[jakeybear]

Originally Posted by TDIwyse

Cool. I'm several generations behind on this tool now. It's been a few weeks since I last updated :-)

"Good grief Charlie Brown... How's a man supposed to keep up?"

[ingenieur]

Originally Posted by pheno

Installed TestO on Linx7 Win8.1 tablet, 1GB RAM, 32GB flash, quad-core 1.83Ghz. FTDI Drivers also installed easily. Seems to be working OK! Did not try yet on my car but I guess it should work fine.

Also updated TestO (05-Mar-2015). You can set update speed for graph from context menu. So it's lighter on CPU when logging.

Originally Posted by pheno

Yep, doing code review with myself

New version uploaded.

I prefer to use a data logviewer rather than the gauges, but then this is more of a diagnostic tool rather than for tuning. Glad to see this forum is actively participating in the feedback as your recent versions have become very versatile, flexible, and easier to configure. Cheers mate!