hey guys and girls,
I got a second had Voron 2.4 350x350 about 6 months ago, it had 1000hrs on it. All was working good was getting some good prints off it. I made the made the mistake of continually doing the updates as the came up, which eventually ended up giving me the dreaded ''MCU unable to connect"' message. So i checked to see what i could do, which led me down the path of re-insstalling the firmware on the BTT pi V1.2 and flashing the BTT octopus V1.01. im a little new to the programing side having only had some Creality K1s. i followed some online tutorials and managed to get it working somewhat again, but it started throwing "'timer too close errors''. So i have tried to reflash the the board and canbus board and it has bought me back to the 'MCU unable to connect' again
Now reading up some say the cord from the board to the canbus may have a break in it and thats why its throwing those errors. I have ordered an new canbus and a new cord to connect it also which will be a couple off weeks away. So will be interesting to see if that is the case. in the mean time i want to see if what I've got programmed is right, bare in mind some of the plugs are in different spots (not my doing)
Anyway if you got through all that info i am going to attach the klippy log to see if any of you guru's can see where I'm going wrong. if it is me then ill have a brand new canbus board ready just incase
Board - BTT Octopus Pro 1.01 with the 429 chip
Canbus - EBB2240
PI - BTT V1.2
Cheers
I got a second had Voron 2.4 350x350 about 6 months ago, it had 1000hrs on it. All was working good was getting some good prints off it. I made the made the mistake of continually doing the updates as the came up, which eventually ended up giving me the dreaded ''MCU unable to connect"' message. So i checked to see what i could do, which led me down the path of re-insstalling the firmware on the BTT pi V1.2 and flashing the BTT octopus V1.01. im a little new to the programing side having only had some Creality K1s. i followed some online tutorials and managed to get it working somewhat again, but it started throwing "'timer too close errors''. So i have tried to reflash the the board and canbus board and it has bought me back to the 'MCU unable to connect' again
Now reading up some say the cord from the board to the canbus may have a break in it and thats why its throwing those errors. I have ordered an new canbus and a new cord to connect it also which will be a couple off weeks away. So will be interesting to see if that is the case. in the mean time i want to see if what I've got programmed is right, bare in mind some of the plugs are in different spots (not my doing)
Anyway if you got through all that info i am going to attach the klippy log to see if any of you guru's can see where I'm going wrong. if it is me then ill have a brand new canbus board ready just incase
Board - BTT Octopus Pro 1.01 with the 429 chip
Canbus - EBB2240
PI - BTT V1.2
Cheers
