MKS-SKIPR icon indicating copy to clipboard operation
MKS-SKIPR copied to clipboard

Published 20 hours ago • verified publisher icon makerbase-mks

CAN functionality

Open NPCarl opened this issue 2 years ago • 10 comments

Trying to query for canbus_uuid, but unable to find any devices. any ideas?

NPCarl avatar Sep 06 '22 03:09 NPCarl

Is your canbus connected to the usb port of the motherboard? The can interface on the motherboard is not supported, you need a usb to can device, connect it to the motherboard, and then switch to can

MKS-hosiey avatar Sep 14 '22 02:09 MKS-hosiey

I am still unable to find canbus_uuid with a u2c device. i have tried both host and board usb. any suggestions?

NPCarl avatar Oct 17 '22 00:10 NPCarl

@MKS-hosiey so you are saying the USB cable needs to be connected all the time? CAN is not enough?

opiswahn avatar Nov 09 '22 09:11 opiswahn

Is your canbus connected to the usb port of the motherboard? The can interface on the motherboard is not supported, you need a usb to can device, connect it to the motherboard, and then switch to can

Why is there a CAN BUS connector and interface if it isn't supported??? How do we use the CAN interface to use for example a BTT EBB36?

G4Cab avatar Dec 03 '22 19:12 G4Cab

her answer by mail https://github.com/makerbase-mks/MKS-THR36-THR42-UTC

please check it

Johnnyyr avatar Dec 06 '22 08:12 Johnnyyr

her answer by mail https://github.com/makerbase-mks/MKS-THR36-THR42-UTC

please check it

and how is this helping with a SKIPR Board?

G4Cab avatar Dec 06 '22 11:12 G4Cab

So I sort of git CAN to work, at least i can find the CAN uuid, and can give commands to the FLY SB2040 board, but only as long as the USB cable is also connected. Is this really the way it should work? I's imagine you only need USB to flash the Toolhead board, and afterwards all communication should go through the CAN interface...

opiswahn avatar Dec 07 '22 12:12 opiswahn

https://klipper.discourse.group/t/mks-skipr-can-bus/5377

G4Cab avatar Dec 21 '22 13:12 G4Cab

If you follow G4Cabs link to klipper.discourse you'll see our progress in the issue analysis. I have measured the CAN-bus with an oszilloskop and a logic analyzer. We have no CAN-bus traffic, no signals from the MCU on pins PB12/13 to the transceiver. So, IMHO the MCU (STM32F407) is not proper initalized for CAN-bus communication. The BTT Octopus Board has a similar CAN-bus hardware implementation and CAN-bus works flawless. The only difference between MKS SKIPR and BTT Octopus is the MCU Type (STM32F446). I suppose somthing between this two MCU is differnt related to the CAN-bus configuration. That could be the fault. So IMHO it is up to the Klipper developers to help.

Radulfus avatar Jan 06 '23 17:01 Radulfus

Issue is solved! https://klipper.discourse.group/t/mks-skipr-can-bus/5377/90?u=cosmicos

Radulfus avatar Jan 15 '23 17:01 Radulfus