Title: Split packets by timeout Post by: ccdr on July 19, 2018, 08:24:43 AM Hello
I issued one query per 5 seconds to my device. One query led to one quick response packet which was split by 2 seconds timeout using Data logger suite. The response is very short so the 2 seconds timeout setting has a quite large margin. But the weird thing is I received THREE lines of identical response parsed value per my query. How could this happen? PS. I checked both data view setting of "data before parsing" and "data after parsing". They both worked in consistent rhythm with my query, i.e. one per 5 seconds. Only "data parsed values" showed triple lines of identical parsed values. Title: Re: Split packets by timeout Post by: Arthur Grasin on July 19, 2018, 09:03:27 AM Hi,
Do you use the latest version of our software? Title: Re: Split packets by timeout Post by: ccdr on July 19, 2018, 09:31:05 AM Hi, Yes, I executed it on version 2.8.2.605.Do you use the latest version of our software? Title: Re: Split packets by timeout Post by: ccdr on July 19, 2018, 09:36:02 AM It seems like one parsed value line corresponds to the data sent i.e. the query, one parsed value line corresponds to the response data, and the last parsed value line corresponds the echo prompt symbol data, i.e. the character "<". Any one mentioned above seems to trigger the parser starting applying the same parser rule to the identical split packet over again.
Title: Re: Split packets by timeout Post by: Arthur Grasin on July 19, 2018, 09:45:20 AM Please, make a backup copy of your configuration and attach here with your incoming data example.
Title: Re: Split packets by timeout Post by: ccdr on July 19, 2018, 10:08:15 AM Please, make a backup copy of your configuration and attach here with your incoming data example. Please refer to the attached files. Title: Re: Split packets by timeout Post by: Arthur Grasin on July 19, 2018, 02:27:48 PM Please, update the following file in program folder\plugins\default
http://www.aggsoft.com/download/beta/default20180719.zip This bug has been fixed. |