OK...what did I miss? (latest updates)

first time ever getting a move out of range. This is the first print since updating everything a couple days ago. RO 2 VC500
Octopus Pro mcu version: v0.11.0-198-g33b18fd6 host Version: v0.11.0-198-g33b18fd6-dirty homing, z-tilt even PAM mesh all ran fine. When it went to purge, the purge bead was now back at the left front (??) it started purging the bead...then lifted about 5mm, kept purging (or oozing) and just sat there..... no drag off or return to bed and wipe. then I notices the console was saying move out of range. ????
Move out of range: 9.967 -15.000 4.980 [26.000]
Move out of range: 9.967 -15.000 4.980 [26.000]
Absolutely nothing changed in my config or slicer settings for this print, as it was a repeat part print. So just to check I pulled it up in my slicer and saw nothing odd. So my Q (#1) is did the latest RO updates, move the purge back to the left front corner (pre-update, last part print...it purged at the right front) Q (#2) what might I have done to have the purge start.... lift during purge... THEN hit a 'move out of range' when it should have moved Y+ and Z- to do the wipe klipper log and printer.cfg follows......
4 Replies
ptegler
ptegler2y ago
ignore all the neopixel stuff ...that was me trying to turn on my nozzle light via a macro in klipperscreen
miklschmidt
miklschmidt2y ago
PAM overrides the priming, so this would be PAM related. Try disabling PAM.
ptegler
ptegler2y ago
I went back in and saw a couple extra setting related to PAM config (for use in printer.cfg) so added offsets and optimus_prime: ..... The prime line THEN did not go to the corner, rather it ran a line across the front middle of the print area but not on the bed. It was printing a prime line but elevated like the lift and pull and wipe of the blob prime @Deleted Userkeck any clue what's up?
Want results from more Discord servers?
Add your server