>Hello Chris, > Last year I had a go at an FTDI device (FT245BM - not the 232 >device), and on Windows they behaved as expected. on Mac OSX I found >that a verbose client (>100kbps) which talked into a serial >application with an open port but which did not empty the buffer (no >serial1.readAll) would reliably fail. To be precise, the OS buffer >would lose chunks, and *fail* to signal to the USB device that it >should assert *TXF (i.e. that the transmit buffer is full). The same >hardware worked correctly on Windows XP using a Win32 build of the >same application; and the same issue was present in Zterm on Mac OS X. > At the time, I was using 10.3 (Panther) and the previous >iteration of the FTDI driver (2.1.0). A new driver has come out, >along with a dylib instead of the virtual com port, so I should >resurrect the application and the hardware and see if it all works now.
Hi Tony, I'd be very interested to hear how the new driver works for you. I actually had a similar problem myself with an FT245 based device (it was sending around 600kBs) on OS X. I stopped work once I realized the problem was with the driver, but haven't had a chance to start up again with the new driver. -- --- Chris Smolinski Black Cat Systems http://www.blackcatsystems.com _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
