Tronxy X5SA 400 connection problems

Good day.
I just started 3D printing and invested money in a Tronxy X5SA 400 (which has no wireless but it has USB). I am trying to use Repetier Server to connect to it but it rarely connects (like after many plugging and unplugging, or restarting) and even if it connects, it is for short while or it connects but it doesn't communicate anything from it.
Serial connection shows in device manager as CH340 (COM3) and I tried using as firmware all of them and tried using automatic Baud Rate and giving it manual as 115200. The RTS & DTR are from Low to High.

In the short moments of connecting (but it did not communicate anything), I attach this log:

Mesg:17:02:59.078: Connection started
Mesg:17:02:59.078: Printer reset requested false
Mesg:17:02:59.079: Dtr: false Rts: false
Mesg:17:02:59.107: Dtr: true Rts: true
Recv:17:03:02.108: Send init commands because we had no signal from a reset, assuming reset not available.
Recv:17:03:02.203: Connection verified by:ok N:1
Mesg:17:03:48.197: Warning: Communication timeout - resetting communication buffer.
Mesg:17:03:48.197: Connection status: Buffered:13, Manual Commands: 7, Job Commands: 0
Mesg:17:03:48.197: Buffer used:13 Enforced free byte:0 lines stored:1
Mesg:17:04:19.208: Warning: Communication timeout - resetting communication buffer.
Mesg:17:04:19.208: Connection status: Buffered:11, Manual Commands: 7, Job Commands: 0
Mesg:17:04:19.208: Buffer used:11 Enforced free byte:0 lines stored:1
Mesg:17:04:50.216: Warning: Communication timeout - resetting communication buffer.
Mesg:17:04:50.216: Connection status: Buffered:11, Manual Commands: 7, Job Commands: 0
Mesg:17:04:50.216: Buffer used:11 Enforced free byte:0 lines stored:1
Mesg:17:04:50.216: Warning: Too many timeouts without response - disabling timeout message!
Mesg:17:18:47.451: Connection closed by os.
Mesg:19:13:19.077: Connection started
Mesg:19:13:19.077: Printer reset requested false
Mesg:19:13:19.078: Dtr: false Rts: false
Mesg:19:13:19.106: Dtr: true Rts: true
Recv:19:13:22.116: Send init commands because we had no signal from a reset, assuming reset not available.
Recv:19:13:22.120: Connection verified by:ok N:1
Mesg:19:13:53.156: Warning: Communication timeout - resetting communication buffer.
Mesg:19:13:53.156: Connection status: Buffered:13, Manual Commands: 7, Job Commands: 0
Mesg:19:13:53.156: Buffer used:13 Enforced free byte:0 lines stored:1
Mesg:19:14:24.162: Warning: Communication timeout - resetting communication buffer.
Mesg:19:14:24.162: Connection status: Buffered:11, Manual Commands: 7, Job Commands: 0
Mesg:19:14:24.162: Buffer used:11 Enforced free byte:0 lines stored:1
Mesg:19:14:55.177: Warning: Communication timeout - resetting communication buffer.
Mesg:19:14:55.177: Connection status: Buffered:11, Manual Commands: 7, Job Commands: 0
Mesg:19:14:55.177: Buffer used:11 Enforced free byte:0 lines stored:1
Mesg:19:14:55.177: Warning: Too many timeouts without response - disabling timeout message!
Mesg:19:57:17.845: Connection closed by os.

Is there any way to help me?

Comments

  • I have that printer my self and communication is no problem with these settings:
    Firmware: Chitu
    Ping-Pong: enabled
    Baud Rate:115200
    RTS and DTR: Low to High

  • edited April 9
    I changed the cable and the port. I tried using those settings too. In the console I get this:

    Mesg:14:59:53.353: Connection started
    Mesg:14:59:53.353: Printer reset requested false
    Mesg:14:59:53.354: Dtr: false Rts: false
    Mesg:14:59:53.383: Dtr: true Rts: true
    Recv:14:59:56.394: Send init commands because we had no signal from a reset, assuming reset not available.
    Mesg:15:01:32.746: Connection started
    Mesg:15:01:32.746: Printer reset requested false
    Mesg:15:01:32.749: Dtr: false Rts: false
    Mesg:15:01:32.776: Dtr: true Rts: true
    Recv:15:01:35.783: Send init commands because we had no signal from a reset, assuming reset not available.
    Mesg:15:02:25.375: Connection started
    Mesg:15:02:25.375: Printer reset requested false
    Mesg:15:02:25.376: Dtr: false Rts: false
    Mesg:15:02:25.405: Dtr: true Rts: true
    Recv:15:02:28.421: Send init commands because we had no signal from a reset, assuming reset not available.

    It keeps connecting and disconnecting. 
  • Just tested it and it looks like this:
    Mesg:17:39:01.661: Dtr: true Rts: true
    Mesg:17:39:01.663: Connection started
    Mesg:17:39:01.663: Printer reset requested false
    Mesg:17:39:01.663: Dtr: false Rts: false
    Mesg:17:39:01.683: Dtr: true Rts: true
    Recv:17:39:04.689: Send init commands because we had no signal from a reset, assuming reset not available.
    Recv:17:39:04.696: Connection verified by:ok N:1
    Mesg:17:39:04.730: ok CBD make it.Date:Nov 21 2019 Time:16:32:55
    Mesg:17:39:04.782: ok C: X:0.000000 Y:0.000000 Z:0.000000 E:0.000000
    Recv:17:39:28.584: //AP_MAC:
    Recv:17:39:28.585: //wifi init done!

    lsusb
    is showing device as
    Bus 001 Device 050: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter

    lsmod
    shows driver
    usbserial              40960  3 ch341

    is loaded. Port is
    /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0

    Just for comparison if you are using same driver.

  • I am on windows but trying to show the information of the port too

    Manufacturer z
    USB\VID_1A86&PID_7523\5&356B5377&0&7
    Port_#0007.Hub_#0002

    [Port7]  :  USB-SERIAL CH340


    Is Port User Connectable:         yes
    Is Port Debug Capable:            no
    Companion Port Number:            23
    Companion Hub Symbolic Link Name: USB#ROOT_HUB30#4&2720bdb3&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
    Protocols Supported:
     USB 1.1:                         yes
     USB 2.0:                         yes
     USB 3.0:                         no

    Device Power State:               PowerDeviceD0

           ---===>Device Information<===---
    English product name: "USB Serial"

    ConnectionStatus:                  
    Current Config Value:              0x01  -> Device Bus Speed: Full (is not SuperSpeed or higher capable)
    Device Address:                    0x27
    Open Pipes:                           3

              ===>Device Descriptor<===
    bLength:                           0x12
    bDescriptorType:                   0x01
    bcdUSB:                          0x0110
    bDeviceClass:                      0xFF  -> This is a Vendor Specific Device
    bDeviceSubClass:                   0x00
    bDeviceProtocol:                   0x00
    bMaxPacketSize0:                   0x08 = (8) Bytes
    idVendor:                        0x1A86 = Nanjing Qinherg Electronics Co., Ltd.
    idProduct:                       0x7523
    bcdDevice:                       0x0264
    iManufacturer:                     0x00
    iProduct:                          0x02
         English (United States)  "USB Serial"
    iSerialNumber:                     0x00
    bNumConfigurations:                0x01

              ---===>Open Pipes<===---

              ===>Endpoint Descriptor<===
    bLength:                           0x07
    bDescriptorType:                   0x05
    bEndpointAddress:                  0x82  -> Direction: IN - EndpointID: 2
    bmAttributes:                      0x02  -> Bulk Transfer Type
    wMaxPacketSize:                  0x0020 = 0x20 bytes
    bInterval:                         0x00

              ===>Endpoint Descriptor<===
    bLength:                           0x07
    bDescriptorType:                   0x05
    bEndpointAddress:                  0x02  -> Direction: OUT - EndpointID: 2
    bmAttributes:                      0x02  -> Bulk Transfer Type
    wMaxPacketSize:                  0x0020 = 0x20 bytes
    bInterval:                         0x00

              ===>Endpoint Descriptor<===
    bLength:                           0x07
    bDescriptorType:                   0x05
    bEndpointAddress:                  0x81  -> Direction: IN - EndpointID: 1
    bmAttributes:                      0x03  -> Interrupt Transfer Type
    wMaxPacketSize:                  0x0008 = 0x08 bytes
    bInterval:                         0x01

           ---===>Full Configuration Descriptor<===---

              ===>Configuration Descriptor<===
    bLength:                           0x09
    bDescriptorType:                   0x02
    wTotalLength:                    0x0027  -> Validated
    bNumInterfaces:                    0x01
    bConfigurationValue:               0x01
    iConfiguration:                    0x00
    bmAttributes:                      0x80  -> Bus Powered
    MaxPower:                          0x31 =  98 mA

              ===>Interface Descriptor<===
    bLength:                           0x09
    bDescriptorType:                   0x04
    bInterfaceNumber:                  0x00
    bAlternateSetting:                 0x00
    bNumEndpoints:                     0x03
    bInterfaceClass:                   0xFF  -> Interface Class Unknown to USBView
    bInterfaceSubClass:                0x01
    bInterfaceProtocol:                0x02
    iInterface:                        0x00

              ===>Endpoint Descriptor<===
    bLength:                           0x07
    bDescriptorType:                   0x05
    bEndpointAddress:                  0x82  -> Direction: IN - EndpointID: 2
    bmAttributes:                      0x02  -> Bulk Transfer Type
    wMaxPacketSize:                  0x0020 = 0x20 bytes
    bInterval:                         0x00

              ===>Endpoint Descriptor<===
    bLength:                           0x07
    bDescriptorType:                   0x05
    bEndpointAddress:                  0x02  -> Direction: OUT - EndpointID: 2
    bmAttributes:                      0x02  -> Bulk Transfer Type
    wMaxPacketSize:                  0x0020 = 0x20 bytes
    bInterval:                         0x00

              ===>Endpoint Descriptor<===
    bLength:                           0x07
    bDescriptorType:                   0x05
    bEndpointAddress:                  0x81  -> Direction: IN - EndpointID: 1
    bmAttributes:                      0x03  -> Interrupt Transfer Type
    wMaxPacketSize:                  0x0008 = 0x08 bytes
    bInterval:                         0x01

  • Ok same chipset. I just connected it to my windows 10 laptop an dit worked as well. In hardware manager in events I saw  CH341SE service was added to CH340 driver. Since linux also uses CH341 that seems a crucial part.

    If you check in hardware manager you see also the correct com port as it should show the ch340 driver - just to make sure you use correct com port if you have multiple.

    If that still does not work deactivate printer and try with a normal serial terminal to connect to printer and see if you get a response eventually just after sending 
    M115

    To see if it responds at all, if not there might be a problem with the printer or it uses different settings then my version.
  • Well, I reinstalled a couple of times the driver and dc and reconnected the printer many times! And I managed to make it work (don't really understand why now). I really managed to send a gcode to the printer to print sth using the server. 

    Thanks for your time and work though!
  • Great. Maybe you trigger installing the ch341 part that you needed. But good to know it works now.
Sign In or Register to comment.