#Disaster BT
1 messages Ā· Page 2 of 1
disable AFC either by uncommenting it or by setting up a bypass filament sensor switch
Ok I was going to remove it from the Voron but dont want to remove the code for now
jsut comment out [include AFC/*] in printer.cfgt
I did
Well guess It's done wont home now ...calling it a nite
Have a good nite
I looked at the extruder on the BT I can see the bmg gear moving a bit ( smidge) when moving the filament manual
_CLIENT_LINEAR_MOVE E=50 F=300
wont print now that Commented out the BT
Leave it to me to be the first š
Thatās how the extruder and all movements get call out with the web guis
Getting " internal prep Error "
TMC 'AFC_stepper lane1' reports error: DRV_STATUS: 00190010 s2vsa=1(ShortToSupply_A!) cs_actual=25
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
bad dstep driver ?
all i did was put the BT back on
i'm just telling you what short to supply means.
Not sure .. i was able to get a print done without the BT
None of the wiring has changed so I'll change the stepper motor
you don't have to change anything to start
just test continuity on the stepper motor wires for lane 1 and verify the pairings
Checked each lead from stepper motor to afc connection get a beep and reading
<@&1304550334839918672> can someone else help mike diagnose his short to supply issue please
Thanks ..thunderkeys
Had to head out I'll mess it tomorrow nite
Mike - what I'd like you to verify:
- disconnect he stepper motor wire from the AFC-Lite.
- test for continuity between the 4 pins. there should be two pins that 'pair up' for two sets (set A and B). Tell me what order the continuity is (AABB, ABAB, or ABBA).
- do this for all 4 stepper motors.
- take a picture of yoru stepper motor driver chips, from the top where the labels are. make sure the labels are visible.
we'll diagnose further from there.
I will do that. But changed motor for fun.
Post your klippy log please
For some reason the following is not in your config anymore, add this to the bottom of your AFC_Turtle_1.cfg or AFC_Hardware.cfg.
[AFC_led AFC_Indicator]
pin: Turtle_1:RGB1
chain_count: 4
color_order: GRBW
E _ _ _ _
R |_|_|_|_|_|
R | \____
O | \
R | |\ X |
! \_________/ |___|
Turtle_1
9:57 PM
lane4 tool cmd: T3 LOCKED NOT LOADED
9:57 PM
lane3 tool cmd: T2 EMPTY READY FOR SPOOL
9:57 PM
lane2 tool cmd: T1 EMPTY READY FOR SPOOL
9:57 PM
lane1 tool cmd: T0 LOCKED NOT LOADED
9:57 PM
'Box Turtle' Turtle_1 Prepping lanes```
So you have filament in your prep sensors for lanes 4 and 1 but not loaded in extruder, remove them and re-insert to load
i have zero filamewnt on turtle
are your prep levers all the way closed?
give like a 5 second wait between triggering them
all 4 triggering
R _____ ____
E / \ | o |
A | |/ ___/
D |_________/
Y |_|_| |_|_|
Turtle_1
10:11 PM
lane4 tool cmd: T3 EMPTY READY FOR SPOOL
10:11 PM
lane3 tool cmd: T2 EMPTY READY FOR SPOOL
10:11 PM
lane2 tool cmd: T1 EMPTY READY FOR SPOOL
10:11 PM
lane1 tool cmd: T0 EMPTY READY FOR SPOOL```
strange thing is I did nothing expect remove th BT to fix tool head
hardware wise
Sorry to be a pain i nthe butt excuse the language
now i have to figure out were the leds are located in the softwar e
since I unloaded it and re-loaded
Thanks
Im going to be quiet as a mouse. .Sorry to bother
Were is the RGB for the TN2 code located on v0.0.0-1298-gcde2a73c-inferred to turn on the led /switch color
do you have this your config?
[AFC_led Buffer_Indicator]
pin: turtleneck:RGB
chain_count: 1
color_order: GRBW
initial_RED: 0.0
initial_GREEN: 0.0
initial_BLUE: 0.0
initial_WHITE: 0.0
along with led_index: Buffer_Indicator:1 in your AFC_buffer section
it may not do anything on starutp ... try cahgning initial values and see if it lights up
I used back up and I get no LED
Klipper reports: ERROR
Pin 'RGB' is not a valid pin name on mcu 'Turtle_1'
Once the underlying issue is corrected, use the "RESTART"
command to reload the config and restart the host software.
Printer is halted
pin: Turtle_1:RGB
chain_count: 1
color_order: GRBW
initial_RED: 1.0
initial_GREEN: 0.0
initial_BLUE: 0.0
initial_WHITE: 0.0```
I just remvoed [AFC_led Buffer_Indicator] maybe TN2 is dead
i doubt it
Unknown pin chip name 'turtleneck' all I keep getting
it woudl be to yoru benefit to stop just restoring from random backups and just configure it by hand
you may have your turtleneck mcu defined differently
if you called it e.g. Turtle_1 or tn2 or turtleneck2 it needs to match that for the pin name.
it loads until I put the buffer indicator in the hardwar.cfg then thats when it fails
your buffer isn't defined as turtleneck
mcu turtleneck doesn't exist, that is what the error is telling you
Fresh install same issue. ..Have a good day/evening
there is insufficient information to help us help you solve this problem.
I gave the default snipped needed for the LED - assuming the mcu is named 'turtleneck'. either your turtleneck mcu is not named turtleneck ,or it is not defined and you have an incomplete configuration.
please post updated full config folder
Is it possible that when installing from script that it's only installing turtleneck v1 and not for TurtleNeck v2. Since I was just chosing the defaults and adding the endstop pin.
The default is turtleneck 1 so yes.
It's an option when installing
What do i change it too as a option before hitting the I for install
It's one of the prompts during install
V2 finally just showed up this time
on the script
now I have find palce to put the TN2 serial
Nope ..ejecting filament after going forward
Working on the bypass so at least I can use the printer
I shelved the project at least I'm back to single color printing.
Got a question when testing the lane 1 the filament spool correct but when calibration bowden length. It rolls backwards
I ran the test lane =1 -4 all spin backwards with ! or no ! for direction pin
Thunder ..you Rock I would have never figured that out
except it just loosened the whole spool instead of bowden length
afc_motor_rwd: Turtle_1:MOT1_FWD #RWD
afc_motor_fwd: Turtle_1:MOT1_RWD #FWD this is only thing i did ..
A video when you run calibration I think will help us see what your are trying to describe so we can help get this working
Youāre rewind direction is now backwards
It tried to do a rewind when doing a retraction move while doing calibration and instead unwound a bunch
That's calibrating bowden length
I changed the fwd/rwd only due to the roll was going wrong way
Something else I need to change too ?
Change your fwd/red back
Itās backwards now
It sounds like that was just hub length calibration too
I heard the switch click and then it started going the opposite direction
If that is intended to be Bowden calibration, your toolhead sensor is stuck/not working or incorrectly configured
It loads to the hub, then does slow moves to the toolhead until it hits the toolhead sensor, then retracts a bit, then moves back in
If the toolhead sensor is in a triggered state, itāll think itās loaded as soon as the hub sensor is hit
But I can see in your video the spool is moving the wrong direction compared to the filament loaded in the lane
afc_motor_rwd: Turtle_1:MOT1_FWD #RWD
afc_motor_fwd: Turtle_1:MOT1_RWD #FWD this is only thing i did ..
What i changed due to spool was only rotating backwards
This is incorrect now
Please change it back
Your video shows your unwinding filament when doing a retraction move
Thunder told me to change it
No, Thunder told you how to change it. Your video clearly shows it should be spinning the opposite direction it currently is
So it needs changed back
Ok
Ill change it tonight and make a new vid
I thought I had a video of it just spinning backwards when running the test lane.
Pretty sure test lane runs the wheels ābackwardsā as thatās the rewind motion iirc
I could be wrong
Not at home to double check it for several days
Yes TEST command moves the wheels in reverse like it's rewinding a spool
You have a sensor stuck or one thing then. I would expect it to rewind when pulling filament back
If you go watch the video you showed earlier it pulled filament back and your spool ran the wrong direction
Correct not sure why it was moving forward for a few then went backwards until I hit emergency stop it would have unwinded the whole spool
But I changed the two pin name to get the bowden length to even get the spool to go in correct direction in the 1st place. It was working correct in previous version of software. I have about 30 min tonight to mess with it
Original PINS ..making a video after printer is rebooted
š
The respoolers are acting correctly based on what the filament is doing
So that is correct
For going backwards?
Yes, your filament was being retracted by the turtle and the spoolers were rewinding it
This is correct
Shouldn't it be pushing filament to the tool head
This is running the bowden tube length test
Are you actually doing the Bowden calibration and not just the hub calibration?
Yes bowden tube length
If so, you have your toolhead sensor stuck, or if you are still trying to do buffer ramming, the buffer is extended
Filament went past hub and stopped turning all together
Spinning backwards infinity with tn in
do you have the sensors showing in mainsail?
double check that the switches for turtle 1 compressed and extended are correct
your hub switch has an issue then since all of the lanes are empty but it is detected
I found a small piece of broekn filaemnt in the hub
white filament go figure didnt see it
ok, try your tests again
Nope stopped spinning forward now its re winding trying too automatic
Ejected and keeps re winding infinity
TN was in the whole time too
Finally made it to the tool head then started screaming at me then it started auto rewinding ..sorry for all the typing
Is it supposed to click and jitter like that on a rewind
yeah, the extruder is doing short moves while the spooler is basically just running against its torque limits
afc_bowden_length: New: 2080.0 Old: 1725.0 at least I got a bowden tube length
its a start
its pushed out the TN 2 times durning the bowden tube test
i held it in
Youāre using ramming as your sensor, right? Because thatās what it needs to do
Hold the TN only until it hits the toolhead, the let it expand on its own, and compress it slowly as it starts to retract
Yes ramming
Yes, you need to assist closing the TN again when it starts retracting from the toolhead
You should only need to hold the TN closed until filament is past it for initial load
IMO, ramming shouldnāt be used when you have toolhead sensors available as an option
I think what they were saying is to use the toolhead for your entry sensor instead of ramming as it will be more consistent
I understand
Now none of tnr trigger are showing any signs of life when trying to load filament in the ptfe tubes even tried rebooting. White flag time ? Im sure you are all tired of trying to helping. So on that note...
what would cause lane 1/3 when pushing the filament ptfe tube backwards I can see the lane1 prep switch but no filament is not being pulled thru at all
something with the load side ?
Check you switches again, otherwise though I am not sure what you are trying to describe
You need to give some time between triggering each lane, like 2 seconds
Ran bowden legth finally got that
but running T0 the TN2 keeps extending before filament getting to the tool head
this is why we suggested the toolhead sensor instead of ramming
I have a tool head sensor instead
then use it and disable filament ramming as your sensor.
I did š
PM
Turtle_1 Status
LANE | Prep | Load |
lane1 | <--> | <--> |
lane2 | <--> | <--> |
lane3 | <--> | <--> |
lane4 | <--> | <--> |
HUB: <-> Tool: <->
sweet finalky I got something right
now to test extruding for correct tension then a 1st layer sqaure
1 step at a time
No extruding
Turtle_1 Status
LANE | Prep | Load |
lane1 | <--> | <--> |
lane2 | <--> | <--> |
lane3 | <--> | <--> |
lane4 | <--> | <--> |
HUB: <-> Tool: <->
10:06 PM
AFC_status
10:06 PM
PAUSING
10:06 PM
lane1 HUB NOT CLEAR WHEN TRYING TO LOAD```
im sure Im missing something
What does the hub switch filament sensor in your gui look like
when you do this it is better to screenshot since color matters
You also have something loaded to you toolhead it looks like
filament is loaded to the toolhead yes
So what are you trying to do then with that last command that you posted?
The hub not clear one
I ran t0 then i was goign to test the tensioner to make sure I had the right tension on the filament at the toolhead.
Ok was lane one already loaded?
Yes
heated nozzle to 220 then hit extrude
So T0 won't work because its already loaded, you need to choose a different lane
ok
This should be fine though since a lane was already loaded
nothing
I tried a fresh 1 st layer square fro mthe beginning, filment is now not making it to the tool head squealing
for another night .. too tired to mes with it
Im trying to update the afc software only allowing me to install which will overwite the settings
It shouldn't, have you been uninstalling and reinstalling AFC? or started new with something that could mess with what the script uses to determine if a forced update is needed?
To update the AFC plugin software, you can simply run the following command:
cd AFC-Klipper-Add-On
./install-afc.sh
erased my settings
made a folder called afc back up
removed the MCU folder
ran 3 times and now it shows the update but already to late
š
The backup folder is all of your old configs and should be able to be restored entirely
trying that now !
hopefully i can get something going this weekend
Been way to long
well that didnt work
Ctrl f5 in your browser
Moved sensor to top of the SB - able to calibrate the lanes. But when calibrating bowden length it keeps failing I can see the filament moving to the tool head and sensor is detected but calibtraion keeps failing
can you post the message that your are getting in the console
yes hold
43 AM
lane1 failed to calibrate bowden length while moving to toolhead. Failed after 2125mm
if filament stopped short of the toolhead sensor/ramming during calibration
use the following command to increase bowden length
SET_BOWDEN_LENGTH HUB=Turtle_1 LENGTH=+(distance the filament was short from the toolhead)
getting so close
It tells you what command you need to run
Increase your Bowden length and then run the calibration again
i have it set at 1650 right niow upped it to 1675
Up it to like 2500 then re-run calibration
Unless I'm wrong on that, been a while since I did the calibration
trying it now
Yeah don't make it that big, it then defeats the purpose of having error logic in case someone's sensor is not working. It the new logic weemantalla added to error out after Bowden length plus some value move
Hmm, I think in this case, unless it's at the toolhead 2200 or something is probably safe. It errored after a move of 2125 and not reaching the toolhead
Point in this case being that 1675 isn't a big enough change to not error
did nt work any way. I put filamenent manual i nthe tool head sensor its triggering but when calibrating its not triggering the sensor
Are you reaching the toolhead?
Fair point didn't look at the length in the printout š¬
Yeah, it was more of a 25mm change isn't enough in this specific scenario lol
Just short at 2500
going to increase it
was reaching it before not sure why its not now
Just keep increasing until it passes, and just watch to see how far it goes everytime
failed in same excact spot
increased by 25mm
ill increased it by another 50mm.. dont think its going to make a difference
Calibration failed again
whats the number its printing out?
No number
11:49 AM
lane1 failed to calibrate bowden length Failed retract from toolhead sensor after 100mm
ok now its not retracting
had to scroll further down
do you have a pullup on your toolhead sensor pin
Ejected filament..what a mess
are your respooler working during eject ?
maybe your rwd_speed_multiplier is too low
check extruder tensions
already did that ..and just keeps failing over and over
spool is stopping o nthe foeward now and also the retract keeps getting stuck
the terse word explanations are not getting us very far.
More videos and logs/configs and descriptions, perhaps even a synchronous voice chat with a teaching turtle if they are available, I think woudl get you a longer ways towards success.
and please, stop starting over from scratch every few days. it makes us have to retread the same ground over and over and over again. Iām startin gto feel like Iām in groundhog day
(sent from the air at 35k feet, so apologies it the above comes off terse. we really do want to get your boxturtle up and working ā¦)
No apology needed. I get it ...No worry about it.
I now just getting Clogs - new g2E print / cutter - rapido V2 UHF. I can get a uncloger all the way to the nozzle.
Mike, I suggest working with @nocturne solstice on this -- he has gotten you further than any of us š
I don't know why things just are not working for you ... your slicer setup at least looks fine (filametn ramming disabled) ...
yes ramming disabled
What am I doing wrong
I printed the parts and the cutter is hitting the front plate ?
what spring did you use
but looks like the wrong part
single and dual sensor versions
i used single version
you did not use the filamatrix one
Reprinting
I did the same thing
@gray spruce Please post your latest debug logs and state of the world and we'll try to get back to this. There's been so many different things we've been chasing over the past 5-6 months I'm not even sure where we are anymore.
I know @nocturne solstice worked with you directly and said your BT was working fine on all lanes, it was all toolhead issues. Sounds like that has since changed.
I have the debugger installedd looking for the command
What is the current state of things? What works, what doesnāt?
right now all green
12:48 PM
Turtle_1 Status
LANE | Prep | Load |
lane1 | <--> | <--> |
lane2 | <--> | <--> |
lane3 | <--> | <--> |
lane4 | <--> | <--> |
HUB: <-> Tool: x
sorry was outside
Toolhead sensor functioning properly?
The hub is showing triggered. Is there filament in the Hub? Also, did you get a chance to move to the D2HW switch for at least the hub?
Cool... can you reliably load filament and switch between all lanes?
No
OK. what is happening?
It will switch a few lanes the intermittently get stuck in toolhead
Or get stuck moving forward for next lane change
It changes all the time
lane1 | <--> | <--> |
lane2 | <--> | <--> |
lane3 | <--> | <--> |
lane4 | <--> | <--> |
HUB: x Tool: x```
ejected all 4 lanes
running t0
and so on
I was trying like 10 times ..never even got past 2 passes
Go ahead and gather the debug logs and post the termbin link. Here are the instructions:https://www.armoredturtle.xyz/docs/troubleshooting/troubleshooting.html#known-issues
Armored Turtle Project Documentation
you ssh into the raspberry pi
When it is getting stuck unloading, is the filament still engaged in the gears?
Im reading line by line
yes
I see no flat spots on the filament
also very light teeth marks on the filament
lane 1 mad e it
switching to lane2 failed on rewind
broke the filament
3rd time it has done that
YOu have a sharp bend when entering the chamber?
no
Actually. is there filament still stuck in the toolhead right now?
yes I just removed it
how much was still below the gears?
I thought you use a cutter?
That end doesn't look like a cut though.
I am leaning towards it is always getting stuck in the toolhead and sometimes breaking the filament. Next time it does this, remove the bowden from the toolhead, draw a line across where the filament enters, pull it out and show a pic please.
I am curious to know how much is left in the toolhead when it occurs. I am not 100% on all of the tool values but I believe tool_stn_unload would need to be increased. @keen vapor ?
@ 71 right now
Yeah, I saw. Lets see where the mark lands after it happens again.
OK. so it failed trying to unload?
So it made it to the toolhead hit the extruder gears.
I thin kI might just send it out for a rebuild ..this is getting crazy
Calibrate the bowden length agin with the turtleneck closed.
ok
I think it is just things being lost in communication. We need to be slow and methodical. Get an exact description of the issue and perform one fix at a time.
It will help you in the long run as you will understand how everything works as well.
Stuck
Not stuck
what message do you have in the console?
not there. the actual console.
1:36 PM
lane1 failed to calibrate bowden length Failed retract from toolhead sensor after 100mm
OK. what does the toolhead sensor show currently?
detected
But the filament isn't there
nope
Disconnect the bowden coupler and triple check.
using a scrap of filament, exercise the toolhead senser a bunch of times and a few of those times. check the statuse a few times as well to ensure that it is as expected. If the room is quiet and you pay close attention, you can feel the switch click on and off.
do it like 20-30 times in a row and make sure everything is going smooth.
Piece must be stuck further down so let me take apart ounce again
Don't need to take it apart
open filament latch, warm up toolhead to printing temp and push about 30mm of filemnt into the toolhead then pull it out.
yep
OK. Eject lane 1 and then do a bowden calibration after reloading.
OK. good. what did it say the difference was in the console?
afc_bowden_length: New: 2080.0 Old: 2075.0
Saved afc_bowden_length:2080.0 in AFC_hub Turtle_1 section to configuration file```
Ok. go ahead and home the printer and send a t0. Once it is loaded. let me know. The next step will be to do a T1. No matter what happens on the T1, just wait and explain what is going on š
did it load properly? If so, go back to T2
Same rule. If anything goes weird, let me know before moving anything š
yes 1 and two loaded and unloaded
cut, poop and, etc?
yes
OK. doing T3 now?
yes
T3 completed
on T4 Now
T4 completed
back to T1 ?
or just revese it to see if it makes Round 2
what I was trying the other day
No... I don't see a need to keep grinding away at the filament.
ok t4 sitting in toolhead
so we have proven that the extruders to the toolhead woork perfect.
Time to test the respoolers.
ok
Load lane 1 and 2 with spools and do the same test. Be ready to assist the spools during rewind if needed.
ok hold
Just dont let the filament tangle. If you need to spin them by hand to assist with the respooling, that is OK at the moment. We just need to talk through that if it is a problem.
Rewound without assistance?
none
Nice. Load lane 3 and move to it. Same rules
Did it not turn at all or did it try and struggle?
did it turn when you were testing the lanes without the spools?
OK. lets eject lane 2 and inspect. Does the rear support spin freely? what posistion is it in? I have better luck with it in the 2nd or 3rd posistion from the back.
yes rear suport spins freely
one fro mthe far back
4th spot
all of the lane are set the same
OK. set the rwd speed multiplier to 1 for that lane
Give it a whirl.
do i need to reboot klipper ?
yes. save and restart.
Just making sure. Do not want to assume anything
ok moving to t4 now
pulsating spool
I don't know what that is
YOu are supposed to be rewinding by hand to prevent that.
*if needed
Easy to fix it when it happens. just an extra annoyance you don't need at the moment š
Rewinder slowly and straight no tanglen
OK. once it is rewound, eject the filament there move the rear spool hold closer by one.
or just lift it up. Your pick.
move them forward one more then.
ok
We are going to be heading out at 3:00 or so
Should be back around 4:30 or 5:00. Let me know how it is going even if I am not here please.
Nice... move lane 2 and 3 up to the same position and try them.
And remember. The turtle from the extruders to the printer are working as expected. Don't take them apart or mess with anything there
lane 3 rewinded nice
awesome
I am not going to worry about that too much at the moment. You will want to use a purge tower at least for your first few prints anyway
The same macro is used for each change. That isn't the turtle though.
correct
DO it one more time and then setup for a test print.
š
Just remember that the turtle is working as intended. Donāt stress out about little issues either. It actually performs better after being used a bit
Something wrong with lane 2 Moved the roller up one and still same results will not roll hardly with a full spool
missing cutter too
not hitting the depessor
Make sure everything is able to spin freely. And do a klipper restart
spinning freely
Put your half spool on lane 2 for now.
ok
Make sure you move the rear roller up on lane 1, update the rwd value and do a test load there. If it works, time for test print
did that and lane 1 failed now
What failed? Respooling?
respooling
Letās start a single color print using only the first lane. Dino clip or similar
Reasoning is twofold. Get some mileage on the lane and reduce the weight a bit
4:04 PM
lane1 filament failed to trigger pre extruder gear toolhead sensor, CHECK FILAMENT PATH
||=====||====||==>--||
lane one snapped filament
switching that roll
We are printing single color from lane 1
How did it snap the filament? it should be moving forward only.
Bad roll i guess. Swappedroll no issue
bad juju
Me and white filament just don't get along. LOL
Where did the filament break?
Afted the hub
Before going to the chamber
Ill let it finish out.
1st print on the Voron in a long while
She is cranky because she isn't getting enough attention.
Don't even touch shaktune until you have another couple hundred hours on the machine. Vibrations are not going to be the source of any issuess for the near term š
Oh ok
Ill reprint the flow test orcaslicef blocks.
Ounce I get all 4 lanes working.
Don't be afraid to do single lane prints just to exercise everything.
Get every lane a chance to play. Good idea
Dino has black cavitys must have been some residue. In nozzle š
usually. Or some buildup on the outside
tryin lane 4 now
4 is giving me all kinds of trouble
Thanks for the help today