Why I am mentioning about Windows 7 64-bit operating system is that in the future more and more computers will have this operating system as a standard unless you can talk the manufacturer into installing a 32-bit operating system. You can Google concerning "Prolific" devices and Windows 7 64-bit operating system and you will see issues about it. You can take my word on this or you can perform this experiment yourself.Īs far as the "Prolific" chip set goes, it has no "latency timer", hence no monitor time issues. The program becomes sluggish and non-responsive to user actions. If the timer interval is set to 500 msecs and the monitor times is 600-700 msecs (typical times with value set to "16") then the timer will fire again before the monitor time is finished.
If the value is set to "16" and the Monitor page is open (timer refreshes at 500 msecs) then you WILL have communications issues in the form of communications lockups.
The difference in the monitor time rate is 6 to 7 times faster when the value is set to "1" (monitor times around 100-150 msecs). For EvDiagnostics proper communications it needs to be set to "1". By default it is set to "16" (range is 1 to 255). (You can Goggle concerning on how to check/set this "latency timer".) Why they call it this name I do not know, but the value is critical for proper communications. The USB Serial Devices that contain the "FTDI" chip set have a "latency timer". View Member Profile Find Member's Topics Find Member's Posts BrpSad
0 kommentar(er)
