Can Octopi now connect to XYZ Da Vinci Junior 1.0?

XYZ new Jan2020 firmware allowed Cura to slice and print to the Da Vinci Junior 1.0 (basic no wifi). The original proprietary xyzware software used a 3w format of encrypted gcode. XYZ printers were cheap but they previously locked in expensive filament. The restrictions are now gone and so I'd like to use the printer again as its good enough for my purposes. Octopi sounds brilliant if /i can get it to work.

I read another post on the Da Vinci Junior 1.0 wifi version which said that as the printer doesnt have "marlin", Octoprint wouldnt work as it needs gcode. I think the new firmware may fix this and allow gcode. Yet another post said it does have marlin.

https://community.octoprint.org/search?q=da%20vinci

I tried Octopi on a pi 3B but the printer connection shows as offline although the pi seems to know something is connected to the usb as i show ttyACM0 in log but fails as it is "busy" - even though the printer is just switched on but doing nothing.

I'd very much like to get this to work but please tell me if it is not doable so I stop going in circles.

I searched for Error 16 and tried various solutions mainly for Arduinos. /nothing worked and so this seems like a monty python dead parrot sketch ...

I have also tried connecting the different baud rates one by one and also tried another usb cable.

If it is possible, please help. /i think this is a popular printer and so its likely others would be interested too.

As my printer is the basic Da Vinci Junior version without wifi, this would mean I can stop directly connecting my laptop to the printer which at present is inconvenient.

Log from terminal:

Changing monitoring state from "Offline" to "Detecting serial port"
Serial port list: [u'/dev/ttyACM0']
Connecting to: /dev/ttyACM0
Changing monitoring state from "Detecting serial port" to "Opening serial port"
Connected to: Serial<id=0x731bfdb0, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Starting baud rate detection...
Changing monitoring state from "Opening serial port" to "Detecting baudrate"
Trying baudrate: 115200
Send: N0 M110 N0*125
Baudrate test retry #1
Send: N0 M110 N0*125
Baudrate test retry #2
Send: N0 M110 N0*125
Baudrate test retry #3
Send: N0 M110 N0*125
Baudrate test retry #4
Send: N0 M110 N0*125
Trying baudrate: 250000
Send: N0 M110 N0*125
Baudrate test retry #1
Send: N0 M110 N0*125
Baudrate test retry #2
Send: N0 M110 N0*125
Baudrate test retry #3
Send: N0 M110 N0*125
Baudrate test retry #4
Send: N0 M110 N0*125
Trying baudrate: 230400
Send: N0 M110 N0*125
Baudrate test retry #1
Send: N0 M110 N0*125
Baudrate test retry #2
Send: N0 M110 N0*125
Baudrate test retry #3
Send: N0 M110 N0*125
Baudrate test retry #4
Send: N0 M110 N0*125
Trying baudrate: 57600
Send: N0 M110 N0*125
Baudrate test retry #1
Send: N0 M110 N0*125
Baudrate test retry #2
Send: N0 M110 N0*125
Baudrate test retry #3
Send: N0 M110 N0*125
Baudrate test retry #4
Send: N0 M110 N0*125
Trying baudrate: 38400
Send: N0 M110 N0*125
Baudrate test retry #1
Send: N0 M110 N0*125
Baudrate test retry #2
Send: N0 M110 N0*125
Baudrate test retry #3
Send: N0 M110 N0*125
Baudrate test retry #4
Send: N0 M110 N0*125
Trying baudrate: 19200
Send: N0 M110 N0*125
Baudrate test retry #1
Send: N0 M110 N0*125
Baudrate test retry #2
Send: N0 M110 N0*125
Baudrate test retry #3
Send: N0 M110 N0*125
Baudrate test retry #4
Send: N0 M110 N0*125
Trying baudrate: 9600
Send: N0 M110 N0*125
Baudrate test retry #1
Send: N0 M110 N0*125
Baudrate test retry #2
Send: N0 M110 N0*125
Baudrate test retry #3
Send: N0 M110 N0*125
Baudrate test retry #4
Send: N0 M110 N0*125
Changing monitoring state from "Detecting baudrate" to "Error: No more baudrates to test, and no suitable baudrate found."
Changing monitoring state from "Error: No more baudrates to test, and no suitable baudrate found." to "Offline (Error: No more baudrates to test, and no suitable baudrate found.)"
Connection closed, closing down monitor
Connecting to: /dev/ttyACM0
Changing monitoring state from "Offline" to "Opening serial port"
Connected to: Serial<id=0x6ac8f110, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Changing monitoring state from "Opening serial port" to "Connecting"
Send: N0 M110 N0*125
No answer from the printer within the connection timeout, trying another hello
Send: N0 M110 N0*125
There was a timeout while trying to connect to the printer
Changing monitoring state from "Connecting" to "Offline"
Connection closed, closing down monitor

Da Vinci Junior 1.0 (note not wifi version)
Octopi version: octopi-buster-lite-0.17.0.zip
pi 3B
Windows 10 using Chrome browser

I'm trying to do the same, did you ever get this working? I can print to my da vinci jr through cura but it seems that octoprint doesn't detect it.

Got it working -- I had connected to the wrong USB port on my pi zero. The printer detects and prints correctly now, including through Cura!

:+1:
but please don't use a pi zero :wink:

1 Like

It's actually working fine, I don't have a webcam connected so there's little network/CPU usage. So far 2hrs into a print and no issues.

good luck :slight_smile:
if it stutters or you got blobs on the prints it's probably the pis fault :wink:

It's the network that kills it, since all the encryption is done on the CPU instead of dedicated. You are usually ok with no webcam and minimal plugins to weigh the system down.