VEMS Home Products Documentation Wiki Webstore
WikiHome ProjectPage DocsPage UnderDevelopment MembersPage SiteIndex RecentChanges Preferences
History of MembersPage/PatrickB
Older Newer
2015-02-27 01:17:12 . . . . catv-80-98-222-153.catv.broadband.hu [p259 provided some protection before being sacrificed .. damaged by insufficient]
2015-02-15 23:43:00 . . . . 120.17.93.171 [Fixed primary trigger problem but now VEMS is dead! MAX232 blown?]
2015-01-01 10:46:19 . . . . d110-32-140-164.sun800.vic.optusnet.com.au [Solved - Sensor GND disconnected from Power GND.]
2014-12-08 10:53:28 . . . . catv-80-98-222-153.catv.broadband.hu [p259 notes: URL of printable and browsable]
2014-12-04 09:05:27 . . . . CPE-110-148-139-35.vxl8.lon.bigpond.net.au [LM1815 VCC is only 1.4V. Why?]
2014-11-09 22:00:03 . . . . catv-80-98-222-153.catv.broadband.hu [minor updates - mostly formatting. Also some pointers]
2014-10-30 22:39:12 . . . . CPE-110-149-153-18.vwl9.win.bigpond.net.au [Still no primary VR on v3.8]
2014-10-26 01:42:20 . . . . CPE-120-144-75-140.lnse5.win.bigpond.net.au [v3.8 Primary Trigger Input (VR) not working - need 3.8 schematic]
2014-10-26 01:11:20 . . . . CPE-120-144-75-140.lnse5.win.bigpond.net.au [v3.8 Trigger Inputs not working - need 3.8 schematic ]
2014-04-04 23:29:17 . . . . 101.160.35.89 [Fuel Pump Output Problem - Need Help]
2013-01-11 13:00:26 . . . . catv-213-222-164-31.catv.broadband.hu [notes]
2013-01-11 11:45:47 . . . . CPE-121-214-125-67.lnse4.lon.bigpond.net.au [Cranking Advance Q.]
2013-01-11 10:09:28 . . . . catv-213-222-164-31.catv.broadband.hu [config example]
2013-01-11 09:28:21 . . . . CPE-121-214-125-67.lnse4.lon.bigpond.net.au [Engine runs briefly after correcting config H[2] for firing order.]
2013-01-10 18:09:07 . . . . catv-80-98-222-153.catv.broadband.hu [more guessing about basic info, another hint (related to 8 cyl)]
2013-01-10 11:43:33 . . . . catv-213-222-164-31.catv.broadband.hu [trigger settings help]
2013-01-10 11:36:35 . . . . catv-80-98-222-153.catv.broadband.hu [benchtest shows misconfiguration]
2013-01-10 11:04:53 . . . . catv-213-222-164-31.catv.broadband.hu [benchtest]
2013-01-10 10:40:02 . . . . catv-80-98-222-153.catv.broadband.hu [sectrig position ? Also fill in basic info about engine]
2013-01-08 08:00:55 . . . . CPE-121-219-180-222.lnse2.lon.bigpond.net.au [VR noise prob solved with LPF but now have spark event issue]
2013-01-08 07:52:03 . . . . CPE-121-219-180-222.lnse2.lon.bigpond.net.au [VR noise prob solved with LPF but now have spark event issue]
2013-01-08 07:49:53 . . . . CPE-121-219-180-222.lnse2.lon.bigpond.net.au [VR noise prob solved with LPF but now have spark event issue]
2013-01-08 06:09:41 . . . . CPE-121-219-180-222.lnse2.lon.bigpond.net.au [Some VR progress]
2012-12-17 18:54:36 . . . . catv-80-98-222-153.catv.broadband.hu [good trigger hardware setup like 100% of the working engines]
2012-12-17 03:22:46 . . . . c122-108-122-145.werrb2.vic.optusnet.com.au [Still have some noise on VR Pri Trig. Need 1.1.96 code to add filter]
2012-12-17 03:20:47 . . . . c122-108-122-145.werrb2.vic.optusnet.com.au [Still have some noise on VR Pri Trig. Need 1.1.96 code to add filter]
2012-12-12 12:03:38 . . . . pes75-2-78-192-98-74.fbxo.proxad.net [2 cents shield]
2012-12-11 02:18:20 . . . . 101.115.99.233 [Corrected VR polarity but still have noise issue. I have an idea for filter algo]
2012-12-10 10:31:39 . . . . 101.115.118.146 [Corrected VR polarity but still have noise issue. I have an idea for filter algo]
2012-12-10 06:07:09 . . . . 101.115.108.17 [VR polarity correct but still have same issue. Have an idea for filter algorithm]
2012-12-07 20:34:21 . . . . catv-80-98-222-153.catv.broadband.hu [images show inverted VR polarity, but maybe soundcard inversion can cause it]
2012-12-02 10:48:38 . . . . 101.115.100.89 [Can someone pls verify my Pri Trig signal is clean?]
2012-11-28 08:26:53 . . . . 202.124.89.137 [Uploaded analog pri trig signal info]
2012-11-19 14:23:31 . . . . catv-80-98-222-153.catv.broadband.hu [let's see the noise in ANALOG domain]
2012-11-19 11:42:31 . . . . 101.115.99.53 [Need new VR PriTrig filtering?]
2012-11-19 11:37:27 . . . . 101.115.99.53 [Need new VR PriTrig filtering?]
2012-11-19 11:33:09 . . . . 101.115.99.53 [Need new VR PriTrig filtering?]
2008-06-16 00:31:25 . . . . 3e44ae3d.adsl.enternet.hu [VR sensor basic checklist]
2008-06-15 22:40:24 . . . . 3e44ae3d.adsl.enternet.hu [you got acc. resolve privately (!).]
2008-06-08 08:48:47 . . . . CPE-124-181-237-38.vic.bigpond.net.au [Need read access to firmware source please!]
2008-06-08 08:47:32 . . . . CPE-124-181-237-38.vic.bigpond.net.au [Need read access to firmware source please!]
2008-06-08 08:46:41 . . . . CPE-124-181-237-38.vic.bigpond.net.au [Need read access to firmware source please!]
2008-06-08 08:45:59 . . . . CPE-124-181-237-38.vic.bigpond.net.au [Need read access to firmware source please!]
2008-06-08 08:44:43 . . . . CPE-124-181-237-38.vic.bigpond.net.au [Need read access to firmware source please!]
2008-06-08 08:43:19 . . . . CPE-124-181-237-38.vic.bigpond.net.au [Need read access to firmware source, please!]
2008-06-04 03:52:53 . . . . tx-71-2-125-72.dhcp.embarqhsd.net [Answer and can you help?]
2008-06-03 13:24:26 . . . . CPE-124-181-237-38.vic.bigpond.net.au [Need to work out trigger problem, so can I have read only access to source (svn)]
2008-05-25 09:18:24 . . . . PatrickB [Q: What config for MSD VR trigger - 4 pulse per rev, no missing tooth?]
2008-05-13 13:31:19 . . . . CPE-121-220-97-42.vic.bigpond.net.au [Updated engine picture and posted question around MSD crank trigger config]
2006-10-03 15:48:29 . . . . PatrickB [Using inductive ign for IonSense test]
2006-09-29 17:22:51 . . . . MembersPage/MarcellGal [are you using inductive or CDI ignition ?]
2006-09-29 04:37:42 . . . . PatrickB [Back with more ionsense experimentation]
2005-01-27 03:50:52 . . . . 155.35.248.112 [more ideas for race code and Q about rev limiting]

Changes by last author:

Changed:
I should also mention that I had previously removed P259 chip. Comms or bootload is not dependent on that, right?
I should also mention that I had previously removed P259 chip.

* Comms or bootload is not dependent on that, right?

** Correct. After p259 removal, everything else should work if there was no problem (but then p259 wouldn't have been damaged). Otherwise (if the problem that damaged p259 remained) basically the board is sentenced to death.

** but if something killed the p259 chip (it really does not die just by itself: most likely insufficient ground connection) => if the harness was carefully fixed or if a solenoid or relay >300mA driven by p259 (or without flyback diode, although v3.8 has onboard diodes for the 6 p259 channels available on EC36 pins) damaged p259 => then it might have been fixed by the disconnection => there is some chance for the mainboard to survive.

** If the primary (harness or other) problem was not fixed, then removing p259 made it virtually impossible for v3 to survive. Apparently this is the case

*** p259 provided some protection (while sacrificing itself), but obviously it cannot provide any protection after it was removed.