Git Product home page Git Product logo

Comments (16)

Arksine avatar Arksine commented on July 17, 2024

Please attach moonraker.log. Its possible that you are using a pin that is reserved by another program (sysfs, or possibly Klipper itself). Moonraker must be able to gain exclusive control over the pin.

from moonraker.

jonathanoeijoeng avatar jonathanoeijoeng commented on July 17, 2024

Thanks for your reply.
Herewith log file for moonraker

moonraker.log

Thanks

Please attach moonraker.log. Its possible that you are using a pin that is reserved by another program (sysfs, or possibly Klipper itself). Moonraker must be able to gain exclusive control over the pin.

from moonraker.

Arksine avatar Arksine commented on July 17, 2024

Thanks. Unfortunately the log file does not contain your attempt to configure with the [power] item enabled, so I am unable to determine what caused it to fail. You'll need to reproduce the error, then get the log without rebooting the Pi as a reboot deletes everything in the /tmp directory.

Just to verify, you aren't trying to use the Pi's gpio17 in Klipper are you?

from moonraker.

jonathanoeijoeng avatar jonathanoeijoeng commented on July 17, 2024

I dont know whether I did reproduce the correctly but this the log I got before I reboot it.
Regarding to GPIO 17, yes, I intend to use that pin, the same pin I use when I use octoprint before moved to fluidd.
Any concern? I dont mind to change to other pin if needed.

thanks so much

moonraker.log

Thanks. Unfortunately the log file does not contain your attempt to configure with the [power] item enabled, so I am unable to determine what caused it to fail. You'll need to reproduce the error, then get the log without rebooting the Pi as a reboot deletes everything in the /tmp directory.

Just to verify, you aren't trying to use the Pi's gpio17 in Klipper are you?

from moonraker.

Arksine avatar Arksine commented on July 17, 2024

Unfortunately the [power] plugin is not configured in that log either. You will need to add the [power printer] section to mooraker.conf, restart moonraker, then grab the log before you reboot the Pi. If moonraker is unable to start you may have to use sftp to do this.

If any other application, such as Octoprint or Klipper, currently has access to gpio17 then Moonraker will be unable to acquire it, this will result in an error. You need to make sure that Klipper isn't using the pin in printer.cfg. If you would like you can also upload klippy.log as well so I can see what your klippy configuration looks like.

from moonraker.

jonathanoeijoeng avatar jonathanoeijoeng commented on July 17, 2024

Herewith the log files.
moonraker.log
klippy.log

btw, regarding to GPIO17. Yes, I was using it in Octopi but it on another micro SD so now only has fluidd in raspberry.

from moonraker.

Arksine avatar Arksine commented on July 17, 2024

Ok, you need to reinstall moonraker. This must be an older installation that never installed the gpiod module dependency.

SSH into the Pi and enter the following commands:

cd ~/moonraker
./scripts/install-moonraker.sh -r -f -c /path/to/moonraker.conf

Replace /path/to/moonraker.conf with the actual path of where the file is located. If moonraker.conf is just in the home directory you can leave it out, ie:

./scripts/install-moonraker.sh -r -f

from moonraker.

jonathanoeijoeng avatar jonathanoeijoeng commented on July 17, 2024

Hi. Thanks for your response.

Just did script ./scripts/install-moonraker.sh -r -f -c /home/pi/klipper_config/moonraker.conf and installed successfully but I found that there is newer version of moonraker available found in UI setting, screenshot attached.
Everything looks good and I uncomment the power section and it freeze again.

Before I send this message, I did update moonraker and it cannot update. Only box with Repo moonraker: Updating Repo... and nothing happen.

Thanks

moonraker.log

klippy.log

image
image

from moonraker.

Arksine avatar Arksine commented on July 17, 2024

The log is showing the power plugin has successfully loaded. With regard to the update, the log doesn't seem to include that request from Fluidd. Sometimes the "git" lock file doesn't get removed properly, however this should result in an error.

SSH into the pi and try to do a manual git pull:

cd ~/moonraker
sudo service moonraker stop
git pull
sudo service moonraker start

If you get an error saying that index.lock exists, you may need to manually remove it:

rm -f ~/moonraker/.git/index.lock

Then you should be able to pull and restart the service.

from moonraker.

jonathanoeijoeng avatar jonathanoeijoeng commented on July 17, 2024

Hi. Thanks so much.
Work very well now and even better you add tab in dashboard to toggle on and off.
Very great work. Appreciate it

image

from moonraker.

dushyantahuja avatar dushyantahuja commented on July 17, 2024

was setting up my printer today with a new version of fluiddpi - and looks like the version of moonraker bundled with fluiddpi doesn't have the power features, not sure why...

from moonraker.

SmoothieAq avatar SmoothieAq commented on July 17, 2024

I have just started with fluiddpi. I had to update Moonraker, but after that Moonraker starts fine with the [power printer] section. However, nothing appears in Fluidd. (sorry, perhaps I ought to report this in the Fluidd rep, but it seems same topics as this issue).
edit: I hadn't read the log properly, I do have an error; I try the pull...

from moonraker.

SmoothieAq avatar SmoothieAq commented on July 17, 2024
cd ~/moonraker
./scripts/install-moonraker.sh -r -f -c /path/to/moonraker.conf

ok, the pull was up to date, but the install script fixed it. Sorry I didn't read before writing...
there seems to be some problem with the current fluiddpi and the update process, that causes the manual install to be needed.

from moonraker.

Arksine avatar Arksine commented on July 17, 2024

Thanks @SmoothieAq for the update.

@dushyantahuja It sounds like fluiddpi was built against an older version of moonraker. Its possible that it didn't have the necessary dependencies required to load the power module (specifically it needs gpiod). I would recommend trying the re-install as mentioned above. Remember to put the actual path to moonraker.conf for the -c option. I'm guessing it is at /home/pi/klipper_config/moonraker.conf, but you will want to check your file system to be sure.

from moonraker.

SmoothieAq avatar SmoothieAq commented on July 17, 2024

Yes it is /home/pi/klipper_config/moonraker.conf
And you can not use a relative path ;-)

from moonraker.

dushyantahuja avatar dushyantahuja commented on July 17, 2024

from moonraker.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    šŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. šŸ“ŠšŸ“ˆšŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ā¤ļø Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.