16F18877
Transmitter Enabled/Disabled to have more than 1 PIC transmitting (using a Busy Line to determine which PIC can talk).
' Enable Transmitter
TX1STA.5 = 1
......
Yeah, i was waaaay overthinking this.
Transmitting (16F18877):
XmitStr CON "["
XmitCode1 var BYTE
XmitCode2 var BYTE
XmitNumber var...
I think I figured out what's written in plain English right in my face:
STR ArrayVar\n{\c}
Receive string of n characters optionally ended in character c
It looks like I can:
- define the...
My dilemma is having multiple record layouts, and having the receiving PIC figure out which format to use.
Using an array long enough to fit the largest transmission seems like a waste to me. My...
It seems the USART analyser (Async Serial) has been updated since I last used it - the formatting has changed a bit.
Again proved invaluable to see if my data was being sent properly.
I love...
I do not have it right now.
String is just array. You can fill each byte separatly.
Interesting. Do you have a sample code of how you process the string array at reception?
I had been looking at HSEROUT in the manual, but I should have been looking at HSERIN; that has more...
I used something like this
On transmis side
HSEROUT "DataStart:",Len, str data\Len, chksum
on receive side
HSERIN wait("DataStart:"), Len, str data\Len, chksum
SOLVED in post #6:
https://www.picbasic.co.uk/forum/showthread.php/26788-Breaking-HSERIN-into-separate-parts?p=156164#post156164
...
Re: SOLVED - Breaking HSERIN into separate parts
The stop character in the Hserin command is needed if you do not know the length of the string.
Ioannis Today, 13:46Since you define the length at the beginning of the transmission, and then use it in the STR...