Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
06/17/10 20:58
Modified:
  06/17/10 21:02

Read: times


 
#176734 - Don't blame the driver or the adapter
Responding to: ???'s previous message
The driver was not installed properly. The user is to blame. Buying a cheap adapter is the fault of the user. Finally, actual data can be lost because of the USB Host Controller that resides on the PCI Bus within the motherboard itself. This is mainly the fault of the advent of USB as there was a discussion a long while back where USB requires a "HUGE" FIFO. What happens is that if the user's program does not "sit" on the USB Host controller's buffer the host controller will over write it's own buffer causing records of data to be lost as the host controller does not have infinite space. So, if the user's program does not poll the serial port fast enough, data is lost. One can account for it by having a large hardware FIFO and increasing the "latency" so that the USB Host controller does not have to continuously service the FTDI chip. There is another method, but one cannot easily perform it with the use of an FTDI chip. In essence, these converters are a generality of a serial port and cannot be made to consistently give correctness for a given application. If someone were to use these converters blindly, do not expect your design to work perfectly. As pointed out before, just because it works, doesn't mean that it is correct.

List of 23 messages in thread
TopicAuthorDate
Serial Port monitor software            01/01/70 00:00      
   Docklight            01/01/70 00:00      
      I use...            01/01/70 00:00      
   monitor and control            01/01/70 00:00      
      br@y terminal??            01/01/70 00:00      
         But that's "just" (sic?) another terminal, surely?            01/01/70 00:00      
      RE: Portmon from Sysinternals            01/01/70 00:00      
         "pi" cable and two serial ports to log rx and tx            01/01/70 00:00      
            OK for simple data logging...            01/01/70 00:00      
               timing etc is just a question of program and OS            01/01/70 00:00      
            Command-response sync?            01/01/70 00:00      
               Don't blame windows here!            01/01/70 00:00      
                  Don't blame the driver or the adapter            01/01/70 00:00      
                     Eh?            01/01/70 00:00      
                        Huge FIFO because max baudrate also much higher            01/01/70 00:00      
                  USB-Windows-drivers            01/01/70 00:00      
                     Digressing: Multiple USB-to-Serial            01/01/70 00:00      
                        Digressing Further...            01/01/70 00:00      
                        Nice            01/01/70 00:00      
                           RE: It's a shame I can't tell the service guys what to buy            01/01/70 00:00      
               8052-based analyser            01/01/70 00:00      
               Timing just depends on OS and where the data is sampled            01/01/70 00:00      
      Scripting for development and testing            01/01/70 00:00      

Back to Subject List