#Disaster1234
1 messages · Page 1 of 1 (latest)
Ok, will have you run a bunch of things from the cli first
ok let me get putty up
sudo apt install tree and then cd ~/printer_data and tree -d. I only need the output from tree -d
and tree -d
i did tree-d
can you show me the output?
can you show me the output of tree -d
it should look something like
├── backup
│ └── 20230913T232928Z
│ └── config
├── certs
├── comms
├── config
│ ├── adxl_results
│ │ └── motors_sync
│ ├── AFC
│ │ ├── macros
│ │ └── mcu
│ ├── config
│ ├── config_backups
│ ├── KAMP -> /home/eric/Klipper-Adaptive-Meshing-Purging/Configuration
│ ├── macros
│ ├── plugins
│ │ └── filter_monitor
│ ├── scripts
│ ├── ShakeTune_results
│ │ ├── axes_map
│ │ ├── belts
│ │ ├── input_shaper
│ │ ├── static_freq
│ │ └── vibrations
│ ├── ukam -> /home/eric/ukam
│ └── update
│ ├── config
│ ├── examples
│ └── images
├── data
│ └── backups
├── database
├── gcodes
├── klipper_menuconfigs
├── logs
├── misc
└── systemd```
but obviously different
and run a ls -l ~
and find . -name "AFC*.cfg"
brought me back to >
cd ~ && rm -rf AFC-Klipper-Add-On
ok
So basically right now, none of the AFC stuff is installed
cd ~
git clone https://github.com/ArmoredTurtle/AFC-Klipper-Add-On.git
cd AFC-Klipper-Add-On
./install-afc.sh
answer all the questions..and then run cd ~/printer_data && tree -d again
~/printer_data not a directory
Ok, great. Upload a copy of your printer.cfg
or just grep include ~/printer_data/config/printer.cfg if it is easier
Ok, perfect, it is setup to do the proper includes
yea been fighing with this for probaly two weeks now
edit your ~/printer_data/config/AFC/AFC_Hardware.cfg to reflect the proper serial: or canbus_uuid as applicable. Is your AFC wired up per Github?
Did you restart klipper? sudo systemctl restart klipper
nevermind it jsut showed up
Thanks, one second
Now it popped up[ saying soemthing bout TN2
yes
look at your ~/printer_data/config/AFC/mcu/TurtleNeckv2.cfg
the serial: /dev/serial/by-id/**YOUR SERIAL HERE** part
I dont have the serial Im noit able to flash it
Ok, lets disable it then
ok
in your ~/printer_data/config/AFC/AFC.cfg file, there is a line, probably around line 6 that should look like Buffer_Name: TN2, put a # in front of it. Then also comment out the [include mcu/TurtleNeckv2.cfg] line in the ~/printer_data/config/AFC/AFC_Hardware.cfg
just firmware restart
tried that ..nothing
ok
had to wipe my config away and whatnot
yah, one second
comment out this section in your AFC_Hardware.cfg
#[AFC_buffer TN2]
#advance_pin: !turtleneck:ADVANCE
#trailing_pin: !turtleneck:TRAILING
#multiplier_high: 1.1 # default 1.1, factor to feed more filament
#multiplier_low: 0.9 # default 0.9, factor to feed less filament
#led_index: Buffer_Indicator:1
and the section for [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```
upload a new klippy.log
Your AFC_Hardware.cfg has this in it
[filament_switch_sensor tool_start]
switch_pin = UNKNOWN
pause_on_runout = False
The pin should reflect your toolhead pin where the filament sensor is
Have a turtle in mainsail?
6:29 PM
R _____ ____
E / \ | o |
A | |/ ___/
D |_________/
Y |_|_| |_|_|
6:29 PM
LEG4 EMPTY READY FOR SPOOL
6:29 PM
LEG3 LOCKED AND LOADED
6:29 PM
LEG2 EMPTY READY FOR SPOOL
6:29 PM
LEG1 LOCKED AND LOADED
something like that?
Great!
Don't change anything that we just did, other than when the TN2 is fixed, updating that stuff
not touching a thing
Now you need to look at the AFC.cfg and look at all of the values, and adjust the appropriately.
You also need to look at AFC_Macro_Vars.cfg and adjust the positions to match your printer for anything you turn on. Like if you turn # Park Settings park: True # Enable Park. park_cmd: AFC_PARK then you need to just adjust the corresponding ```#--=================================================================================--#
######### Park ########################################################################
#--=================================================================================--#
[gcode_macro _AFC_PARK_VARS]
description: Park macro configuration variables
gcode: # Leave empty
Position to park the toolhead
variable_park_loc_xy : 270, 310
Height to raise Z when moving to park. Leave 0 to disable
If you want z_hop during toolchanges please set the value in the AFC.cfg
variable_z_hop : 0``` in the AFC_Macro_vars.cfg file
yep, sorry, stray animals outside
all good ...
For right now, you can simple comment out the [include AFC/*.cfg] in your printer.cfg if you don't want to load any of the AFC stuff. I'm out on a business trip the rest of this week, but I'm sure someone else will be more than willing to help out with the next steps
Ok and Again thank you...
Did the filament get ejected when you hit load?
So, when you load it by hand, does the extruder grab it and pull it in further?
hold for a sec let me take a look
If not we'll just need to reverse the stepper direction
ok sorry broke buffer wire resoldering
hub/switch sensor /tool start are all saying empty now
maybe this stuff beyond my skills
do you have filament loaded? if not they should all say empty
LEG3 NOT READY CHECK FILAMENT AT TRIGGER
4:52 PM
LEG3 NOT READY CHECK FILAMENT AT TRIGGER
||==>--||----||-----||
TRG LOAD HUB TOOL
4:51 PM
LEG2 NOT READY CHECK FILAMENT AT TRIGGER
4:51 PM
LEG2 NOT READY CHECK FILAMENT AT TRIGGER
||==>--||----||-----||
TRG LOAD HUB TOOL
4:51 PM
LEG1 EMPTY READY FOR SPOOL``` sounds like its just grinding ..leg 1 has a roll in it
when you are pushing it in at the trigger does the extruder pull the filament in?
no
Yes far right
lanes go 1-4 left to right normally
if you remove all filament. does it PREP cleanly
yes appears to o
FAILED TO LOAD, CHECK FILAMENT AT TRIGGER
4:56 PM
FAILED TO LOAD, CHECK FILAMENT AT TRIGGER
||==>--||----||------||
TRG LOAD HUB TOOL
4:54 PM
LANES READY, HUB NOT CLEAR
4:54 PM
LANES READY, HUB NOT CLEAR
||-----||----|x|-----||
TRG LOAD HUB TOOL
4:54 PM
E _ _ _ _
R |_|_|_|_|_|
R | \____
O | \
R | |\ X |
! \_________/ |___|
4:54 PM
LEG4 NOT READY FAILED TO RESET EXTRUDER
4:54 PM
LEG4 NOT READY FAILED TO RESET EXTRUDER
||=====||=x--||-----||
TRG LOAD HUB TOOL
4:52 PM
LEG3 NOT READY CHECK FILAMENT AT TRIGGER
4:52 PM
LEG3 NOT READY CHECK FILAMENT AT TRIGGER
||==>--||----||-----||
TRG LOAD HUB TOOL
4:51 PM
LEG2 NOT READY CHECK FILAMENT AT TRIGGER```
my thinking is either a) too tight of tension on the guidlers, b) incorrect extruder direction (try inverting dir_pin by adding or removing a ! (opposite of what is there) or c) pwm motor pins are reversed maybe?
that is not a clean prep
that's a dead lookin'turtle 😄
can you post your AFC/AFC_Hardware.cfg file?
and post a picture of your wiring at hte AFC board, and let us know if you wired the switches Normally Open or Normally Closed?
standby
working on osmething
try creating a new file in printer_data/config called test-afc.cfg, contents belwo:
[mcu AFC]
canbus_uuid: ed03c62ed475
[include AFC/mcu/AFC_Lite.cfg]
[filament_switch_sensor trg1]
switch_pin: ^!AFC:TRG1
pause_on_runout: False
[filament_switch_sensor trg2]
switch_pin: ^!AFC:TRG2
pause_on_runout: False
[filament_switch_sensor trg3]
switch_pin: ^!AFC:TRG3
pause_on_runout: False
[filament_switch_sensor trg4]
switch_pin: ^!AFC:TRG4
pause_on_runout: False
[filament_switch_sensor ext1]
switch_pin: ^AFC:EXT1
pause_on_runout: False
[filament_switch_sensor ext2]
switch_pin: ^AFC:EXT2
pause_on_runout: False
[filament_switch_sensor ext3]
switch_pin: ^AFC:EXT3
pause_on_runout: False
[filament_switch_sensor ext4]
switch_pin: ^AFC:EXT4
pause_on_runout: False
[filament_switch_sensor hub]
switch_pin: ^AFC:HUB
pause_on_runout: False
comment out hte include AFC/*.cfg and instead do include test-afc.cfg
then you can easily see the base status of all your switches in mainsail/fluidd with the names, and see if any are change state as you test them (e.g. move the trigger)
if they don't chagne, you hvae a broken wire. if they trigger ''backwards' you may need to invert the pin definition
you can test the extruder ones by removing hte ptfe nad sticking a iece of filament through on the rear side and seeing if it triggers. same for hte hub.
we have to make sure everything is mechanically correct before we try to tackle the software side of things.
👍
now its giving me another errorr ..auto made a back up file I have to mess with it tomorrow or Saturday
Include file '/home/pi/printer_data/config/AFC/AFC/mcu/AFC_Lite.cfg' does not exist
i didn't create a 2nd AFC folder
Hmmm maybe I have a typo
Unknown config object 'AFC'
Once the underlying issue is corrected, use the "RESTART"
command to reload the config and restart the host software.
Printer is halted```
Send main printer.cfg please
I’m away from PC but maybe someone else will spot something
Just sat down, so if you send that I can take a look
Because you commented out the AFC folder you no longer have the aliases to reference.
Be later tonight have to take care of few things tonight I can be back aon around 10pm est. or another day .thanks everyone
try just include mcu/AFC_Lite.cfg instead that line
nope same error ..ill be back on tonight
Zip up printer_data/config directory and klippy.log and send if you get a chance later
Can you zip your entire printer_data/config folder? That zip only had printer.cfg in it
That's better, lemme look here
ok
missing the test-afc.cfg i sent
Yep, hold on Thunder
Please upload this in your config directory
Change lines 11 and 12 of printer.cfg to this
[include test-afc.cfg]```
Remember he needs the afc aliases
oop hold on
Aliases are included I believe
aliases are i nthe AFC/mcu/AFC_Lite.cfg file
They're included in the test file Thunder profiled earlier
Yeah
ping TRG1 used multiple times... excuse me wat
config/printer.cfg:[include AFC/.cfg]
config/printer.cfg:[include AFC/.cfg]
he has it in printer.cfgt twice
on line 11 and on line 1219
OH
Because of the installer
Mike, delete the include on line 1219 near the bottom of your file
No, the installer did it
Nope, we disabled software, but you have all your lanes now
so you see how your triggers are different?
I see 3 lanes loaded
one is empty (good)
the others are detected (not good unless you're holding them)
far right lane
Unload it and see if Trg1 changes
it changesd
Okay, so you have your lanes backwards
4 lane did so the pins are backwards
well, backwards and pins inverted
Wait, screenshot now?
wut
Can you check if 2 and 3's triggers are touching the switches?
Okay, do the switches all change states in Klipper when triggered?
yes
Okay, so you might need to adjust the position of the switches on 2 and 3
That's pretty simple
Or are the legs getting stuck?
3/4 are
Ah, okay
That's going to be a you thing to figure out later on, might need to file the part a bit
Let's move on as long as the switches are working
yep they are
Remove any PTFE between the extruders and hub
After that, insert some filament inthe the back of the extruders and the hub and verify all of those switches are working
All good
Perfect! So now, make sure all switches are in an empty state report in Klipper
After that, change lines 11 and 12 in printer.cfg to this (You can remove line 12 if you please)
#[include test-afc.cfg]```
empty sTATE
Klipper reports: ERROR
Unknown config object 'AFC'
Once the underlying issue is corrected, use the "RESTART"
command to reload the config and restart the host software.
Printer is halted
removed line 12
Okay, do a FW restart
same
klippy.log and screenshot of error
Okay, can you zip everything up and send it again?
Interesting, I don't see any reason this isn't seeing the AFC
Can you do a full host reboot?
Same error
Unknown config object 'AFC'
Once the underlying issue is corrected, use the "RESTART"
command to reload the config and restart the host software.
Printer is halted
ls -l ~/klipper/klippy/extras/AFC*
at a ssh prompt
why you are working on the Im re-printing the TN internal PTFE parts
no rebuilding!
oh trust me I'm not
we're missing AFC.cfg
no?
you have AFC_Hardware.cfg and AFC_Macro_Vars.cfg
but no AFC.cfg
that's the issue
bma@HAVEN:/mnt/c/Users/bma/Downloads/z/config$ find . -name AFC.cfg
bma@HAVEN:/mnt/c/Users/bma/Downloads/z/config$
AFC/AFC.cfg
wrong screen shot
we'll need to create that
cp ~/AFC-Klipper-Add-On/Klipper_cfg_example/AFC/AFC.cfg ~/printer_data/config/AFC/AFC.cfg
do I just run that from putty
yes
did nt like that
screenshot/error please
oh
i'm on an older afc
here download that, then upload into config/AFC
i copied the file over
eventually it will give you an error and let you download klippy.log. send that.
gotcha
Will have to pick back up another time for me but maybe someone else can carry the torch
tn error just poped up
HAPPY TURTLE
no lanes showing but i heard the lanes moiving
HAPPY TURTLE
That is prep at work
Yep
Nice!
been a adventure im sure alot on my end
getting ready to 1st coat on rc cbr 1000 motor cycle 3d print
nothing to do with turtle
big thanks to all
You have time to try loading stuff and verifying stepper direction?
sure
Let's try Lane 1 since it wasn't sticky
Is that the one you tried loading?
Did you push the filament all the way down to the extruder?
yes hitting extruder
Okay, let's reverse lane 4, you will likely need to do all 4, but let's just start there
Change line 94 on AFC_Hardware.cfg from
dir_pin: AFC:M4_DIR
to
dir_pin: !AFC:M4_DIR
So, 4 is loaded?
yes
Okay, let's do lane 1 now
Yep, let's do the far left one
Did you swap before or after?
1 does?
yes
11:31 PM
LEG4 LOCKED AND LOADED
11:31 PM
LEG3 EMPTY READY FOR SPOOL
11:31 PM
LEG2 EMPTY READY FOR SPOOL
11:31 PM
LEG1 LOCKED AND LOADED
11:34 PM
LEG4 LOCKED AND LOADED
11:34 PM
LEG3 LOCKED AND LOADED
11:34 PM
LEG2 EMPTY READY FOR SPOOL
11:34 PM
LEG1 LOCKED AND LOADED
iam now
Once positions are good, you can start trying to change filament
11:38 PM
R _____ ____
E / \ | o |
A | |/ /
D |__/
Y ||| |||
11:38 PM
LEG4 LOCKED AND LOADED
11:38 PM
LEG3 LOCKED AND LOADED
11:38 PM
LEG2 LOCKED AND LOADED
11:38 PM
LEG1 LOCKED AND LOADED
Kick kicks the poop off, so it should be similar to poop iirc
Yep, you'd want to poop on the plate then kick it into the basket
probably a good idea to look through all your macro variables to make sure the values look correct for your printer
Ill do some testing tomorrow night
Whoo! At least we got it loading now
Yep, no more hardware changes lol
waiting on china for leds 😅
Yeah, you got the TN2 to flash, so you can start doing print stuff
yep
got the PTFE tube to fit too
4am comes early so i need to get some sleep...Again thanks for all the help
i have the TN2 serial number copied over and enabled the TN2 stuff
have all the lanes loaded and filament to the extruders
resolved it
nice!
TN2 is lit up
more testing probally tomorow or this weeekend
calling it a nite now woint see the TN2
dead turtle
Whats going on with it?
Everything..can't see any mcus
OK, what was the last thing you did before that happened?
Is there an error or anything?
OK lets take another step back then. Did you reboot because you made a config change?
No change
Do you have any errors?
Well klipper is in an error state so they may not show.
true
Is the TN2 plugged in?
yes
Little green light inside is on?
yes
Mike, can you ssh into the pi and run
ls /dev/serial/by-id
And also please zip up your configs. To me it looks like your TN2 is unplugged (Just from the error)
changed USB plug ... ok got this now 9:17 PM
9:17 PM
LEG3 EMPTY READY FOR SPOOL
9:17 PM
LEG2 EMPTY READY FOR SPOOL
9:17 PM
LEG1 NOT READY CHECK FILAMENT AT TRIGGER```
guess bad usb
Hit T0 and it ran far left and filament got stuck
T0 should try to load the left most lane, yes
So just to make sure im following, you fed the filament in again, then hit T0 to load Leg1?
Where did it get stuck at?
I dont see any filament to the hub
What do you mean?
Its not making it out of the extruder body?
nope
What switches do you have
df2
Is the BB stuck?
I shook the extuders to make sure they were moving around
i manged to push filament to the hub but took some force
I would think it shouldn't be that tight
Do you have the PTFE chamfered? Was it that?
Do you have any more of that PTFE laying around?
If so I would take a peice of filament and see if it has a ton of drag
Is it punching into the side?
Try ejecting that lane.
No.
We need to figure out what is making the filament jam coming out of the extruder
appears to be soemthing wrong with leg1
Im think im going to have to the extruders reprinted for the 3rd time they are all doing the same thing
wait why do you think reprinting the extruders will fix a problem?
Maybe x1c not printing for abs shrinkage...but I'm not sure
but does everything fit correctly in your extruder and you have no troubles manually pushing filament through the extruder without the motor engaged?
no take alot pressure to push it thru
hmm ok
If you are going to reprint, I would suggest just print one and get that working before printing all them again
After sitting here debating on it ..sicne it will be there 3rd time I might just hit up fabreeko and pay htem to print the parts
If all you need is extruder bodies, hmu we can work something out
Buddy is bringing over a 2mm drill bit to drill the holes out so maybe that will help
👍
dril ed out 2 lanes still the same wont even unload filament either
hear the motors spining but that is all
My buddy Ken says hes not sure either what to do
LEG1 NOT READY PAST HUB, CHECK FILAMENT PATH
4:03 PM
LEG1 NOT READY PAST HUB, CHECK FILAMENT PATH
||=====||==>--||-----||
TRG LOAD HUB TOOL
4:02 PM
Extruder below min_extrude_temp, heating to 5 degrees above min
4:02 PM
Tool Change - None -> leg1
4:02 PM
T0
2:54 PM
Unknown command:"BEDFANSOFF"
2:20 PM
R _____ ____
E / \ | o |
A | |/ ___/
D |_________/
Y |_|_| |_|_|
2:20 PM
LEG4 EMPTY READY FOR SPOOL
2:20 PM
LEG3 EMPTY READY FOR SPOOL
2:20 PM
LEG2 EMPTY READY FOR SPOOL
2:20 PM
LEG1 EMPTY READY FOR SPOOL```
maunal push filament thru. Pretty smooth all the way to the hub
What's going on with it this time?
Is there a ball bearing stuck in one of your extruder bodies?
I get locked and loaded ..just keeps pulsating for awhile
then stops
Im now click ing on t0
all i get
dang roll fell off and got damged
LEG1 NOT READY PAST HUB, CHECK FILAMENT PATH
from console
I hear it pulsing but not pulling any filament
correct
can you push the filament in more and it grab it?
Do all lanes do that?
yes all the lanes are dong the same
so I took and long piece of filament ....from trigger and was able to get all the way to the hub
manual
Assume that's with the guidler open?
no guidler closed
You should not be able to push filament from the trigger, through the extruder, and all the way to the hub
so the tension too loose then
Tension too loose, anti-squish too far out, or your motors aren't meshing with the gears
give me a min ill tightend the tension a smidge
You could realistically crank down on them some then back the anti-squish out a smidge
Ill crank them down and back off 1 turn
one turn still digs in pretty good. might 2 or 1.5
i think i have a mix of both 2 and 1.5 on mine
Progress! lol
What'd it to at the buffer? Just stop, or did it make any kind of noise?
like a cranking noise
i unloaded leg 1 the spool never reversed but kick the filament out so I had to rewinfd it on the spool
Eject doesn't run the spooler motors
that make sense
il lsee wha tT0 does again
I must must be missing something for the buffer
Most likely, we can go through that config in a bit because it looks like you're just missing a minor thing there
It doesn't sound like it's trying to do the long move
?
When it reaches the hub it should be doing a single long move but it's pulsing like it's still trying to do a short move
maybe take out the spring ?
That's not a TN2 issue, you should feed through it pretty easily
ok
If you take the bowden off the back of the turtle and feed by hand, does it go through really easily?
hold
You should make it through everything to the tool head without issue
long tube is getting stuck
Where?
im going to ran a new ptfe tube give me a few
Do you have good chamfers on every transition of the ptfe?
found the issue its the inlet of the TN2
That would do it
Yep, run a 2mm drill bit through that
Extrude only move too long (-420.000mm vs 50.000mm)
One sec
looks like I need 180mm
in printer config i take it
Either in your printer.cfg or if you have a separate config for your toolhead board
Kinda figured ok saved
I still need to fix the buffer thing
6:13 PM
Warning: No buffer defined in config file
Can you zip and send your configs real quick?
And while I look at those, try doing a filament load
yep
Well trying too
found some reading material to be more positive ...boy do I need it ..dang ADHD
sorry for the rant
ok
That will fix the buffer warning you are getting
yes sir it did
6:22 PM
R _____ ____
E / \ | o |
A | |/ /
D |__/
Y ||| |||
LEG4 LOCKED AND LOADED
6:22 PM
LEG3 LOCKED AND LOADED
6:22 PM
LEG2 LOCKED AND LOADED
6:22 PM
LEG1 LOCKED AND LOADED
6:21 PM
Box_Turtle Turtle_1 Prepping lanes```
That's one happy looking turtle
snappy is broken in main, I am currently fixing it in DEV
oh really
I saw the Snappy stuff was moved in dev
filament stopped in about same spoit
Is it doing short moves?
no
the pauses were taken out, it might work but I doubt it
Is it a dead stop or does it continue doing other things?
dead stop
And are you able to provide a video of that?
uhh
Oh
Because it doesn't think it ever loaded
Try an eject, it'll make a mess but should pull it out
nope
doing that now
Don't
found a tangle in filament
yep i cut it out
slow moves then stop like 3 or 4
I missed it on video
about same spot though
Take your time
of course
rebooting wont unload
7:18 PM
Print already paused
7:18 PM
HUB NOT CLEAR TRYING TO LOAD LEG1
hmmm
going to reboot again
Is there a reaso nthat the Unload doesn't work
i have to reboot to get it to unload
I believe BT_TOOL_UNLOAD won't work until it thinks it's loaded, however a restart will try to clear all sensors
gotcha
now itsd not making to the hub
didnt touch anything
Im sure you have other things to do. Not going to bother you with this tonight
hub
R _____ ____
E / \ | o |
A | |/ ___/
D |_________/
Y |_|_| |_|_|
7:33 PM
LEG4 LOCKED AND LOADED
7:33 PM
LEG3 LOCKED AND LOADED
7:33 PM
LEG2 LOCKED AND LOADED
7:33 PM
LEG1 NOT READY FAILED TO RELOAD, CHECK FILAMENT AT TRIGGER```
error i just got
probably means trigger is triggered but extruder is not loaded
Can you get a video of the full change up to that point?
whatcha mean full change
Video from the moment you hit T1 or whichever lane, to that point
mighty have a wqork around
Ah okay
were do I set that at
afc_bowden_length in AFC.cfg
is there a ETA for Snappy ?
It's fixed in DEV now
is there a link
I would wait until it goes pushed to main
ok Sorry !
Well i have time anyway.. leg 1/2 was working but now not So ill take hem aprart to see if i see anything
finaly got it too the tool head
WHOO
im think i might print a cube to make sure it prints
at least I can print one color
now i need to look up orca slicer settings
am I stil lable to use better start macro with box turtle
Good place to start. My first print was just 2 first layers from different lanes. Then went to 4 first layers. Then sent the print
Should be able to, just need to add a little to it
Check out https://discord.com/channels/1229586267671629945/1300558899572904090 for link to the github for slicer settings
But your almost there
found it
T[next_extruder]
i found the issue ,,,
put in wrong spot in orca ...
See if i can at least get 1 color to print
M140 S0
print_start EXTRUDER=[first_layer_temperature] BED=[first_layer_bed_temperature] CHAMBER=[chamber_temperature] CHAMBERMIN=50
PRINT_MIN={first_layer_print_min[0]},{first_layer_print_min[1]} PRINT_MAX={first_layer_print_max[0]},{first_layer_print_max[1]} TOOL={initial_tool}```
chanber extruder/chamber no longer heating up
i just added the Print_MiN line
post your updated config.zip and the gcode file you are trying to print
trying 1st print single color chamber no longer heating up or extruder heating up. Using better start macro. Just added the gcode start line in git hub into orcaslicer
did I do that wrong
also the print_start is all on one line
(PRITN_MIN/PRINT_MAX/TOOL are not on separate lines)
M104 S0 ; Stops OrcaSlicer from sending temp waits separately
M140 S0
print_start EXTRUDER=[first_layer_temperature] BED=[first_layer_bed_temperature] CHAMBER=[chamber_temperature] CHAMBERMIN=50
PRINT_MIN={first_layer_print_min[0]},{first_layer_print_min[1]} PRINT_MAX={first_layer_print_max[0]},{first_layer_print_max[1]} TOOL={initial_tool}
;BEFORE_LAYER_CHANGE
;[layer_z]
G92 E0
BTW .. Im using the better print start macro from jontek
that's good
don't forget teh config.zip
print_start EXTRUDER=260 BED=105 CHAMBER=0 CHAMBERMIN=50
PRINT_MIN=166.884,165.156 PRINT_MAX=183.052,184.755 TOOL=0
you have these on two lines
it needs to be on one
(that won't cause your issue though)
I don't see why this should not work
in the interim you can just remove those M140/M104 l.ines in your starting gcode and your chamber should heat up again
ok let me give it a try
Still the same no extruder heating and chamber
just the bed
so the bed may heat up first...
before hte extruder...
wait for bed to get to target
bed already at targeet
@lean zealot wake up and do your magic here 🙂
👍
Alright, lemme download these configs and compare what you had before
Okay, print_start looks okay, did you make changes in Orca to your start gcode other than adding the tool?
No
What does your start and tool change gcode look like?
Okay, that's right
klipper screen after hitting print
chamber used to go to 70 then extuder was heating up at same time
now just stays off
If the bed reaches temp does it kick on the other heaters?
nope
its used too. only thing that changed was the line added in orcaslicer for the BT
Im wondering if something in the Jontek print macro in the printer cfg need to be changed
but im not a program coder
I'm not seeing anything in particular. Is the "Heater Chamber" an actual chamber heater?
no its just a fan
I used to have a PTC Heater but removed it cause it went bad
and not really allowed to talk about that in the voron world
😛
Okay, what I see in the start macro is that it only kicks on everything if the bed is already higher than either your set temp, or 90, otherwise it heats and waits 5 minutes.
yep
if I comment all the turtle everything works normal
other V2 is setup the same way
What do you mean? If you disable all the turtle stuff?
Remove the ; after chambermin
tried that too already
print_start EXTRUDER=[first_layer_temperature] BED=[first_layer_bed_temperature] CHAMBER=[chamber_temperature] CHAMBERMIN=50 PRINT_MIN={first_layer_print_min[0]},{first_layer_print_min[1]} PRINT_MAX={first_layer_print_max[0]},{first_layer_print_max[1]} TOOL={initial_tool}
all one line
Really to start as long as you have the T[next_extruder] in the tool change you can take the initial tool off the print_start. It will just run the T command for the first tool after print_start completes.
TOOL={initial_tool} take this off ?
What did you add that seems to break the print_start? The min max and tool?
PRINT_START EXTRUDER=[nozzle_temperature_initial_layer] BED=[bed_temperature_initial_layer_single] Chamber=[chamber_temperature] PRINT_MIN={first_layer_print_min[0]},{first_layer_print_min[1]} PRINT_MAX={first_layer_print_max[0]},{first_layer_print_max[1]} TOOL={initial_tool}
M140 S0
print_start EXTRUDER=[first_layer_temperature] BED=[first_layer_bed_temperature] CHAMBER=[chamber_temperature]```
what I had before
plus the chambermin=50
If your old routine worked just add TOOL={initial_tool} at the end of it and see if it works.
you can take the min and max off also just run your original print_start and ill look over your macros
didnt like that at all
Error?
Malformed command 'print_start EXTRUDER=260 BED=105 CHAMBER=0 CHAMBERMIN= 50 TOOL=0'
looks like an extra space before tool
Yea its a strange one for sure
that shoudln't matter tho
Its funny about that stuff. If you seperate those params by line it breaks it too.
yes I'd expect that.
My first print failed as i had the extrude length error which I have now changed. However, the BT only started to move the filament half way through the first purge line. These are the last two sections of my start print macro, do I need to change stuff when using the BT? Thanks
Did you pass in the tool number in your print start macro and then call a T(x) before your purge line
no
Is there reference for this somewhere?
This line that I am point to
Here’s an example from my set up #1276754953226027091 message
thanks
those two arrows are the important ones, just need somewhere in your print_start
I think I get it, this line just uses the first colour chosen by the slicer for purge
Well just whats currently loaded until there is a T(x) call in your files gcode
Thanks again jimmyjon711 you are a real star and will definitely go to heaven 🙂
I will give it a go
Is it best practise to pre load a spool or just let the BT do its thing?
I just let BT do its thing and just do more skirt loops if I am not using a prime tower to make sure the last color is gone
It works well, now if I change from PLA to ABS or vise versa I manually do the change
Thanks again, I am being called for food so will try later
Hi again, I inserted T{target_init_tool} into the printer start macro but klipper did not seem to enjoy it and the purge started without plastic. ? I have since had an issue with the lane 2 extruder not getting passed the hub, it did on the first test, I will get back when I have resolved this. Maybe the hub switch.
Looks like its calling macro T which is not valid it should be T(number), you passing in your starting tool correctly from your slicer code?
after hitting print bed heats up and that is all
I think so, I will review. Does this mean I will have to input the tool number everytime? ATM I keep getting this error....."LEG1 NOT READY PAST HUB, CHECK FILAMENT PATH" will this be to do with the buffer? Both the hub switch & the tool start switch seem to be working correctly. If I manually use the extruder it will pass the hub, I suppose I can isolate the buffer to test.
Revert to your working startup g-code then
I would have to remove all the turtle stuff then
Comment out
no just put the print start back the way it was with out the TOOL
just did that
and still sitting on bed heat for more then 5 mins?
yep
whats the console say
your passing chambermin now so its not gonna do anything till the chamber is at that temp
try setting chambermin to 0 and see if everything else starts going
k it will do your normal print start with the purge even though there isnt anything loaded then it should load the lane
but I had it set for the print job to wait until chamber was at 50c before printing
but lets see what happens
ya thats why it was just sitting on the bed temp and nothing else. It was waiting for them chamber to get to 50 before heating the nozzle
I Agree
dang timer to close
did it load and was printing?
No qgl
yep trying now
selected print... but just noticed there is nl filament at the tool head
and just got the TTC again
wow so many messages lol
Ok last message then
nooooo, you're so close
looks like a trsync timeout. Open the klipper/klippy/mcu.py and change these values to this
TRSYNC_TIMEOUT = 0.05
TRSYNC_SINGLE_MCU_TIMEOUT = 0.50
TRSYNC_SINGLE_MCU_TIMEOUT should be 0.5
👍
try that and send it again and see what happens
have to get 4 new rolls Im going to have to rewind all these rolls they loose now
@ivory stone I forgot about updating this you may need to do this in your config as well
yeah don't stop. Iwas just looking at all the new stuff lol.
ok question I loaded a model sliced but tool head has no filament at the tool head will it load it before print job starts or am I missing something
correct it will run your print start then load the first tool then print
ok I just loaded 4 pla roll since the ASA's will have to re-wind
Dang Im determined to get this
you'll get it. final stages now
do i need to ssh for this?c
cant see it in fluidd
yes
this was more complicated then printing a RC 1/8th scale and building it
but that is just me
once you get this one running i bet you could whip the second one out in no time
I have enough printed parts now
set them to 0.05 and 0.5
aight
gonna attempt a 4 colour serial now lol
fingers crossed
just sad i missed bt-007 as went out
keep at it your close
I might try today too if I can get on print today
TTC again
how I felt as I was working towards BT-005 so I understand
yeah, ive just either had timeouts, sometimes not relating to BT even i think, and then the weird doesnt do long move or stalls..... like.... if it wasnt for that itd be fine
what are your SBCs you are using to run?
lol i wanted it so i could name myself Agent BT-007
SBCs?
... yeah, i had the same thought 😄
small board computer ... like a raspberry pi
as the error indicates it can often mean an overloaded host computer or mcu ... cb1s have it a lot
have seen people swap out a cb1 for a cm4/pi4 and all their ttc errors go away
Yeah usuage sits reallyyyyyyyy low
its a modified mks pi
View STM32F401xB,C Datasheet by STMicroelectronics and other related components here.
STM32F402
yeah CB1 is kinda hot garbage, definitely not worth lol
im not sure this is accurate though
stm
red is the printer main board, rp2040 is the toolhead board afaik
and ofc mcu afc, is the afc
perhaps i'm not being clear
those are hte mcus
klipper doesn't run directly on the mcu like marlin does
there's a host computer
mks pi?
i guess so
yeah I wasn't sure how to find out what his is
the board is a modified mks pi WITH a onboard stm
we were talking about it last night
i see
so its a mks pi, with a onboard stm basically
that's what i was looking at/for
same cpu as a CB1 basically
Cortex A53
pi4 uses a cortex a72
yeah I have a feeling it's not enough.
you could try doing things like reducing your microsteps, turning off any webcams
i get it, i do
He needs to run a pi4 or something on top of his current one but I'm not sure how to do that
i'm just relaying what i have seen before as a potential cause
fair
my BT is down to 8 microsteps, my x and y are 16 and my z is 128
thats default values
thats what it is default
try changing that to 32
z should be one of the lower ones lol
my z are 32
maybe its due to the fact it uses the bed to auto home and auto Z etc?
ah
you could always try it and if it doesn' thcange anything, swap it back
automatically
Using tapv2 for my z offset
Dam ttc again
wonder if you can tell the onboard computer to shut up and just connect a PI to usb to control the stock MCU

you got a pi4 and still having issues lmfao?
pi5 won't solve that imo
i got a pi 4 4gb lol..... i aint liking the sound of this if you still got issues 🤣
just after putting the TN2
Are you running cameras as well?
only have 3do nozzle cam and TN2 ..so I juts turned off the 3do Nozzle cam
only 1 cam
Ive got a camera too 🫡
Only one, runs at like 5 fps…. Though…. 1080p
mine 30fps/ 1080p
i set mine to 5 at idle, and 15 when focused
I hate to turn it off since I used it for remote monitoring
i kinda need to be able to watch it sadly
else i gotta stand there the entire time
theres this weird thing where if it fails to load or something, it raises my printbed, up into the purge bucket/wiper thing (since my toolhead is in its park position over the bucket)
and i cant pinpoint why its doing or what macro, since its not my pause macro
guess no printing today
mines printing so ill see if these changes fix it for me
good luck .. i think I have wasted enough time today
i wasted enough earlier today and last night tbh..... so 🤞 this print actually..... completes
I can t even get a print to start
i think im done for today
Ill use the X1c for now to get some stuff printed
and its time for a drink anyway
😀
coffee
any luck ?
it is a hateful error
maybe something else is going on with this printer
not unique to BT
its a crappy error that give no information
I understand that
im thinking soemthing wrong with this printer
I didnt have any TTC until this
maybe there should be soemthing developed
might have been straw that broke camel's back with canbus
have you sent over the canbus debug script output before?
the trsync changes seem to have done it for me so far so.... idk what else could try thats a similiar change
I have ran it before
TTC again Im done for tonight
maybe the pi4 is crapping out
Dont know
I mean with the extra can device
when you have sanity for a moment please run the script above and send output here
everything i would expect to see i see above
so this is one of those canbus sucks times :/
Has he ohm checked the can bus to make sure it’s 60?
don't think so but it'd be good to check wiring andc termination setups
maybe time to get rid of canbus and get anothe NHSB
out of usb ports
I just wanted to clarify that my comment earlier was in no way about you talking to much or anything, was just coming in to see the progress being done and happy to see you working on it. Keep at it! In this game we always have little things in our builds that like to test our limits, that's how we grow and get better at these things keep at it 🙂
i too ran out recnetly - am using a usb hub
plugged into rear keystone outlet and then have box turtle and tn2 plugged into that.
I have a cheap 4 port hub underneath mine as well
yeah I need to do something for mine too lol
No its all good ... i beginning to think I have reached my limit or capability of this stuff ...I mean 1 step forward 20 backwards
that's how it is sometimes, but you can do it don't give up.
gotta change your perspective and believe you can finish it lol
my perspective was yea ii can do this for sure.
if you built a voron you can build this
1st voron was a struggle ..2nd voron was easy
so he's just having software issues now @lean zealot ?
Correct
the timing too close thing
same I had 0 of that, my printer said it once today but a reboot and it never came back lol
now leg1 having issues again
what kind of issues?
hmm
delete the afc.var possibly still thinks something is loaded from the ttl crash
