Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ultimaker 2 - Octolapse not working (Stabilization ERrOR + G21 ERROR) #624

Closed
TomyVertigo opened this issue Nov 11, 2020 · 39 comments
Closed
Labels
duplicate possible resolution A non-confirmed solution exists for this issue. It may or may not be available on the master branch

Comments

@TomyVertigo
Copy link

TomyVertigo commented Nov 11, 2020

Octolapse v0.4.0

OctoPrint Version 1.4.2

plugin_octolapse.log]

I have Ultimaker 2 and slicing with Cura 4.8.0

When I try to make octolapse I keep getting Stabilization Error and G21 error as mentioned in some other posts, but did not get solution how to fix it anywhere. :(

G21 ERROR:
The printer profile requires an explicit G21 command before any position altering/setting commands, including any home commands. Stopping timelapse, but continuing the print.

Thank you.

@TomyVertigo TomyVertigo changed the title Ultimaker 2 - Octolapse not working (Stabilisation EROOR + G21 ERROR) Ultimaker 2 - Octolapse not working (Stabilization ERrOR + G21 ERROR) Nov 11, 2020
@FormerLurker
Copy link
Owner

I need your settings json and other info that was in the issue template. Are you running on a raspberry pi or some other OS? If so, which one and which version. Are you using OctoPi? If so, which version?

However, it does look like the same error I'm seeing in other places and is likely caused by some bad compilation. Try the classic layer trigger and see if that works.

@FormerLurker
Copy link
Owner

See Issue #566

@TomyVertigo
Copy link
Author

TomyVertigo commented Nov 11, 2020

Here you go:
settings.zip

I am running RaspBerry Pi4 8GB. Yes, I am using OctoPi v0.18.

Layer triggering not working. The only thing that is working (with error, tough) is:
Stabilization: Disabled
Trigger: SMART - Snap to print

What can I do?

@FormerLurker
Copy link
Owner

Are you running python 3 or python 2?

You could try to update your distro, then uninstall and re-install Octolapse (you don't have to delete your settings). I suspect this issue is compiler related.

Here is a guide for updating installed packages.. Just run the first two apt updates: sudo apt update and sudo apt full-upgrade.

FYI, this appears to be happening only for some ppl using the PI4, for only some flavors of linux, and on some instances running on MacOs. I've got a pi4 on order, so hopefully I will finally be able to replicate this.

I'll leave this issue open until I hear if the above fixed things for you, then you can head over to Issue #566 for updates. Sound good?

@TomyVertigo
Copy link
Author

FormerLurker, I did as you suggested and it looks like the G21 error is gone, but still facing
Stabilization Error
An unexpected error was encountered while running the timelapse snapshot procedure.

Octolapse is not working.

@TomyVertigo
Copy link
Author

Well G21 Error is not gone all the way:
Octolapse Timelapse Stopped
The printer profile requires an explicit G21 command before any position altering/setting commands, including any home commands. Stopping timelapse, but continuing the print.

Octolapse settings:
Stabilization: Centered
Trigger: Classic - GCODE

@FormerLurker
Copy link
Owner

Yeah, so I think you're still hitting the same issue, which is a problem communicating to the compiled python extension. Maybe I can send an SO file you can drop into the installation folder that I know works. I can grab one off my pi. Will send it soon.

@FormerLurker
Copy link
Owner

Hey, are you using python 2 or 3? It makes a difference, because I need to link to a different library.

@TomyVertigo
Copy link
Author

That would be great.

I am running python v2.7.16.

@FormerLurker
Copy link
Owner

GcodePositionProcessor.zip

put it here: home\pi\oprint\lib\python2.7\site-packages\GcodePositionProcessor.so

Let me know if that fixes it or if your pi catches fire and explodes :)

@FormerLurker
Copy link
Owner

OH, you will need to completely reboot your pi for that to take affect.

@TomyVertigo
Copy link
Author

So... I do completely fresh install of the OctoPi?

@FormerLurker
Copy link
Owner

No, you just copy that file to the path (i recommend sftp, like filezilla), reboot (not just restartin octoprint) and try again

@FormerLurker
Copy link
Owner

If it works, at least it will narrow down what is causing this.. if the same issue happens... Not sure

@TomyVertigo
Copy link
Author

OK. Will do that and let you know.

I really hope this fixes all. :)

@FormerLurker
Copy link
Owner

You and me both... Been working on my new plugin, arc welder, and have been swamped with new issues since the pi 4 and hd picam came out. Would be happy to figure out what is going on

@TomyVertigo
Copy link
Author

I have only home\pi\oprint\lib\python3.7\site-packages\ and there is none file named GcodePositionProcessor.so
Is that OK? Should I put it here?

@FormerLurker
Copy link
Owner

I thought you said you were running python 2??? I'm really confused. you shouldn't even have a 3.7 directory!

Can you search for GcodePositionProcessor.so and tell me where you find it? FYI, something must be up with the permissions because I've not been able to find my copy via the find / command..... As if things aren't already complicated enough :)

@FormerLurker
Copy link
Owner

FormerLurker commented Nov 11, 2020

Ok.. find is .. odd. Try running this from the home folder:

find . -name GcodePositionProcessor.so -type f

That should tell you where the current file is. Then put the file I attached in there and overwrite it.

@TomyVertigo
Copy link
Author

So... there was only file GcodePositionProcessor.cpython-37m-aarch64-linux-gnu so I replace this file.
But,,, when I reboot my OctoPrint there was no Octolapse installed anymore...

@TomyVertigo
Copy link
Author

And now I am getting an Internal server error in Cura.

@FormerLurker
Copy link
Owner

Yeah, that shouldn't have been overwritten i don't think. Not sure what the cura error is.

@FormerLurker
Copy link
Owner

Will get back to yot tomorrow after I sleep and have time to think.

@TomyVertigo
Copy link
Author

No improvement in Octolapse, still facing the same errors.
plugin_octolapse (1).log

@FormerLurker
Copy link
Owner

What steps did you perform since last time??

@TomyVertigo
Copy link
Author

there was only file GcodePositionProcessor.cpython-37m-aarch64-linux-gnu so I replace this file. With the file you send me. I also copied an unchanged file into this folder.

Any other suggestions?

@TomyVertigo
Copy link
Author

@FormerLurker do you think that could be related to 64bit structure of (RaspBerry Pi4) 8GB version?

@FormerLurker
Copy link
Owner

Good question. It is entirely possible. Maybe try a 32 bit version as a test if you have a spare sd?

@TomyVertigo
Copy link
Author

I also ordered 4GB version of RaspBerry Pi4 and will be testing it for the weekend. I want to come to the ground to this problem.

FormerLurker added a commit that referenced this issue Nov 17, 2020
@FormerLurker FormerLurker added possible resolution A non-confirmed solution exists for this issue. It may or may not be available on the master branch and removed need more info labels Nov 17, 2020
@FormerLurker
Copy link
Owner

@TomyVertigo, can you try installing from the plugin manager using this link in the From Url... box: https://github.com/FormerLurker/Octolapse/archive/88aa71f0fbac306b0d9acf19dff7388a30b29b64.zip

See if that fixes it.

@TomyVertigo
Copy link
Author

@FormerLurker this feels like a great improvement, (at least) for now G21 is gone, but full functionality is still not there. Just tried orbit mode and it is not working correctly.

@FormerLurker
Copy link
Owner

I need more info to help you with that. How exactly is it not working?

@TomyVertigo
Copy link
Author

Here you go. Some files regarding the latest Octolapse.
OctoLapse.zip

Octolapse settings:
image

@FormerLurker
Copy link
Owner

Are you familiar with what the 'snap to print' trigger actually does? It doesn't allow the printhead to move off of the part or away from the tool paths at all, so it creates a time lapse that is as close as possible. Try using a fixed position stabilization for that, like back left or something. If you want a true orbit, try using ng the smart layer trigger.

@FormerLurker
Copy link
Owner

I should have mentioned this sooner, but check in the trigger profile setting for the little blue question marks. I have added a lot of info that should explain what each trigger does and how the settings affect them. If i misunderstood your issue, please let me know

@TomyVertigo
Copy link
Author

Are you familiar with what the 'snap to print' trigger actually does? It doesn't allow the printhead to move off of the part or away from the tool paths at all, so it creates a time lapse that is as close as possible. Try using a fixed position stabilization for that, like back left or something. If you want a true orbit, try using ng the smart layer trigger.

OK. I left it from before when nothing else didn't work. I will try now and let you know.

I still get stabilization errors tough.

@FormerLurker
Copy link
Owner

If the stabilization errors keep occurring, I recommend creating a new issue. I recommend running a very small print (calibration cube or something similar) and logging with the 'debug' profile until the error occurs, then you can stop the print and upload the log. Here are some instructions for accomplishing this that should yield a clean log file.

@TomyVertigo
Copy link
Author

Run a few test prints now and no error accourd. Great job @FormerLurker 💯

@FormerLurker
Copy link
Owner

Awesome! Going to close this. If you have any other issues, please let me know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate possible resolution A non-confirmed solution exists for this issue. It may or may not be available on the master branch
Projects
None yet
Development

No branches or pull requests

2 participants