date-created: 2024-04-08 12:22:10 date-modified: 2024-05-21 10:39:08

My Voron Trident 350 | Eleonora

anchored to [[410.00_anchor|410.00_anchor]]

Overview

In December 2023 [[DayPlanner-20231222]] I bought a Voron Trident 350 from Gizzle.

It took me some time to transport it to Tübingen as I’ve asked several people whether they would travel across Nürnberg to pick up the machine on the go. Later we also anticipated to gather the printer ourselves - depicted in [[week-2024-07]] - in a small journey with a rented car however this failed due to planning reasons and such. I then drove by train and transported it for a whole day.

I love this printer a lot, its pretty / cute and all.

I bought it for 850€

Configuration

  • CR3D Bett mit Keenovo Heater und Schnitzel-PEI
  • LDO 2504 auf XY und LDO Spec Motoren auf Z
  • LDO Frame
  • Vonwange Rails auf Y und Z
  • Lightweight X-Achse mit CNA Medium Preload Rail
  • Fushi Lager mit Pins Mod in den XY Joints und Idlern.
  • Rapidburner Toolhead mit Dragon UHF und VzHextrudort Extruder
  • Mellow SHT V2 CAN Toolboard
  • Euclid Probe
  • Fysetc Spider Board mit TMC2209 Treibern

Nitpicks in Config

The current Offset for PEI-Sheets is set to : 0.325+ default one the default is set to: 10.600

Log of events

the first week after gathering it - [[week-2024-08]] - I was calibrating and testing it. Especially to understand the printer and its components better.

I wanted to print some test with ASA to get replacement parts.

What I noticed during the time:

  • Z-Offset is not correct and had to be corrected up
  • several screws were loose –> expected after transport
  • I tensioned the belts - without enough experience to evaluate whether its good or not
  • when printing ASA the can board seems to disconnect after some time –> due to heat supposedly, as the logs suggest

[!Important] Culprit of sudden shutdown Found this issue on [[DayPlanner-20240224]] I may have found the issue causing the printer to randmly shutdown after printing for a while -> usually around 2-3hrs at most. It seems that the system is running low on space and will simply shutdown due to this error –> klipper log denoted that there was no space left to log and thus it stopped operating. I can fix this easily luckily! Yet I will have to reinstall everything onto a new sd-card soon-ish. I will buy a replacement sd-card on monday in person to have the replacement ready!

[!Warning] wrong suspect aboves possible suspect for causing random shutdowns was proven wrong. I monitored the space available and there was no correlation between the available disk space and the availability of my printer. In fact it did not change much while it was running and crashed still!

I ran a lot of tests on [[DayPlanner-20240225]] to find the issue or to potentially fix it. So far - 2020 - I was not able to find the issue itself. I tried reflashing the board - but failed connecting to it in the first place. Then I also found out that the cable for the umbilical cord was loose and resoldered that. This fixed an issue that occurred while searching for the solution of the former so at least something gained. I ran through some forum entries denoting the following:

  • possible wiring issue -> not the case, causes are differently
  • the 64-bit version of raspbian that causes the usb-driver to have issues from time to time. I tried solving it by using the recommended driver instead. see here
    • https://github.com/raspberrypi/firmware/issues/1804
    • https://github.com/jens-maus/RaspberryMatic/issues/1002

The overall pattern of this issue is rather strange and seemingly random -> sometimes it starts and works for some time, sometimes it dies directly after starting the system.

I’m considering buying an RPI4 to maaybe overcome this issue, although I cannot really pin point the issue to be coming from the RPI3

The USB-driver may have fixed the issue? At least right now I was able to have like 2x continuous prints without the system crashing? –> it was like 4hrs in total I think. This sounds rather good but I dont want to set the hopes too high yet. I will see tomorrow!

[!Tip] Issue cause The described issue was caused by one of the cables of the canbus coming loose. I had this like 2 - 3 times already and its always been the same cable. fixed it on DayPlanner-20240520 once more and bought a replacement cable in case its happening again!