search

makerbase-mks / MKS-SKIPR

MKS SKIPR is an all-in-one board launched by Makerbase for running Klipper. It integrates the RK3328 SOC running the Klipper host and the STM32F407VET6 MCU responsible for executing specific machine actions. It meets the use of most 3D printers.
GNU General Public License v3.0
91 stars 15 forks source link

CAN functionality #6

Open NPCarl opened 2 years ago

NPCarl commented 2 years ago

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

MKS-hosiey commented 2 years ago

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

NPCarl commented 1 year ago

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

opiswahn commented 1 year ago

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

G4Cab commented 1 year ago

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?

Johnnyyr commented 1 year ago

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

please check it

G4Cab commented 1 year ago

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?

opiswahn commented 1 year ago

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...

G4Cab commented 1 year ago

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

Radulfus commented 1 year ago

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 commented 1 year ago

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