Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members!
After trying everything I have installed a 32 bit system on my Pi 3 and using Kiauhu I have installed Klipper, Moonraker , Mainsail, Klipper Screen. After installing everything on 32 bit system after hours of printing I don’t even get one retransmit and printer prints like a champ!
previously...
My Voron software crashed. Since lately I do not have time to go over the setup I'm looking for someone in Denver Metro who is willing to set up just the software.
The printer was working before, and I do have a valid working Config file for it.
All I need is to install the software again and...
In my build Im having increasing invalid bytes on the Can bus communication with EBB36 V1.2. They increase about 50 to 100 bytes every 5 minutes even when the printer is ideling. When I crank the printing faster it gets even worst to the point Im getting the print stopped due to the Can Bus...
Im getting hi sdreaded timer too close error, sometimes even before the head starts moving and sometimes hours into the print.
Definitely not the CAN Bus cable, installed new EBB36, re installed the firmware on Octopus.
My CAN Bus runs at 1000,000 speed
This happens often when I do the input...
Well it turned out to be way more involved than I thought :)
Here are some very helpful next steps to learn the insides if someone is at the stage that they just got running the accelerometer and want to dial everything in
https://github.com/Frix-x/klippain-shaketune
Can anyone advise why Im seeing Z spikes
Im wondering if axes are described right in the map settings in config
I wonder if the axis in the graph actually correspond to actual X,Y,Z in the printer
Im attaching the acceleromited axis dirrections in the EBB36
should it still be defined as ...
I just have run the first resonance on my printer and looking for some input on the results as they do not look great
Im attaching the graphs.
Im using EBB36 with this axis setup
axes_map: x,y,z
That worked fine setting up the config file
Thank you!
added this section right after and Im able to do tests
[resonance_tester]
accel_chip: adxl345
accel_per_hz: 50 # Default is 75. Lowering this value reduces sampling rate to mitigate high vibrations.
probe_points: 175,175,10
I didnt know that I can not define my own SPI bus. Im attaching the picture of my EBB36 pinout with description. It seems like the SPI bus name is SPI 2
Should I use this as the SPI bus name instead ?
like this:
[spi_bus SPI2]
mcu: EBBCan
sclk_pin: PB10
miso_pin: PB2
mosi_pin: PB11...
Im attaching part of my printer.cfg file that defines the onboard acceleroiter in EBB36 V1.2
The klipper is not happy about this setup. Can someone advise why?
I get this message in the console :
Klipper reports: ERROR
Section 'spi_bus spibus' is not a valid config section
[mcu]...
Im looking for advise. At this point Im out of ideas.
Have build the printer with Octopus V1.1 that initially was in Can Bridge mode firmware. Everything was working fine but after 2 hours of printing it was stopping. Klippy was showing alot of retransmits counting in thousands after 2 h of...
Klipper just updated on both main board and toolhead over the can bus with no problems but the printer still reports alot dropped messages between the toolhead and mainboard
Follower Esoterical guide to set my trident 350 can bus on EBB36/Octoprint v1.1
during the first print the printer stops mid print . Klippy log shows CAN bus dropping bitrates alot.
I have checked the basics like wiring and terminating resistors on both ends. My can bus wire is twisted but not...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.