Someone here who succeeded and who could provide a link to the equipment they purchased and who can provide a tutorial to make it work with the mks skipr?
@NAPCAL This sounds saddly, but not critical. System works with some uncomfortables, but overal fine.
Thanks for the detailed answer, I somehow didn’t think about the speed, although canbus setting is set to 250 kb/sec, not so much and all devices works fine at toolhead (tmc driver, ws2812, analog and digital IO). Of course, I understand that the project is free and the developers put a lot of effort into its implementation, for which special respect.
Unfortunately, I am more of an electronics engineer, I develop and repair various devices, I am familiar with the basics of programming only at an elementary level, and my level will not help solve the problem of translating uart to canbus.
I dont know, maybe arduino ide may to recover bootloader for 32 bit boards? I have a problem with arduino mega and restore it with IDE and USBASP. On a 32 bit mcu maybe the same procedure?
Or you may download dump from mks skipr github page or make it yourself with klipper compiler with proper parameters, maybe it contain bootloader. On a board i see button to load mcu in boot mode.
Modern mcu’s looks few easy ways to recovery, unlike 8bit, native usb\microsd support.
Thanks for Helping.
I bought a used board and read out the MCU. I read this BIN into my defective SKIPR and now it works again. It would have been easy for everyone to read and share the MCU. Thanks.
i want not read all replays 
what is at moment possible to use my skipr with a BTT EBB36…with usb it work but i need all usb ports for touchscreen, wlan and cam :-/ can i use the the host-usb to connect it with the ebb36?
greets from germany!
i “belive” the connection via cunbus works but iam get no connection to the mcu part :-/ how i set the serial(?) conection to the skipr on printer.cfg. if i try to get the mcu id it will nothing show on USB/uart (via kiauh)
News? I currently use the MKS SKIPR with a THR36 IN USB (NOT CAN)
But I often get errors: “MKS_THR timer too close”
Do you think switching to CAN will solve my problem?
Could I suggest that you start a new thread in “General Discussion”?
Please include your klippy.log
1 Like
I created a discussion but still haven’t gotten any help:
I have replied with a question back to you on your original thread.
Again, don’t hijack somebody else’s thread because you aren’t getting an answer on yours.
People do watch the various conversations and will pipe up when they have something to add but putting questions on other people’s threads (especially ones marked as having solutions) will make it confusing for people looking for answers to their problems and it’s rude.
1 Like
Yes of course I understand but I was really interested in the “normal” CANBUS and I had been reading this conversation for months without writing anything but I will try to write in the best place now
Gentlemen, I’m new to this forum mainly because I was searching for help with my SKIPR CAN woes. My apologies for adding to a thread which already seems to be endless. After hours of frustration getting the CAN bus to work from the Klipper (Pi) side, I managed to compile the STM firmware with the USB to CAN bridge. I’ve purchaed the SKIPR together with the THR42 and the IPS50 Touch screen,. Not only for the CAN trouble I’m not so happy with my purchase. After all, I managed to get it to work via the USB to CAN bridge, with two CAN addresses showing up in the scan and having to replace the /dev/ttySO connection in printer.cfg for the Pi to talk to the MCU is now over the USB-CAN Bridge. The second id showing up was the THR42. Upon purchasing, I really thought that the Pi Side of the SKIPR can naturally talk over the CAN bus. Retrospectively, I’d probably would have been better off with the old stetup SKR 14.Turbo and Pi4 with 7" Pi Screen and an additional CAN Hat plus the THR42. Do I understand the conclusion of this thread that there will be no chance to use the CAN bus of the STM over the UART bridge? I was surprised that the /dev/ttyS0 is no longer working but has been replaced by the USB CAn Bridge,
kind regards
Michael
No, the hardware is not capable of supporting this configuration. It will never exist in Klipper.
1 Like
Dang! I’m sort of running out of USB ports. Ist the USB Cable that plugs into the MCU USB-C to connect to the USB-A 3.0 connector? If so, would it be safe to use a USB 3.0 hub, because that connector is supposed to connect my USB camera. Those stiff plugs and wires, especially HDMI use too much clearance space for their own good. Sigh.
Kind regards
Michael
p.s. did Makerbase engineers ever tried their own sh*t?
Hi all. I am still using skipr with 2x CAN Toolheads successfully. After killing my STM and replacing it with a new one (resoldered), it’s working again, though I had some random connection dropouts.
I found the culprit to be the CAN-connector on the SKIPR. Very unreliable. This is my Solution:
1 Like
Hopefully you’re going to put some electrical tape or (ideally) epoxy on those bare wires as that looks like an accident waiting to happen.
3 Likes
Hello, I am building my first Voron 2.4 and I bought the MKS skipr board and the MKS THR36 to be able to use canbus, just now trying to install it I came across this POST. I managed to make it work via USB but my idea is to make it work via canbus, but when I change the firmware to canbus and connect it, my board does not detect it, it returns this error:
OSError: [Errno 19] No such device
My question is, could anyone make it work via canbus directly to the mks skipr? since I do everything as the tutorial says but it doesn’t recognize it when I connect it.
Greetings
Yep. I have a worked config. Micro molex on skipr connect to 4 pins canbus THR42.
Tutorial for all:
- Compiling firmwares for SKIPR and TOOLHEAD (in my case THR42)
(standart procedure)
Be carefull, CANBUS SPEED NEED THE SAME, 1000000 (screenshots from different times, when i try to find solution with "mcu shutdown, timer to close)
-
Upload firmwares, then connect usb type-c from mcu (on skipr) to one of 3 usb ports of raspberry side. Skipr connet board itself from mcu usb to raspbery usb. Connect Micro molex to toolhead (4 wires)
-
make a new file
/etc/network/interfaces.d/can0
write inside:
allow-hotplug can0
iface can0 can static
bitrate 1000000 # Ensure it's the same as selected for MCU firmware.
up ifconfig $IFACE txqueuelen 128 #for default MKS SKIPR linux image
#up ip link set $IFACE txqueuelen 128 #for self compiled linux from redrathnure
do CHMOD - 777
- reboot. Make a query of MCU NODE ID’s. Edit you printer.cfg.
[mcu]
canbus_uuid: 93873e400572
[mcu MKS_THR]
canbus_uuid: 827da64c9388
- Profit
Sorry - its a short breef manual.
1 Like
Hi, can you help me replace the stm32?
Can you please help a noob here…
Do I really need to reflash the MKS Skipr for the CAN to work? How do I install the created klipper.bin created for the SKIPR board?
I have just reflashed it with the latest image from Makerbase, adjusted my configurations and installed KAMP again. I wonder if, to enable CAN, I need to redo all this again (which does not make a lot of sense to me).