›

repetier server not recognizing usb

jaykswanjaykswan
in Repetier-Server
I am trying to setup repetier server on an ubuntu laptop. the printer that I'm having troubles with is a longer lk4 that I am connecting via serial port.  my issue is that repetier does not recognize the port that my printer is connected to. Ive tried dev/tty.USB0,    dev/tty0,  dev/tty, and none of them works.  when I unplug and plug in the usb it shows that the printer is conncted to  /dev/serial/by-path/pci-0000:00:15.0-usb-0:2:1.0-port0. but only for a split second (barely long enough for me to click on it) and then it dissapears.   what in the world is going on? Ive tried installing ubuntu additional drivers, but still not working.   also the dropdown list of devices/ports gives me like over a hundred options from dev/tty  all the way up to dev/tty63. then from dev/ttyS0 up to dev/ttyS31.  it also give me dev/ttyprintk,    dev/pts/ptmx,      dev/ptx/0      and virtual/delta    and virtua;/cartesian.    Ive tried many of these and none work.

Comments

  • Repetier_SupportRepetier_Support
    Hello. 
    Please select the devices beginning with /dev/serial/by-id or /dev/serial/by-path.
    Make sure that you always attach the printer to the same port when using the /dev/serial/by-path method

    For your disappearing issues: Please make sure that the baud rate is correct. If it is, could you show us the system log and the server log? 
  • jaykswanjaykswan
    unfortunatly the sys log is too large to upload the entirety. here is a bit about the usb device.

     Jul  1 17:41:34 pi-server kernel: [  177.888041] usb 1-5: new full-speed USB device number 4 using xhci_hcd
    Jul  1 17:41:34 pi-server kernel: [  178.068520] usb 1-5: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
    Jul  1 17:41:34 pi-server kernel: [  178.068549] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    Jul  1 17:41:34 pi-server kernel: [  178.068552] usb 1-5: Product: CP2102 USB to UART Bridge Controller
    Jul  1 17:41:34 pi-server kernel: [  178.068554] usb 1-5: Manufacturer: Silicon Labs
    Jul  1 17:41:34 pi-server kernel: [  178.068557] usb 1-5: SerialNumber: 0001
    Jul  1 17:41:34 pi-server mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:15.0/usb1/1-5"
    Jul  1 17:41:34 pi-server mtp-probe: bus: 1, device: 4 was not an MTP device
    Jul  1 17:41:34 pi-server snapd[508]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
    Jul  1 17:41:34 pi-server kernel: [  178.240069] usbcore: registered new interface driver usbserial_generic
    Jul  1 17:41:34 pi-server kernel: [  178.241481] usbserial: USB Serial support registered for generic
    Jul  1 17:41:34 pi-server systemd[1]: Starting Braille Device Support...
    Jul  1 17:41:34 pi-server kernel: [  178.251876] usbcore: registered new interface driver cp210x
    Jul  1 17:41:34 pi-server kernel: [  178.253046] usbserial: USB Serial support registered for cp210x
    Jul  1 17:41:34 pi-server kernel: [  178.253366] cp210x 1-5:1.0: cp210x converter detected
    Jul  1 17:41:34 pi-server kernel: [  178.257364] usb 1-5: cp210x converter now attached to ttyUSB0
    Jul  1 17:41:34 pi-server mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:15.0/usb1/1-5"
    Jul  1 17:41:34 pi-server mtp-probe: bus: 1, device: 4 was not an MTP device
    Jul  1 17:41:34 pi-server brltty[4844]: BRLTTY 6.4 rev BRLTTY-6.4 [https://brltty.app/]
    Jul  1 17:41:34 pi-server brltty[4844]: BRLTTY 6.4 rev BRLTTY-6.4 [https://brltty.app/]
    Jul  1 17:41:34 pi-server brltty[4844]: executing as the invoking user: root
    Jul  1 17:41:34 pi-server brltty[4844]: brltty: executing as the invoking user: root
    Jul  1 17:41:34 pi-server snapd[508]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
    Jul  1 17:41:34 pi-server snapd[508]: hotplug.go:199: hotplug device add event ignored, enable experimental.hotplug
    Jul  1 17:41:34 pi-server kernel: [  178.524733] input: PC Speaker as /devices/platform/pcspkr/input/input20
    Jul  1 17:41:35 pi-server brltty[4844]: CLDR open error: No such file or directory: /usr/share/unicode/cldr/common/annotations/en.xml
    Jul  1 17:41:35 pi-server brltty[4844]: brltty: CLDR open error: No such file or directory: /usr/share/unicode/cldr/common/annotations/en.xml
    Jul  1 17:41:35 pi-server brltty[4844]: possible cause: the package that defines the CLDR annotations directory is not installed
    Jul  1 17:41:35 pi-server brltty[4844]: brltty: possible cause: the package that defines the CLDR annotations directory is not installed
    Jul  1 17:41:35 pi-server brltty[4844]: emoji substitutiion won't be performed
    Jul  1 17:41:35 pi-server brltty[4844]: brltty: emoji substitutiion won't be performed
    Jul  1 17:41:35 pi-server brltty[4844]: BrlAPI Server: release 0.8.3
    Jul  1 17:41:35 pi-server brltty[4844]: brltty: BrlAPI Server: release 0.8.3
    Jul  1 17:41:35 pi-server systemd[1]: Started Braille Device Support.
    Jul  1 17:41:35 pi-server kernel: [  179.113323] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input21
    Jul  1 17:41:35 pi-server brltty[4844]: Linux Screen Driver:
    Jul  1 17:41:35 pi-server brltty[4844]: brltty: Linux Screen Driver:
    Jul  1 17:41:35 pi-server brltty[4844]: USB configuration set error 16: Device or resource busy
    Jul  1 17:41:35 pi-server brltty[4844]: brltty: USB configuration set error 16: Device or resource busy
    Jul  1 17:41:35 pi-server brltty[4844]: USB interface in use: 0 (cp210x)
    Jul  1 17:41:35 pi-server brltty[4844]: brltty: USB interface in use: 0 (cp210x)
    Jul  1 17:41:35 pi-server kernel: [  179.308314] usb 1-5: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1
    Jul  1 17:41:35 pi-server kernel: [  179.309805] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
    Jul  1 17:41:35 pi-server kernel: [  179.309845] cp210x 1-5:1.0: device disconnected
    Jul  1 17:41:35 pi-server ModemManager[611]: <info>  [base-manager] port ttyUSB0 released by device '/sys/devices/pci0000:00/0000:00:15.0/usb1/1-5'
  • jaykswanjaykswan
    here is the server debugging log.

    [01.07.2022 17:54:04] : error fetchTextFromWeb:DNS error: Temporary DNS error while resolving: download.repetier-server.com
    [01.07.2022 18:56:01] : error: Reading serial conection failed: End of file. Closing connection.
    [01.07.2022 18:57:01] : error: Reading serial conection failed: End of file. Closing connection.
    [01.07.2022 18:57:16] : error: Reading serial conection failed: End of file. Closing connection.
    [01.07.2022 18:58:06] : error: Reading serial conection failed: End of file. Closing connection.
    [01.07.2022 18:58:06] : error: Reading serial conection failed: End of file. Closing connection.

  • RepetierRepetier
    Jul  1 17:41:34 pi-server kernel: [  178.257364] usb 1-5: cp210x converter now attached to ttyUSB0

    So device name is /dev/ttyUSB0

    Jul  1 17:41:35 pi-server ModemManager[611]: <info>  [base-manager] port ttyUSB0 released by device '/sys/devices/pci0000:00/0000:00:15.0/usb1/1-5'

    You have ModemManager installed. If you have no mobile connector you should remove it. It opens every new serial port preventing server from succeeding when a port appears. Will take several retries at bootup to make server start connection.

    Your other problem seems to be brltty which seems to think your printer is a console and tries to connect:
    Jul  1 17:41:35 pi-server kernel: [  179.308314] usb 1-5: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1
    Jul  1 17:41:35 pi-server kernel: [  179.309805] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
    Jul  1 17:41:35 pi-server kernel: [  179.309845] cp210x 1-5:1.0: device disconnected

    Maybe they are connected. But from what I see they interfere with printer serial port.

    [01.07.2022 18:57:01] : error: Reading serial conection failed: End of file. Closing connection.

    Means linux closed port. Answer is most likely in syslog as you already showed 2 apps interfering here. So stop them and see if it gets better. Best you run 
    tail -f /var/log/syslog
    in a parallel console to see the effects immediately.
Sign In or Register to comment.