Greetings all.
I was following the schematic here: http://sodoityourself.com/max232-serial-level-converter/
Checking with my OLS logic analyzer, I can confirm that the arduino is firing out serial data, and after going through the MAX232, the data is inverted. Now I think this is what's meant to happen, however, any program (using Linux by the way) such as Minicom or Kontrollerlab's serial monitor or even the Arduino serial monitor just displays gibberish.
I've checked my wiring numerous times and can't see any issues, I'm completely stumped with this. The only thing I can think of is that the USB to Serial cable I'm using might already have a MAX232 or equivalent chip inside it. Haven't been able to check the circuit as 1. It has some weird rubber coating on the plug and 2. The rubber is transparent and it looks like a black blog is hiding the chip.
Any ideas folks?So I have Mint17 on a laptop at work and I use it with a Prolific usb-serial adapter to access network equipment using minicom. Works great- just plug and play.
However, I have a laptop at home that when I plug in a Prolific usb-serial adapter.... nothing happens. The output of 'lsusb' doesn't show the device, and 'dmesg' doesn't show anything being connected. Thru much trial and error, I discovered that if I do a 'sudo lusb -v', the adapter is somehow detected. After running it one time with a sudo, it then shows up under the non-sudo lsusb and it also shows up under dmesg as being connected, and finally, ttyUSB0 also shows up- which is ultimately what I'm after.
Both installs are pretty much the same, my user is a member of dialout on both. Whats the difference? Why does it work without intervention on one laptop, but require 'sudo lsusb -v' to get detected on the other? I thought lsusb just reported on connected equipment- is it somehow also forcing detection when I run it as 'sudo lsusb -v'?. At one point, I just assumed I had screwed up the permissions somehow on my home laptop, so I wiped it and installed Mint 17.1- and the behavior was no different!
Has anyone any experience with USB to serial cables and MAX232 chips? I was attempting to make a simple serial box for talking to various black boxes with serial ports.
I have a USB to Serial port adaptor, Prolific Technology, Inc. PL2303 Serial Port which works on ubuntu 10.04, and win xp, win7 machines. However, I have problems with it on Ubuntu 13.10 and 14.04 LTS. PL-2303 HXD USB to RS-232 Cable Prolific PL-2303 HXD chipset USB to serial converter cable, compatible with Windows 8 & Windows 10. Type A male USB to 9 pin male serial connector.
I was following the schematic here: http://sodoityourself.com/max232-serial-level-converter/
Checking with my OLS logic analyzer, I can confirm that the arduino is firing out serial data, and after going through the MAX232, the data is inverted. Now I think this is what's meant to happen, however, any program (using Linux by the way) such as Minicom or Kontrollerlab's serial monitor or even the Arduino serial monitor just displays gibberish.
I've checked my wiring numerous times and can't see any issues, I'm completely stumped with this. The only thing I can think of is that the USB to Serial cable I'm using might already have a MAX232 or equivalent chip inside it. Haven't been able to check the circuit as 1. It has some weird rubber coating on the plug and 2. The rubber is transparent and it looks like a black blog is hiding the chip.
Any ideas folks?So I have Mint17 on a laptop at work and I use it with a Prolific usb-serial adapter to access network equipment using minicom. Works great- just plug and play.
However, I have a laptop at home that when I plug in a Prolific usb-serial adapter.... nothing happens. The output of 'lsusb' doesn't show the device, and 'dmesg' doesn't show anything being connected. Thru much trial and error, I discovered that if I do a 'sudo lusb -v', the adapter is somehow detected. After running it one time with a sudo, it then shows up under the non-sudo lsusb and it also shows up under dmesg as being connected, and finally, ttyUSB0 also shows up- which is ultimately what I'm after.
Both installs are pretty much the same, my user is a member of dialout on both. Whats the difference? Why does it work without intervention on one laptop, but require 'sudo lsusb -v' to get detected on the other? I thought lsusb just reported on connected equipment- is it somehow also forcing detection when I run it as 'sudo lsusb -v'?. At one point, I just assumed I had screwed up the permissions somehow on my home laptop, so I wiped it and installed Mint 17.1- and the behavior was no different!
Any help?