#IP OVER SERIAL MACOS BLUETOOTH#
Adding bluetooth to the scenario is just one more thing to fail, wireless is hardly reliable, and troubleshooting bluetooth drops is a nightmare.
I don't know why people want to buy that overpriced AirConsole hipster crap anyway. I bought one of these in 2015 and back in 2019 and they have authentic chips:Īnd finally while I don't have one, I've been told these newer Sabrent adapters have real FTDI chips and work well: I have a ton of these that I've bought across almost 10 years now: I can vouch for these Techtoo multi-port adapters. If you use multiple adapters this is a huge upside. On linux you can use this to map a specific adapter to a specific /dev/ttyX device. Using an A-to-C adapter is easy, going from C-to-A is more complicated, there's no technical up-side to going native USB C, and there's a lot less inventory to choose from if you decide to go with a native C plug adapter.Īnd, while I'm thinking about it: An advantage of FTDI adapters is they all have a unique serial number. Spending more money won't necessarily get you the good stuff either.Īlso, I would advise you to go with a classic USB A connector rather than USB C. Some of the clones are really really good, and some are really garbage. The only reliable chip for MacOS is an FTDI adapter. It's the chip inside that matters, so look past branding and don't buy Tripp Lite (don't even ask me to explain, just don't). There's a bunch of different Serial-to-USB chips out there: ch341 (sub-garbage), pl2303 (pretty good), FDTI (great but complicated history), cp2102(newer, good, has quirks), and there's a few more. This is subject matter I know a lot about because I do both network engineering and embedded device dev, and I've had to do it off MacOS in the past.
0 kommentar(er)
