Problems controlling multiple pics

[mister_e]

Different method to do that, i'll suggest to have a look at the following link

How to make your own PIC network
http://www.picbasic.co.uk/forum/showthread.php?t=1192

This could give you some pointers.

HTH

PS: most here, including myself, don't recommend to use the internal OSC for serial communication for reliability reasons. If your PIC have a USART, you should use it. HSERIN/HSEROUT. I'll also suggest you to read the available Modifier list. WAIT will be handy in your case.

[gandora]

I am using 16f88 which does have an internal AUSART. But what is the difference between serin2 and hserin. I am a little confused about it.

[Sergeant]

Serin2 & HSerin share modifiers you can use, but to use HSerin you must set the config bits in the PIC to specify you are using a hardware communication option instead of "bit banging" the serial comms using Serin2 (or Serin, for that matter).

Sorry, but you'll have to spend some more time in both the manual and the datasheet for your PIC to get it set up properly. Do a search in the Archives here in the forum, and with Google if you need more help. I've just about finished getting my comms working as I need, using these same procedures.

Good luck!
Brad

[mister_e]

I am using 16f88 which does have an internal AUSART. But what is the difference between serin2 and hserin. I am a little confused about it.

HSEROUT or HSERIN use the PIC Hardware USART, while SERIN/SERIN2/DEBUGIN use a software Serial communication solution.

The only restriction when you're using HSERIN/HSEROUT is the I/O and the amount of serial port. With HSERIN/HSEROUT, you MUST use the PIC dedicated i/o (RX/TX) while any other software solution (SERIN.. ) allow you to choose any i/o.

Using the PIC USART give you for free at very least, a 2 Bytes receiver buffer, and interrupt trigger sources.