Can WinWedge cope with varying record lengths? The instrument's record starts with an ID, followed by two bytes which tell you how long the record is, then the record, then a checksum & then an end of record character (the hex symbol for 77). Would WinWedge be able to parse this correctly?
Yes. WinWedge can search for any ASCII character to determine the end of record. You may also specify delimiter characters to break the record up into fields.