nickelflippr
Member
Got around to pasting a FT232R onto a proto board to give it a go. Windows XP recognized, it and was able to then install the latest driver.
Not having any luck communicating with a terminal, getting some gibberish, so TX from the PIC-->Max232 seems to be working. The odd thing is that a loopback test works just fine by shorting the RX and TX pins on the PIC side of the Max232.
In the Bray's terminal the transmit window indicates a 'frame error'. Played around with different baud rates. Tried device manager to change the ComPort buffer to smaller values, 64 bytes and latency to 4ms. Tried inverting the RX and TX in the Mprog (FTDI eeprom programmer), that didn't work.
Using a Prolific USB/Serial cable everything works as expected, so the software shouldn't be a problem.
Will say that the manual shows a 0.01uf polarized cap across the power pins on the bus powered setup that is implemented. Only able to come up with a ceramic cap for that, could that be a problem?
So checking to see if anyone has had this 'frame error', and where I might look to fix it.
Not having any luck communicating with a terminal, getting some gibberish, so TX from the PIC-->Max232 seems to be working. The odd thing is that a loopback test works just fine by shorting the RX and TX pins on the PIC side of the Max232.
In the Bray's terminal the transmit window indicates a 'frame error'. Played around with different baud rates. Tried device manager to change the ComPort buffer to smaller values, 64 bytes and latency to 4ms. Tried inverting the RX and TX in the Mprog (FTDI eeprom programmer), that didn't work.
Using a Prolific USB/Serial cable everything works as expected, so the software shouldn't be a problem.
Will say that the manual shows a 0.01uf polarized cap across the power pins on the bus powered setup that is implemented. Only able to come up with a ceramic cap for that, could that be a problem?
So checking to see if anyone has had this 'frame error', and where I might look to fix it.