#Unable to retrieve can bus uuid

1326 messages · Page 2 of 2 (latest)

lyric sable
#

Now this ! Error during homing probe: Communication timeout during homing

#

Yet I can select home and homes fine

frosty tangle
lyric sable
#

The probe issue and mesh ebb time out happen at exactly the same point which to me doesn't make sense as wiring issues would be varied. I've moved wires I to another position too so would happen at a different time which I doesn't

#

I'll uninstall obico

warm sandal
lyric sable
#

well only teo things that differ cam added or obico otherwise no issues prior

#

oh and the flow calibration from orca

#

otherwise printer reliable with cura cube several times

#

@frosty tangleade no difference still getting the follow.

Error during homing probe: Communication timeout during homing

frosty tangle
#

what made no difference- what did you do

lyric sable
#

Iade the adjustment you pinned for me. Nice=-10

#

And the failure happens at exactly the same point again

#

Obico and webcam removed

#

We shall see

#

Ok so exactly same issue at same point again

#

Give up with this now

frosty tangle
#

how far in?

#

have we seen a log file recently?

lyric sable
#

it fails as exatly the same pint every time. the voron logo on tool head dies and then comes back. im checking klippy log noew

#

im turning off for tonight at ill get back to it tomorrow. the connection from toolhead to octopus is the custom can bus cable not any home made connections

frosty tangle
#

your bytes_retransmit reading does climb towards the end of the log, which does point to a physical cable issue, usually

lyric sable
#

Is it possible there's is a power drop. From psu?

#

It was just odd the see the RGB led die and then come back or is that indicator or cable issue

warm sandal
lyric sable
#

Ok I shall pull the cabling apart and see what the issue is tomorrow

#

Thank you all again for advice. Is there any know issue using the moulded can bus cable that comes with the sb2209 rp2040?

#

I know anything is possible but issue with a moulded cable with zero movement

frosty tangle
#

still benefits from strain relief at the toolhead end, the xt30 connector can be a bit wobbly

lyric sable
#

Ok shall look into it

#

@warm sandal you say climbing. As in the error gets worse till it affects the communication. Hence what it fails at same point during the bed mesh

frosty tangle
#

it's just a pointer to wiring that's losing CAN messages

warm sandal
lyric sable
#

And would that be similar to an accumulated timer where when it hits a limit it shuts down the communication or reboots tool head ?

warm sandal
digital ocean
#

You do not want it retransmitting if you can avoid id. Wiring again

lyric sable
#

Ok so easiest thing first, wires. Was curious to understand why it's giving that info

pulsar topaz
# warm sandal i'd assume that when `bytes_retransmit` hits a certain threshold, klipper assume...

some unasked for nerd knowledge:
it's not really that it hits a certain threshold, it's just that a bytes_retransmit means a "packet" had an error in it and had to be retransmitted.
No harm no foul as long as the retransmitted packet can still get to the MCU within the required timeframe. THere is a buffer of queued commands so as long as the packet/informatino is retransmitted before the mcu "needs" it it's all fine.

However, if you're getting any bytes_retransmit then you likely have an underlying issue which will cause more errors. Maybe in the same packet (requiring it to get resent multiple times) or just enough packets so too much overall time is sent retransmitting rather than unique data.

Enough retransmits can cause this timing winow to fail and you get timer too close errors.
Or if the keepalive checks stop coming in because of the connection being down (or maybe because it's spending too much time retransmitting) you get a lost comms error.

"comms timeout during homing" isn't necessarily linked to bytes_retransmit. Homing/probing actions are on a much tighter timing window to normal operations so if the Pi-side is being slow for whatever reason you can miss this 25ms window and get the "comms timeout during homing" even though all the wiring/data is perfectly fine.

That's not the case here as there are clearly bytes_retransmit in the logs, but thought I'd mention that timeout during homing isn't necessarily the same thing as lost comms or TTC (though retransmits can also mess with homing windows)

warm sandal
lyric sable
lyric sable
#

all wires and cables checked and immobilised connections checked and confirmed with continuity, and the tool head stops at exatly the same point

#

it cannot be wires. the wires are in diffrent place and tied down. so if the issue is wires it would fail at a different point but its exactly the same every time

#

this is bed mesh config

speed: 300
horizontal_move_z: 15
##--------------------------------------------------------------------
##    Uncomment below for 250mm build
#mesh_min: 40, 40
#mesh_max: 210,210

##    Uncomment for 300mm build
#mesh_min: 40, 40
#mesh_max: 260,260

##    Uncomment for 350mm build
mesh_min: 40, 40
mesh_max: 310,310
##--------------------------------------------------------------------
fade_start: 0.6
fade_end: 10.0
probe_count: 9,9
algorithm: bicubic
zero_reference_position: 150, 150```
#

now its say lost connection with EBBCan. Ive checked all connection all crimps are doubled up iwht solder to prever fraying. the printer was work flawlessly until i started orca calibrations

#

as the tool head has to move for homing and QGL and at some point the crosses the same point as where it fails during mesh. So why is it not failing there!

#

I have removed crowsnest and bed mesh appears to be working but will repeat and see

#

Nope now get further on mwah and fails again is there no some way of pin pointing the issue!.

#

New error


Can not update MCU 'mcu' config as it is shutdown
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer```
#

Console output

11:55
Klipper state: Disconnect
11:55
FIRMWARE_RESTART
11:54
Klipper state: Disconnect
11:54
Probing failed due to printer shutdown
11:54
Probing failed due to printer shutdown
11:54
Lost communication with MCU 'EBBCan'
11:54
Lost communication with MCU 'EBBCan'
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown```
#

So working the issue, wires and connectors tested and checked. What else can it possibly be?

#

Spontaneously disconnecting now !

#
12:06
Klipper state: Disconnect
12:06
FIRMWARE_RESTART
12:05
Klipper state: Disconnect
12:05
Lost communication with MCU 'EBBCan'
12:05
Lost communication with MCU 'EBBCan'
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
12:05
Lost communication with MCU 'EBBCan'
12:05
Lost communication with MCU 'EBBCan'
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
12:05
Lost communication with MCU 'EBBCan'
12:05
Lost communication with MCU 'EBBCan'
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
12:05
Lost communication with MCU 'EBBCan'
12:05
Lost communication with MCU 'EBBCan'
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
12:05
Lost communication with MCU 'EBBCan'
12:05
Lost communication with MCU 'EBBCan'
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown```
#

Is it a faulty tool head board ?.

#

I've removed Nice=-10 from klipper.service

#

Same issue no matter what i do! Lost communication with MCU 'EBBCan'
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown

#

12:17 PM
Klipper state: Disconnect
12:17 PM
Probing failed due to printer shutdown
12:17 PM
Probing failed due to printer shutdown
12:17 PM
Lost communication with MCU 'EBBCan'

#

This is ridiculous. It is not wires the failure is at exactly the same point. And a wire issue would be intermittent. Yes would fail but not at exactly the same place every time !

#

There must be a better way to figure the issue.

#

Is there a way to interigate the connection?

#

I feel it's like a power drop out!

lyric sable
#

Silly question. If there is a communication issue why does it carry on ?

#

Now this


Printer is not ready
The klippy host software is attempting to connect.  Please
retry in a few moments```
#

Doesn't change! Has this got something to do with the can bus connection issue right at the start

#

I have to be logical there has to be a better way to figure this out

#

@pulsar topaz sale issues and even random disconnect and firmware will not restart. I did update klipper the other day. Maybe I missed something on update

#

I haven't updated configs etc below is current versions

klipper
v0.13.0-328-g47080385
KlipperScreen
v0.4.6-12-gb3115f9b
led_effect
v0.0.14-0-g83e8c46a
mainsail
v2.14.0
mainsail-config
v1.2.1-1-gff3869a6
moonraker
v0.9.3-121-gf2bb93ff

pulsar topaz
#

Your log will show why it's not starting

lyric sable
#

Klipper doesn't start and then after a while that pops up

#

Think I'm going to hard wire to toolhead board and avoid connector

digital ocean
#

wiring issue. it cannot talk to the toolhead

lyric sable
#

@digital ocean I've stripped out the canbus cable outer and checked wires you are correct there was a micro fracture

#

Did simplest thing to do strip wires out and test by gently pulling wires

lyric sable
digital ocean
#

It helps!

lyric sable
#

But i feel its important i put my hand up when its my fault. Appreciate the guidance.

kindred whale
#

when putting in new wires into the chain make sure they have some slack and restrain them before and after the chain. that way they will have space to move around and not get pinched easily
What kind of wire are you using by the way?

lyric sable
kindred whale
lyric sable
#

I used the canbus cable provided with repaired wire.

kindred whale
#

the small bend radius of the cable chain is what generally kills cables

digital ocean
#

You want multi strand for sure.

#

If it's solid core it's just a matter of time

kindred whale
#

i mean the btt cable should be multi strand, but the housing itself (of the wires or overall cable) can cause issues if that's not flexible enough

lyric sable
#

@digital ocean multi strand just 6 inches down the cable it was broken

digital ocean
#

K

lyric sable
#

Ultra stupid question I'm struggling to get z offset dialed in for klicky probe. In the rp2040 config there is a z offset parameter. I keep needing to lower the print head during start on the fly to get the right height. The current offset is 5.8mm if I'm lowering the nozzle for right height does that mean I increase or decrease the z offset?

kindred whale
#

Why to move that block to the printer.cfg? Klipper won't change these things in included files, it only does that automatic "magic" when the value is your printer.cfg

lyric sable
#

@kindred whale had issues with it saving but do it manually. Just need to I ow if I should increase or decrease the value when I -z adjust

kindred whale
lyric sable
#

So if the current is 5.07 and I adjust -0.07 then I change to 5.00

kindred whale
#

I think you need 5.14 then

#

With what I mentioned above you don't have to think and just hit save

#

You don't use a z endstop right?

lyric sable
#

I had issues with saving previously as the probe had to be in the tool head config or it wouldn't work

lyric sable
kindred whale
#

Good that's correct then

lyric sable
#

Was getting miss matches and issue using original end stop

kindred whale
kindred whale
lyric sable
lyric sable
kindred whale
lyric sable
#

I can copy it across an mainsail will know what the ebbcan gpio is without have to use any kind of redirect code? What the point in have tool head cfg if is all readable on main printer cfg

raw tartan
#

multiple config files is strictly an organizational tool

kindred whale
raw tartan
#

klipper doesn't really care about it (other than the save_config thing)

lyric sable
#

@kindred whale ok will give it a go bit it's not what was recommended with toolhead instructions

kindred whale
#

I like to have everything pin related in the printer.cfg and just put the macros in an included file

lyric sable
#

So I could copy everything out of toolhead configuration and paste to printer config so when I do Input shaping and PID it will save to right place

kindred whale
lyric sable
#

Ok but if I put EBBCan: gpoi22 for probe in printer config under probe section it will work fine ?

raw tartan
#

might need to check your spelling on that

#

but yes

lyric sable
#

@raw tartan yeah I'm not at pc just on phone

raw tartan
#

that's the whole reason for the 2 part name: so that klipper knows both the mcu and the pin (which is all it needs to know)

kindred whale
#

pin: gpio23 referenced the pin in the MCU with no name. Mostly the "main" MCU.

pin: can:gpio23 references the mcu named can

lyric sable
#

Ok cool I'll get rid of toolhead configbas it's confusing going back and forth

#

So pin: EEBCan:gpio22

kindred whale
#

Something that often happens: someone changes a thing in the toolhead config, but there's the same line in the printer.cfg. the line which is lower overwrites the one before

#

And they are wondering why nothing is changing

digital ocean
#

Unable to retrieve can bus uuid

lyric sable
#

I've copied all functions from tool head config to printer config. Looks like extruder is now under extruding. What is the default e steps for stealth burner again.?

eager hill
lyric sable
#

The small clockwork style stepper is that 16 microsteps?

#

@eager hill just se to 22 and it's hardly moving

#

Is the tmc2209 bit at bottom needed?

[extruder]
step_pin: EBBCan:gpio18
dir_pin: !EBBCan:gpio19
enable_pin: !EBBCan:gpio17
microsteps: 16
rotation_distance: 22
nozzle_diameter: 0.400
filament_diameter: 1.750
heater_pin: EBBCan:gpio7
sensor_type: EPCOS 100K B57560G104F
sensor_pin: EBBCan:gpio27
#control = pid
#pid_kp = 26.213
#pid_ki = 1.304
#pid_kd = 131.721
#pid_Kp=35.542
#pid_Ki=8.171
#pid_Kd=38.651
min_temp: 0
max_temp: 300

[tmc2209 extruder]
uart_pin: EBBCan:gpio20
run_current: 0.650
stealthchop_threshold

#

Asked for 125mm to be extruded but it's only extended 26.25mm

eager hill
lyric sable
#

Where is that meant to be ?

eager hill
eager hill
lyric sable
#

That's far better

#

New rotation is 22.5192 which from what I gather from previous comments is about right

eager hill
#

Yep. Sounds about right to me

digital ocean
#

How did that end up falling in the floor from a copy paste

lyric sable
#

@digital ocean no idea but was a direct copy from tool head cfg to printer cfg. Lots of issues and now have to re calibrate again

kindred whale
lyric sable
#

@kindred whale no I used the default toolhead cfg that it came with. If I removed any code it would be commented out not deleted

kindred whale
# lyric sable <@490535095183212564> no I used the default toolhead cfg that it came with. If I...

Yes, we figured out that you were missing the gear ratio.

My guess is that your config was "read" from two different [extruder] sections.

If there is a line like for example rotation_distance in both section, the read latter is the one which gets used.

If the btt config was missing the gear ratio but it was present in the your printer.cfg extruder section it would have been used.

If you delete the section in the printer config the gear ratio uses default value of one because the config isn't telling Klipper to use a different one

lyric sable
#

The tool head was working fine with it's own cfg file as that didn't need the 50:10 comment

#

The printer cfg extruder was uncommented so would not be used.

#

Is the tmc2209 bit at bottom needed?

[extruder]
step_pin: EBBCan:gpio18
dir_pin: !EBBCan:gpio19
enable_pin: !EBBCan:gpio17
microsteps: 16
rotation_distance: 22
nozzle_diameter: 0.400
filament_diameter: 1.750
heater_pin: EBBCan:gpio7
sensor_type: EPCOS 100K B57560G104F
sensor_pin: EBBCan:gpio27
#control = pid
#pid_kp = 26.213
#pid_ki = 1.304
#pid_kd = 131.721
#pid_Kp=35.542
#pid_Ki=8.171
#pid_Kd=38.651
min_temp: 0
max_temp: 300

[tmc2209 extruder]
uart_pin: EBBCan:gpio20
run_current: 0.650
stealthchop_threshold

#

Do I also need the [tmc2209 extruder] section

kindred whale
lyric sable
#

Ok

kindred whale
lyric sable
#

No was uncommented as there was a conflict. Mainsail was using code from toolhead cfg to control extruder

kindred whale
#

Ok.

lyric sable
#

Either way it's work but not accurate so will carry on with calibration etc.

kindred whale
#

Do you have a copy of the state of both configs before you moved them together? Might be easier that way to get the same calibration state like before?

lyric sable
#

I do but I've just gone through the calibration and Voron cubes etc. I will have to do that anyway. I've beend ry all my filaments for better accuracy

lyric sable
#

I've now come across belt issues as tension not there. I have the red two trees tensiometer. Do we have a table of expected deflection in mm as I cannot find anything online.

warm sandal
lyric sable
lyric sable
warm sandal
warm sandal
lyric sable
lyric sable
warm sandal
warm sandal
lyric sable
warm sandal
lyric sable
warm sandal
lyric sable
warm sandal
lyric sable
#

@warm sandal well with a tolerance

#

I'm getting withing 0.02-0.05 mm variation

warm sandal
lyric sable
#

The belt holding part of the guage was floating or moving away from guage it's self. The pivot screw was useless as holding guage in place. So glued 3d printed part and guage to prevent unwanted movement. The gauges measures 8mm which equate to 2mm to 2.2mm deflection from what I can see

warm sandal
lyric sable
warm sandal
lyric sable
#

well we shall see. the reality is the tool has the be used differently.

#

I would want to know what the above guage is related to actual belt deflection in mm no just a guage value

lyric sable
#

Not really

#

I'm getting 0.85mm actual belt deflection

warm sandal
lyric sable
#

But I would like to know what the creators of the above are getting

#

@warm sandal what does 1.9 actually mean on the above guage

warm sandal
lyric sable
#

@warm sandal yes I agree but it's still able to measure a value.

warm sandal
lyric sable
#

So what does 1.9 mean on the above guage

warm sandal
lyric sable
#

No I mean the pfmakes gauge

frosty tangle
#

Pounds of tension

lyric sable
#

@frosty tangle thank you and how are pfmakes getting that measurement. By using a calculation based on the deflection of guage correct?

warm sandal
lyric sable
#

@warm sandal correct but how are the getting the values

warm sandal
lyric sable
#

I see a linear movement turned into a rotation movement.

#

@warm sandal not I disagree. It has to he calculated otherwise it's not repeatable

#

So again using the pfmakes guage what does 1.9 mean in mm of belt deflection

warm sandal
lyric sable
#

@warm sandal ok so the question that has to he asked is how are they getting the lbs of tension related to deflection of belt. Because that's how we measure it.

warm sandal
lyric sable
#

@warm sandal I absolutely agree but it still comes down to belt deflection so plenty as. Using a spring to apply a variable calibrated pressure to then convert a linear motion to a rotational gear dial. Tonnes of variables there. So I would want to know what is the deflection needed for the measurement. Because the crappy Chinese tyre guage can to that quite easily and repeatable.

#

@warm sandal then there is absolutely no reason to calibrate the tool if it's guess work

warm sandal
lyric sable
#

@warm sandal I shall see

warm sandal
lyric sable
#

@warm sandal no in an engineering sense

#

Back lash of the making gear would be my first concern.

#

I'll see what I come up with this crappy Chinese guage

warm sandal
lyric sable
#

@warm sandal I can

#

I would also want to know the tolerances

warm sandal
lyric sable
#

Again I'm curious so want to see what the differences are mad why

#

@warm sandal no I want to see how the crappy Chinese took compares

#

There are far less variables with the crappy Chinese guage regardless of use etc

#

I'll get back to you

warm sandal
shut comet
lyric sable
#

@warm sandal agreed.

#

@shut comet I have seen. But it's all down to deflection as that's how the belt is measured. I'll look into it

shut comet
#

Exactly. The spring provides a linear force and the tension on the belt is the counter force.

lyric sable
#

I get how it works. But what does 1.9lbs equally to in belt deflection

shut comet
#

It depends on the span that you measure it across.

#

The PFmakes tool measures the deflection between the two pins so it is consistent.

kindred whale
#

The pfmakestool has alternative calibration guide suspending a jug of water on a specificed length. You could use that with your belt meter as reference

lyric sable
#

Yes I can set up all sorts of experiments to determine a value. Bit the question stands. They says 1.9 is the acceptable value for belt tension but what is the in relation to belt deflection because that's what's being measured

kindred whale
#

3lbs over 250mm is the go-to value. At least you're then in the ballpark

lyric sable
#

Ok again we can come up with a million experiments etc. Bit the question stands what does the guage reference of 1.9lbs equate to in mm of belt deflection

kindred whale
#

We don't know that. You could look into the GT2 sheet and there might be formula.

#

I was trying to give a simple test to measure that with your tool with a known good value

shut comet
lyric sable
#

@shut comet yes I see the specs but there is a linear mechanism converting to a rotation. So the Linear has to be defined but a value which is the distance the belt deflects i.e. 1mm of deflection equals 1.9lbs of tension.

shut comet
#

The numbers on the PF makes gauge are arbitrary from memory and is based on the spring rate and calibration.

#

I mean, the tool works and is relatable and easy to use. 🤷‍♂️

lyric sable
#

But we have not data on why it works or how

#

And without data nothing is reliable

#

I'll email

warm sandal
#

at the end of the day, i really don't care about the numbers

i use the tool to tension my belts and i get great looking prints, that's all that matters to me

limber viper
lyric sable
#

@warm sandal no worries but I do. So you are welcome to no respond

limber viper
#

many springs were tried to find a rate that was as linear as possible for the given belt tension range

lyric sable
#

@limber viper thanks you for jumping in.

#

I get the tensions and gears etc. so are we saying this is guess work.

warm sandal
warm sandal
lyric sable
#

@warm sandal no worries take care

lyric sable
#

@shut comet I agree

limber viper
#

if memory serves

lyric sable
#

@limber viper in getting 0.85mm deflection

#

Thank you for jumping in and taking the time to answer

limber viper
shut comet
lyric sable
#

@limber viper I agree but that can be figured.

warm sandal
limber viper
lyric sable
#

The question I was hoping to find out was with your guage 1.9lbs equates to what in mm of belt deflection

limber viper
#

I would recommend using a water jug and an accurate scale if you go that route

lyric sable
#

I do believe this can be calculated accurately with math

shut comet
lyric sable
#

Hence why I've been asking continuously what is the deflection with your guage at 1.9lbs

#

@shut comet correct but math can figure it out

limber viper
lyric sable
#

Yes I agree

#

But I wanted to know 1.9lbs = X mm of belt deflection

#

Apologies I tend to want to understand how things work and why rather than accepting because someone says

#

@limber viper what is the compression force required for the main spring. Because the calibration to are performing is just adjusting the spring preload as I see it

limber viper
limber viper
#

and also since each spring is slightly different the preload needs to be calibrated

lyric sable
#

@limber viper there is no rush this is curiosity and understanding more than anything

lyric sable
limber viper
lyric sable
#

I get a little annoyed when people say that's pointless when ive grown up with calipers and micrometers from a young age. Yes the crappy Chinese guage is that it is but it still makes an accurate measurement. But I would prefer to understand why and how your works. But yes the calibration is just spring preload. I'm not saying anything is better than yours but it's the lateral to rotation which will have plenty of backlash compounded by the inaccuracies of 3d printing. I've always been told what calibrates the calibrator.

limber viper
lyric sable
#

@limber viper yes but ultimately regardless of tool you are measuring deflection

#

So given a spring of a set force that has preload adjusted will deflect a set length of belt and that deflection is indicated by your guage 0-3

#

@limber viper I know you are at work but get back to me when you can but I'm curious to understand more

shut comet
lyric sable
#

@shut comet absolutely agree

shut comet
#

If you have a weight, you can calibrate your gauge the same way.

lyric sable
#

But the force of the spring is set by preload so it's a specific defind reference but the guage is measuring the deflection

shut comet
#

Anyways. I’m board a plane for VICE so I’m signing off.

lyric sable
#

@shut comet no worries take care

limber viper
lyric sable
#

@limber viper give me a shout on DM when you are next free. Thank you for taking the time

versed dove
#

this has it on page 65-66 but isn't the one I'm thinking of

lyric sable
#

@versed dove thank you

lyric sable
#

Is there a common issue with filament delivery. I se to be getting resistance as filament goes from spo to tool head. Any mods ?

frosty tangle
#

the most common thing we see is people using too small an internal diameter PTFE tube for the reverse bowden

other issues are too tight corners

lyric sable
#

I'm using the wide internal diameter PTFE. But still getting issues. It's physically difficult moving the filament through Bowden. Any chance you have image of your tube route.

frosty tangle
#

i can't find a pic and my printer locations aren't conducive to photography

versed dove
#

cut a section and see if its a lot of resistance still

lyric sable
#

@frosty tangle no problem

#

@versed dove even with a section of just filament in PTFE and no spool there is a ridiculous amount of friction which should be the case as the tube is ptfe

versed dove
lyric sable
#

I have a loop as there isnt any other way to get tube to go in a different direction

#

Hence why I ask of there are and pics?

versed dove
#

(I don't have a 2.4)

lyric sable
#

How is it meant to go?

#

I'm going to convert to vertical feed recert to a vertical feed as 90° from Voron fram.is way too tight

raw tartan
#

There's a bunch of other nonsense on the back of this machine, but..

lyric sable
#

@raw tartan it's not it's free moving just the angle. Is there a vertical mod?

raw tartan
#

(Though I admit, I have been known to do it anyway, when printing soft tpu)

#

I'd really suggest just getting the printer farther away from that wall, so you can route the tubing more cleanly first

#

Also, I think your ptfe is sticking out too far over your spool holder, which may be causing some oddities

lyric sable
#

I can't understand why there isn't a plastic guide for the 90° bend.

raw tartan
#

Do you see how nicely mine is sitting?

#

I don't have any guides in there