PIC HANGS with SERIN and Timeout?

[koossa]

Skimask, thank you very much for your feedback.

I have taken a look at the idling thing, but don't understand it.

I have also tried both SERIN and SERIN2 with timeout (10 milliseconds)

Koossa

[skimask]

I have taken a look at the idling thing, but don't understand it.
I have also tried both SERIN and SERIN2 with timeout (10 milliseconds)
Koossa

Well, I've never had the idling problem myself, so I can't really comment.
About all I can suggest is to read the threads again (there's one by Melanie that's especially long and useful) and you're answer will be in there somewhere.
If I would have to guess, I would say that your input pin is just sitting there at a low logic level. If it is, pull it high and see if the timeout works.
If it's sitting high, pull it low and see if the timeout works.

[mackrackit]

I do not use spaces in the SERIN2. Try:

SERIN2 P1,N2400,10,Loop,[wait("T"),DATARECEIVED]

And maybe use 16780 instead of N2400? And DEC before DATARECEIVED.

Maybe

[skimask]

I do not use spaces in the SERIN2. Try:

SERIN2 P1,N2400,10,Loop,[wait("T"),DATARECEIVED]

And maybe use 16780 instead of N2400? And DEC before DATARECEIVED.

Maybe

I haven't had a problem with spaces in PBP2.50, had problems back in 2.42 I think it was.
I've got a program that has about 50-60 different SERIN2 lines and they all look like:

SERIN2 serialinpin , 84 , 5000 , baddata , [ WAIT ( ">" ) , STR string\255 ]

Lots of spaces, etc.etc.etc...like I said, the older PBP, broke, newer, good.

[mackrackit]

COOL ,Now I need to upgrade. I am still at 2.47.

[skimask]

COOL ,Now I need to upgrade. I am still at 2.47.

I tell ya, in my little world, it's those LONG's that make all the difference.

[koossa]

Thank you for your replies!!
I Think this is it!!

http://www.picbasic.co.uk/forum/show...highlight=idle

[skimask]

Thank you for your replies!!
I Think this is it!!
http://www.picbasic.co.uk/forum/show...highlight=idle

That be the one...I'm fairly sure anyways...

[mackrackit]

I tell ya, in my little world, it's those LONG's that make all the difference.

I just came out of a four hour meeting with one of those as Dilbert says Pointy Haired Bosses. So my brain is still a bit dead...

What are you talking about? "LONGs" ?

[skimask]

I just came out of a four hour meeting with one of those as Dilbert says Pointy Haired Bosses. So my brain is still a bit dead...
What are you talking about? "LONGs" ?

LONGs = double words, 32 bits (31 bits + sign) math, no more DIV32 (not included in PBPL because PBPL will do 32 bits)...
Check the melabs website for the upgrade info.

[Ron Marcus]

I haven't had a problem with spaces in PBP2.50, had problems back in 2.42 I think it was.
I've got a program that has about 50-60 different SERIN2 lines and they all look like:

SERIN2 serialinpin , 84 , 5000 , baddata , [ WAIT ( ">" ) , STR string\255 ]

Lots of spaces, etc.etc.etc...like I said, the older PBP, broke, newer, good.

This may be a moot point, but, I recently had the hang situation with a GPS unit interface. The unit's serial output would go to ground when the unit was put into sleep. I did a little loop that would sense if the line went high at all over a hundred mS period. If not,I would skip the Serin line. It works quite well without any hardware changes.
Ron

[koossa]

Thank you Ron, I will keep that in mind!

[koossa]

I'm a real beginner with PICS and don't understand the posts about idling that good.

If I connect he Serin Pin to ground it don't hang anymore, or if I rather use the "True" and not "inverted" state.
Is any one of these a reliable solution?

[ardhuru]

Sorry to jump in late. Just tie a 4.7 K between the serin pin and ground; should solve the problem.

Regards,

Anand