IssueReports (2007-11-12 12:47:23)

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

Trigger issue with config problems. Firmware 1.1.24, MegaTune 2.25.

http://www.vems.hu/wiki/index.php?page=MembersPage/PeteKrgr


Firmware:

http://www.vems.hu/wiki/index.php?page=MembersPage%2FKeithHargrove%2FFirmwareBugs

my config at the end of

http://www.vems.hu/wiki/index.php?page=MembersPage%2FKeithHargrove%2FAlfaSpider

may also happen with 1.0.73 but I could not get my config to work with 1.0.73 after going to the SVN


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