Source code for RsFsw.Implementations.Applications.K6_Pulse.Sense.Rtms.Capture.Offset

from .......Internal.Core import Core
from .......Internal.CommandsGroup import CommandsGroup
from .......Internal import Conversions


# noinspection PyPep8Naming,PyAttributeOutsideInit,SpellCheckingInspection
class OffsetCls:
	"""
	| Commands in total: 1
	| Subgroups: 0
	| Direct child commands: 1
	"""

	def __init__(self, core: Core, parent):
		self._core = core
		self._cmd_group = CommandsGroup("offset", core, parent)

[docs] def set(self, time: float) -> None: """ ``[SENSe]:RTMS:CAPTure:OFFSet`` \n Snippet: ``driver.applications.k6Pulse.sense.rtms.capture.offset.set(time = 1.0)`` \n This setting is only available for secondary applications in MSRT mode, not for the MSRT primary. It has a similar effect as the trigger offset in other measurements. :param time: This parameter defines the time offset between the capture buffer start and the start of the extracted secondary application data. The offset must be a positive value, as the secondary application can only analyze data that is contained in the capture buffer. Range: - [pretrigger time] to min (posttrigger time; sweep time) , Unit: S """ param = Conversions.decimal_value_to_str(time) self._core.io.write(f'SENSe:RTMS:CAPTure:OFFSet {param}')
[docs] def get(self) -> float: """ ``[SENSe]:RTMS:CAPTure:OFFSet`` \n Snippet: ``value: float = driver.applications.k6Pulse.sense.rtms.capture.offset.get()`` \n This setting is only available for secondary applications in MSRT mode, not for the MSRT primary. It has a similar effect as the trigger offset in other measurements. """ response = self._core.io.query_str(f'SENSe:RTMS:CAPTure:OFFSet?') return Conversions.str_to_float(response)