History of MembersPage/PeterJensenFtid
Older Newer
2011-05-09 19:30:41 . . . . 0xbcb4d0f2.cpe.ge-0-1-0-1104.rdnqu2.customer.tele.dk [FTDI USB to rs232]
2011-05-06 12:04:53 . . . . 3e44a184.adsl.enternet.hu [more options if windows usbserial driver is broken: real serial port, wifi, blue]
2011-05-06 10:54:20 . . . . 3e44a184.adsl.enternet.hu [Ideas]
2011-05-05 21:21:00 . . . . 0xbcb4d0f2.cpe.ge-0-1-0-1104.rdnqu2.customer.tele.dk [USB to rs232 problems FTDI]


Changes by last author:

Changed:
USB to rs232 problems
FTDI USB to rs232 problems

Hello Peter,

The USB disconnect could be caused by EMC possibly from the engine.

You could try increasing the reset pipe retry count described in section 5.1of our advanced drivers application note

(http://www.ftdichip.com/Documents/AppNotes/AN_107_AdvancedDriverOptions_AN_000073.pdf).

5.1 Adjusting the Reset Pipe Retry Count

In some rare cases, it may be necessary to increase the number of times the driver tries to reset a USB pipe on which an error has occurred, for example in noisy environments where a lot of USB errors occur.

The default value for the reset pipe request retry count is 50. This default value may be changed in the FTDIBUS.INF file by editing or including the following fragment.

[FtdiBus.NT.AddService]

AddReg = FtdiBus.NT.AddService.AddReg

[FtdiBus.NT.AddService.AddReg]

HKR,Parameters,"RetryResetCount",0x00010001,100

In this example fragment, the reset pipe request is set to 100.

This value is held in the registry key located at

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FTDIBUS\Parameters\RetryResetCount