feat(boards/cuav_x25-mega): Add cuav/x25-mega board support#26664
feat(boards/cuav_x25-mega): Add cuav/x25-mega board support#26664cuav-chen2 wants to merge 7 commits intoPX4:mainfrom
Conversation
|
|
||
| ## Assembly/Setup | ||
|
|
||
| - Not provided. |
There was a problem hiding this comment.
Is there an intent to provide or a link you can point us to for instructions?
There was a problem hiding this comment.
I mean this kind of thing https://docs.px4.io/main/en/assembly/quick_start_cuav_pixhawk_v6x
There was a problem hiding this comment.
No relevant information yet; to be updated later.
There was a problem hiding this comment.
This PR(#26882) adds the quick start guide for X25 EVO, which also applies to X25 MEGA. After merging, I will update the Assembly/Setup section in cuav_x25-mega.md.
| - Dimensions: | ||
|
|
||
|  | ||
|
|
There was a problem hiding this comment.
Can you please add weight information.
There was a problem hiding this comment.
No relevant information yet; to be updated later.
|
|
||
| ## RC Input | ||
|
|
||
| The RC input pin is directly connected to the FMU UART6 TX. |
There was a problem hiding this comment.
Thanks for this. I can see that this is the RC IN port. I can also see that RC_INPUT is present in the config so the rc_input module will be present, and that module is enabled by default to autodetect protocols.
A few questions:
-
Did you mean "TX" in
FMU UART6 TX? I.e is this actually a single wire connection? -
Does using a single wire (if so) create any limits on what RC recievers can be connected?
Or to put it another way, above you say that RC IN supports "Spektrum / DSM and S.Bus". HOwever the module states support for: PPM, SBUS, DSM, SUMD, ST24, TBS Crossfire (CRSF). So I am wondering if the connection to the port means that you can only support the listed ones due to the way the port is connected, or you support all the protocols through
RC IN?
There was a problem hiding this comment.
- Yes, single-wire connection.
- We only have PPM and SBUS devices; these two protocols are supported, while other protocols cannot be confirmed.
| If the PX4 autopilot detects a sensor failure, the system seamlessly switches to another sensor to maintain flight control reliability. | ||
| - Independent LDO power control supplies power to each sensor group. | ||
| A vibration isolation system filters high-frequency vibrations and reduces noise to ensure accurate readings, enabling better overall flight performance for the vehicle. | ||
| - Integrated Microchip Ethernet PHY for high-speed communication with onboard devices like mission computers via Ethernet. |
There was a problem hiding this comment.
IF this supports Ethernet, probably worth adding this to the list in https://docs.px4.io/main/en/advanced_config/ethernet_setup#supported-flight-controllers
IF it were me, I would also add a heading for Ethernet setup, and link to that doc (or explain any differences in normal setup)
There was a problem hiding this comment.
Documentation added. No configuration differences.
|
@cuav-chen2 please see above from @hamishwillee |
hamishwillee
left a comment
hamishwillee
left a comment
There was a problem hiding this comment.
@mrpollo Can you review this please. The docs are OK. There are still some "TBDs". Not sure whether we should allow that or not. But in any case the rest of this needs a look.
cuav-chen2
changed the title
cuav-chen2
force-pushed
the
add_cuav_x25-mega
branch
from
80041cb to
bdc2294
Compare
3 participants
Add support for CUAV-X25-MEGA board.