Add optional forward_command_on_receive to module manager interface#23
Add optional forward_command_on_receive to module manager interface#23danprudky wants to merge 1 commit into
Conversation
…face - introduces forward_command_on_receive(unsigned int device_type) as an optional export - returning OK signals MG to forward the received command to the device immediately, without waiting for the next status - if not exported by the module, MG defaults to NOT_OK (existing on-next-status behaviour)
|
Warning Review limit reached
More reviews will be available in 39 minutes and 50 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Adds forward_command_on_receive(unsigned int device_type) as an optional export to the module manager interface.
When a module exports this function and it returns OK, Module Gateway forwards the received command to the device immediately upon receipt, without waiting for the next status message. If the function is not exported, Module Gateway defaults to NOT_OK - preserving the existing on-next-status behaviour.
Implemented to support BAF-1562 (Teleop Control bridge), where commands must reach the device within 100 ms end-to-end and cannot wait for the next periodic status cycle.