#Qidi plus4 beacon issues

1 messages · Page 1 of 1 (latest)

stable lion
#

I’m getting an issue with my plus4 after installing the beacon mod and following the GitHub to get it running I will include the logs I have. I’m expecting to turn on my printer and not get this error. I’ve gone through the GitHub and the cfg but don’t see what could cause this. When I get back Sunday I plan to fix it so having any help will be nice as I don’t know what I’m missing.
Links included:

https://github.com/qidi-community/Plus4-Wiki/tree/main/content/bed-scanning-probes/Beacon3D/RevH-Normal

GitHub

Contribute to qidi-community/Plus4-Wiki development by creating an account on GitHub.

delicate timberBOT
#
This post has been closed due to inactivity.

This post has been inactive for over 1 hour and so has been closed. To reopen this post simply send another message.

stable lion
#

Damn benchy I can’t believe you’ve done this to me

jovial crag
#

Maybe check the pinout for the beacon probe against the pinout for the original (electrical diagram)
It's saying pins aren't specified in the config file i think, so the pinout might be different? 🤔

stable lion
#

Maybe? But it’s the revH like the git and the error is for the smart_effector section which was just there in the cfg before adding beacon. I’ll start there when I get back tho just to make sure

delicate timberBOT
#
This post has been closed due to inactivity.

This post has been inactive for over 1 hour and so has been closed. To reopen this post simply send another message.

stable lion
#

Nooooo benchy don’t do this to me

delicate timberBOT
#
This post has been closed due to inactivity.

This post has been inactive for over 1 hour and so has been closed. To reopen this post simply send another message.

stable lion
#

Noooo benchy stawwwwwp

delicate timberBOT
#
This post has been closed due to inactivity.

This post has been inactive for over 1 hour and so has been closed. To reopen this post simply send another message.

stable lion
#

Once again asking benchy to bring me back so I can hopefully get some other options

delicate timberBOT
#
This post has been closed due to inactivity.

This post has been inactive for over 1 hour and so has been closed. To reopen this post simply send another message.

ebon garden
stable lion
ebon garden
#

did you comment out every line or just the section name?

stable lion
#

I tried just uncommenting the pin but that just read klippy not ready until I changed it back

ebon garden
#

Then probably something else in the config wants to have this line present and throws the error

stable lion
#

Hmmm

#

Then I’ll have to search what else needs smart effector to run and see what I can do about it

delicate timberBOT
#
This post has been closed due to inactivity.

This post has been inactive for over 1 hour and so has been closed. To reopen this post simply send another message.

stable lion
#

I looked into that smart effector pin and it doesn’t go to anything else

#

I’m not sure. I’m home and double checking the git wiki now

#

Just went through the wiki I double checked everything in the printer.cfg area where my error is originating from and nothing

#

I’ve done everything there is for there I’m checking his cfg now

#

That pin isn’t specified anywhere else in the cfg’s

stable lion
#

this is now solved,

#

## [smart_effector]
#
# z_offset = -0.090

#

this is at the bottom of you .cfg file, deleting it removed this final error and it is running. I will not close this yet as I haven't calibrated yet and may come into another issue

stable lion
#

I have come into another issue but it is just mesh max. I will update this when that is complete and close this thread for anyone in the future who stumbles upon it

delicate timberBOT
#
This post has been closed due to inactivity.

This post has been inactive for over 1 hour and so has been closed. To reopen this post simply send another message.

stable lion
#

Update: the mesh max with my specific mount is 270x270. After you finish initial install delete smart_effector and z offset lines you see above located at the bottom of the config, other than that follow the wiki and the beacon quick start guide