IssueReports (2008-08-12 17:32:10)

Here you can link your report issues with your Genboard V3, firmware, tuningprogram or hardware problems.

Make your report on your MembersPage, and place link in the relevant section (with a "title", so it can be remembered easily). If you dont know the section, put it under "Unknown".

In the report, include at least:

The report, to be considered, must contain ALL necessary info. Without the necessary info, question-answer iterations are needed, so solution is delayed in the best case. If there is not enough info to reproduce, the report is neglected (especially if it contradicts experience). Re-post with the necessary info if you believe it holds.


Hardware: - usually wiring. These are normally answered even if you only use your MembersPage, but if you insist...


Config: please use your MembersPage where the full setup (engine, triggers, whatever related) is described


Firmware:

TODO: mcd/mct (I do not have the dumps from during the incident, I was on the side of the road. Is it still useful to dump the ecu now?)

Description: May have one or two problems. I have been driving this car/ecu for 3 weeks, over 1000 miles. Been about a week since I even had the computer connected to it. This morning, engine would not start. In MT, I see that the cranking fuel pulsewidthis not being applied to the base pulsewidth. The startup enrichment table showed the correct values (22ms cold and 10ms hot)(stock injectors)

I opened and burned my calibration file, and the enrichment worked and the car started OK.

Then, I was driving for about an hour, and all of the sudden the fuel would cut anything over 2300 rpm. It appears that the KPA value was being ignored.

I changed the value to 9900 rpm, and it fixed the cut.

Values: KPA = 18, Cut = 2300, Enable = 2000

Kevin Black

my config at the end of MembersPage/KeithHargrove/AlfaSpider
  • HansK : I tryed 1.0.73 (from VemsMT1.0.73) with 14x16 and it also holds ignition on after trigger stops until fuelpump stops.
may also happen with 1.0.73 But I could not get my config to work with 1.0.73 . Why ? You should try 1.0.73 or 1.0.75 to eliminate possible problem with your compiler

Tuningprogram (Megatune):


USB-rs232 adapter cable windows driver - prolific pl2302

We found a NASTY problem with the USB-adapter windows driver.

The windows driver is unstable when 62 byte runtime-log is logged (D command), even if it seems reasonably stable when 56 byte is logged (A command). The user had no problem with 1.0.73 but found newer megatune 1.1.2x unusable ... as we found out later, because of the bigger runtime block. We got certain when reconfiguring the 1.1.2x megatune to use the shorter 56byte block from the A command, it became stable again.

When it freezes, the app cannot be killed from taskmanager, and usually the machine must be hard-rebooted. It is almost certain it is not an application bug, but a windows driver bug. If it was an application, the app would be easy to kill from task-manager "End task". And it would not show up with the alternative "bray terminal" app.

We have to admit it was more stable (maybe freezing every 10 mins not every 2 min) with older windows, even with 62 byte.

Anyway. I'm writing to prolific.

I doubt that it's a MegaTune bug (or intentional behaviour) because v3gui and even a simple terminal program had the same problem

Workaround for now: megatune vemsv3.ini must be configured with ochblocksize=56 and "A" command, not "D" command


V3GUI