HSERIN and XOUT command

[aratti]

I am facing a singolar behaviour using a pic 16F628 working @ 3.3 Volts.

I am receiving a string of 9 characters via Xbee, the string is serially collected in an array using HSERIN command. The string is than decoded and an X10 command is generated via XOUT. Everything work fine only for two strings sent, with the third string the HSERIN doesn't work anymore, I need to reset the pic to get HSERIN to work again (but still for two strings only)

Using SERIN2 the problem disappear and the system works fine, but since I want to use the chip USART capability, I did try to understand the reason for such a behaviour, but with no luck.

Here the USART setting

DEFINE HSER_RCSTA 90h ' Enable serial port & continuous receive
DEFINE HSER_TXSTA 24h ' Enable transmit, BRGH = 1
DEFINE HSER_SPBRG 25  ' 9600 Baud @ 4MHz, 0,16%
DEFINE HSER_CLROERR 1 ' Clear overflow automatically

Here the X10 command code

High TxEnable ' enable pwr line transmission
pause 5
Xout X10Tx,Zcrox,[House\Unit,House\Unit2]
low TxEnable

Does anybody know if there is any incompatibility between the two commands "HSERIN and XOUT"?

Al.

[aratti]

Adding to the code : INCLUDE "Modedefs.bas", HSERIN and XOUT now work!

Fantastic, but the question remains, why.

Al.

[Archangel]

Adding to the code : INCLUDE "Modedefs.bas", HSERIN and XOUT now work!

Fantastic, but the question remains, why.

Al.

Hi Al, if you open MODEDEFS.BAS you find the following code

' Xout Commands
Symbol UnitOn = %10010
Symbol UnitOff = %11010
Symbol UnitsOff = %11100
Symbol LightsOn = %10100
Symbol LightsOff = %10000
Symbol Dim = %11110
Symbol Bright = %10110

[aratti]

Hi Joe, thank you for your reply.
My perplexity still remain, I don't think anything in MODEDEFS.BAS can interfere with HSERIN command.

The XOUT command was working without MODEDEFS.BAS file (because I am using my own X10 coding), the only problem was that I had to use SERIN2 instead of HSERIN .

Al.

[Archangel]

Hi Al,
It was HSERIN that didn't work . . . Thought it was the x10 code . . . I should have read it through . . . might have something to do with the RX ports idle state, perhaps the code in modedefs.bas affected it that way. I DO know hserin likes to idle high.

[mister_e]

Are you using the TX pin for XOUT? If so, yes It may give you some weird problem, because XOUT may try to modify the TRIS setting, and/could disable the USART.
Try
RCSTA=0 before XOUT
RCSTA=$90 after Xout
and see how good, worst it is.

From what I know, there's no good reason why MODEDEFS should solve the problem. If it wasn't there, you would probably have some compilation error but not much.