-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Resource Remapping? #2923
Comments
It is not available |
i have the same thing :( its not yet implented in inav, maybe it will come later im also an omnibus user, betaflight has this function but inav doesnt have it yet, im using uart 1 for gps uart 3 for compass and uart 6 for sbus i need 1 more for frsky telemetery |
OK. Thanks, shellixyz. FinalX1992: If you have an Omnibus F4 V3 you might want to try the nav_1.9.0_OMNIBUSF4V3_I2C_REMAP.hex firmware found near the end of this thread: #2658 It appears to give you a fully functional SOFTSERIAL port (I haven't experimented with it much but it did appear to disable the LED strip feature.) For the now the best option may be to switch to the Matek F722-STD board. It has 5 UARTS available and it is supported in iNAV 1.9 |
i dont have the F4V3 i have the F4V5 so thats the issue that the FW wont work with it did tho XD |
Resource remapping is extremely useful feature. Please implement it |
@artempolikarpov Please see this discussion about it: #1145 |
I have a F4V5 original omnibus board I'm installing into a fixed wing plane. Using iNAV, Wraith32 65A ESC, Frsky X8R, DJI NAZA GPS. |
If I can use UART 1 for both Smart Port RX & ESC telemetry on TX, how do I remap in CLI if remapping is needed? Set UART 1 to soft serial & bidirectional? |
The telemetry RX and TX would not need high priority as they are both used just to monitor system status. |
Duplicate of #1145 Closing |
I see where SOFTSERIAL can be enabled as a feature but I'm unable to free-up an unused motor pin to use with IRC Tramp. Is resource remapping undocumented or just unavailable?
iNAV 1.9 and Omnibus F4 v3
The text was updated successfully, but these errors were encountered: