Cube Orange Support Thread

PX4 Autopilot
23

Is this thread still alive?

Lately I am experiencing issues with 2 Cube Oranges: they don’t respond properly anymore, as if parts in it are slowly dying… I’ve used these before, uploading firmware frequently…

This is what I get:

Nov 16 17:59:50 traveller kernel: [ 1511.349645] usb 1-4: new full-speed USB device number 34 using xhci_hcd
Nov 16 17:59:50 traveller kernel: [ 1511.477688] usb 1-4: device descriptor read/64, error -71
Nov 16 17:59:50 traveller kernel: [ 1511.713687] usb 1-4: device descriptor read/64, error -71
Nov 16 17:59:51 traveller kernel: [ 1511.949650] usb 1-4: new full-speed USB device number 35 using xhci_hcd
Nov 16 17:59:51 traveller kernel: [ 1512.077695] usb 1-4: device descriptor read/64, error -71
Nov 16 17:59:51 traveller kernel: [ 1512.313692] usb 1-4: device descriptor read/64, error -71
Nov 16 17:59:51 traveller kernel: [ 1512.421832] usb usb1-port4: attempt power cycle
Nov 16 17:59:52 traveller kernel: [ 1513.073662] usb 1-4: new full-speed USB device number 36 using xhci_hcd
Nov 16 17:59:52 traveller kernel: [ 1513.073876] usb 1-4: Device not responding to setup address.
Nov 16 17:59:52 traveller kernel: [ 1513.281893] usb 1-4: Device not responding to setup address.
Nov 16 17:59:52 traveller kernel: [ 1513.489663] usb 1-4: device not accepting address 36, error -71
Nov 16 17:59:52 traveller kernel: [ 1513.617666] usb 1-4: new full-speed USB device number 37 using xhci_hcd
Nov 16 17:59:52 traveller kernel: [ 1513.617859] usb 1-4: Device not responding to setup address.
Nov 16 17:59:53 traveller kernel: [ 1513.825872] usb 1-4: Device not responding to setup address.
Nov 16 17:59:53 traveller kernel: [ 1514.037665] usb 1-4: device not accepting address 37, error -71
Nov 16 17:59:53 traveller kernel: [ 1514.037805] usb usb1-port4: unable to enumerate USB device
Nov 16 17:59:55 traveller kernel: [ 1516.661693] usb 1-4: new full-speed USB device number 38 using xhci_hcd
Nov 16 17:59:55 traveller kernel: [ 1516.789734] usb 1-4: device descriptor read/64, error -71
Nov 16 17:59:56 traveller kernel: [ 1517.025733] usb 1-4: device descriptor read/64, error -71
Nov 16 17:59:56 traveller kernel: [ 1517.261705] usb 1-4: new full-speed USB device number 39 using xhci_hcd
Nov 16 17:59:56 traveller kernel: [ 1517.389792] usb 1-4: device descriptor read/64, error -71
Nov 16 17:59:56 traveller kernel: [ 1517.625744] usb 1-4: device descriptor read/64, error -71
Nov 16 17:59:56 traveller kernel: [ 1517.733851] usb usb1-port4: attempt power cycle
Nov 16 17:59:57 traveller kernel: [ 1518.385740] usb 1-4: new full-speed USB device number 40 using xhci_hcd
Nov 16 17:59:57 traveller kernel: [ 1518.385953] usb 1-4: Device not responding to setup address.
Nov 16 17:59:57 traveller kernel: [ 1518.593905] usb 1-4: Device not responding to setup address.
Nov 16 17:59:57 traveller kernel: [ 1518.801705] usb 1-4: device not accepting address 40, error -71
Nov 16 17:59:58 traveller kernel: [ 1518.929714] usb 1-4: new full-speed USB device number 41 using xhci_hcd
Nov 16 17:59:58 traveller kernel: [ 1518.929949] usb 1-4: Device not responding to setup address.
Nov 16 17:59:58 traveller kernel: [ 1519.137955] usb 1-4: Device not responding to setup address.
Nov 16 17:59:58 traveller kernel: [ 1519.345707] usb 1-4: device not accepting address 41, error -71
Nov 16 17:59:58 traveller kernel: [ 1519.345866] usb usb1-port4: unable to enumerate USB device

Of course tried it out on different machines with the same result. There was a related PX4 thread where a new mission planner fixed it. And so I tried it on Windows but no luck there too.

Any idea?

I appreciate any feedback/suggestion.

Update: after having tried the 3rd Cube Orange which also didn’t work, I started to doubt the USB cable… And yes, it seems that this original ‘Cube cable’ was the issue. I tried a different original USB cable and that one is working ok. I guess I have damaged the cable in some way, although I did not expect this effect.

Cheers,
Raymond

24

This is regarding GPS NMEA messages not being read by Pixhawk v2.1 CUBE with PX4 stack .

My GPS module outputs GNGGA , GNGSA ,GPGSV , GQGSV , GAGSV , GBGSV , GNSVD,GNRMC , GNGST .
I am surprised not one of these messages are detected by Orange CUBE Px4 !

25

@sibujacob that’s not Cube specific, let’s follow up in Enabling GPS using NMEA - #3 by sibujacob

1 Like
26

Hi,
I am glad one developer is here to support the px4 forum…:slight_smile: …

27

Hi,

I am getting an error message of “Accel 1 clipping, not safe to fly” on cube orange with PX4 version 1.13.2 but when change the firmware to 1.11.0, Accel 1 clipping error doesn’t show up.

Is this an issue of the firmware?

28

Hi,
Are you saying here that the GPS works on Px4 v1.11.0 . I am currently on v1.12.3 .
What are you getting when you use the mavlink console with the command gps status . Does it give you both primary & secondary GPS readings .

29

That’s probably because accel clipping was not supported in v1.11. In any case, accel clipping means that the vibrations are too high and exceeding the measurable range of the accelerators. You need to check if anything of the Cube is loose (e.g. Cube loose on base board) and also check if any cables are inducing vibrations, or if propellers or other things are unbalanced causing vibrations.

30

There have been numerous improvements and bugfixes in v1.13.2, so I highly recommend to use that version over older ones, especially on hardware based on the STM32H7 like the CubeOrange.

1 Like
31

i am afraid that i will not be able to install the firmware properly through QGroundControl and the larger headache is the Herelink Radio Telemetry system which has a mind of its own. Currently the settings are satisfactory with my Quadcopter and i do not see major issues during flight.

PS:
Did the Px4 V.1.13.2 resolve the Mavlink console issue where the commands were not working through QGC.

32

Yes, it’s fixed in main but not released yet. It will be part of v1.13.3.

1 Like
33

Hi @JulianOes .
Thank you for replying so fast. Actually the Accel Clipping error started occurring after my quad experienced a drastic landing.
The Cube Orange is on my desk right now and the error is occurring while it is on my desk. I haven’t taken any flights after the crash. So there are no vibrations in my case.

1 Like
34

Oh, create a logfile while it is sitting on the desk and upload that to logs.px4.io and share it here.

You can do that by setting SDLOG_MODE to 2.

And maybe add some more topics to SDLOG_PROFILE, easiest using QGroundControl.

35

The accel clipping error has been resolved.

What I did was: -
I flashed v1.11.0 (it didn’t show any accel clipping error) and took a flight at altitude and position modes, the flights were very stable and no clipping occurred during the flight.
After the successful flight on v1.11.0, I reflashed Cube Orange with PX4 v1.13.2 and no accel clipping error occurred. I took a flight at altitude and potion modes, the flights were stable and no errors occurred.

I have taken a lot of flights since doing this and till now no error seems to have surfaced.

1 Like
36

@ Numair that is valuable feedback…!!

37

Ok, so it remains a mystery why the accel clipping warnings appeared. A well, at least the problem is solved for you :wink: .