no i didnt i will check another one now
Serial port list: ['/dev/ttyAMA0']
Connecting to: /dev/ttyAMA0
Changing monitoring state from "Detecting serial port" to "Opening serial port"
Connected to: Serial<id=0x67bdb6b0, open=True>(port='/dev/ttyAMA0', 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
Could not write anything to the serial port in 5 tries, something appears to be wrong with the printer communication
Changing monitoring state from "Detecting baudrate" to "Offline (Error: Could not write to serial port)"
Connection closed, closing down monitor
Closing down send loop
should i add something to the additional serial port or not ?
as long as it isn't detected by your pi that wouldn't help
it looks like this in dmesg when you printer is connected (not the same - this isn't an skr board)
[19801.674010] usb 2-3: USB disconnect, device number 3
[19923.281851] usb 2-3: new full-speed USB device number 7 using xhci_hcd
[19923.730481] usb 2-3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63
[19923.730487] usb 2-3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[19923.730490] usb 2-3: Product: USB2.0-Serial
[19923.775114] usbcore: registered new interface driver usbserial_generic
[19923.775126] usbserial: USB Serial support registered for generic
[19923.777306] usbcore: registered new interface driver ch341
[19923.777332] usbserial: USB Serial support registered for ch341-uart
[19923.777368] ch341 2-3:1.0: ch341-uart converter detected
[19923.788731] usb 2-3: ch341-uart converter now attached to ttyUSB0
i found a blown fuse and replaced it now am getting this Changing monitoring state from "Detecting baudrate" to "Offline (Error: Could not write to serial port)"
Closing down send loop
Connection closed, closing down monitor
Changing monitoring state from "Offline" to "Detecting serial port"
Serial port list: [u'/dev/ttyACM0', '/dev/ttyAMA0']
Trying /dev/ttyACM0
Could not connect to or enter programming mode on /dev/ttyACM0, might not be a printer or just not allow programming mode
Trying /dev/ttyAMA0
Changing monitoring state from "Offline" to "Detecting serial port"
Serial port list: [u'/dev/ttyACM0', '/dev/ttyAMA0']
Trying /dev/ttyACM0
Could not connect to or enter programming mode on /dev/ttyACM0, might not be a printer or just not allow programming mode
Trying /dev/ttyAMA0
alright what does dmesg show now?
[ 11.143370] 8021q: 802.1Q VLAN Support v1.8
[ 11.172933] Adding 102396k swap on /var/swap. Priority:-2 extents:1 across:102396k SSFS
[ 11.668802] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 11.668840] brcmfmac: power management disabled
[ 12.026422] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 12.026433] 8021q: adding VLAN 0 to HW filter on device eth0
[ 14.816283] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 18.256744] Bluetooth: Core ver 2.22
[ 18.256825] NET: Registered protocol family 31
[ 18.256828] Bluetooth: HCI device and connection manager initialized
[ 18.257796] Bluetooth: HCI socket layer initialized
[ 18.257815] Bluetooth: L2CAP socket layer initialized
[ 18.257864] Bluetooth: SCO socket layer initialized
[ 18.272995] Bluetooth: HCI UART driver ver 2.3
[ 18.273007] Bluetooth: HCI UART protocol H4 registered
[ 18.273107] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 18.274861] Bluetooth: HCI UART protocol Broadcom registered
[ 18.554724] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.554733] Bluetooth: BNEP filters: protocol multicast
[ 18.554749] Bluetooth: BNEP socket layer initialized
pi@PREDATOR:~ $
opertionalllllllllllll
are you sure you only disconnected and reconnected the printer?
Because the time in your dmesg indicates that your pi has peen restarted.
now it says operational first time i see that and connected i think we are good now
I think we should check why the time indicated a restart. Did you restart/unplug the pi or did it restart by itself when you plugged in the printer?
[ 11.143370] 8021q: 802.1Q VLAN Support v1.8
[ 11.172933] Adding 102396k swap on /var/swap. Priority:-2 extents:1 across:102396k SSFS
[ 11.668802] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 11.668840] brcmfmac: power management disabled
[ 12.026422] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 12.026433] 8021q: adding VLAN 0 to HW filter on device eth0
[ 14.816283] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 18.256744] Bluetooth: Core ver 2.22
[ 18.256825] NET: Registered protocol family 31
[ 18.256828] Bluetooth: HCI device and connection manager initialized
[ 18.257796] Bluetooth: HCI socket layer initialized
[ 18.257815] Bluetooth: L2CAP socket layer initialized
[ 18.257864] Bluetooth: SCO socket layer initialized
[ 18.272995] Bluetooth: HCI UART driver ver 2.3
[ 18.273007] Bluetooth: HCI UART protocol H4 registered
[ 18.273107] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 18.274861] Bluetooth: HCI UART protocol Broadcom registered
[ 18.554724] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.554733] Bluetooth: BNEP filters: protocol multicast
[ 18.554749] Bluetooth: BNEP socket layer initialized
tell me what i need to do 
am all ears
Yeah that's what I mean. The time says that the pi was online for 18 seconds at the last entry.
When you connect your printer you should get something like I posted above and it should show a time like 600 seconds because you're working on it for some time now..
I think your SKR board is powering via usb and the pi restarts every time you plug in the cable
Check if this jumper is on the same position as in this picture
that jumper is on VDD and i found what blow the fuse , there is a card from bigtree called DCDC and that is what was causing the fuse blow it suppose to give more amps i guess
I haven't tried that dcdc-board yet but afaik you have to switch the jumper next to the SERVOS_Probe text if you use it
do you have experience with sensorless homing the plugs for the XYZ do they need to be still pluged in even if its sensorless homing ?i learend that i cant have sensorless homing because i cut the diag from the motor drives ( all of the 3 ) so how can i make sure the sensorless homing is disabled ? because the sensor for the motor which it doesnt stop change state from red light to off
one of the motors dont stop when doing home i did G33 and here is the screen
Send: G33
Recv: G33 Auto Calibrate
Recv: Checking... AC
Recv: .Height:450.00 Ex:+0.00 Ey:+0.00 Ez:+0.00 Radius:227.00
Recv: . Tx:+0.00 Ty:+0.00 Tz:+0.00
Recv: T:22.50 /0.00 B:26.14 /0.00 @:0 B@:0
Recv: echo:busy: processing
Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
Recv: T:23.12 /0.00 B:26.14 /0.00 @:0 B@:0
Recv: echo:busy: processing
Recv: T:21.87 /0.00 B:26.25 /0.00 @:0 B@:0
Recv: echo:busy: processing
Recv: T:22.50 /0.00 B:26.25 /0.00 @:0 B@:0
Recv: echo:busy: processing
Send: M112
Send: N2 M112*35
Recv: Error:Printer halted. kill() called!
i will open a new thread so i dont mix up issues thanks a lot for your help
ttyAMA0 is only if you are using a direct serial connection to the GPIO on the pi. If it is a USB cable it should be ttyUSB0 for the port
1 Like
its all good now i found a blown fuse if you can help me i have another issue for bed level i do g33 v3 and it give me pause for user what do i need to do to make it go ahead ?