Parsing Strings...

[mackrackit]

I still think separating the numbers on the way in is the way to go. Although Jerson's code is pretty slick.

Here is what I was thinking. Just tested it using SERIN2 as the chip I have on the bench is not set up for HSERIN right now.

The first WAIT is to keep garbage out.

N1	VAR	LONG
N2	VAR	LONG
LOOP:
SERIN2 PORTD.2, 16416, [WAIT("X"),DEC N1,WAIT(","),DEC N2]
GOTO DISPLAY

DISPLAY:
Serout2 PORTC.6, 16416, [ DEC N1, $d, $a]
Serout2 PORTC.6, 16416, [ DEC N2, $d, $a]
GOTO LOOP

If you need the data in an array just modify the above with STR...

[TerdRatchett]

Both great suggestions for which I appreciate!!! I'm pondering....

[TerdRatchett]

I've tried dozens of ideas along those lines and no solution works....

Like:
hserIN 65535, oops, [STR smallp\5, WAIT(","), STR largep\5\13]

problem here is the string size I expect to receive is variable, but the STR forces you to put in the string length. If it's shorter the function doesn't return anything, yet it doesn't time out. I'm ending up with the comma in my first string, even though I'm only looking for it as a seperator and after I receive the first serial data, every time thereafter there is a non-acsii character in the first byte of smallp.

If the data was always the same length it would be a breeze...

[mackrackit]

From the manual:

STR followed by a byte array variable, count and optional ending
character will receive a string of characters. The string length is
determined by the count or when the optional character is
encountered in the input.

[STR smallp\10\,]
See if that will get the first part correctly.

Does the data comming in have a qualifying character before the data you want? If so then the first example I gave will work. If it does not have a qualifying character then leave that part out.

[TerdRatchett]

I appreciate your help! Very confused

hserIN 65535, oops, [STR smallp\10\","]

The first time thru I get the correct first part of the string. the device was sent 777,53 and smallp received 777.

The second time and every time thereafter the data is skewed. For example if the next packet that comes in is 766,59 smallp receives a 53766. The 53 from the last packet sent....

[Charles Linquis]

It would seem to be a lot easier to capture the whole sequence, then later scan the array for any commas and deal with it that way, especially since when you are using SERIN you have very little processing time available between characters.

[TerdRatchett]

I think that's a great suggestion and I agree. I have been unable to successfully parse it after the fact.