Voron 0.1/2 Back in action.

[TitusADuxass]

I managed to get my v0.1/2 back up and running.

I ditched the troublesome Manta M5P / CB1 mainboard. I could not get it flashed.

It used to be relatively straightforward, but something has been changed, and no the esoteric guide does not help (it's Pi orientated).

After a bit of research and a few YouTubes, I went with a BTT SKR Pico, a BTT Pi v2.0 (I got it cheap) and a BTT U2C. I kept the EBB36.

The whole lot went together easily and with the U2C being pre-flashed it was up and working in no time.

I'm just about to start the Orca calibration tests. Then there's a bit of tidying up of the wiring.

Then I'll try and see if it works without wifi, i.e. via ethernet.

[TitusADuxass]

That PICO board didn't last for long, I sourced another (the old one will be returned)

I wish I could remember the guide I used to get this working, for the life of me I cannot find the one I followed.

All the ones that I have found are using a small CAN adaptor (the esoterical guide shows one but doesn't explain how it's used).

As anyone got a good guide how to flash the board?

I thought I'd cracked it when I got the canbus uuid display. Then I plugged in the U2C and it disappeared, now I just get mcu is unable to connect errors.

[TitusADuxass]

I think I have found the problem - 

mcu 'mcu': Starting CAN connect
Created a socket
mcu 'mcu': Unable to open CAN port: Failed to transmit: [Errno 105] No buffer space available

Now to find a solution.

[mvdveer]

10 hours ago, TitusADuxass said:

As anyone got a good guide how to flash the board?

I just flashed a BTT Pico for my v0.1 to V0.2 upgrade and just used this guide from the BTT Github. In saying that, I tried the Esoterical guide to get katapult flashed to the board without success. Ended up just flashing the board with klipper over USB from my Mac as per the guide. 

Also my setup is different to yours: Raspi Pi4B 8GB, UTOC-1.

 I ditched the U2C as I just for the life of me, could NOT get it working - did not show the can network no matter what I did and how many times I flashed it. Connected a UTOC-1 to the Raspi and can network immediately showed up.  Also tried with a waveshare can Pi hat (have that on the RIG) and the network showed up first time. 

The only issue with not having katapult on the PICO, is that future mcu flashes will have to be through USB and not CAN ,which can be a pain. May revisit the katapult issue at some stage. Have ordered another Pico board to try and set up.

See if your can network shows up when you ssh into the BTT Pi and issue:

ip -s -d link show can0

You should see the can network. If not try a different can adapter if you have one. The waveshare Pi canhat is very cheap but don't know if it will work with the BTT Pi.

[TitusADuxass]

My can network is there.

[TitusADuxass]

7 hours ago, mvdveer said:

I just flashed a BTT Pico for my v0.1 to V0.2 upgrade and just used this guide from the BTT Github. In saying that, I tried the Esoterical guide to get katapult flashed to the board without success. Ended up just flashing the board with klipper over USB from my Mac as per the guide. 

 

I'll give that guide a try, if that doesn't work I think I'll buy a proper Pi.

[TitusADuxass]

I think the EBB36 had gone down. I replaced it and can see it's UUID with python3 ~/katapult/scripts/flash_can.py -q and it's in Katapult mode.

But now I've got the no buffer space available again.

mcu 'mcu': Starting CAN connect
Created a socket
mcu 'mcu': Unable to open CAN port: Failed to transmit: [Errno 105] No buffer space available
webhooks client 548395522704: New connection
webhooks client 548395522704: Client info {'program': 'Moonraker', 'version': 'v0.9.2-6-gf735c04'}

 

 

[TitusADuxass]

I updated the /etc/network/interfaces.d/can0 to what is in the esoterical guide, rebooted.

The no buffer space error has gone, there's now this error:

File "/home/biqu/klipper/klippy/serialhdl.py", line 61, in _error
    raise error(self.warn_prefix + (msg % params))
serialhdl.error: mcu 'mcu': Serial connection closed
 

[TitusADuxass]

I cleared that be changing the can L & H around.

Now klipper log gives me this:

mcu 'mcu': Starting CAN connect
Created a socket
webhooks client 548069465056: New connection
webhooks client 548069465056: Client info {'program': 'Moonraker', 'version': 'v0.9.2-6-gf735c04'}

Which looks okay.

[TitusADuxass]

Moonraker log has one error:

Git Repo KlipperScreen: Warnings detected:
  Repo has untracked source files: ['panels/obico.py']
 

[TitusADuxass]

Reboot and the no buffer error is back!!

Time to buy a Pi4 think.

[claudermilk]

I feel your pain. I think I need a new Pi4 myself--Trident is currently dead because the Pi won't boot any more.

[mvdveer]

11 hours ago, TitusADuxass said:

Moonraker log has one error:

Git Repo KlipperScreen: Warnings detected:
  Repo has untracked source files: ['panels/obico.py']
 

That is not an error that will affect function. You can try installing Obico again or remove it completely and see what happens