I do not use spaces in the SERIN2. Try:
And maybe use 16780 instead of N2400? And DEC before DATARECEIVED.Code:SERIN2 P1,N2400,10,Loop,[wait("T"),DATARECEIVED]
Maybe
I do not use spaces in the SERIN2. Try:
And maybe use 16780 instead of N2400? And DEC before DATARECEIVED.Code:SERIN2 P1,N2400,10,Loop,[wait("T"),DATARECEIVED]
Maybe
Dave
Always wear safety glasses while programming.
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.
COOL ,Now I need to upgrade. I am still at 2.47.
Dave
Always wear safety glasses while programming.
Thank you for your replies!!
I Think this is it!!
http://www.picbasic.co.uk/forum/show...highlight=idle
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
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?
Sorry to jump in late. Just tie a 4.7 K between the serin pin and ground; should solve the problem.
Regards,
Anand
Oh...hey...good point...no kidding.
Jeez, sometimes the simplest fixes are the best.
And if tying it to ground doesn't work (which it should), tie it high, or maybe use a 10K instead of a 4.7K, or maybe a 1K. Might take a bit of experimentation. But I don't see why 4.7K shouldn't work just fine.
Bookmarks