Can't get Octopi to talk to my printer

What is the problem?
Can't get Octopi to talk to my printer. I have a Davinci Pro 1.0

What did you already try to solve it?
Turned off printers Wi-Fi since I thought it may be interfering with the serial port connection. I also created a profile for my printer using "generic" and changed all of the settings to match my printer including build plate size, etc. I tried both the auto and the dev/ttyACMO serial port settings with auto for the baud rate.

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, octoprint.log, serial.log or output on terminal tab, ...)

I'm using Octoprint version 1.3.9 on a raspberry pi3. I have successfully connected to Octopi using my browser over its Wi-Fi. The terminal log of the connection process follows:

Connecting to: /dev/ttyACM0
Changing monitoring state from "Offline" to "Opening serial port"
Connected to: Serial<id=0x71b795d0, open=True>(port='/dev/ttyACM0', baudrate=230400, 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"
There was a timeout while trying to connect to the printer
Changing monitoring state from "Connecting" to "Offline"
Connection closed, closing down monitor
Changing monitoring state from "Offline" to "Detecting serial port"
Serial port list: ['/dev/ttyACM0']
Connecting to: /dev/ttyACM0
Changing monitoring state from "Detecting serial port" to "Opening serial port"
Connected to: Serial<id=0x73112cd0, open=True>(port='/dev/ttyACM0', baudrate=230400, 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: 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: 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: 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

Please format your logs, they are really hard to read otherwise.

Are they formatted properly now? Thanks

I'm not sure if that printer is supported since I remember that it apparently uses some proprietary firmware. But it can be flashed with something that works. Not sure how and what though, Google should probably be able to help though.