-->
Page 1 of 2

Opening Serial Monitor changes port

PostPosted: Fri Feb 09, 2018 5:37 pm
by liderbug
Running 1.8.5 NB on a RasPi3
ssh -X me@raspi

So the Serial Monitor wasn't a problem until the last couple of days ago

I plug in my proto board with a 8266
From the command line I run "arduino"
up comes the last sketch(or2)
> ls /dev/ttyUSB*
I get ttyUSB0
Tools->Port sel usb0
click on mag-glass and up pops the Serial Monitor
Double check Tools and "Port" is blank
> ls /dev/tty...
USB1 ah...
Tools->Port usb1
Sketch->Serial Monitor
error: ttyUSB1 is not avail
and Port is empty - again
insanity is doing the same...........

Yes - Serial.begin (9600);
Yes - I am a member of dialout

I'm in twisty little passages all alike....

Re: Opening Serial Monitor changes port

PostPosted: Sat Feb 10, 2018 1:09 am
by lethe
Your USB to serial chip is probably resetting (check the output of "dmesg" to confirm).

Most likely causes for such an issue are faulty USB cables or you are drawing too much power from the USB bus, causing the chip to brown out.

Re: Opening Serial Monitor changes port

PostPosted: Sat Feb 10, 2018 12:59 pm
by liderbug
OK, ... Tools->Port ttyUSB0
Tools (popup) and yup, USB0
Click on SerMon icon and dmesg gives this
Tools (popup) and Port is blank
Line 168032 "usb discon..." dev# increments every time I do the above.
It's as if the
void Bring_Up_Ser_Mon()
{
discon_current_port ();
.....
}

PS I seem to remember something about a file in /etc/udev ...????


Code: Select all 
[18042.168032] usb 1-1.5: USB disconnect, device number 31
[18042.168378] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[18042.168411] ftdi_sio 1-1.5:1.0: device disconnected
[18042.462613] usb 1-1.5: new full-speed USB device number 32 using dwc_otg
[18042.620084] usb 1-1.5: New USB device found, idVendor=0403, idProduct=6001
[18042.620094] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[18042.620098] usb 1-1.5: Product: FT232R USB UART
[18042.620102] usb 1-1.5: Manufacturer: FTDI
[18042.620106] usb 1-1.5: SerialNumber: 00000000
[18042.628107] ftdi_sio 1-1.5:1.0: FTDI USB Serial Device converter detected
[18042.628216] usb 1-1.5: Detected FT232RL
[18042.628959] usb 1-1.5: FTDI USB Serial Device converter now attached to ttyUSB1
[18042.936022] usb 1-1.5: USB disconnect, device number 32
[18042.936867] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[18042.936911] ftdi_sio 1-1.5:1.0: device disconnected
[18043.232705] usb 1-1.5: new full-speed USB device number 33 using dwc_otg
[18043.391354] usb 1-1.5: New USB device found, idVendor=0403, idProduct=6001
[18043.391369] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[18043.391378] usb 1-1.5: Product: FT232R USB UART
[18043.391385] usb 1-1.5: Manufacturer: FTDI
[18043.391393] usb 1-1.5: SerialNumber: 00000000
[18043.399819] ftdi_sio 1-1.5:1.0: FTDI USB Serial Device converter detected
[18043.400009] usb 1-1.5: Detected FT232RL
[18043.401041] usb 1-1.5: FTDI USB Serial Device converter now attached to ttyUSB1
[18047.544010] usb 1-1.5: USB disconnect, device number 33
[18047.544368] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[18047.544401] ftdi_sio 1-1.5:1.0: device disconnected
[18047.842615] usb 1-1.5: new full-speed USB device number 34 using dwc_otg
[18048.000229] usb 1-1.5: New USB device found, idVendor=0403, idProduct=6001
[18048.000245] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[18048.000253] usb 1-1.5: Product: FT232R USB UART
[18048.000261] usb 1-1.5: Manufacturer: FTDI
[18048.000269] usb 1-1.5: SerialNumber: 00000000
[18048.008747] ftdi_sio 1-1.5:1.0: FTDI USB Serial Device converter detected
[18048.008952] usb 1-1.5: Detected FT232RL
[18048.009820] usb 1-1.5: FTDI USB Serial Device converter now attached to ttyUSB0

Re: Opening Serial Monitor changes port

PostPosted: Sat Feb 10, 2018 10:32 pm
by liderbug
More parts of the puzzle. I switched over to a NodeMCU 1.0 and I have Serial Monitor.
I was using a FTD1232 with a Generic 8266-01 and the problem I'm having.
Driver??? But it was working. I did do an apt-get update.
<sigh>