Serial connections with baudrate >9600 not working

[Brent Sergent]

I'm running iTerm2 ver 3.0.4 on OSX 10.11.5 (El Capitano). iTerm2 worked well in Yosemite with higher baud rates over 9600.

Serial Baud rate @115200 specifically doesn't work and provides garbled output similar to a speed mismatch. As proof of setup I've installed the app 'Serial' for mac's and confirm both drivers and usb serial connector work fine at 115200 baud.

iTerm2 command = [screen /dev/tty.usbserial-FTGSYDCB -s 115200]

Has anyone experienced this issue and or have a fix.

Thanks

[George Nachman]

I think this is unlikely to be an iTerm2 issue. Sorry I don't have anything more useful to contribute.

--
You received this message because you are subscribed to the Google Groups "iterm2-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iterm2-discus...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Brent Sergent]

Im not sure why you would post this comment without offering an logical reason for your comment? As explained the serial program was able to successfully connect at 11500 baud.

The issue logically would be linked to how iterm2 interacts with OS X, via serial usb. Has anyone had this issue with El Capitan?

You received this message because you are subscribed to a topic in the Google Groups "iterm2-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/iterm2-discuss/ZO1kHFWRXAQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to iterm2-discus...@googlegroups.com.

[CSS]

I’m not a fan of using “screen” as a terminal program, it provides varied results.

Try with an actual serial terminal program like minicom or picocom.

Charles

[George Nachman]

iTerm2 does not interact with the serial port. It is just a vehicle to display the output of the command you ran, which is screen. Now, it's certainly possible that screen broke in 10.11. I think CSS's advice above is good.

[Shankar Unni]

Probably because iterm itself isn’t doing any serial communication (or communication of any sort)?

You’d usually be using some other program like screen, minicom or picocom (or ssh or telnet or ..) to do the communication, and executing that as the command in iterm.  You should be looking at whatever your shell command is.

And as a data point, I’m on 10.11.5, and I routinely use both screen and picocom to connect to our test devices at 115200 baud (in an iTerm 3.0.5 window), with absolutely no problems in the serial communication.