Skip to content

Resolve V1730/V1740 generator timestamp mismatching #66

@jwaiton

Description

@jwaiton

Due to the method of increasing timestamps for V1730/V1740 generator digitisers relying on a 'overflow' tracking bit, the timestamp numbers for WaveDump 1 output often ends up unreliable, and self repeating.

The logic is as shown here:

Image

This can be seen in the code being interpreted as a signed 32 bit integer, which is fine before the overflow bit switches to 1, at which point it gets misinterpreted as a negative 32 bit integer and recast to 64 bits, giving the current values.

Image

Methods for resolving this aren't inherently trivial, but may be easy enough to implement with some thought.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Projects

    Status

    No status

    Status

    Triage

    Status

    Mid value Issues

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions