Smart 'device', dedicated to data display...

[Schrade]

Can this be done?

Instead of your laptop, while sitting only in the garage, maybe use an Android, or Apple i-x, or similar smart-device, onto which data logging software could be loaded, and mount it permanently, somewhere on the dash / console.

Or has someone here already done this?

[Kevin]

would be awesome if that could be done. I think the issue is the cable required

[RiceEatingZR1]

What software are you using for your laptops?

[RiceEatingZR1]

Found this in the App Store:


https://itunes.apple.com/us/app/itsx/id461100848?mt=8

http://www.sctflash.com/showsctproducts.php?Prod=iTSX

[DaveK]

Certainly can be done but you may have to develop the interface protocols yourself (as in programming). OBD I is considered obsolete so not much in the way of support for it.

Dave

[Kevin]

Found this in the App Store:


https://itunes.apple.com/us/app/itsx/id461100848?mt=8

http://www.sctflash.com/showsctproducts.php?Prod=iTSX

that says obd2 which doesn't help us

[-=Jeff=-]

Are you looking to record data? r just monitor it?

I have heard that some Android Devices can use a Serial adapter and a set of Serial drivers that I have seen on Google Play. so the question then becomes making the protocol to work in an android environment.

I think it can be done, but the issue I have is with the CCM, keeping it quite to get data.. but when you silence it I think it stops other things. If you don't need data as fast as fast can be, then I might be able to work it out.. I bought a Nexus 7, but need to learn how to program an app.. I have played with the datastream info on Tunerpro and I have also been able to capture data slowly with my own software. If I had an ecm bench with a LT5 ECM and a LT5 programmed CCM it would be a bit easier to work on it..


I think Bluetooth could be done too

[GOLDCYLON]

Are you looking to record data? r just monitor it?

I have heard that some Android Devices can use a Serial adapter and a set of Serial drivers that I have seen on Google Play. so the question then becomes making the protocol to work in an android environment.

I think it can be done, but the issue I have is with the CCM, keeping it quite to get data.. but when you silence it I think it stops other things. If you don't need data as fast as fast can be, then I might be able to work it out.. I bought a Nexus 7, but need to learn how to program an app.. I have played with the datastream info on Tunerpro and I have also been able to capture data slowly with my own software. If I had an ecm bench with a LT5 ECM and a LT5 programmed CCM it would be a bit easier to work on it..



I think Bluetooth could be done too

Cool -=JEFF=- it would have to be somebody like you to figure this out because I just dont see anybody doing it for OBD1 for our cars its would be sweet and maybe something you could even sell as an app

[scottfab]

Wow what a great idea for new cars.
All data viewable on your smartphone.
Phone become the ignition key when you get
in via bluetooth.
Car calls you if towed or tampered with in any way.
Car calls and makes appointments for service (warranty)
Car call attorney when a flash is detected by photo radar.
Ideas for it are endless.

You know once this all exists making the interface an older car
may become worth it..
Definitely doable from what I see of the internal serial com line.

[Schrade]

DEDICATED to DATA DISPLAY. as in ... NOT a phone any longer

PERMANENT - mounted to the dash / console.

I guess those words can be AMBIGUOUS. I should have made myself more clear in original post.

ME
...
onto which data logging software could be loaded, and mount it permanently, somewhere on the dash / console
...



(couldn't tell if one post was facetious or serious.. ( anyway, do new cars' display show pulsewidth? EVAP purge cycle? etc.?) )

[-=Jeff=-]

DEDICATED to DATA DISPLAY. as in ... NOT a phone any longer

PERMANENT - mounted to the dash / console.

I guess those words can be AMBIGUOUS. I should have made myself more clear in original post.



(couldn't tell if one post was facetious or serious.. ( anyway, do new cars' display show pulsewidth? EVAP purge cycle? etc.?) )

Okay.. has it been done with OBD1.. not to my knowledge, but I am pretty sure my post still addressed some of the pieces, You still have not answered if you need it to actually record the data, if so how fast?

Why not just a CarPC in place of the stereo then your choice of datalogger.. that will work too.

This is something I have wanted to try, just not sure when I would get to it. I have seen one where it would display but not record the data that would essentially be permanent

The Issue that could potentially be there is the Datalogger has to silence the CCM for the fast as fast can be logging, on a permanent install I am not sure how well the car would react all the time to that, so that is an unknown.

[scottfab]

.... snip...
The Issue that could potentially be there is the Datalogger has to silence the CCM for the fast as fast can be logging, on a permanent install I am not sure how well the car would react all the time to that, so that is an unknown.

I'm confused by both statements.
"silence CCM" ?
"permanent install ...... react" ?

I have a diacom ( ODB I to PC connector and ap) that has been connected before while driving. No issues.
Data can be logged and saved as you drive.

[-=Jeff=-]

I'm confused by both statements.
"silence CCM" ?
"permanent install ...... react" ?

I have a diacom ( ODB I to PC connector and ap) that has been connected before while driving. No issues.
Data can be logged and saved as you drive.

Yes, same with my EASE. But I found with ease it is sending different messages then what has been exposed to many of us..

Tunerpro uses different messages and gets the same result, but with tunerpro I remember having issues with losing packets of data.. not a ton, but quite a few.

Silencing the CCM is something that is done in tunerpro to stop the chatter on the serial line for data packets to be sent. It would be nice to see a Portmon log while running Diacom to see what commands are being sent and if the CCM is still chattering as well. I have not touched any of my Communication stuff from our cars in years honestly.. I would need to plug it back in and see where I left off.

I did find this: http://lukeskaff.com/?page_id=305 that could easily be adapted to our cars and it is permanent or could be.. but there is no logging.

Another thought would be using a Rasberry Pi and making a datalogger that works in Linux

[scottfab]

Yes, same with my EASE. But I found with ease it is sending different messages then what has been exposed to many of us..

Tunerpro uses different messages and gets the same result, but with tunerpro I remember having issues with losing packets of data.. not a ton, but quite a few.

Silencing the CCM is something that is done in tunerpro to stop the chatter on the serial line for data packets to be sent. It would be nice to see a Portmon log while running Diacom to see what commands are being sent and if the CCM is still chattering as well. I have not touched any of my Communication stuff from our cars in years honestly.. I would need to plug it back in and see where I left off.

I did find this: http://lukeskaff.com/?page_id=305 that could easily be adapted to our cars and it is permanent or could be.. but there is no logging.

Another thought would be using a Rasberry Pi and making a datalogger that works in Linux

Looks like some work has been done in that direction (Raspberry Pi)
at: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=44&t=7982&p=106819&hilit=aldl#p106819

I wonder though, if this project were a "permanent" addition to the instrument cluster whether a more invasive approach wouldn't be better. Rather than using the UART approach in Dig 7 on the ALDL of the lukeskaff link why not open the serial line (using a solid state relay) between the ECM and CCM under program control from the smartphone (or whatever used) ?

But backing up a bit I wonder if loss of packets is all that important.
For purposes of simply reporting to the car driver what's going on with key systems I wonder if the loss couldn't be characterized and normalized out of the way?

I know the diacom operates at 600 b to get the 160b data.
Now that I think back (to 1999) it does drop stuff now and then.
The data I did get was still very useful. (~98% accurate)

Certainly developing a retro ODB I for our cars would not be profitable but sure would be interesting and of great use toward sustaining the ZR-1 into the future. This could be a long term slow moving target for a virtual ZR-1 Net Registry team to tackle.