Skip to content

[BUG]: Burst mode for signal generation is not disabled when not used #440

@michaelwagoner

Description

@michaelwagoner

Description of the bug

If you generate a signal with burst on an AFG and subsequently generate a non-burst signal via the generate_function the non-burst signal will be incorrect and still have burst enabled. As part of the generate_function we should set the burst state for the AFG/Internal AFG (TekScope) drivers

Steps To Reproduce

from tm_devices import DeviceManager
from tm_devices.drivers import AFG3K

with DeviceManager(verbose=True) as dm:
    # Create a connection to the AFG and indicate that it is an AFG3K for type hinting
    afg3k: AFG3K = dm.add_afg("192.168.0.1")

    # Generate a RAMP waveform on SOURCE1 of the AFG3K with burst
    afg3k.setup_burst(
        function=afg3k.source_device_constants.functions.RAMP,
        channel="SOURCE1",
        frequency=10e6,
        amplitude=0.5,
        burst_count=2,
        offset=0,
        symmetry=50.0,
    )
    assert afg3k.query("SOURCE1:BURST:STATE?") == "1"
    # Generate a RAMP waveform on SOURCE1 of the AFG3K without burst
    afg3k.generate_function(
        function=afg3k.source_device_constants.functions.RAMP,
        channel="SOURCE1",
        frequency=10e6,
        amplitude=0.5,
        offset=0,
        symmetry=50.0,
    )
    assert afg3k.query("SOURCE1:BURST:STATE?") == "0"  # Currently returns 1

Environment Information

No response

Additional Information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    SCPIStandard Commands for Programmable InstrumentsbugSomething isn't workinggood first issueGood for newcomerspython

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions