Jump to content

Unable to connect to XYZPrinting Da Vinci Pro 1.0 on Linux via USB or WiFi/WLAN


makerjrgn

Recommended Posts

Posted · Unable to connect to XYZPrinting Da Vinci Pro 1.0 on Linux via USB or WiFi/WLAN

Hi, I'm new to Cura and to 3D Printing at all. I got a XYZPrinting Da Vinci Pro 1.0 Printer and I would like to use it with from my Linux Machine with Cura.

 

I installed Cura 4.13.1, added my Printer as a "Non Network Printer", choose the right model, but it doesn't show up in the Monitor.

 

Then I started researching...

 

By the way, I am on Manjaro Linux

 

uname -a
Linux NB03L 5.10.105-1-MANJARO #1 SMP PREEMPT Fri Mar 11 14:12:33 UTC 2022 x86_64 GNU/Linux

 

I connected the Printer via USB while watching at the "dmesg" output:

 

dmesg -w
...
[ 6457.857810] usb 1-2: new full-speed USB device number 12 using xhci_hcd
[ 6457.998983] usb 1-2: New USB device found, idVendor=11f1, idProduct=2520, bcdDevice= 1.00
[ 6457.998989] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=3
[ 6457.998993] usb 1-2: SerialNumber: 3F1AWPEU4TH66QT354
[ 6458.002702] cdc_acm 1-2:1.0: ttyACM0: USB ACM device
[ 6632.343315] usb 1-2: USB disconnect, device number 12
[ 6636.654175] usb 1-2: new full-speed USB device number 13 using xhci_hcd
[ 6636.795602] usb 1-2: New USB device found, idVendor=11f1, idProduct=2520, bcdDevice= 1.00
[ 6636.795609] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=3
[ 6636.795613] usb 1-2: SerialNumber: 3F1AWPEU4TH66QT354
[ 6636.800344] cdc_acm 1-2:1.0: ttyACM0: USB ACM device
...

 

so the Printer should be available as "/dev/ttyACM0" - let's start Cura ...

 

I tried to run via command line as "root" to avoid Permission issues and see debug output. From there I can see that Cura seems not to be able to find a proper Baud Rate:

 

2022-03-15 10:00:43,116 - INFO - [MainThread] cura.Machines.MachineErrorChecker._setResult [213]: Error check finished, result = False, time = 0.8s
2022-03-15 10:00:43,255 - DEBUG - [JobQueueWorker [0]] USBPrinting.AutoDetectBaudJob.run [49]: Checking /dev/ttyACM0 if baud rate 115200 works. Retry nr: 0. Wait timeout: 3
2022-03-15 10:00:43,552 - DEBUG - [JobQueueWorker [1]] cura.Machines.ContainerTree.__getitem__ [120]: Adding container tree for custom took 0.25663256645202637 seconds.
2022-03-15 10:00:43,552 - DEBUG - [JobQueueWorker [1]] cura.Machines.ContainerTree.run [185]: All MachineNode loading completed
2022-03-15 10:00:47,715 - DEBUG - [MainThread] UM.Controller.setActiveStage [180]: Setting active stage to MonitorStage
2022-03-15 10:00:47,784 - DEBUG - [JobQueueWorker [0]] USBPrinting.AutoDetectBaudJob.run [49]: Checking /dev/ttyACM0 if baud rate 250000 works. Retry nr: 0. Wait timeout: 3
2022-03-15 10:00:52,287 - DEBUG - [JobQueueWorker [0]] USBPrinting.AutoDetectBaudJob.run [49]: Checking /dev/ttyACM0 if baud rate 500000 works. Retry nr: 0. Wait timeout: 3
2022-03-15 10:00:53,041 - DEBUG - [MainThread] cura.AutoSave._onTimeout [64]: Autosaving preferences, instances and profiles took 0.015588998794555664 seconds
2022-03-15 10:00:56,794 - DEBUG - [JobQueueWorker [0]] USBPrinting.AutoDetectBaudJob.run [49]: Checking /dev/ttyACM0 if baud rate 230400 works. Retry nr: 0. Wait timeout: 3
2022-03-15 10:01:01,301 - DEBUG - [JobQueueWorker [0]] USBPrinting.AutoDetectBaudJob.run [49]: Checking /dev/ttyACM0 if baud rate 76800 works. Retry nr: 0. Wait timeout: 3
2022-03-15 10:01:05,804 - DEBUG - [JobQueueWorker [0]] USBPrinting.AutoDetectBaudJob.run [49]: Checking /dev/ttyACM0 if baud rate 57600 works. Retry nr: 0. Wait timeout: 3
2022-03-15 10:01:10,311 - DEBUG - [JobQueueWorker [0]] USBPrinting.AutoDetectBaudJob.run [49]: Checking /dev/ttyACM0 if baud rate 38400 works. Retry nr: 0. Wait timeout: 3
2022-03-15 10:01:14,818 - DEBUG - [JobQueueWorker [0]] USBPrinting.AutoDetectBaudJob.run [49]: Checking /dev/ttyACM0 if baud rate 19200 works. Retry nr: 0. Wait timeout: 3
2022-03-15 10:01:19,324 - DEBUG - [JobQueueWorker [0]] USBPrinting.AutoDetectBaudJob.run [49]: Checking /dev/ttyACM0 if baud rate 9600 works. Retry nr: 0. Wait timeout: 3
2022-03-15 10:01:38,844 - DEBUG - [JobQueueWorker [0]] USBPrinting.AutoDetectBaudJob.run [49]: Checking /dev/ttyACM0 if baud rate 115200 works. Retry nr: 1. Wait timeout: 15
2022-03-15 10:01:58,864 - DEBUG - [JobQueueWorker [0]] USBPrinting.AutoDetectBaudJob.run [49]: Checking /dev/ttyACM0 if baud rate 250000 works. Retry nr: 1. Wait timeout: 15

 

Now this is running in an endless loop. - Any Ideas on that?

 

cura.log

  • Link to post
    Share on other sites

    Posted · Unable to connect to XYZPrinting Da Vinci Pro 1.0 on Linux via USB or WiFi/WLAN

    This seems to be a popular problem with the DaVinci printers.  Most searches come back with answers regarding Windows issues, but the same thing may be going on with Linux.  One fix that worked occasionally was plugging the printer in to different USB ports in the computer and then all of a sudden things came to life.  That would seem to indicate that the port driver only installed on one port rather than being available on all of them.

    The "cache" size seems important as well.  Connections have been made with the DaVinci at a baud rate of 250k.  That is one of the rates that Cura checks.  FYI - it looks like Repetier Host has the same problem with the DaVinci's.

     

    Since no Ultimaker printers use USB printing anymore, it is unmaintained unless someone from the community wants to take a shot at updating it.  The Octoprint/RaspPI combination seems to work well.

  • Link to post
    Share on other sites

    Posted · Unable to connect to XYZPrinting Da Vinci Pro 1.0 on Linux via USB or WiFi/WLAN

    Hi, and thanks for your quick response.

    I will definitively try different USB Ports. Maybe that works.

     

    But how do you get to the following conclusion?

     

    On 3/15/2022 at 12:56 PM, GregValiant said:

    The Octoprint/RaspPI combination seems to work well

     

    On the Projekt Website they don't even mention the XYZPrinting Devices - neither for being known working nor not working.

     

    Thank you

  • Link to post
    Share on other sites

    Posted · Unable to connect to XYZPrinting Da Vinci Pro 1.0 on Linux via USB or WiFi/WLAN

    That is a general observation since for most machines it's a viable alternative to Cura's USB Printing.

    Questions about the DaVinci's come up here every once in a while and I tried to do some research to try to help.  It was like pulling teeth trying to find anything useful though.

  • Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    • Our picks

      • UltiMaker Cura 5.7 stable released
        Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more. 
         
          • Like
        • 18 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
          • Like
        • 0 replies
    ×
    ×
    • Create New...