have a look at this thread for some ideas on serial transmission with interrupts
http://support.melabs.com/threads/28...terrupt-Serial
have a look at this thread for some ideas on serial transmission with interrupts
http://support.melabs.com/threads/28...terrupt-Serial
The BT modules could be the issue have they got Flow Control on the RS232. A data sheet would help.
Steve Earl www.datageo.co.uk
Hi,
If SERIN/SEROUT without flow control works across the BT-link (which it apparently is) then HSEROUT/HSERIN will work too. It's just a matter of getting it setup correctly.
Having an oscilliscope or logic analyzer and probing the signals as it enters/exits the PIC would help. Doing so with the "working" version using SEROUT/SERIN and the with the HSEROUT/HSERIN comparing what you get would most likely reveal the issue.
/Henrik.
My understanding is that serin never worked but serout did, post #44, which is why I suspect flow control, we were given the wrong impression when we were told using hardware usart had solved the problem. Do we need more information? or will this lead to more misinformation depending on how I read it.If SERIN/SEROUT without flow control works across the BT-link (which it apparently is) then HSEROUT/HSERIN will work too.
Steve Earl www.datageo.co.uk
Flow control.... hmmmm. Makes me think I may have somethiny else amiss... could it be terminal settings? Serin/serout works fine. I have hooked up an LED to the rx on the pic and I see it flicker on data send. I havent tried to cross the tx/rx to look for echo but I suspect ill get it. Was there something I needed to change in the terminal program to make the data "legit" ? I seem to remember a flow control dropdown box......
I suppose I can also scope the data coming out of the bt and into the pic, but I dont think itll yield much more than seeing the led flicker... unless you want me to somehow capture and post the raw scope results to actually interpret them
I'll be back home in about an hour if you would like me to do that...
The flow control I was thinking of was between the 16f1829 and the BT connected to it.
Steve Earl www.datageo.co.uk
Bookmarks