-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
pixhack v5 RC is not detected on master #9989
Comments
Is this pixhack v5? If so what about pixhawk 4? |
@dagar correct this is for the Pixhack v5 works fine with Pixhawk 4. |
FYI @davids5 |
@dannyfpv I can see the FMU was a V511 but I need to know exact HW did you use for the RC and how and where was it connected (what connector?)? A Picture is always helpful. |
I had a look at the schematic it has some pop option and depending on what is populated the RC in is not compatible with FMUv5. |
|
The developer version of Pixhack v5 does not further support. We can close this issue. |
Hi @jinger26 could you elaborate?? I have exactly the same Problem! RC is detected on 1.8.1 but not on 1.9.0 Alpha / Master. Is my v5 now a brick for PX4 Community? |
Hi @tops4u , Pixhack v5 that has a "developer version" marked on the hardware was a release candidate for evaluation purpose only and not in production anymore. Do you have that version of the hardware or do you have a "V5" version of the hardware? |
@jinger26 I have not seen such a marking on my HW. On the console it shows up as HW Ver V551. |
@tops4u It is marked on the top of the cube. In white lettering. Based on the value I would assume you have V5. See https://github.com/PX4/Firmware/blob/master/boards/px4/fmu-v5/src/manifest.c#L88-L91 Master supports the FMUv5 Spec. 1.8.1 did not have the full RC (PPM, SBUS) support for FMUv5. The board you have is not wired to the FMUv5 Spec for RC. But as I say above it is unclear to me which chips, resistors are populated and what the we could get working 100% reliably |
Thanks @davids5 I don't know that either. What I can say is:
Shall I open a new Issue for my non working RC? Should I have a look inside? Why does Boot stop only due to Config change? Should I open an Issue for this? |
It is a know issue.
I do not think it will add value. We do not have a way to ID the components back to the schematic. The vendor has not given me a list of the pop option and how they are installed. So I can not tell you what has to be removed/fixed. The change that is most likely affecting the circuit is initializing the F7's USART 6 and not getting it it to "Single wire" mode. You could test this By removing USART 6 from the boar/nuttx config on the FMU and ensuring those GPIOs are left as inputs.
I am not sure what you mean.
Yes and give full details |
@davids5 could you tell me where the known Issue is tracked? I could not find an issue for this. I've opened Issue #11223 for the Boot issue. Regarding the RCIN Problem I have, could this be a Problem with Communication to the IO? This is what I get when I send px4io Status to the v5:
Using Version:
When I reverted back to 1.8.1 and cleared all Params, the IO was reachable and gave me proper results as follows:
|
Todays master tested on 2 units. Works on my HW.
|
All I did was set the SYS_AUTOSTART to 4011 |
I grabbed your params from the boot issue. I loaded them and power cycled. RC is still working fine. |
So my Unit is just different then - or I'm handling it wrong :-/ Those are two different Problems. With 1.8.1/1.8.2 and the mentioned Parameters the Unit will just not finish the boot process but RC works and the IO is reachable. I have not checked wether I get RC on the newly initialized Device on Master. I'll check this today. |
@tops4u - It is hard to say. As I said I did load your params. I had only USB, JTAG and and the XSR connected. To debug it, You and I can get to a common minimal state with Please ask @dagar to help you find the serial port mappings that had been in the rcS. Then see if you have something using USART6 in you params. |
Found it! Sorry it was stupid. I was using the same SD I had in the mRo X2.1 before. For the OSD I have put the following line in extras.txt: mavlink start -d /dev/ttyS6 -b 57600 -m osd -r 10000 This caused all the havoc with RC In and also with the communication with the IO. Strange still, that it did not happen with 1.8.2 So a big sorry for the inconvenience, and thanks a lot for the help! |
On the pr and master, the copter does not detect the radio, only on stable works well
first, send to manual mode and later to hold mode
https://review.px4.io/plot_app?log=bf71d883-0596-4723-95cc-ed70f2412ce6
**Drone
f450, pixhack, 20ams hobbywing esc and iris motors
on the firmware master 3293fe still work good @dagar
The text was updated successfully, but these errors were encountered: