hardware_integration Directory Reference

Directory dependency graph for hardware_integration:

Files
	available_can_drivers.hpp
	A utility to include all of the available CAN drivers. Should mainly be used for testing purposes.
	can_hardware_interface.hpp
	The hardware abstraction layer that separates the stack from the underlying CAN driver.
	can_hardware_plugin.hpp
	A base class for a CAN driver. Can be derived into your platform's required interface.
	canal.h
	canal_a.h
	flex_can_t4_plugin.hpp
	An interface for using FlexCAN_T4 on a Teensy4/4.1 device.
	innomaker_usb2can_windows_plugin.hpp
	An interface for using an InnoMaker USB2CAN device.
	InnoMakerUsb2CanLib.h
	libusb.h
	mac_can_pcan_plugin.hpp
	An interface for using a PEAK PCAN device through the MacCAN PCBUSB driver.
	mcp2515_can_interface.hpp
	An interface for using the MCP2515 can controller.
	pcan_basic_windows_plugin.hpp
	An interface for using a PEAK PCAN device.
	PCANBasic.h
	PCBUSB.h
	socket_can_interface.hpp
	An interface for using socket CAN on linux. Mostly for testing, but it could be used in any application to get the stack hooked up to the bus.
	socketcand_windows_network_client.hpp
	A windows hardware plugin for connecting to and using a socketcand server.
	spi_hardware_plugin.hpp
	A base class for SPI communication between hardware devices. Can be derived into your platform's required interface.
	spi_interface_esp.hpp
	A (synchronous) implementation for SPI communication with (CAN) hardware devices on ESP platforms.
	spi_transaction_frame.hpp
	A class containing the data for a single SPI transaction. Used in combination with SPIHardwarePlugin and allows for multiple transactions to be queued.
	sys_tec_windows_plugin.hpp
	An interface for using a SYS TEC sysWORXX USB CAN device.
	toucan_vscp_canal.hpp
	An interface for using a Rusoku TouCAN device via the VSCP CANAL api.
	twai_plugin.hpp
	A driver for using the Two-Wire Automotive Interface (TWAI) with the stack.
	Usbcan32.h
	UsbCanLs.h
	UsbCanUp.h
	virtual_can_plugin.hpp
	An OS and hardware independent virtual CAN interface driver for testing purposes. Any instance connecting to the same channel and in the same process will be able to communicate.