#attempting to get my first print going but having issues
1 messages Β· Page 1 of 1 (latest)
<@&1304550334839918672>
You can adjust the speed of the respooler motors by changing this setting
the motors are studdering when they are going in reverse
They are supposed to stutter that's the pwm working
Mine were going too fast so I slowed them down like this
I think 0.5 was the defaults
If yours are going to slow you would probably need to raise the numbers higher
I'm speculating however
you can go over 1 with that value, some have it set to 1.5 or 2
No they're separate
no they should be different, if you set fwd too high it can run faster than your extruder and unspool more
For me it is at least glad Jimmy John is here he's the guy to ask
you got it as well π
I'm still on the old software though LOL
Also to set higher than 1 you need to manually update your config, I got to fix the macro to allow greater than 1
I get confused on which one to adjust because my motors ran backwards so I edited things to reverse them
I should just change my connectors
yeah idk what im doing wrong
the spool doesnt even spin
the filament moves around the spool
Can you roll The idler rollers freely with your fingers
yes
And the tires they spin freely the edges aren't rubbing anything?
correct not rubbing anything
reversing your pin assignment does not change which direction is fwd/rwd from the software point of view. If that makes sense
idk the command
Yeah I think I agree with what you just said also
But I have never been totally sure
TEST LANE=lane1 spins the spoolers
It works with how I have things set so I've assumed I'm correct
Just taught me something new LOL
it spins like trying to rewind the spool
oh
kay 1 is wrong
okay they alll correct but 1
how do i reverse the direct of the spool motor
Switch the FWD with rwd for that motor
i did that
And it didn't fix it
I'm never tried this test command before so I'm not sure
Theoretically that should have worked that's how mine are
Yay
Perhaps it's time to run the calibration utility again?
Not sure
Or just try to load
You know you like yolo
its like the spools are 2 heavy for the wheels to spin in the direction to respool
Try changing the position
we didnt change anything from the last time i did
ive tried them all
It they're not slipping they just don't have enough power to turn?
Damn I'm not sure what to say are you using the motors you had from smuf
wheel ditters
The wheel supposed to jitter
I'm just wondering what voltage and what RPM your motors are
Can you take a video
Of them working perhaps so you can see what you mean by the jittering
I can try to see if I can make mine run that command and do a video of mine
I'm thinking mine are 500 RPM 12 volt
I mean I can post the link to where I got them from Amazon if you'd like
I don't have enough experience to know otherwise so perhaps Jimmy John might
yeah he sai di had to up it more
i cant tho because the macro has to change
and idk what to change i was waiting for him to respond
It looks normal to me
Maybe I'm high
I'm trying to make a video of mine but I can't record on this phone and operate the printer at the same time
So I'm trying to charge a device quickly
yeah it spins forward
well its trying to rewind, just more of an FYI we have been working on updating the logic to help with getting the spools moving better. This may help your situation as well.
do longer lane moves greater than -200 spin them better?
they all do the same thing
the weird thing is me and plump have pretty much all the same parts
There's no chance that you're 30t gear is slipping on the shaft
I'm just I'm at a loss I don't know otherwise
it spinds forward fine
@radiant reef what do i have to change to go above 1?
yeah i pushed them all to 1
What happens if you set them to 1.1
you can change them greater than 1, just gotta do it manually in the config
I think the calculation kinda maxes out at 5 for reverse
Me too LOL
oh wtf
That don't sound good LOL
it worked then it stopped
Here is the math I did for those fields the other day #boxturtle message
soo max is 2.1?
1.5 helped alot
it didnt work after the first time tho
oh yeah
2 was the key
i can go both ways now
is there a rewind speed?
how am i supposed to unload the filament when it doesnt reverse the extruder motor
so the box turtle can pull it out?
use BT_LANE_EJECT to remove it
i thought i tried that macro
its not spinningthe extruder also
its not even trying to cut
oh if the lane is loaded to the toolhead you need to use BT_TOOL_UNLOAD
@radiant reef something is wrong
when i use lane eject it does not spin my extruder also
it also doesnt stop
soo this filament has a bump in it now
and i cant get it to let go of the filament
the onyl way to stop this is to estop
what are we looking at here?
i keep clogging
idk why
its like the extruder on the printer and the extruder on the box turtle are fighting one another
check your turtle neck to make sure its detected correctly
it does
hmmm,
plump said maybe i have to calibrate the roational distance on the extruder in the box turtle?
it out all the way
is this backwards?
i would assume expanded would be triggered
i thought this was correct before
sucked back in
i think i might be wrong about what i said lol
Yeah those are backwards
ty ill fix that and try agian
Its written up here as well on how you should see it https://www.armoredturtle.xyz/docs/boxturtle/initial_startup/05-additional-tests.html#turtleneck-buffer
ty
is it acceptable to switrch the pin in config or should i just switch the plug
switching it in the config is easier, dont see a problem with that as long as you remember why it was done
gotcha
i think ima just switch the plug
so im like everyone else
less confusion later on if i need to get help
fair
also does the print 4 the serial have to be 4 colors?
yes
kk
It runs prep to initialize AFC, also what syntax is wrong?
it needed a space
infront of enable
atleast it was for me and plump when we compared
but then the false doesnt show correct syntex
like it does everywere else in my config
its blue not red
when i added the space it turned it red
So
Klipper should error if there is a space in front of the enable
Normally does not like the space
Coloring syntax really should not make a difference, but π€·ββοΈ
it doesnt
but i also put false and it still preped my lane
with and without the space
which wheel?
Jimmy, the error I was complaining about in the past is happening to him
When we thought it was cause I was hitting emergency stop
It then ejects the filament slowly and locks up klipper and the pi
my tube is 2meters long this takes years to do
What are the states of your sensors before you restart klipper?
i just stopped a print
Sorry oc video chat with noodle and can't voice to text
I'm always afraid to restart klipper by hitting save_config
I'm on old software noodle is on new software
Send code...
11:43 PM
E _ _ _ _
R |_|_|_|_|_|
R | \____
O | \
R | |\ X |
! \_________/ |___|
Turtle_1
11:43 PM
lane4 tool cmd: T3 LOCKED AND LOADED
11:43 PM
lane3 tool cmd: T2 LOCKED AND LOADED error in ToolHead.
Lane identified as loaded
but not identified as loaded in extruder
11:43 PM
lane2 tool cmd: T1 LOCKED AND LOADED
11:43 PM
lane1 tool cmd: T0 LOCKED AND LOADED
11:43 PM
'Box Turtle' Turtle_1 Prepping lanes
11:43 PM
AFC Version: v1.0.11-1404-83fb073
11:43 PM
Klipper state: Disconnect
11:43 PM
SAVE_CONFIG
11:40 PM
Beacon model offset has been updated, new value is 0.01000
You must run the SAVE_CONFIG command now to update the
printer config file and restart the printer.```
is there any way to stop this from happening? i can replicate this issue everytime now
it happens to every lane
Still don't understand how you guys keep finding this problem π
your tellin me
this is my life
i always find the issues lol
im also super confused as to why my prints keep coming off my bed but that isnt a turtle issue -.-
wondering if its related to me having to update?
rule of thumb don't update klipper stuff unless you really need something from that update π
oh ive learned that the hardway
lol
i more or less just use it as a way to know i need to update
So you are saying right now that a lane is loaded into your toolhead?
lane2
ill get the error
i was going to load lane 2 yes
i can load it then restart
so you can see
ah ok I see, so in your AFC/AFC.var.unit file change lane2 tool_loaded: True to tool_loaded: False
did you by chance start loading lane 2 and then restart your printer or something, lane 2 is in a weird state. But something that I have been meaning to update so hopefully these weird states dont occur
i did at somepoint yesterday
upload your klippy.log
Yeah restarting your printer while it loads can cause the states to become weird
i mean you told me id get this error yesterday
ok
still doing it
i just updated it
oh it should be lower case false tool_loaded: false
kk
that fixed it
soo when i load it now
and then save/restart
that shouldnt happen?
hopefully it does not error out....
but after your load it capture your AFC.vars.unit file before restart
capture after the load is successful
kk
atleast my cutter and load routine works π
pooper doesnt work yet either -.-
i need to fix the distance
for purging
its started the load
so is a lane supposed to be loaded?
hmm, the file does not show it as loaded
this should be populated as well and its not
I would not think so, if you look now is it updated?
hmmmm, its like its not saving for some reason
should i update maybe?
also maybe i installed the box turtle stuffs wrong when i did it the first time?
lets try this, unload your box turtle completely and then delete the AFC.var.unit file and then restart. Then load a lane and see if that file gets updated,
Then if it does load to your toolhead and see if it gets updated
well just remove the filament from the lane so nothing is triggered
ill reload 2 now
its in the turtles extruder
homing then going to load it to toolhead
after
oh that error may be causing it to not save
yeah but that error is probably causing it to not save, there should be more printouts from AFC
but i know i have top update
i also have ALL the debug stuff turned on
figured that would help
unload your toolhead before restarting and make sure your kick works, you can manually call AFC_KICK to make sure it does not error out
but this shows that we should probably save the file and update variables before calling these macros, something to update in the software
yup
so file looks good as well?
"Turtle_1": {
"lane1": {
"name": "lane1",
"unit": "Turtle_1",
"hub": "Turtle_1",
"extruder": "extruder",
"buffer": "Turtle_1",
"buffer_status": "Advancing",
"lane": 1,
"map": "T0",
"load": false,
"prep": false,
"tool_loaded": false,
"loaded_to_hub": false,
"material": null,
"spool_id": null,
"color": null,
"weight": null,
"extruder_temp": null,
"runout_lane": "NONE",
"filament_status": "Not Ready",
"filament_status_led": "#ff0000",
"status": null
},
"lane2": {
"name": "lane2",
"unit": "Turtle_1",
"hub": "Turtle_1",
"extruder": "extruder",
"buffer": "Turtle_1",
"buffer_status": "Advancing",
"lane": 2,
"map": "T1",
"load": true,
"prep": true,
"tool_loaded": false,
"loaded_to_hub": true,
"material": null,
"spool_id": null,
"color": null,
"weight": null,
"extruder_temp": null,
"runout_lane": "NONE",
"filament_status": "Ready",
"filament_status_led": "#00cc00",
"status": "Loaded"
},
"lane3": {
"name": "lane3",
"unit": "Turtle_1",
"hub": "Turtle_1",
"extruder": "extruder",
"buffer": "Turtle_1",
"buffer_status": "Advancing",
"lane": 3,
"map": "T2",
"load": false,
"prep": false,
"tool_loaded": false,
"loaded_to_hub": false,
"material": null,
"spool_id": null,
"color": null,
"weight": null,
"extruder_temp": null,
"runout_lane": "NONE",
"filament_status": "Not Ready",
"filament_status_led": "#ff0000",
"status": null
},
"lane4": {
"name": "lane4",
"unit": "Turtle_1",
"hub": "Turtle_1",
"extruder": "extruder",
"buffer": "Turtle_1",
"buffer_status": "Advancing",
"lane": 4,
"map": "T3",
"load": false,
"prep": false,
"tool_loaded": false,
"loaded_to_hub": false,
"material": null,
"spool_id": null,
"color": null,
"weight": null,
"extruder_temp": null,
"runout_lane": "NONE",
"filament_status": "Not Ready",
"filament_status_led": "#ff0000",
"status": null
}
},
"system": {
"current_load": null,
"num_units": 1,
"num_lanes": 4,
"num_extruders": 1,
"extruders": {
"extruder": {
"lane_loaded": null
}
},
"bypass": {
"enabled": false
}
}
}```
its only in the turtle
not in printer atm
and onyl lane 2
ah I see you were testing your kick
yes
i also changed this from 5 to 45
thinking ill actually have a correct purge
because my toolhead sensor (im not sure which one its asking for) i have 2
is more then 5mm lol
yeah, 5 is way toooo low
guess you missed this at the bottom π¬ https://www.armoredturtle.xyz/docs/boxturtle/initial_startup/03-install-plugin.html
π
soooooooo
there needs to eb a way to stop
when
your filament is gripped in the extruder
i cant stop this
and it sjust fucking my filament
in 1 spot
now ill have to cut 2m of filament
i just have to wait for it to figure out its not moving
its locked in the extruder
and then the file is messed up no
AFC cannot even stop what klipper is doing once the command is issued
well because you successfully loaded to toolhead and the file updated
oh yeah it should say and loaded to toolhead.... π
so file did not get updated for loaded to toolhead because of the long extruder error
kk
do SET_LANE_LOADED LANE=lane2 to force it to be loaded
they are all documented here for reference https://www.armoredturtle.xyz/docs/afc-klipper-add-on/klipper/commands.html
ty
"Turtle_1": {
"lane1": {
"name": "lane1",
"unit": "Turtle_1",
"hub": "Turtle_1",
"extruder": "extruder",
"buffer": "Turtle_1",
"buffer_status": "Advancing",
"lane": 1,
"map": "T0",
"load": false,
"prep": false,
"tool_loaded": false,
"loaded_to_hub": false,
"material": null,
"spool_id": null,
"color": null,
"weight": null,
"extruder_temp": null,
"runout_lane": "NONE",
"filament_status": "Not Ready",
"filament_status_led": "#ff0000",
"status": null
},
"lane2": {
"name": "lane2",
"unit": "Turtle_1",
"hub": "Turtle_1",
"extruder": "extruder",
"buffer": "Turtle_1",
"buffer_status": "Advancing",
"lane": 2,
"map": "T1",
"load": true,
"prep": true,
"tool_loaded": true,
"loaded_to_hub": true,
"material": null,
"spool_id": null,
"color": null,
"weight": null,
"extruder_temp": null,
"runout_lane": "NONE",
"filament_status": "In Tool",
"filament_status_led": "#0000ff",
"status": "Tooled"
},
"lane3": {
"name": "lane3",
"unit": "Turtle_1",
"hub": "Turtle_1",
"extruder": "extruder",
"buffer": "Turtle_1",
"buffer_status": "Advancing",
"lane": 3,
"map": "T2",
"load": false,
"prep": false,
"tool_loaded": false,
"loaded_to_hub": false,
"material": null,
"spool_id": null,
"color": null,
"weight": null,
"extruder_temp": null,
"runout_lane": "NONE",
"filament_status": "Not Ready",
"filament_status_led": "#ff0000",
"status": null
},
"lane4": {
"name": "lane4",
"unit": "Turtle_1",
"hub": "Turtle_1",
"extruder": "extruder",
"buffer": "Turtle_1",
"buffer_status": "Advancing",
"lane": 4,
"map": "T3",
"load": false,
"prep": false,
"tool_loaded": false,
"loaded_to_hub": false,
"material": null,
"spool_id": null,
"color": null,
"weight": null,
"extruder_temp": null,
"runout_lane": "NONE",
"filament_status": "Not Ready",
"filament_status_led": "#ff0000",
"status": null
}
},
"system": {
"current_load": "lane2",
"num_units": 1,
"num_lanes": 4,
"num_extruders": 1,
"extruders": {
"extruder": {
"lane_loaded": "lane2"
}
},
"bypass": {
"enabled": false
}
}
}```
ty jimmyjon
π
how do i stop it from lowering into the poop after it did it
wait you don't like to smush your poop first....
lolol
The kick/brush macros in DEV have been updated to not smash your poop, just have not been moved over to main yet
The way I got around that initially was I just used a starting location about 5 mm further to the right for the kick start location.
not sure why its a sad turtle
i just reloaded it then restarted
getting logs for you now
Because filament was not triggering the load sensor
oh nice π its the sensor in the extruder
no I dont think that will solve it...
you should be able to just remove the filament and then stick it back in
i tried that
the other thing is there is nothing loaded to the tool head
i just realized it says that
did something error out... because your afc.vars.unit file shows lane 2 should be loaded. You can fix that with UNSET_LANE_LOADED macro command
the mysterious breaker and fixer of software π€£
im great at breaking stuff
i have everything done
i just need to get my purge amounts or feed amounts correct
when i feed in from the box turtle
before it does the purge routine
it pushs material out of the nozzle
lower your tool_stn value then
nice i was right π
i was about to test it then the box turtle messed up on me
i just fixed my blobifer π
bigger servo now
you can lower it without restart
meh, get close with guessing and then tune a bit. Kinda what I do lol
fyi, i had a similar issue to yours where the spool wasnt rewinding, i went back and tightend the wheel grub screws and problem solved
is there any walkthroughs on how to setup the kick or purge stuffs to go with it
Damn you make me excited to get back home again I catch the plane tomorrow evening and then I'll be able to help LOL
I really want to install the new software and get on board
I've been going through printer withdrawal this week