> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/holoscan/sensor-bridge/2-7-latest/api-reference/emulation-api/classes/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/holoscan/sensor-bridge/_mcp/server.

# Classes

## Docs

- [hololink::emulation::AddressMemory](https://docs.nvidia.com/holoscan/sensor-bridge/2-7-latest/api-reference/emulation-api/classes/addressmemory.md): Representation of the internal memory space of the HSBEmulator and its registers.
- [hololink::emulation::BaseTransmitter](https://docs.nvidia.com/holoscan/sensor-bridge/2-7-latest/api-reference/emulation-api/classes/basetransmitter.md): Abstract base class for all transmitters.
- [hololink::emulation::COEDataPlane](https://docs.nvidia.com/holoscan/sensor-bridge/2-7-latest/api-reference/emulation-api/classes/coedataplane.md): The DataPlane implementation for IEEE 1722B Camera-over-Ethernet link layer transport.
- [hololink::emulation::DataPlane](https://docs.nvidia.com/holoscan/sensor-bridge/2-7-latest/api-reference/emulation-api/classes/dataplane.md): DataPlane is the partially implemented Abstract Base Class with which HSB Emulator applications control data transmission and HSB Host applications establish "connections" and data flow via Bootp enumeration. The parent instance of any DataPlane implementation will manage Bootp broadcasting. Each implementation must interface with the HSB Emulator's internal memory model (AddressMemory) to update and manage metadata and any state needed for the metadata or transport layer for the corresponding Transmitter.
- [hololink::emulation::HSBEmulator](https://docs.nvidia.com/holoscan/sensor-bridge/2-7-latest/api-reference/emulation-api/classes/hsbemulator.md): The HSBEmulator class represents the interface that a host application has to an HSB and acts as the emulation device's controller. It manages the DataPlane objects and the I2CController and all communication with the internal memory model; see AddressMemory for more details.
- [hololink::emulation::I2CController](https://docs.nvidia.com/holoscan/sensor-bridge/2-7-latest/api-reference/emulation-api/classes/i2ccontroller.md): class that manages virtual I2C peripherals from the host. This is mostly for the linux emulator where the use case is for virtual sensors
- [hololink::emulation::I2CPeripheral](https://docs.nvidia.com/holoscan/sensor-bridge/2-7-latest/api-reference/emulation-api/classes/i2cperipheral.md): Abstract base class for all I2C-based emulated sensors giving them access to I2C transactions originating from the HSB host.
- [hololink::emulation::RegisterMemory](https://docs.nvidia.com/holoscan/sensor-bridge/2-7-latest/api-reference/emulation-api/classes/registermemory.md): 
- [hololink::emulation::RoCEv2DataPlane](https://docs.nvidia.com/holoscan/sensor-bridge/2-7-latest/api-reference/emulation-api/classes/rocev2dataplane.md): The DataPlane implementation for RoCEv2 UDP transport.