that should show you the groups (-G) you are in with the names (-n) rather than numbers. You would need to be in the dialout group to use the usb serial.
you can add yourself to that group with
sudo adduser bob dialout
once you do that, you shouldn’t have to change permissions etc.
Not an expert at Linux, but some thoughts / notes…
1 ) I take it this particular USB converter has tested out OK on Windows or Mac.
2 ) [quote=216194:@Bob Keeney][ 79.894335] usb 2-2.2: pl2303 converter now attached to ttyUSB0
[ 2026.596446] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
[ 2043.653543] usb 2-2.2: pl2303 converter now attached to ttyUSB0
[ 3078.017310] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
[ 3089.347848] usb 2-2.2: pl2303 converter now attached to ttyUSB0[/quote]
I’m guessing that these mean you unplugged and replugged the device a couple of times - if not it’s strange.
These don’t look great : I have tried Googling, but no luck so far.
if it exists in /dev then Linux at least thinks it has - the following command will show a line if it has…
ls -l /dev/ttyUSB0 … ( The l characters are lowercase L )
If it does not, then the driver is not loading properly
I don’t think it is a privilege issue as If I look at serial ports with Xojo I still see them OK as a normal user, but need privilege to actually open them.
Privilege issue is typically solved by adding the user to the dialout group - ( or running Xojo apps with root privileges ).
you can test if it works using the program ‘screen’
screen /dev/ttyUSB0 9600
should open a terminal and connect it. if there is nothing connected to the serial port, then when you type you should see nothing returned.
if you then connect pin 2 to pin 3 (anything metal will do, like the end of a screwdriver, or a biro ) you should see what you type on the screen, this proves that what goes out of the tx pin, is received at the rx pin. it also proves the serialport is working and the driver is good.
Revisiting this (now that I have time). I do get messages if I send them to screen.
When I create a very small test project to work with serial I get an Access Denied Error when I attempt to open the serial port through the Xojo application. Changing the Permissions on the Port doesn’t change anything.
Actually, this isn’t on the Pi, it’s Linux Mint and doing this through VMWare. The client has a real computer to work with.
Using sudo usermod -a -G dial out pi with the appropriate username doesn’t appear to do anything (though no errors). And I’m not getting any messages consumed by the Xojo app.
The customer on their Dell laptops can’t get any of the data either so I don’t think VMWare has anything to do with this issue. Plus, using screen I can see the messages coming through on the serial port. What’s not happening is that the Xojo application can’t read the serial port data.
So there’s some level of disconnect between the OS and the Xojo application.
Update on this. It looks like there might be a bug in Linux using the DTR line in Serial. <https://xojo.com/issue/41513>
The customer is using a Fiber to RS232 converter at the end of the USB to Serial converter (yeah, lots of converters) and is using the DTR line power it. Works on all versions of Mac and Windows tested but not in Linux.