Thanks for the replies - I will try Bray's terminal out..

I feel rather stupid all of a sudden :-)

Engaging my reserve brain cell, I figured if Hyperterminal is pouring out=20
newlines constantly then the PIC must be sending them, unless there is some=
=20
real magic going on..
I waited till it happened, then hit break and stepped through the code -=20
there was a sneaky little newline() command in the default of a select case=
=20
that receives data commands from the PC (why? I'm not sure, I didn't write=
=20
the code, I'm just fixing it) In any case I would have noticed it before bu=
t=20
for some reason it does not pour newlines out in PicKit2s UART tool so it=20
went unnoticed..
Anyway, sorry for wasting anyone's time with this imaginary problem :-) I=20
got rid of the offending newline and it works fine now.
While I'm on the subject though - is it worth adding handshaking to make it=
=20
more solid? Can I expect the odd case of overflow/data loss just sending it=
=20
like this. I figured that at 4800 baud and with a 50ms delay between 8-byte=
=20
(2 bytes per sensor)readings sent that it should be easily slow enough not=
=20
have any issues. However, in the interests of making things as bulletproof=
=20
as possible, could someone advise me how to implement handshaking, of where=
=20
there is a good discussion of the subject..=20


--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.