VEMS Home Products Documentation Wiki Webstore
WikiHome ProjectPage DocsPage UnderDevelopment MembersPage SiteIndex RecentChanges Preferences
History of MembersPage/FSTeamDelft
Older Newer
2008-03-28 12:09:02 . . . . MembersPage/MarcellGal [mcd, mct, etc...]
2008-03-26 18:35:40 . . . . dut-tech-09.DUTRACING [watchdog timer?]
2008-03-18 23:02:27 . . . . dut-tech-09.DUTRACING [4-cylinder configuration]
2008-03-18 22:56:46 . . . . dut-tech-09.DUTRACING [Crash problem]
2008-03-18 09:51:27 . . . . 131.180.24.21 [Vems crash with incorrect EGO warmup time]
2007-10-31 15:35:51 . . . . tls.xs4all.nl [RPM constant]
2007-10-25 17:22:34 . . . . DUT-TECH-08.DUTRACING [Small changes]
2007-10-25 16:46:21 . . . . DUT-TECH-08.DUTRACING [Fuel pump cross talk]
2007-10-17 13:18:29 . . . . MembersPage/MarcellGal [Next trigger tooth: 0 BAD !]
2007-10-15 11:34:41 . . . . dut-tech-03.DUTRACING [constant for rpm calc added]
2007-10-15 11:32:47 . . . . dut-tech-03.DUTRACING [Image fix etc.]
2007-10-15 11:26:56 . . . . dut-tech-03.DUTRACING [Trigger problem]
2006-12-19 18:59:00 . . . . dutw666.wbmt.tudelft.nl [Update]
2006-09-19 12:51:43 . . . . cust.12.229.adsl.cistron.nl [bit more information]
2006-09-19 12:50:19 . . . . cust.12.229.adsl.cistron.nl [added some information ans resized picture.]
2006-09-19 12:38:01 . . . . cust.12.229.adsl.cistron.nl [Team information added]

Changes by last author:

Changed:
After upgrading to 14x16 firmware and setting all the tables, my VEMS crashes after about 5 minutes running. When the engine is not running, the VEMS does not crash
After upgrading to 16x14 firmware and setting all the tables, my VEMS crashes after about 5 minutes running. When the engine is not running, the VEMS does not crash
Added:
There is no such known problem.

Some windows-USB-serial adapter driver combinations can sometimes crash MT (so that windows reboot needed) if ochblocksize=62 ('D' command) but they usually work with ochblocksize=56 ('A' command). Controller does not crash though.

Maybe this behaviour is somehow special to your configuration.

* publish mcd

* mct

* firmware version

* captured log before the crash. Can you reproduce on the bench, with same trigger pattern played from soundcard ?

** maybe you have access to another controller (different HW, with same fw+mcd+mct)