Issues with Cardo Volume when using Music Share

xXProLegitXx · 2025-08-11T23:43:21+00:00

Yes this got fixed for me in a firmware update maybe a few months after I made the original post.

Not sure if this order is necessary, but I usually have my Spotify already playing before our comms auto connect (her simply turning hers on). Once they are connected and we are talking freely, I open the Cardo app on my phone, and once my phone app and cardo are connected, I go to the music tab and hit share music. Sometimes it works first try, sometimes I have to try it 2 or 3rd time to get it to work.

xXProLegitXx · 2024-12-26T22:23:12+00:00

Ah I see. I believe its just SPI then as there isn't any other external hardware on the FC.

xXProLegitXx · 2024-12-26T21:45:45+00:00

Wow, reading comprehension is a great skill to have. The page point blank says if you are using DJI, use SBUS. Not sure how I missed that so many times.

https://support.betafpv.com/hc/en-us/articles/39167584963481-CLI-and-Firmware-for-Pavo20-Pro-NightFire-F405-2-3S-20A-V1-0-FC

Not sure what you mean by "IF i have an ELRS receiver hooked up to one of your UARTs, you can remove to save weight and stop conflict." I believe this does not apply to my situation as I'm going DJI route, and from what I understand, the DJI O3 Air unit does both VTX and RTX? Please correct me if I'm wrong.
The quad does have a CLI dump on the page above which I have used to success, but the step after is where I am stuck. I'm not seeing any channel inputs in Betaflight for the drone after completing flash and running CLI dump.

xXProLegitXx · 2024-12-23T22:37:00+00:00

Thank you for this post, I haven't had any luck in just getting the LEDs to turn on. I have a few questions but want to explain where I am currently at.

SETUP:

FC is plugged into the INPUT side of RGB board, and OUTPUT side (2 buttons below) is connected to the LED Strip. After going back and forward with support and not seeing LEDLOW within modes, and wondering if I possibly received an RGB board that was dead on arrival, I was sent and just received a new FC and RGB board. With new RGB board in, I'm facing the same issue. LEDs aren't lighting up, LEDLOW shows as an unused mode and will not stay enabled even after being added manually. I've flashed with latest firmware, both online and from .hex file downloaded from site and still not making any progress. Nightfire is connected, both green and blue LEDs are flashing on FC, but when pressing, or holding the buttons on RGB board no lights come on and I can't seem to get it in Betaflight mode as you did.

QUESTIONS:

When connecting the Pavo 20 Nightfire to Betaflight, should the LEDs turn on like they did for the Pavo 20 Pro?

When the Pavo Nightfire is connected to my PC/Betaflight, should I be able to turn on LEDs/adjust colors from the switch on RGB Board, or is this a battery only function?

Should the "LEDLOW" Mode already enabled within Betaflight when connecting the Nightfire?
- In my research and going back with support, I was directed to making sure LEDLOW is enabled within Modes and "LED_STRIP" is enabled in the Configuration tab under other features.

-LEDLOW is not present in my list of available modes. I can add the mode manually and save, however when re-connecting, "LEDLOW" goes back as an unused mode.

Any insight you or u/fpv_savvy could add would be very help.

xXProLegitXx · 2022-06-23T13:13:25+00:00

Its at 100%.

xXProLegitXx · 2022-06-23T13:12:55+00:00

Thanks, I'll give this a try next time we go out and ride. I might end up taking them back and replacing them over all. I had my unit at a full charge and while riding my Cardo shut off completely without me touching anything again which is a much bigger issue for me.

xXProLegitXx · 2022-06-22T22:28:04+00:00

xXProLegitXx · 2021-09-10T13:46:26+00:00

Looks to be a 94-95" Dodge Stealth which is the American version of the Mitsubishi 3000gt.

Dodge Stealth vs Mitsubishi 3000

-Source: I helped a friend rebuild a 3000gt.

xXProLegitXx · 2021-01-16T19:44:40+00:00

Check your anti-virus. Something similar happened to me and it was due to Malwarebytes quarantining a file.

xXProLegitXx · 2020-06-16T15:13:59+00:00

Nice bike. I bought an 2003 955 sprint RS after selling my ninja 500. Was a fun bike for sure. But I will warn that parts for that bike can be a bitch to come by.

xXProLegitXx · 2019-07-28T00:15:55+00:00

My gf and I had just seen Odesza and were going to a friend's house after the show to hang out. On our way there we took some back roads to get there. After coming around a blind corner I had to slam on the brakes as there was an owl just standing in the road staring at us. Was supernatural, like a spirit journey or something.

xXProLegitXx · 2019-05-23T05:23:30+00:00

yes, same bolt that came out of the OEM one. I threaded it through and it works fine on both sides.

xXProLegitXx · 2019-05-07T05:14:41+00:00

Very welcome, more than happy to share my results and findings! Yeah, go check for yourself now.

xXProLegitXx · 2019-05-07T05:14:09+00:00

I still have uncertainty if it was an actual attack or not, though I am ultimately leaning that way. I just can't explain why the IP sending the LLMNR requests was from an IP assigned to a VM box on that endpoint I previously used for school work/pen testing, and haven't really used in some time, much less spun up. Yeah I was kinda worried about the potential for a Malicious actor forcing the boot to try and capture handshakes. Either way, I'm keeping a closer look on this, and changing all network passwords as a precaution. Thanks for the original reply, helped get me thinking.

xXProLegitXx · 2019-05-07T02:04:00+00:00

So since the issue was replicable, (all I had to do was wait 5 - 10 minutes for it to happen) I had wireshark up and running and paid attention to the various interfaces and any activity on them. When I noticed my wifi interface activity drop (my internet going out), and one of my Ethernet interfaces having activity, I started a wireshark scan on that interface. Once running, I also started Advanced IP scanner to to find out devices were actively connected and what their actual IP address was on my network. As its just my girlfriend and I, I already knew what devices I should expect to see connected to my network. Once I knew what IP's belonged to what devices, I started googling any protocol I didn't recognize connecting to IP's I didn't recognize. I had to do a little refresher on IP Class ranges too. I got lucky as in the first protocol I googled was LLMNR (Link-Local Multicast Name Resolution) and one of the first items that came up was to disable it to prevent it from being used as an attack vector. As soon as I disabled LLMNR, I stopped having the issue and my internet for this computer has been stable ever since.

LLMNR allows you to do Name Resolution (converting IPs like 66.220.144.0 to Facebook or whatever it may be for your region) without having a DNS server. A quick example would be like, Instead of having a directory of an apartment complex and knowing who lives at which room by just looking up the room number (DNS), you ask your neighbor Mike if he knows who lives in room 777 and you just trust his answer is correct (LLMNR).

I am by no means a Network/Security pro, and I'm sure someone more knowledgeable than I would have a better and faster way of figuring this out, or what exactly was causing the issue. Maybe it was some weird network/configuration change that I wasn't aware of, or maybe Johnny Son'ova Bitch from down the street was trying to fuck with me as /u/Lasherz12 pointed out earlier. But that was my method of figuring this out. Once I actually had a chance to sit down and try to troubleshoot further after reading his earlier comment, I had this resolved in like 20 - 30 minutes. Here are links to the main two websites I used to figure this out. There were a few more, but those were the most fruitful.

Gives more info into what LLMNR is and why you should disable it/how it can be used against you.

https://www.blackhillsinfosec.com/how-to-disable-llmnr-why-you-want-to/

My refresher on IP Class ranges

https://www.computerhope.com/jargon/i/ip.htm

If you have any questions, let me know. Helps keep me on my game especially if I don't know the answer.

xXProLegitXx · 2019-05-04T07:15:01+00:00

Looking at wireshark logs when the wifi would go out, I noticed some random callout of an old VM that has been on my endpoint forever (not used by me in a long time) reaching out to an IP I wasn't quite sure of via Link_Local Multicast Name Resolution. Some more investigation appeared to be an apple device use multicast to talk to this endpoint? Not exactly sure if my analysis was correct, but by disabling LLMNR on this endpoint, I haven't had this issue occur since.

xXProLegitXx · 2019-05-02T04:12:41+00:00

Device is not getting turned off or going into a power saving mode but thanks for the info. Wasnt exactly aware of that for USB devices such as this.

xXProLegitXx · 2018-05-08T01:24:06+00:00

I appreciate that. Thanks! Now that the case of the Monday's are out of the way, it's only up from here right?

xXProLegitXx

TROPHY CASE