|
Its a cable going directly to a DoubleTalk text-to-speech board.
I am defining OSC 48 yes.
I initially started at 9600 baud, and lowered to 2400 to see if that would fix it, which it didn't.
When i use SEROUT or SEROUT2 the corrupted characters cause the text-to-speech to mispronounce the words. HSEROUT is flawless. No issues at all.
The reason I need this is I need at least 2 serial outputs and this PIC only has 1 hardware USART.
"I think fish is nice, but then I think that rain is wet, so who am I to judge?" - Douglas Adams
|
Semi-silly idea for you...but might be easier than you think. Might even be able to write a macro to handle the switching for you...Originally Posted by Kamikaze47
Use the HSEROUT for your serial out as you've already planned it out...
Get your hands on a couple of AND gates, or whatever works...
Use another PIC pin or two as STEERING LOGIC.
|
Thats a pretty good idea.
"I think fish is nice, but then I think that rain is wet, so who am I to judge?" - Douglas Adams
|
Well, heck, glad I could help...
Generally I'm useless
Does your program have any interrupts running in it?
|
Actually, i do have 3 interrupts in this program. Maybe SEROUT is getting interrupted and thats messing with the data.
I'm gonna try disabling the interrupts while I run SEROUT... Not the best long term solution as It wouldnt be good to miss one of those interrupt events, but its worth a try to see if thats whats causing my problem.
"I think fish is nice, but then I think that rain is wet, so who am I to judge?" - Douglas Adams
|
Are you using assembly int's (i.e. DT's fast ints) or the ON INTERRUPT types?
|
I tried to test the interrupt theory with a simple GIE=0 before SEROUT and GIE=1 after it, but disabling the interrupts makes my program do unexpected things and makes it impossible to test. But i'd say its a high probability that the interrupts are the issue.
So I guess i'll have to stick with the hardware USART and, as skimask suggested, multiplex its output.
*edit*: Using ASM interrupts as timing is important.
Last edited by Kamikaze47; - 3rd March 2008 at 16:24.
"I think fish is nice, but then I think that rain is wet, so who am I to judge?" - Douglas Adams
|
I've used serout and debug out to run to two different Double-Talk boards at 9600 baud, both performed perfectly, so I'd have to say that you're right, it's probably the interrupts. I tried it using two different LabX-Usb boards, with 18f4550's, with a DEFINE OSC 48. The boards have 20 Mhz crystals, and the oscillator selection is for HS_PLL.
Jerry.
If your oscilloscope costs more than your car...
|
condition the data line first.
My serial data errors all went away as soon as I started presetting the data line before transmission.
For example, RS-232 defines the IDLE or MARK state to be negative volts at the RS-232 connector. That means positive volts at the PIC before the MAX232 inverter.
Try something like
HIGH TxData
pause 2
Serout/Serout2/Hserout your message.
It works for me.
HTH
BrianT
|
I just lowered the SEROUT2 baud to 600 and it works by the look of it. But that is much too slow and it holds up my program.
With a 48Mhz clock, i'm not sure why it would struggle with 9600 baud, let alone 2400.
"I think fish is nice, but then I think that rain is wet, so who am I to judge?" - Douglas Adams
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks