SOLVED - Breaking HSERIN into separate parts

[Demon]

SOLVED in post #6:

https://www.picbasic.co.uk/forum/sho...164#post156164

----------------------------------------------------------------------------

USART

Is it "safe" to send HSEROUT header, data,

then receive:

- HSERIN header
(depending on header, use proper data format)
- HSERIN data

Or should I send Header and Data on 2 separate transmissions?

Objective:

I'm looking for a safe and simple way to transfer data of varying lengths.

Header is a prefix that identifies the data layout.

[pedja089]

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

[Demon]

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

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 options.

[pedja089]

I do not have it right now.
String is just array. You can fill each byte separatly.

[Demon]

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 messages will range from sending a single value, to the entire set (possibly 30 values).

One alternative is to blindly use the longest possible array on reception, even if I only send one value. I have no clue if that opens up a can of worms.

I see that you can add a LENGTH parameter, maybe that can be used (got some testing to do).

[Demon]

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 array at the longest possible length,
- stop reception on character c,

This way I can embed a Data Layout Number at the start of the message, and use that to branch to code to treat the array properly.

I understand quickly, you just have to be patient and explain it to me a whole bunch of times.