PAM & Optimus Prime
@Helge Keck
Hi, is there a way how to properly set up "Optimus Prime". It mostly works, but it seems it has weak spot at the left front corner of the bed (following photos are examples of postions of print where print itself is repsented by one layer square frame surrounded by skirt)
Hi, is there a way how to properly set up "Optimus Prime". It mostly works, but it seems it has weak spot at the left front corner of the bed (following photos are examples of postions of print where print itself is repsented by one layer square frame surrounded by skirt)
122 Replies
Problematic left front
Ok (moreless) right front
Ok right back
Ok-ish left back
i will test this here
I believe I just missed some cfg. I just don't know what 🙂
with eva no config is needed
it should work by its own
try primeblob instead
Vcore3.1 with EVA 3.1 here
Primeblob almost destroyed fan duct
a primeblob cant destroy a fan duct
it's simply too high
overall, I'm not fan of primeblob exactly because of this
the toolhead should not cross the blob at all
should not, but it does
is this ratos v1 or v2?
v2
please show me your printer.cfg
heh 🙂
give me a moment
download the printer.cfg from mainsail and drag and drop the file into this discussion
this is not a organized printer.cfg
organized?
almost everything on the wrong palce
???
you are including pam, and later other macros that override the pam behaviour
I had to, since your PAM overwrites my PRIME_LINE
then I tried your version of PRIME_LINE
(because the idea is basically the same)
well, my primeline extension is needed for adaptive primeing
no wonder it doesnt work
i recommend to put all hardware related settings before your custom includes
you have stepper condfigs and such in the very end of the file
also, pam must be initialized after your complete mesh config
since RatOS doesn't count on that cfg
you have some mesh entries after pam
anyway, without my priming macro adaptive priming wont work
ok, I move PAM back at the end where is was originally (I moved it before my PRIME_LINE because since yestarday(?) PAM suddenly start to provide PRIME_LINE macro)
eh, how to start
At first I used your PAM only and my (adaptive) PRIME_LINE
but since yesterday PAM overwrites my PRIME_LINE
so I moved PAM before my PRIME_LINE
which worked
well, the new primeline macro is identical to the ratos primeline macro
if you have something specific in it you need to override the new macro
but then I realize "oh, I can use your
optimus prime version and not my adaptive primeline because idea is basically the same - move prime_line close to the print"
so I commented my PRIME_LINE and tried yours
and here I amif you want to use your primeline feature you can do that
just remove the include and use
[pam]ok, pam included as last thing in prionter.cfg and I'll try next attempt now
then you dont have the new macro
I want to try your primeline instead of mine 🙂
That's the point now 🙂
So just to be sure, this should be recommended place of include, right?:
this is enough:
[include pam/ratos.cfg]
[pam]
optimus_prime: True I know, the rest is default values
and
offset isnt used anymoreoh, ok 🙂
so, even with prime blob this works now, the toolhead jumps over the primeblob before going back to the print
Same as before
please show me your new printer.cfg
show me the gcode file please
please try with primeblob
is a bug
will fix
primeblob... I think I got the issue with prime blob
error doesnt happen with primeblob, only with primeline
jsut tested it here
With primeblob, I think I need to modify
toolhead_offset_back(?)no
its a bug
i need to fix it here#
because... well, I have EVA 3.1... but I also have MFBS's "Gaping Maw" back of EVA & his 4028 fan mount
no
i have to fix it here
primeblob too?
primeblob works here for me, its the primeline
I hit the primeblob, that's the issue I have with primeblob
and primeline crossing print itself (which could be bug)
the new tool jumpos over it
i just told you its a bug
at the end, did you hear (and see) it?
thats not a bug
its indeed your toolhead poffset
i mean the documentation tells you this
that's why I wrote this
yes, in the blob caase, but this has nothing to do twith the actual bug we are talking about
and that's why I wrote basically the same few lines earlier
for the momenbt please use primeblob as it works
will fix the primeline thing
nvrmind, is it
toolhead_offset_back I'm looking for (to correctly set the primeblob)?yes
changed cfg to:
and no, primeblob has issues too
the blob itself is created far enough not to interfere with print itself
but when primeblob finishes, the carriage moves over it... and crashes with blob regardles how big
toolhead_offset_back is
(...and continue crashing the bottom of duct because blob is stucked there)please update
If you don't mind, first attempt will be without filament 🙂
interesting...why is the priming semi-centered on the bed and then he goes to near 0,0, to start printing? I though even the adaptive priming kept the prime near the print area, but out of the way based on the offsets.
this is obviously a bug i am working on together with my friend here
that's what I meant.... seems dims are 'wrapping around zero' or something.... if prime is to the left and forward of the print area ...and he's trying to print at zero, zero....
...don't envy you here 😛
primeline with print in the left front corner look like primeline is created directly on/in front of print 😦
directly on/in front ofi am sorry, i dont speak chinese, do you have a photo? however, you dont need to make any more tests i am working on ti thanks anyway
I don't have photo, I'm trying it without filament now (tests with primeblob convinced me to do that this way. At least for the first time)
what do you print? granite?
the crunching and squeaking didn't sound healthy, sorry
hmm, your toolhead design must be extremly close to the bed
a blob is jsut 4 or 5mm high
and made out of hot soft plastic
there's about 4mm clearance
lowrider
it's definitely not hot at that moment, 4028 does it's job
hmm, even less. 3.5mm
and you were asking why not the blob 🙂
i updated the script to respect the offset for the jump
i got no feedback from you
you jsut mentioned the line again
i was updating the blob thing
working on it 🙂
at this moment, I have primeline only (almost worst case scenario)
yes, you showed me that before, but i was working on the blob thing the whole time, one fix after the other
Test with primeblob will be soon
Primeblob
difficult to see from the angle, is it touching the blob or not?
no
ok, now update and try the primeline
plus, show me then the console output, i made some changes here to better understand what happens on your site
you didnt updated the script
or it doesn't show with primeblob
no, you didnt updated the script
its on older version you are showing me here
it tells me
v0.4.0-30-geb9adfc is the latest availablemaybe you got a cached vesion
tr to update again
i believe in mainsail is a minimum time between update thing or something
😛
i cant see the monitor atm
what is this
that's your commit log
i dont knwo what this means
that means the version I should have, wasn't there a minute ago
you dont get me, i mean this is my first day in the internet
maybe too subtile
anyway, can you test please
I'm sorry, if you joking... my english isn't good enough to get if you are joking or not
I guess it means yes 🙂
you want output from timeline or timeblob?
i mean i obviously can see the monitor if i am typing
timeline please
I'm easy target for this 🙂
yeah, i am starting to realize this 😂
and how does the print look
nice
you can turn on Auto Relative Reference Index
i have seen in your config you have a custom safe z home position, would be good to see if that works too
custom safe z home is due to historical reason - about two(?) years ago I've had unreliable Z-homing, so Z homing in the middle of the bed wasn't the greatest idea. Homing in the one of the back quadrant has natural failsafe - if Z homing fails and Z will continue up, it just tilt the bed from magnets
is
Index 8 the closes probe point to your home z position?home z position is X=50, Y=250
easiest way to test it is to set a suqare corner at the point where the home z is, this corner index should be the index
but this looks right
index 8 is in this area
damn, even google translate didn't help
nvm, index 8 is correct
I'm glad I can abandon another piece of my attempts of very similar things (first was "Dynamic BED_MESH_CALIBRATE" in favor of "PAM". Now it is "Adaptive PRIME_LINE" in favor of "Optimus Prime"). Thank you