What is the problem?
Installed a ezboard into CR-10S confirmed everything was functional via control box. Attached pre-existing octopi setup to usb. powered pi and went to webpage. Page came up no serial connection. tried several different settings and boot patterns. nothing. Re-flashed sd with latest and greatest. nothing. installed plugins etc nothing. lost count of how many reboots i have done. Tried different usb cables. Moved pi further away from printer. added ferrite bead to usb cable. tried it on each end.
What did you already try to solve it?
tried several different settings and boot patterns. nothing. Re-flashed sd with latest and greatest. nothing. installed plugins etc nothing. lost count of how many reboots i have done. Tried different usb cables. Moved pi further away from printer. added ferrite bead to usb cable. tried it on each end.
Logs (octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support!)
syslog1.log (234.6 KB)
octoprint.log (131.7 KB) plugin_pluginmanager_console.log (49.2 KB)
plugin_softwareupdate_console.log (13.5 KB)
serial.log (752 Bytes)
Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible)
pi 3b
octoprint 1.4
octopi 0.17
pi cam 8 months old no idea ver do know its is a newer one
Cr-10s w/ ezboard w/ TH3D unified 2.0 ezabl pro
chrome
windows 10
Hi 
disconnect your printer, connect it again, enter dmesg | tail -n 20 and post the output here.
I just want to see what happens when the new connection is established.
Be sure that the printer is turned on.
pi@octopi:~ dmesg | tail -n 20
[ 12.977927] brcmfmac: power management disabled
[ 13.802928] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 13.803114] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 14.731224] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 16.593050] Bluetooth: Core ver 2.22
[ 16.593114] NET: Registered protocol family 31
[ 16.593117] Bluetooth: HCI device and connection manager initialized
[ 16.593132] Bluetooth: HCI socket layer initialized
[ 16.593140] Bluetooth: L2CAP socket layer initialized
[ 16.593163] Bluetooth: SCO socket layer initialized
[ 17.309789] Bluetooth: HCI UART driver ver 2.3
[ 17.309799] Bluetooth: HCI UART protocol H4 registered
[ 17.309853] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 17.309980] Bluetooth: HCI UART protocol Broadcom registered
[ 22.721142] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 22.721157] Bluetooth: BNEP filters: protocol multicast
[ 22.721180] Bluetooth: BNEP socket layer initialized
[ 23.183268] EXT4-fs (mmcblk0p2): resized to 3145728 blocks
[ 34.962811] EXT4-fs (mmcblk0p2): resized to 5767168 blocks
[ 43.896388] EXT4-fs (mmcblk0p2): resized filesystem to 7725184
pi@octopi:~ pi@octopi:~ $ dmesg | tail -n 20
[ 13.802928] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 13.803114] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 14.731224] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 16.593050] Bluetooth: Core ver 2.22
[ 16.593114] NET: Registered protocol family 31
[ 16.593117] Bluetooth: HCI device and connection manager initialized
[ 16.593132] Bluetooth: HCI socket layer initialized
[ 16.593140] Bluetooth: L2CAP socket layer initialized
[ 16.593163] Bluetooth: SCO socket layer initialized
[ 17.309789] Bluetooth: HCI UART driver ver 2.3
[ 17.309799] Bluetooth: HCI UART protocol H4 registered
[ 17.309853] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 17.309980] Bluetooth: HCI UART protocol Broadcom registered
[ 22.721142] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
-bash: pi@octopi:~: command not found
[ 22.721157] Bluetooth: BNEP filters: protocol multicast
[ 22.721180] Bluetooth: BNEP socket layer initialized
[ 23.183268] EXT4-fs (mmcblk0p2): resized to 3145728 blocks
[ 34.962811] EXT4-fs (mmcblk0p2): resized to 5767168 blocks
[ 43.896388] EXT4-fs (mmcblk0p2): resized filesystem to 7725184
mhmm no connection at all.
Does your printer work with your pc with a something like pronterface?
nope tried direct connecting to pc and no detection
Well then my guess is that you got either a bend pin inside of the connector of your printers maindboard or something is wrong with your printers firmware.
Both should be fixable.
Worst case would be something like a broken ftdi chip. That would also be fixable but it depends on your skill level.