Todo List

Member isobus::AddressClaimStateMachine::update ()

Non-arbitratable address contention (there is not a good reason to use this, but we should add support anyways)

Member isobus::CANNetworkManager::send_can_message (std::uint32_t parameterGroupNumber, const std::uint8_t *dataBuffer, std::uint32_t dataLength, std::shared_ptr< InternalControlFunction > sourceControlFunction, std::shared_ptr< ControlFunction > destinationControlFunction=nullptr, CANIdentifier::CANPriority priority=CANIdentifier::CANPriority::PriorityDefault6, TransmitCompleteCallback txCompleteCallback=nullptr, void *parentPointer=nullptr, DataChunkCallback frameChunkCallback=nullptr)

Allow sending 8 byte message with the frameChunkCallback

Class isobus::ExtendedInputAttributes::CodePlane

Finish ExtendedInputAttributes implementation

Member isobus::InnoMakerUSB2CANWindowsPlugin::read_frame (isobus::CANMessageFrame &canFrame) override

error frame handling

Member isobus::SysTecWindowsPlugin::read_frame (isobus::CANMessageFrame &canFrame) override

Can probably optimize this better somehow by using the RX callback from the driver and a condition variable?

Member isobus::TaskControllerClient::process_queued_commands ()

process PDACKs better

Member isobus::TaskControllerClient::process_rx_message (const CANMessage &message, void *parentPointer)

Localization label partial pool handling

Member isobus::TransportProtocolManager::send_clear_to_send (std::shared_ptr< TransportProtocolSession > &session) const

apply CTS number of packets recommendation of 16 via a configuration option

Member isobus::VirtualTerminalClient::process_rx_message (const CANMessage &message, void *parentPointer)

load the preferred assignment into parentVT->assignedAuxiliaryInputDevices

save preferred assignment to persistent configuration

save preferred assignment to persistent configuration

figure out how to best pass other status properties below to application

The standard requires us to not perform any auxiliary function when learn mode is active, so we probably want to let the application know about that somehow

maybe a better way available than relying on aux function callbacks registered?

maybe a better way available than relying on aux function callbacks registered?

Member isobus::VirtualTerminalClient::send_auxiliary_functions_preferred_assignment () const

load preferred assignment from saved configuration

Member isobus::VirtualTerminalClient::update ()

We should make sure that when we disconnect/reconnect atleast 500ms has passed since the last auxiliary maintenance message

Member isobus::VirtualTerminalClient::update_auxiliary_input_status (std::uint16_t objectID)

Change status message every 50ms to every 200ms for non-latched boolean inputs on interaction

Change values based on state of auxiliary input, e.g. for non-latched boolean inputs we have to change from value=1 (momentary) to value=2 (held)