turbominicooper Posted July 22, 2016 Share Posted July 22, 2016 so i bought this little device from this site - jfbreton.blogspot.com/ https://www.youtube.com/watch?v=YfbG_h_PlrE i got the harness (£30) and plugged (£35) version down: install was easy with the plug: but a bit more trickier with the harness. due to me having a mk1 GT i did not have an ecu with TE2 pin nor did the wire go to the diagnostic plug so there was some messing about getting it to work for me but for anyone with a more recent ecu (non-green labelled) should be ok for plug-n-play. once setup it was just a case of downloading the TOYODB1 app from the PlayStore (android only) and setting up: turn the key, and... data: easy data im not selling these so please dont send me enquiries. ThanksRyan Quote Link to post Share on other sites
morgey Posted July 22, 2016 Share Posted July 22, 2016 Whats the delay time on these and whats actually displayed? I like the idea but i remember some older ones and they had a fair amount of lag Quote Link to post Share on other sites
mech5107 Posted July 22, 2016 Share Posted July 22, 2016 Nice presentation. I guess that having the data (even slow) is better than no data at all. Could you do some logs with it and post the file? Quote Link to post Share on other sites
turbominicooper Posted July 22, 2016 Author Share Posted July 22, 2016 Whats the delay time on these and whats actually displayed? I like the idea but i remember some older ones and they had a fair amount of laglooking on logs it's bout 1.3 seconds flash rateill post logs in next hour Quote Link to post Share on other sites
Foggy Posted July 22, 2016 Share Posted July 22, 2016 Where can these be got ? Quote Link to post Share on other sites
turbominicooper Posted July 22, 2016 Author Share Posted July 22, 2016 (edited) Nice presentation. I guess that having the data (even slow) is better than no data at all. Could you do some logs with it and post the file? log will be here for 30 days LINK can do more if your wantingWhere can these be got ? jfbreton.blogspot.com/ Edited July 22, 2016 by turbominicooper Quote Link to post Share on other sites
Foggy Posted July 22, 2016 Share Posted July 22, 2016 How are you finding it? Any good ? Quote Link to post Share on other sites
turbominicooper Posted July 22, 2016 Author Share Posted July 22, 2016 How are you finding it? Any good ? data is data Quote Link to post Share on other sites
Foggy Posted July 22, 2016 Share Posted July 22, 2016 True but what I mean is it working as it should or any issues? Quote Link to post Share on other sites
mech5107 Posted July 22, 2016 Share Posted July 22, 2016 That's a very strange format for the log... not many software would open it easily. Do they provide a tool to view the log? Quote Link to post Share on other sites
turbominicooper Posted July 22, 2016 Author Share Posted July 22, 2016 True but what I mean is it working as it should or any issues? once id sorted the ecu and wire for te2 pin it was just a case of turning on the engine and data was there within a couple seconds. That's a very strange format for the log... not many software would open it easily. Do they provide a tool to view the log? csv is excel format so microsoft office or polaroid viewer on the android device Quote Link to post Share on other sites
mech5107 Posted July 22, 2016 Share Posted July 22, 2016 It's not the file type, it's the fact that the data are in the same cell both numbers and text. For example in the injection colums it says 1.6ms... You can't plot/work easily with that type of formation. But an excel script to take out the "garbage" would be very easy to do... Quote Link to post Share on other sites
zf_165_gt4 Posted July 22, 2016 Share Posted July 22, 2016 Hi,I'm the one making those tools and developing the app,refresh rate is effectively 1.3s, this is a limitation that all toyota obd1 ecu have. about logs, the format is meant for it being read in ms excel or open office, on top is the human readable data, down low is the raw data.it's mostly meant to be read as is for troubleshooting( I know this is not the best ;) ) or run custom vba macros on that data.It's also meant to be imported back into other's people android device for data replay or building back maps from a few engines logs.if there are some very popular standards for logs I will consider them just let me know. so to view logs, you can do a data replay directly in the android app, no ffwd pause or anything else yet. you can also export to .ctr files to open logs with the old russian Cartester8000 app in windows where you can do a replay too and play/pause the data. Quote Link to post Share on other sites
mech5107 Posted July 23, 2016 Share Posted July 23, 2016 (edited) Hi mate, congrats on the tool. Perfect to get the some info on the stock map of the 4efte and have a good base map for standalones. About the formating, it would be easier for everyone if it was exporting the log like most data loggers do First line goes like: Time,TPS,RPM,ECT,Inj,Ign,....Second line are the units: sec,%,rpm,degC,ms,deg BTDC,...Third line and on are the data for each timestep. I can provide a sample log if you like... Edited July 23, 2016 by mech5107 Quote Link to post Share on other sites
Calum122 Posted July 23, 2016 Share Posted July 23, 2016 Dayum! Seeing as I'm a Developer, the logs will be all I care about. I run a raspberry pi on my car anyway for the media centre. So this would do nicely! Will have to keep an eye on this. Quote Link to post Share on other sites
zf_165_gt4 Posted July 24, 2016 Share Posted July 24, 2016 mech5107 yes please share a sample thanks Quote Link to post Share on other sites
mech5107 Posted July 24, 2016 Share Posted July 24, 2016 Here you go: http://www.filedropper.com/2_77 It's missing the units, but units are not needed in most S/W. Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.