Files
MicrOBU/obu-firmware/external/vanetza-idf/vanetza/dcc/entity.hpp
T
Ashin Walpola d107534eb2 Keep vanetza-idf in obu-firmware, so a plain clone builds the firmware
obu-firmware builds against the vanetza-idf C-ITS library, which until now
came from the colleague's microbu-esp32c5 tree beside the repository and was
not tracked here, so a clone of this repository could not build the firmware
it ships. The library alone is now part of obu-firmware, as
obu-firmware/external/vanetza-idf: their external/vanetza-idf at commit
cf4b99f, unchanged (9775 files; see its PROVENANCE.md). CMake takes it from
there by default; -DVANETZA_IDF_DIR still points the build elsewhere.

The rest of the colleague's tree (their own VAM firmware, PKI tooling,
station-link Python tools, the V2X2MAP bridge) stays out of this repository
and gitignored; nothing is pushed to their repository. NOTES.md, docs/06,
TODO.md and the pcap verifier's usage line point at the new location.
2026-09-24 10:56:05 +02:00

38 lines
814 B
C++

#ifndef ENTITY_HPP_KUAWS3PK
#define ENTITY_HPP_KUAWS3PK
#include <vanetza/dcc/channel_probe_processor.hpp>
#include <vanetza/dcc/transmit_rate_control.hpp>
namespace vanetza
{
namespace dcc
{
class Entity
{
public:
/**
* Provide TRC interface for Facilities
*
* Cooperative Awareness adapts its message rate according to TRC (T_GenCam_Dcc).
* \see EN 302 637-2 V1.3.2 (section 6.1.3)
*/
virtual TransmitRateControl& transmit_rate_control() = 0;
/**
* Provide interface for reporting channel probes.
*
* Usually, radio hardware will generate these reports periodically.
*/
virtual ChannelProbeProcessor& channel_probe_processor() = 0;
virtual ~Entity() = default;
};
} // namespace dcc
} // namespace vanetza
#endif /* ENTITY_HPP_KUAWS3PK */