This feature request comes from wanting to support a type of data I have been told some instruments generate, but currently isn't supported.
This change would update VariableLength class to support variable length fields where the length is determined by another field in the packet. For example, you could have fields data1_len which sets the length of the data array, and then data2_len which follows it and sets the length of the data2 array.
This feature request comes from wanting to support a type of data I have been told some instruments generate, but currently isn't supported.
This change would update
VariableLength
class to support variable length fields where the length is determined by another field in the packet. For example, you could have fieldsdata1_len
which sets the length of thedata
array, and thendata2_len
which follows it and sets the length of thedata2
array.An example is below: