History of IssueReports
Older Newer
2017-03-16 12:51:55 . . . . catv-80-98-142-196.catv.broadband.hu [minor cleanup]
2017-01-06 15:33:25 . . . . 94.160.52.103 [1.2.36 bug]
2014-07-15 14:19:18 . . . . catv-80-98-222-153.catv.broadband.hu [BT serial recommendations]
2014-07-02 10:20:15 . . . . MembersPage/MattiasSandgren [Still disconnect on config upload, now reverted to 1.2.11 and works fine]
2014-07-02 10:15:19 . . . . catv-80-98-222-153.catv.broadband.hu [notes about changing coil => missing tooth (reboot needed)]
2014-07-01 15:01:56 . . . . MembersPage/MattiasSandgren [ECU with fw 1.2.27 disconnects on small config change]
2014-06-29 12:07:42 . . . . 0x4dd554e3.adsl.cybercity.dk [Vems BT corrupt data]
2014-06-29 12:06:03 . . . . 0x4dd554e3.adsl.cybercity.dk [BT corrupt data]
See complete list (125 entries)


Changes by last author:

Changed:
** any report without these will be deleted. Add .vemslog or .vemscfg

** and besides these, (especially if a trigger problem, with new firmwares like 1.1.81) also a triggerlog (so the team can get a chance to reproduce and help to resolve the case).

** Note that newer firmwares have new trigger-settings in config bits that were previously "don't care". Bad settings of these will simply prevent triggering, so carefully check after uploading an 1.0.x or 1.1.7x or older config to a new 1.1.8x firmware)

** Add .vemslog (or .vemscfg, but log is better)

** any report without these is useless (will need more data).

** a triggerlog and/or scopeshot is also needed if the problem is trigger related (scopeshot helps, but not always strictly needed) so the team can get a chance to reproduce and help to resolve the case

** Note that newer firmwares have new trigger-settings in config bits that were previously "don't care". Bad settings of these will simply prevent triggering, so carefully check after uploading an 1.0.x or 1.1.7x or older config to >1.1.8x firmware (or upto 4 trigger for recent >=1.2.36 .. 1.2.38 fw that supports controlling upto 4 camshafts)

Changed:
* MegaTune version (when MegaTune is used at all)
* VemsTune version
Changed:
"rising" wheelspeed sensor edge option not present
* "rising" wheelspeed sensor edge option not present

** either rising or falling should work the same for wheelspeed

** fixed in 1.2.38 and up, or was just a VT ini typo and fixed retroactively ?