since MacOS update from 12 to 13 USB to serial converter doesn't work anymore

It works fine on my M1 24" iMac. I even tried 2 different FTDI chips.

Here is the terminal session determining which file in \dev to use. Note that the first ls has two entries, while the second ls after I plugged in the FTDI shows three. The last line is the screen command used.

Here is the screen session with the FTDI serial device in loopback showing that I am transmitting and receiving.

One thing is that FTDI is clamping down on non-FTDI chips. It could be that the driver will only work with FTDI.

cu.Bluetooth-Incoming-Port is the only item in my drop list. On my old computer, which no longer works, I had this entry, plus one other, something like cu.usbserial-1141, which I would choose and it would work. I tried plugging the USB cord into both of my MBP USB-C slots, but the MBP doesn’t acknowledge anything plugged in, in either case.

Neither. Yet, when I plug in any other device (camera, Arduino, external backup disk), The USB works just fine. Could it be the Sprog device at the other end of the USB cable? Hey! So I just that Sprog device and unplugged it, then plugged it back in. Immediately, a dialog box popped up on my Mac asking me if I wanted to connect Sprog! I did, and all works just fine now, and I am able to choose cu.usbmodem1101. So problem solved! All I had to do was reboot the Sprog device. Thanks for all the help!

Does this help?

https://ftdichip.com/wp-content/uploads/2020/08/AN_134_FTDI_Drivers_Installation_Guide_for_MAC_OSX-1.pdf

"A VCP driver for most FTDI USB to serial converters is provided as part of the kernel in OS X 10.9 and

later. OS X loads this driver (AppleUSBFTDI.kext) when a device with standard FTDI vendor and product

identifiers is connected. To use FTDI’s own VCP instead, or to use D2XX programs, AppleUSBFTDI must

be disabled, unloaded or blocked, as follows."

I have the same issue, but without the resolution shown below. I downloaded and installed the FTDI driver. The installer reported a successful installation. Rebooted the M2 MacBook Pro. Still, no /dev/cu.* shows up except for Bluetooth. I followed all the suggestions mentioned here, but without the positive end-result. So, I'm still puzzled. I'm running the latest MacOS Ventura 13.0.1.

Well, I have already installed JMRI software on my new laptop to interface with my model trains.

The JMRI software fully works except there is no longer an available serial port for JMRI to communicate with the train hardware (at the far end of the USB cable).

Are you sure it is FTDI?

look here:

https://ftdichip.com/drivers/vcp-drivers/

And try the driver for Monterey. Nothing listed yet for Ventura, and the MacOs 11/12 drivers are listed as "Beta"

Did you try the drivers for Big Sur/Monterey? They might be universal or run under Rosetta.

While not FTDI, my USB to serial drivers for TI launchpads run just fine under M1 and Monterey.

I have heard no other complaints about this, but I will try with my iMac24 and a real FTDI chip over the weekend. I cannot yet put Ventura on my work MacBookPro.

Have you tried contacting FTDI?

Whatever driver that was in Monterey worked on an M1. I just tried it on my MacBookPro.

I will see about Ventura this weekend.