DEENESPTFRRUARHIKOZHNL

estrutura ara::tsync::TimePrecisionMeasurement

[SWS_TS_01400] Upstream: RS_TS_00034 texto ainda não importado

struct TimePrecisionMeasurement final {...};

Structure with detailed data for precision measurement of the Time Slave .

Header-Datei#include "ara/tsync/time_precision_measurement_type.h"
Forwarding-Header#include "ara/tsync/tsync_fwd.h"
Scopenamespace ara::tsync

Guia do utilizadorGERADO POR IA

Fornece dados de medição detalhados e bits de status para a avaliação da precisão da sincronização de tempo de um Time Slave.
GERADO POR IA não revisado Modelo: gemini-3.8-flash-medium · Esforço: medium · Temperatura: não controlável · Prompt: 360378009f87 Procedência Perguntas em aberto (1)
traduzido do guia alemãogemini-3.8-flash-low · 2026-10-13 · Original em alemão

Fornece dados de medição detalhados e bits de status para a avaliação da precisão da sincronização de tempo de um Time Slave.

A estrutura ara::tsync::TimePrecisionMeasurement fornece valores de medição detalhados para o registro de precisão de um Time Slave sincronizado em relação a uma base de tempo global. Ela registra timestamps locais imediatamente antes e depois da sincronização ([SWS_TS_01401], [SWS_TS_01406]), bem como desvios de tempo de propagação e de taxa. Por meio do campo de bits de status [SWS_TS_01403], ela também sinaliza condições de erro como timeouts, saltos excessivos de tempo ou ultrapassagens de taxa.

Contexto

A estrutura de dados ara::tsync::TimePrecisionMeasurement destina-se ao fornecimento de dados de medição detalhados para o registro de precisão de um Time Slave sincronizado em relação a uma base de tempo de nível superior. Dentro do módulo tsync, ela captura instantâneos do relógio local imediatamente antes e após o alinhamento com a base de tempo global durante um evento de sincronização. A estrutura forma, assim, a interface para o monitoramento metrológico, avaliação de qualidade e diagnóstico da sincronização de relógios em sistemas distribuídos.

TimePrecisionContext Master Global Time Master / Time Gateway Slave Time Slave (ara::tsync) Master->Slave Synchronisations- nachrichten Measurement ara::tsync:: TimePrecisionMeasurement Slave->Measurement erzeugt & befuellt Consumer Anwendung / Diagnosemonitor Consumer->Measurement liest Messdaten & Statusbits

Diagrama de contexto: registro e repasse de dados de precisão entre a base de tempo, Time Slave e a aplicação de monitoramento. Fontes: [SWS_TS_01401], [SWS_TS_01403], [SWS_TS_01408]

Ciclo de vida

Como uma estrutura final sem gerenciamento próprio de ponteiros ou recursos, TimePrecisionMeasurement é instanciada como um objeto de valor (Value Object). A instanciação e o preenchimento ocorrem normalmente de forma cíclica pelo Time Slave da Adaptive Platform imediatamente após uma etapa de sincronização. A estrutura não possui fases de ciclo de vida dinâmicas ou transições de estado internas; seu estado é imutável a partir do momento do preenchimento como um registro consistente de medição. Como a estrutura provavelmente é repassada por cópia ou por meio de referências constantes para componentes de avaliação, não existem relações de propriedade de nível superior ou requisitos complexos de destruição. O acesso simultâneo de leitura a uma instância preenchida a partir de múltiplas threads de execução é considerado não crítico, desde que nenhuma operação de escrita concorrente ocorra. Pergunta Q-11af6e7f794e4acb (aberta)

Caminho de utilização

A avaliação típica dos valores de medição segue um padrão fixo para a análise da precisão de marcha, saltos de sincronização e atrasos de rede:

  • Verificação do status de sincronização: primeiro, o campo de bits [SWS_TS_01403] (timeBaseStatus) é analisado para determinar se existe uma sincronização global válida ou se ocorreram condições de erro.
  • Determinação do salto de tempo: comparando os timestamps da base de tempo local imediatamente antes da sincronização ([SWS_TS_01406] locSeconds, [SWS_TS_01407] locNanoSeconds) com os valores diretamente após a sincronização ([SWS_TS_01401] glbSeconds, [SWS_TS_01402] glbNanoSeconds), o salto de correção aplicado pode ser calculado com precisão.
  • Determinação da qualidade da transmissão: por meio de [SWS_TS_01408] (pathDelay), avalia-se o tempo atual de transmissão e de propagação de sinal em nanossegundos. Complementarmente, [SWS_TS_01405] (rateDeviation) fornece o desvio de taxa calculado da frequência de clock local diretamente após a medição de taxa.
  • Associação ao tempo local virtual: os 32 bits menos significativos da base de tempo local virtual ([SWS_TS_01404] virtualLocalTimeLow) permitem a correlação do momento de sincronização com o relógio de referência contínuo do nó.

Cenários de erro

Condições de erro e estados de exceção não são relatados por meio de exceções de C++, mas sim codificados diretamente através dos bits de status em [SWS_TS_01403] (timeBaseStatus). Os componentes de avaliação devem verificar quais condições de erro estão presentes antes de prosseguir com o processamento dos valores de tempo:

  • Timeout de recepção: se o bit 0 (TIMEOUT, 0x01) estiver definido, ocorreu um timeout na recepção de mensagens de sincronização.
  • Saltos de tempo: os bits TIMELEAP_FUTURE (0x10, bit 4) ou TIMELEAP_PAST (0x20, bit 5) sinalizam que um valor limite configurado para correções bruscas de tempo para o futuro ou passado foi excedido.
  • Erros de taxa: se o bit 7 (RATE_EXCEEDED, 0x80) estiver definido, a taxa de clock calculada excede os valores limites definidos; já o bit 6 (RATE_CORRECTED, 0x40) indica se uma correção de taxa válida pôde sequer ser calculada.
  • Condição de dependência: de acordo com [SWS_TS_01403], os bits TIMEOUT, TIMELEAP_FUTURE, TIMELEAP_PAST e SYNC_TO_GATEWAY (0x04, bit 2) só podem estar definidos se o bit 3 (GLOBAL_TIME_BASE, 0x08) estiver definido. Se GLOBAL_TIME_BASE estiver ausente, a base de tempo local funcionou até agora exclusivamente com base no relógio de referência local e nunca foi sincronizada com a base de tempo global.

Este guia foi criado por uma IA com base na especificação AUTOSAR R25-11.

Mapa de membros

Diagrama de classes

Hohle Dreieckspfeile = Vererbung (zeigt zur Basisklasse); Klicken öffnet die jeweilige Klassenseite.

G nara__tsync__TimePrecisionMeasurement344 «struct» TimePrecisionMeasurement + glbNanoSeconds + glbSeconds + locNanoSeconds + locSeconds + pathDelay + rateDeviation + timeBaseStatus + virtualLocalTimeLow

Vista de detalhes

Selecione uma entrada no índice.

Constantes

glbNanoSeconds variável

Nanoseconds of the Local Time Base directly after synchronization with the Global Time Base. Range: 0..999999999 (4 Byte)

std::uint32_t glbNanoSeconds;
glbSeconds variável

Seconds of the Local Time Base directly after synchronization with the Global Time Base. Range: 0..4294967295 (4 Byte)

std::uint32_t glbSeconds;
locNanoSeconds variável

Nanoseconds of the Local Time Base directly before synchronization with the Global Time Base. Range: 0..999999999 (4 Byte)

std::uint32_t locNanoSeconds;
locSeconds variável

Seconds of the Local Time Base directly before synchronization with the Global Time Base. Range: 0..4294967295 (4 Byte)

std::uint32_t locSeconds;
pathDelay variável

Current propagation delay in nanoseconds. Range: 0..4294967295 (4 Byte)

std::uint32_t pathDelay;
rateDeviation variável

Calculated Rate Deviation directly after rate deviation measurement. Range: 0..+-32000 (2 Byte)

std::int16_t rateDeviation;
timeBaseStatus variável

TimeBaseStatus. Time Base Status of the Local Time Base directly after synchronization with the Global Time Base TIMEOUT 0x01 Bit 0 (LSB): 0x00: No Timeout on receiving Synchronisation Messages 0x01: Timeout on receiving Synchronisation Messages SYNC_TO_GATEWAY 0x04 Bit 2 0x00: Local Time Base is synchronous to Global Time Master 0x04: Local Time Base updates are based on a Time Gateway below the Global Time Master GLOBAL_TIME_BASE 0x08 Bit 3 0x00: Local Time Base is based on Local Time Base reference clock only (never synchronized with Global Time Base) 0x08: Local Time Base was at least synchronized with Global Time Base one time TIMELEAP_FUTURE 0x10 Bit 4 0x00: No leap into the future within the received time for Time Base, 0x10: Leap into the future within the received time for Time Base exceeds a configured threshold TIMELEAP_ PAST 0x20 Bit 5 0x00: No leap into the past within the received time for Time Base 0x20: Leap into the past within the received time for Time Base exceeds a configured threshold.

std::uint8_t timeBaseStatus;

Least significant 32 bit of the Virtual Local Time directly after synchronization with the Global Time Base. Range: 0..4294967295 (4 Byte)

std::uint32_t virtualLocalTimeLow;

Documentação das constantes / variáveis

variável glbNanoSeconds [SWS_TS_01402] Upstream: RS_TS_00034 texto ainda não importado

std::uint32_t glbNanoSeconds;

Nanoseconds of the Local Time Base directly after synchronization with the Global Time Base. Range: 0..999999999 (4 Byte)

Header-Datei#include "ara/tsync/time_precision_measurement_type.h"
Scopestruct ara::tsync::TimePrecisionMeasurement
SymbolglbNanoSeconds
Typstd::uint32_t

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_TS_01402
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_01402@rel:R25-11#0cec2137
Content hash
0cec2137
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_01402
Status: valid/unmigrated Version: rel:R25-11#237761c4 Versionshistorie & Revisions (1 transition, 7 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_TS_01402@rel:R25-11#237761c4
Point-in-Time History:
Recorded Revisions (7):
  • R25-11rel:R25-11#6ce5f9892026-09-30
  • R20-11rel:R20-11#dcc055a12026-10-14
  • R21-11rel:R21-11#dcc055a12026-10-14
  • R22-11rel:R22-11#fa4c93492026-10-14
  • R23-11rel:R23-11#237761c42026-10-14
  • R24-11rel:R24-11#237761c42026-10-14
  • R25-11rel:R25-11#237761c42026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill

variável glbSeconds [SWS_TS_01401] Upstream: RS_TS_00034 texto ainda não importado

std::uint32_t glbSeconds;

Seconds of the Local Time Base directly after synchronization with the Global Time Base. Range: 0..4294967295 (4 Byte)

Header-Datei#include "ara/tsync/time_precision_measurement_type.h"
Scopestruct ara::tsync::TimePrecisionMeasurement
SymbolglbSeconds
Typstd::uint32_t

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_TS_01401
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_01401@rel:R25-11#9c50219b
Content hash
9c50219b
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_01401
Status: valid/unmigrated Version: rel:R25-11#c7a8c118 Versionshistorie & Revisions (1 transition, 7 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_TS_01401@rel:R25-11#c7a8c118
Point-in-Time History:
Recorded Revisions (7):
  • R25-11rel:R25-11#8ce5c9a62026-09-30
  • R20-11rel:R20-11#3eb4084a2026-10-14
  • R21-11rel:R21-11#3eb4084a2026-10-14
  • R22-11rel:R22-11#755f009a2026-10-14
  • R23-11rel:R23-11#c7a8c1182026-10-14
  • R24-11rel:R24-11#c7a8c1182026-10-14
  • R25-11rel:R25-11#c7a8c1182026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill

variável locNanoSeconds [SWS_TS_01407] Upstream: RS_TS_00034 texto ainda não importado

std::uint32_t locNanoSeconds;

Nanoseconds of the Local Time Base directly before synchronization with the Global Time Base. Range: 0..999999999 (4 Byte)

Header-Datei#include "ara/tsync/time_precision_measurement_type.h"
Scopestruct ara::tsync::TimePrecisionMeasurement
SymbollocNanoSeconds
Typstd::uint32_t

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_TS_01407
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_01407@rel:R25-11#57db846f
Content hash
57db846f
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_01407
Status: valid/unmigrated Version: rel:R25-11#bf68c493 Versionshistorie & Revisions (1 transition, 7 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_TS_01407@rel:R25-11#bf68c493
Point-in-Time History:
Recorded Revisions (7):
  • R25-11rel:R25-11#aa5525982026-09-30
  • R20-11rel:R20-11#b0d215ed2026-10-14
  • R21-11rel:R21-11#b0d215ed2026-10-14
  • R22-11rel:R22-11#cdd6414a2026-10-14
  • R23-11rel:R23-11#bf68c4932026-10-14
  • R24-11rel:R24-11#bf68c4932026-10-14
  • R25-11rel:R25-11#bf68c4932026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill

variável locSeconds [SWS_TS_01406] Upstream: RS_TS_00034 texto ainda não importado

std::uint32_t locSeconds;

Seconds of the Local Time Base directly before synchronization with the Global Time Base. Range: 0..4294967295 (4 Byte)

Header-Datei#include "ara/tsync/time_precision_measurement_type.h"
Scopestruct ara::tsync::TimePrecisionMeasurement
SymbollocSeconds
Typstd::uint32_t

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_TS_01406
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_01406@rel:R25-11#a7eabba2
Content hash
a7eabba2
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_01406
Status: valid/unmigrated Version: rel:R25-11#ddbe78ef Versionshistorie & Revisions (1 transition, 7 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_TS_01406@rel:R25-11#ddbe78ef
Point-in-Time History:
Recorded Revisions (7):
  • R25-11rel:R25-11#ae7070552026-09-30
  • R20-11rel:R20-11#c06b058b2026-10-14
  • R21-11rel:R21-11#bd6d8eb32026-10-14
  • R22-11rel:R22-11#004237c12026-10-14
  • R23-11rel:R23-11#ddbe78ef2026-10-14
  • R24-11rel:R24-11#ddbe78ef2026-10-14
  • R25-11rel:R25-11#ddbe78ef2026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill

variável pathDelay [SWS_TS_01408] Upstream: RS_TS_00034 texto ainda não importado

std::uint32_t pathDelay;

Current propagation delay in nanoseconds. Range: 0..4294967295 (4 Byte)

Header-Datei#include "ara/tsync/time_precision_measurement_type.h"
Scopestruct ara::tsync::TimePrecisionMeasurement
SymbolpathDelay
Typstd::uint32_t

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_TS_01408
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_01408@rel:R25-11#6fb5694d
Content hash
6fb5694d
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_01408
Status: valid/unmigrated Version: rel:R25-11#ec89c91b Versionshistorie & Revisions (1 transition, 7 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_TS_01408@rel:R25-11#ec89c91b
Point-in-Time History:
Recorded Revisions (7):
  • R25-11rel:R25-11#b72bc7652026-09-30
  • R20-11rel:R20-11#dd666fae2026-10-14
  • R21-11rel:R21-11#dd666fae2026-10-14
  • R22-11rel:R22-11#42bda34a2026-10-14
  • R23-11rel:R23-11#ec89c91b2026-10-14
  • R24-11rel:R24-11#ec89c91b2026-10-14
  • R25-11rel:R25-11#ec89c91b2026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill

variável rateDeviation [SWS_TS_01405] Upstream: RS_TS_00034 texto ainda não importado

std::int16_t rateDeviation;

Calculated Rate Deviation directly after rate deviation measurement. Range: 0..+-32000 (2 Byte)

Header-Datei#include "ara/tsync/time_precision_measurement_type.h"
Scopestruct ara::tsync::TimePrecisionMeasurement
SymbolrateDeviation
Typstd::int16_t

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_TS_01405
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_01405@rel:R25-11#709e5ae7
Content hash
709e5ae7
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_01405
Status: valid/unmigrated Version: rel:R25-11#a522ccb0 Versionshistorie & Revisions (1 transition, 7 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_TS_01405@rel:R25-11#a522ccb0
Point-in-Time History:
Recorded Revisions (7):
  • R25-11rel:R25-11#e439fe9e2026-09-30
  • R20-11rel:R20-11#4dd015bf2026-10-14
  • R21-11rel:R21-11#4dd015bf2026-10-14
  • R22-11rel:R22-11#6b8a92e42026-10-14
  • R23-11rel:R23-11#e18bf2962026-10-14
  • R24-11rel:R24-11#a522ccb02026-10-14
  • R25-11rel:R25-11#a522ccb02026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill

variável timeBaseStatus [SWS_TS_01403] Upstream: RS_TS_00034 texto ainda não importado, RS_TS_00021 texto ainda não importado

std::uint8_t timeBaseStatus;

TimeBaseStatus. Time Base Status of the Local Time Base directly after synchronization with the Global Time Base TIMEOUT 0x01 Bit 0 (LSB): 0x00: No Timeout on receiving Synchronisation Messages 0x01: Timeout on receiving Synchronisation Messages SYNC_TO_GATEWAY 0x04 Bit 2 0x00: Local Time Base is synchronous to Global Time Master 0x04: Local Time Base updates are based on a Time Gateway below the Global Time Master GLOBAL_TIME_BASE 0x08 Bit 3 0x00: Local Time Base is based on Local Time Base reference clock only (never synchronized with Global Time Base) 0x08: Local Time Base was at least synchronized with Global Time Base one time TIMELEAP_FUTURE 0x10 Bit 4 0x00: No leap into the future within the received time for Time Base, 0x10: Leap into the future within the received time for Time Base exceeds a configured threshold TIMELEAP_ PAST 0x20 Bit 5 0x00: No leap into the past within the received time for Time Base 0x20: Leap into the past within the received time for Time Base exceeds a configured threshold.

Bit 6 RATE_CORRECTED 0x00: Valid rate correction not calculated for the Synchronized Time Base, 0x40: Valid rate correction calculated for the Synchronized Time Base. Bit 7 RATE_EXCEEDED 0x00: Calculated rate for Time Base does not exceed limits, 0x80: Calculated rate for Time Base exceeds limits. Description Bit 1 is always 0 (reserved for future usage) Variables of this type are used to express if and how a Local Time Base is synchronized to the Global Time Master. The type is a bitfield of individual status bits, although not every combination is possible, i.e. any of the bits TIMEOUT, TIMELEAP_ FUTURE, TIMELEAP_PAST and SYNC_TO_GATEWAY can only be set if the GLOBAL_ TIME_BASE bit is set.

Header-Datei#include "ara/tsync/time_precision_measurement_type.h"
Scopestruct ara::tsync::TimePrecisionMeasurement
SymboltimeBaseStatus
Typstd::uint8_t

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_TS_01403
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_01403@rel:R25-11#cfc30646
Content hash
cfc30646
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_01403
Status: valid/unmigrated Version: rel:R25-11#dee1f15d Versionshistorie & Revisions (1 transition, 7 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_TS_01403@rel:R25-11#dee1f15d
Point-in-Time History:
Recorded Revisions (7):
  • R25-11rel:R25-11#6a53bfde2026-09-30
  • R20-11rel:R20-11#be77789b2026-10-14
  • R21-11rel:R21-11#ab49120e2026-10-14
  • R22-11rel:R22-11#7ad12e822026-10-14
  • R23-11rel:R23-11#4e6eadf32026-10-14
  • R24-11rel:R24-11#4e6eadf32026-10-14
  • R25-11rel:R25-11#dee1f15d2026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill

variável virtualLocalTimeLow [SWS_TS_01404] Upstream: RS_TS_00034 texto ainda não importado

std::uint32_t virtualLocalTimeLow;

Least significant 32 bit of the Virtual Local Time directly after synchronization with the Global Time Base. Range: 0..4294967295 (4 Byte)

Header-Datei#include "ara/tsync/time_precision_measurement_type.h"
Scopestruct ara::tsync::TimePrecisionMeasurement
SymbolvirtualLocalTimeLow
Typstd::uint32_t

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_TS_01404
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_TS_01404@rel:R25-11#11d4392b
Content hash
11d4392b
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_TimeSynchronization.pdf#nameddest=SWS_TS_01404
Status: valid/unmigrated Version: rel:R25-11#fd280f7c Versionshistorie & Revisions (1 transition, 7 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_TS_01404@rel:R25-11#fd280f7c
Point-in-Time History:
Recorded Revisions (7):
  • R25-11rel:R25-11#8c0320502026-09-30
  • R20-11rel:R20-11#502db2192026-10-14
  • R21-11rel:R21-11#502db2192026-10-14
  • R22-11rel:R22-11#e776b8532026-10-14
  • R23-11rel:R23-11#fd280f7c2026-10-14
  • R24-11rel:R24-11#8f66b6822026-10-14
  • R25-11rel:R25-11#fd280f7c2026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill