Forum
Please or Register to create posts and topics.

About Control Endpoint

According to  RTSA http stream server endpoint document.Settings  bellow can be changed with control endpoints:
stream start and stop, frequency range , rotate antenna , mission reload and save.

Is there a setting for managing zones ?

Also are there any other settings that are supported but not presented in the document?

 

Uploaded files:

The /control endpoint cannot be used to configure zones. Remote configuration of zones is currently not supported.

The following settings are supported by the /control endpoint (note: most of these settings only apply to specific blocks):

  • type="capture":
    • receiverUUID
    • receiverName
    • frequencyCenter
    • frequencyStart
    • frequencyBins
    • referenceLevel
    • start
  • type="deviceconnect"
    • receiverUUID
    • receiverName
    • start
  • type="streaming"
    • receiverUUID
    • receiverName
    • filename
    • start
  • type="recording"
    • receiverUUID
    • receiverName
    • filename
    • start
  • type="mission"
    • save
    • load (target filename must be specified using the "file" setting)
    • reload
  • type="antenna"
    • receiverUUID
    • receiverName
    • latitude + longitude (must be specified both)
    • azimuth + declination
    • rotate
  • type="camera"
    • receiverUUID
    • receiverName
    • latitude + longitude
    • azimuth + declination
    • aperture
    • channel
    • altitude
    • start

The generic "receiverUUID" and "receiverName" settings can be used to limit the requested setting to individual blocks, the corresponding values should be requested first. In some cases it may be necessary to specify them. "start", "rotate", "save", "load" and "reload" are boolean settings. "filename" must be an absolute path in the local filesystem of the target system, using slashes as path separators.

Please note that these are one-off requests. If they cannot be executed or conflict with the local configuration the behavior is undefined.

In the document, RTSA http Stream Server Endpoints #11.pdf, there is a section that describes how to set the frequency range for measurement devices:

{
"frequencyCenter" : 1200000000,
"frequencySpan" : 44000000,
"frequencyBins" : 448,
"referenceLevel" : -20,
"type" : "capture"
}

We are using a spectrum analyzer within Aaronia RTSA application, and we want to adjust the center frequency, span, and reference level. To ensure that our application’s user interface aligns with the RTSA, we’ve represented the span value as an enumeration (e.g., “Full,” “1/2,” “1/4,” …, “1/512”). However, when attempting to use the frequencySpan value via the API, it doesn’t behave as expected on the RTSA.

 

For example:

Given "frequencyCenter" : 2440000000
And "frequencySpan" : 1220000000
We expected that setting the span to half of the center value would result in a span of 1/2. However, the actual behavior is different. Is there a specific relationship between frequencyCenter and frequencySpan? If so, how should we handle this? Alternatively, how can we use the frequencySpan value?

 

Thank you for your assistance!

Uploaded files:
  • rtsa_spectran.png

Please see https://github.com/Aaronia-Open-source/python_RTSA_HTTP_API_Sequence_Example/blob/main/rtsa_record_sequence.py for a working example, including the span.