History of MembersPage/TrifanCatalin
Older Newer
2013-06-13 21:07:52 . . . . catv-80-98-222-153.catv.broadband.hu [BT steps]
2013-06-13 15:56:59 . . . . 5-13-111-105.residential.rdsnet.ro [HELLPPPPP!]
2013-06-10 19:22:51 . . . . 5-13-111-105.residential.rdsnet.ro [Knock sensing and bluetooth problems]
2013-02-01 22:11:32 . . . . 5-13-111-171.residential.rdsnet.ro [Final dyno pulls, and thanks.]
2013-01-25 07:11:16 . . . . 0x3ec671bf.inet.dsl.telianet.dk [Knock]
2013-01-24 18:47:55 . . . . 5-13-111-171.residential.rdsnet.ro [Knock problem]
2013-01-23 08:11:19 . . . . 62-101-48-216.sheab.net [answer for fuelcut]
2013-01-23 08:10:40 . . . . 62-101-48-216.sheab.net [answer for fuelcut]
2013-01-22 22:16:12 . . . . catv-80-98-222-153.catv.broadband.hu [firing order ign /inj table]
2013-01-22 21:40:59 . . . . 5-13-111-171.residential.rdsnet.ro [To make sure about ignition/injection ]
2013-01-22 14:47:04 . . . . catv-80-98-222-153.catv.broadband.hu [injout and ignout sequence note for VT (intuitive in new VT)]
2013-01-22 14:36:37 . . . . catv-80-98-222-153.catv.broadband.hu [injout and ignout sequence note for VT (intuitive in new VT)]
2013-01-21 22:35:11 . . . . 5-13-111-171.residential.rdsnet.ro [More help ]
2013-01-21 21:34:11 . . . . 82-137-12-184.rdsnet.ro [Knock detection problem]
2013-01-20 14:40:54 . . . . 5-13-111-171.residential.rdsnet.ro [Knock and cam settings info needed]
2013-01-10 18:33:26 . . . . catv-80-98-222-153.catv.broadband.hu [correct and clear info => correct conclusion (minor cleanup)]
2013-01-09 08:47:57 . . . . 5-13-111-27.residential.rdsnet.ro [correction]
2013-01-09 00:16:03 . . . . catv-80-98-222-153.catv.broadband.hu [yes. Adjusted polarity info for clarity]
2013-01-08 17:41:53 . . . . 5-13-111-27.residential.rdsnet.ro [Check]
2013-01-06 14:36:51 . . . . catv-80-98-222-153.catv.broadband.hu [you must read longtooth-shortgap wheel]
2013-01-05 21:31:07 . . . . 5-13-111-27.residential.rdsnet.ro [Polarity checked, trigger wheels question ]
2013-01-03 21:42:17 . . . . catv-80-98-222-153.catv.broadband.hu [use higher baudrate in triggerlog]
2013-01-03 19:50:05 . . . . 5-13-111-27.residential.rdsnet.ro [Triggerlog recorder issue]
2012-12-30 22:47:34 . . . . catv-80-98-222-153.catv.broadband.hu [if no scope, try the pull-away metal metod at least ]
2012-12-27 17:42:52 . . . . 5-13-111-27.residential.rdsnet.ro [change]
2012-12-24 15:57:26 . . . . TrifanCatalin [File Attachment]
2012-12-24 15:48:31 . . . . TrifanCatalin [Introduction and first problem]


Changes by last author:

Added:
* yes:

** make sure to be able to connect with vemstune and USB-serial

** try vemstune with the BT-serial. Make sure that works first (measure 5V supply, and supply current if it does not).

* bluetooth and Android does work for many, after enabling BT, without special tricks. Of course there can be several possible reasons for no-connect: if windows can connect via same BT module, but the android cannot, then the BT-serial driver in the specific Android version can be a suspect. Or it was not enabled, or perhaps the pin-code was not entered for it ?

** if there is some telephone-application installed that hijacks the BT-serial module (opens the port and tries to send some messages that of course v3 does not understand), that can be a problem

** much much more information is needed, go through the above steps, and don't forget to take note of versions.