SOLVED - Breaking HSERIN into separate parts

[Ioannis]

The stop character in the Hserin command is needed if you do not know the length of the string.

Since you define the length at the beginning of the transmission, and then use it in the STR modifier, what is the point of "]" in that modifier? It will never engage!

Ioannis

[Demon]

... what is the point of "]" in that modifier? It will never engage!

Ioannis

That was one area that had me overthinking USART. STR ArrayVar\n{\c}, receives a maximum of n bytes, unless it receives character c.

If I misinterpreted the manual, I'd definitely appreciate being corrected before I code my entire project.


Initially I was copying what Pedja was doing, but I've since dropped the Length parameter and use only the StartOfData and EndOfData delimiters. I have a LOT of different Data Layouts, and calculating Length was becoming tiresome, and a possible source of human error. It's also cumbersome when you modify the Data Layout.

I am using variables in HSEROUT, an array (equal to the longest data layout) in HSERIN, which is then moved into variables depending on Header values; it's much more simple (for me).

[Ioannis]

OK, if you drop length then makes sense.

Using length variable in the STR modifier on the other hand, is very clever.

Ioannis

[Demon]

OK, if you drop length then makes sense. ...

Yeah, I updated my post with a comment to clear that.

Using length variable in the STR modifier on the other hand, is very clever. ...

I didn't field particularly clever after racking my brains trying to find the most efficient way to move data around.