USB-C support for Mac

[jimmyarturopaiz]

Once upon a time, you could use a Radiomaster TX16S, running Edge TX, via USB (although, only via a USB-A to USB-C adapter) on a Mac, which allowed you to use the controller as a joystick for training in the Liftoff app, and also allowed you to connect to Companion and Buddy.

This does not exist anymore. Edge TX controllers cannot connect to the Mac anymore, which makes an Edge TX controller a virtual brick. I hope I am explaining this correctly, and as I'm sure there are others who feel me, I hope this can be taken up as real topic of interest towards resolution.

Not being able to use Companion, Buddy, or the Joystick option—to put it mildly—makes Edge TX all but useless, which it's obviously not. I hope greater minds can collaborate to tackle this huge disappointment.

[pfeerick]

That would be news to at least three users of EdgeTX, as they all use MacOS and are developers 😆

In other words, I would suggest something has changed for you. i.e. between it "working" and now "This does not exist anymore. ", have you changed version of MacOS? USB cables? Have you tried with another computer in case it is the USB port on the handset that is faulty? Double checked the connector both ways? Tried with a different USB-C to USB-A hub/adapter?

And just as a friendly reminder - you need to be used the TOP usb port for the computer link... bottom USB port is only for charging.
;)

[jimmyarturopaiz]

I've scoured the net, the discussion boards, the tutorials, and even prayed. Despite all the basic/common suggestions you mentioned and others, there's no logical conclusion to the dilemma. With the volume of experiences similar to mine across the web, and across time, it seems to me that there's something fundamentally inoperable within EdgeTX. Maybe I'll throw away my Mac and get a Windows PC just to use EdgeTX Companion and Buddy and Joystick mode. Or, maybe there's a way to identify why EdgeTX can't communicate with Mac ports in the modern age, without all the runaround. Maybe there's a way to just make it work like a USB port should work. If anyone is working on this, I would love to help in anyway I can to find a solution.

[philmoz]

My TX16S (and other radios) all work fine on both Intel and Arm based Macs.

On the Radio Setup page what is the 'USB mode' setting? If it is set to 'Storage' or 'Serial' change it to 'Ask'.
Have you tried changing USB cables?
Have you tried another computer?
If you are running Sonoma or later on an Arm based Mac then you might have denied the radio permission to connect. Check the 'Allow accessories to connect' setting in Privacy & Security. If it's set to 'Ask for New Accessories' try changing it to 'Ask Every Time' (or 'Always') and reconnect the radio.

[jimmyarturopaiz]

Thank you, philmoz. I tried your suggestion, but that option does not show. I looked up what you mean, and know what it looks like when it appears, but I don't have it.

Please see the screenshot.

I'm currently running 15.2 (24C101) on a Mac Mini - Apple M2 Pro

[jimmyarturopaiz]

I just found out that the option you mentioned only serves mobile macs, not the mac mini.

[inventor7777]

My TX16s and MT12 work fine with my MacBook Air M1. Have you tried using the cable that came with the radio? (And a good adapter such as Syntech?)

[inventor7777]

I ask that because the only cable that works with my tx16 is the OEM cable and a select few A-to-C cables.

[pfeerick]

I ask that because the only cable that works with my tx16 is the OEM cable and a select few A-to-C cables.

Some "cheap" cables are charge only, and don't have all the wires/connections. It should work with any fully compliant USB A-to-C cable...

From that article, the "Allow accessories to connect" option seems to be something that is new/specific to hardware that has this enhanced security mode, so if the option is no there, it is simply because it does not apply, and you won't need to worry about it blocking stuff.

To rule out software configuration on handset side, you could try entering the bootloader (hold the horizontal trims inwards when powering on the handset) and connecting the USB then. It should detect the connection, and the SD card content should be viewable on the Mac, if everything is working.

Another simple test you can do to check if it is the USB cable and/or the connector on the handset itself rather than the Mac (as I am assuming you have actually tried on another computer to rule out the Mac as the issue here) is to simply plug the top USB into a power bank or charger... as the test of "is the handset plugged into the computer" used by the firmware is a simple a test of "is power present at the connector?"... so if you plug the top USB in, and it doesn't ask what mode to use (when running the firmware if configured to ask) or say "USB connected" (when at the bootloader)... that would suggest either your cable is not supplying power, or the USB connector on the handset itself is faulty/perhaps the internal connector is loose.

[inventor7777]

@pfeerick Yes, you’re right. I suppose what I meant is that they don’t work well with USB-C only cables and ports (on my dock which has both C and A ports, only the A ports work unless you use a C-to-A converter.

I’m assuming @jimmyarturopaiz ‘s problem lies in cable and adapter choice, or even in radio settings. It wouldn’t make any sense to block all connections with no popup.

[jimmyarturopaiz]

Thank you all for all your help and the time you spent working through this with me. Alas, there is no resolution and I'll call it a dead discussion at this point. As for the cables, adapters, etc, yes, yes, yes, I've tried it all. It's very expensive to search for solutions to what, in 2025, should just work. After scouring the net, I know that I am not alone in this and I hope one day a solution can be implemented by the experts working in the background. Again, thank you all so much.

[pfeerick]

I suppose what I meant is that they don’t work well with USB-C only cables and ports

Yeah, I've always thought that was a strange one... And wonder if it is less than it doesn't work. AT ALL, but if the CC lines are property configured, so the connector simply doesn't work one way. At least, IIRC, the charger on the TX16S MK2 doesn't work in one plug orientation with one of my USB-PD chargers ... At least I don't have to do the three-attempt USB plug dance to get it plugged in 😂😂😂

in 2025, should just work

I hear you on that one. But if I had a dollar for everytime someone said that !!! 😂

I hope one day a solution can be implemented

That can only really happen if as inventor7777 pointed out some missing information provided and checks are done. i.e. If you actually have a hardware issue and are blaming MacOS, EdgeTX, USB compatibility etc .. there is no way we can fix that. 🤭 Once foundational hardware issues can be conclusively ruled out, there is then hope for a software fix.

[jimmyarturopaiz]

Thank you all for all your help and the time you spent working through this with me. Alas, there is no resolution and I'll call it a dead discussion at this point. As for the cables, adapters, etc, yes, yes, yes, I've tried it all. It's very expensive to search for solutions to what, in 2025, should just work. After scouring the net, I know that I am not alone in this and I hope one day a solution can be implemented by the experts working in the background. Again, thank you all so much.

[inventor7777]

How can EdgeTX solve this “issue” if you don’t give them details of what you’ve actually tried? You haven’t told us what cable you’re using, if the port on the radio actually works, or even what your USB settings on the radio are. Sorry if I sound annoyed, but I’m just not understanding why it works on my MacBook Air but not a mini, which are very similar in how they work, and the details you’re giving aren’t very specific.

Also, are you using the usb-a ports on the mini or the usb c ports?

[jimmyarturopaiz]

Guys! It works again, after returning to "Providence" v2.9.4. I haven't tried any other version out of fear of losing connectivity, but not only does Companion read my radio, so does the Mac sidebar file manager, and Liftoff works again. I assume then, that there's a code issue somewhere along the line, but that's outside my wheelhouse.