I am using speedy bee f405 v4, radiomaster rp4td, radiomaster pocket. Ardupilot copter. The ELRS Rx module is attached to uart2 (not the sbus pin. I’ve double triple quadruple checked Rx to TX tx to Rx.) I’ve set parameters that are required for ELRS in all kinds of recommended combinations. Nothing seems to enable the Rx of rcinput. If anyone has any idea what’s going on please help me out. I’m new to ardupilot and im really getting frustrated with this as I’m not incompetent and didn’t think this was so difficult seeing everyone else got it working just fine.. I’m fairly decent with figuring out issues but this one is kicking my butt!!! It sees a bitrate in the mavlink inspection tool but no channel data is parsed. The radio is bound properly. Ive tried all the “solutions" Google and forum diving have brought to light but again. No change. Tried different uarts, nothing (including the uart used for gps was tested. Which is working with the gps but not ELRS receiver.) I’ve had a friend of mine whose good with software to have a look and he said it should just work the way I have it set up. But it doesn’t see the values from rc radio. Am I missing something? (Ps I don’t know how to pull logs or anything; it keeps saying logging error anyways. I’m new so I doknow if that means there are no logs or if it logged but not properly??? Guidance here would be helpful for troubleshooting I think.)
Moderator edit: please share parameters as a file rather than thousands of lines of posted text.
hardware:
FC: speedybee f405 v4 (they sent a replacement for free and now i have two of these that arent doing “the thing” it should be. ive purchased f722 flight controllers from a defferant brand and maybe that will solve the issue? perhaps its a processor speed issue with the f405 chip used on these specif boards?? it feels like taking a paddle boat / raft out to the open ocean and using a string with a paperclip on the end for a hook tied to a branch to go fishing for that monster blue fin tuna fish. all the odds are against me here it seems!
RC RX: EITHER RP4TD OR XR4 (have tested with basic generic elrs modules aswell same deal. total rx module models tested = 4)
RC TX: radio master pocket with the radiomaster nomad module installed on the back. the internal rf is off and external is on. radio binds fine with either the internal tx or the external tx and also works on other drones. its 100% the uart coms
VTRX: N/A (postponed until sucsesful proving flight has occured.)
Companion Computer(CC): Raspberry pi zero 2 w. (use case development postponed. see VTRX section. disconnected for diagnostic reasons.)
voltages are all spot on the tolerances. no shorts, no mixed up wires, the firmware seems to operate correctly aside from rc input, it does accept a joystick passtrough with missionplanner but still disarms due to no rc input. doesnt matter if the battery is on it or just usb power. and agian all this also occurs in betaflight too.
Of course it doesn’t. That is Flight Controller dependent and that FC doesn’t have it. Now go back and edit your post and delate that pages long parameter list. If you want to share it just attach it as a file.
yes i made that reply to someone who told me to change that parameter. i am aware that it not applicable to my board..hence the full param list posted so everyone can see the options i have at my control. the site here WILL NOT let me upload any files. it sits there for hours trying to upload. my appoligies for its length, it is the only way ive been able to post it here. i presume its a network issue on my end as my file downloads are slow too. (will try to figure that out too ugh)
ive applied those paramters to the f405 with the rp4td on it that i have on the bench here. did not work.. no green bars in mission planner radio cal. page.
alright mine also Speedybee V4 like yours so don’t worry it should be working with ELRS, the setting were like my prev post above, but on Serial6 and FYI this speedybee have a picky Serial issue f.e GPS it can only detected on certain Serial (i forgot which one) but for ELRS i definitely still remember i put on Serial6
okay heres where things get funny!! ive tried swapping the gps and elrs uarts. (gps works on both uarts funny enough. ive tried no gps incase the dma acsess was an issue. nope.) the elrs unit does not communicate with the flight controller still. ive also tried serial3 and 5. no go.
Nope Unfortunately you are wrong, I did use Arducopter & ELRS with this Speedybee V4 without any problems at all (of course just need the correct Serial to use), I will try to check again tomorrow when I get home and report back in here with detail what version of Arducopter FW and detail setting from the ELRS it self, i’m still confidence i’m not wrong because just last week i play with it
ardupilot is often (not always a true staement) not listed on manufacturers documents. you need to referance the ardupilot ducomentation about flight controllers here. ( Choosing an Autopilot — Copter documentation ) this lists all verifed flight computers and the limits they have; if any. besides if this board was not supported then there wouldnt be a stable nor an “offical” (according to mission planner and ardupilot firmware database) ardupilot firmware build for this board. its a little confusing at times and almost got me when picking out a flight computer the first time. happens to the best of us.
i have purchased (a cheap enough to buy two units on a whim!) radiolink f722 flight controller with betaflight installed. wired up elrs as per the flight controllers diagram. enables serail rx on serail 2 and save restart. BOOM IT WORKED NO ISSUES!! therfore it is conclusive to blame the speedy bee f405 v4 boards for not handling the serial exhange properly or at all. be it due to settings or pin configuration issues that is yet to be seen. BUT THE ISSUE IS WITH THE FLIGHT CONTROLLER!!! this is great we now know and see progress with the bug hunting! ive been at this since september. i am going stir-crazy over this silly collection of capable rocks and minerals! like i gotta be smarter than a rock with minerals on it right….. you know thats it. we gotta think like the flight computer. think like a quad. what would you do if you were a flight computer on a quad???
Your conclusion is flawed. I have no idea what you did wrong throughout this saga, but there are countless success stories that conflict with your findings.
There are a few glaring areas of misconfiguration and misunderstanding, most of which have already been pointed out. For example, the GPS going undetected is most likely a case of configuring multiple serial ports for GPS rather than an autopilot issue.
EDIT/UPDATE: The root cause appears to be incorrect firmware version. Re-flashing with STM32CubeProgrammer in DFU mode with the correct firmware target fixed the issue, as can be observed ~40 posts below this one.
