#mainsail keeps spamming no sd printing in console

1 messages · Page 1 of 1 (latest)

thorn bridge
#

Can you make a screenshot? I am not sure what you mean

sinful grail
#

also how to solve this ?

thorn bridge
#

That is really strange, never seen that

#

The second one shows that you somehow deleted your moonraker.conf

sinful grail
#

is seems something like a m27 command of marlin

#

must it be in the printer_data folder or in klipper_config

#

all my other files are in printer_data/config

thorn bridge
#

That depends when you setup and when you updated

sinful grail
#

iam on latest version

#

of everything

thorn bridge
#

Then it looks like the script of moonraker fails in that update

#

How was that system setuped

sinful grail
#

via mainsail

thorn bridge
#

Mainsail is a web GUI … Do you mean MainsailOS

sinful grail
#

yes mainsailos

thorn bridge
#

Ok open the machine tap and tell me the distro version

sinful grail
thorn bridge
#

Ok that’s an old install, where the moonraker update script should have generate symbolic links

#

SSH in the pi cd printer_data ls -l

#

Make a screenshot of the output

sinful grail
#

ls-l command not found

thorn bridge
#

There is a space missing sorry

#

ls -l

sinful grail
thorn bridge
#

Ok so no links anymore. That’s not normal for a 0.7.x distro

#

I guess that the moonraker service still looks in klipper_config

#

How educated your are in modifying files direct on the PI?

sinful grail
#

if you want me to lets go

thorn bridge
#

I try to find out what the better way would be. We either need to modify multi service files and check stuff. That is at least 1h of work going back and forth. Or you flash a new SD with MainsailOS 1.0.1 and install klipperScreen, the telegram bot and pgcode after that

#

Before a new SD you need to save the config/ gcodes/ and database/ folder to your PC

sinful grail
#

if you tell me the commands the multi service files edit would be better realy installing the sd again is not my favor

thorn bridge
#

As I am not sure how you come to that situation I am not sure if we end up with a new SD anyhow

#

But let’s see what we have

sinful grail
#

this sh.t happend when there was a update that changed the configfile dirs to printerdata

thorn bridge
#
ls -l
cd ../systemd 
ls -l```
#

Do not blame us blame moonraker

sinful grail
#

i dont blame anyone realy faults can happen 😉

#

but that update screwed up all this

#

ok lets go sir i will do the commands

thorn bridge
#

cat moonraker.env

sinful grail
thorn bridge
#

Ok there is the first problem

#

nano moonraker.env

#

Now you are in an editor

sinful grail
#

ok

#

done

thorn bridge
#

Change the line to MOONRAKER_ARGS="/home/pi/moonraker/moonraker/moonraker.py -d /home/pi/printer_data"

sinful grail
#

ok to what

thorn bridge
#

See my line

sinful grail
#

then save exit ?

thorn bridge
#

CTRL key X

sinful grail
#

done

thorn bridge
#

Then y return

#

Perfect

#

cat crowsnest.env

sinful grail
#

that looks good

thorn bridge
#

Good that’s correct

#
ls -l
cd ../config
cat moonraker.conf```
sinful grail
thorn bridge
#

Ok first stuff should be ok now do a reboot

sinful grail
#

reboot done

thorn bridge
#

And is the orange message gone?

sinful grail
#

yep its gpne now

thorn bridge
#

Good first thing solved

sinful grail
#

👍

thorn bridge
#

Now open your printer.cfg in mainsail

sinful grail
#

done

thorn bridge
#

That works also and you do not see a read only behind the name?

sinful grail
#

no

thorn bridge
#

Perfect

sinful grail
#

i think

thorn bridge
#

It would look like

#

So yes it works

#

Ok is your virtual so card only defined in your mainsail.cfg or also in your printer.cfg?

#

Or let’s make it easier send me the klipper.log please

sinful grail
#

in the 2

thorn bridge
#

Ok please remove one, personally I would remove the one in the printer.cfg as that not specifies the error Goode

sinful grail
#

done

thorn bridge
#

At the moment it depends where your include of mainsail.cfg is, is it above virtual_sdcard in your printer..cfg the printer.cfg wins if it is below mainsail.cfg wins. That’s the reason why I ask for only one

#

Ok now restart klipper

#

Is your first problem still there?

sinful grail
thorn bridge
#

Ok I need the Klippy log

sinful grail
thorn bridge
#

Could it be that you never had [include mainsail.cfg] in your printer.cfg

sinful grail
#

i dont know

thorn bridge
#

Yes it looks like that

#

From the log it seams that everything even the PAUSE/RESUME/CANCEL_PRINT macros are in your printer.cfg

#

Ist that correct?

sinful grail
#

yes

thorn bridge
#

Ok then my last advice was wrong. Copy the virtual_sdcard information back in your printer.cfg

sinful grail
#

done

thorn bridge
#

Restart again the error message should be gone (by the way I am only guessing what it says 😉)

sinful grail
#

only restart klipper back ?

thorn bridge
#

Yes

sinful grail
#

yes error gone

thorn bridge
#

Good is your initial problem still there?

sinful grail
#

the sd thing you mean

thorn bridge
#

Yes

sinful grail
#

that starts when i stop a print

#

but it think it is gone

#

but why do i have 2 klipperscreen.configs?

thorn bridge
#

I do not know, it’s your printer

#

The one with the capital K would be KlipperScreen default version

sinful grail
thorn bridge
#

yes it says your default thats like SAVE_CONFIG in klipper

sinful grail
#

a ok did not know

thorn bridge
#

open the other one what you see in that

sinful grail
#

you sayed there is mainsail 10.0 im still on 7

thorn bridge
#

Mainsail 1.0.1 not 10 😉 . There are 3 differences:

  • it uses bullseye (Debian 11) instead of buster (Debian 10). Buster is end of live will still get updates but we do not know how long
  • it has integrated the complete printer_data structure so that problems like yours should not happen
  • the mainsail.cfg is now a own git repository so that every user can benefit from improvements in that area

In reality you are 1 release (and 1 bug fix) behind as we jumped from 0.7.1 to 1.0.x as bullseye is a major step

sinful grail
#

can i just update to it so that iam not behind

thorn bridge
#

guy you drive me nuts, sure you can but than we waist the last hour fixing all the stuff

sinful grail
#

i didnt know that going to new version needed a total new install i tought i would be just a commandline and it would update...

thorn bridge
#

as said:

  • backup /config /gcodes/ database folder to your PC
  • flash a new SD with RP Imager
  • copy the files from the 3 folders back Do not copy the moonraker.conf
#

Then you are done

#

Nope that a Images to setup a system. That is a one time task. There is no official way to switch from buster to bullseye. That is something that is not supported by the raspberry Foundation

#

we can setup the mainsail repo thats not a big deal but you do not use it at akll currently. But what we can not fix is the jump from buster to bullseye

sinful grail
#

ok i will stay on buster for a while then till maybe there will be BIG changes in the bulleye where i would benefit from

#

maybe 2 other questions

#

do you know how i can stop the telegram thing to stop making time elapses and trashing my sd card ?

thorn bridge
#

Sorry I do not use the bot

sinful grail
#

@thorn bridge the spamming problem still there sorry to report you back so late

thorn bridge
#

Switch of your bot

#

I really believe your problem is there

sinful grail
#

@molten sandal

thorn bridge
#

As said stop the bot and check if the problem is gone. And please do not tack random people

sinful grail
#

Alexz if it was the bot then alot of people would have the problem,also it worked before in combo with mainsail so why would it now be a problem?

#

maybe octoprint i install is messing with mainsail because i also install octoprint on my py to test some things and it is still on it, maybe mainsail read a config file of octoprint maybe can that be uberhaupt?

#

when i read on internet for sd printing byte text then it points to m27 gcode command

thorn bridge
#

Same argument would be true for mainsail, that is used much more than the bot😂

#

No mainsail reads no config file from octo. So if you suspect your gcode than send that gcode.

#

It’s a simple fact that Klipper does not send a message like that by default and the console reading you see is not generated by mainsail for sure.

#

It’s also extrem hard to debug a problem if you get feedback only once a week

#

Switching off the bot is a simple yes/no test.

#

But if that message is while you print through octo than that would be explainable

sinful grail
#

turned bot off problem still there

hallow jackal
#

this output is for octoprint to update the print progress

sinful grail
#

that was what i was thinking but why does it appear on mainsail

hallow jackal
#

because mainsail is a klipper gui and display all from klipper

#

so octoprint send a gcode to klipper to report the print progress. klipper respond with this via console -> mainsail display this console

#

octoprint works komplettly different as the moonraker based guis like mainsail. its the worst case to control/connect klipper with both systems at the same time. in this way you have to expect negative effects on both sides. i would recommend you to simply decide for one direction.

#

if you don't want to make a decision, you have to expect negative things.

sinful grail
#

whats the command to delete octoprint and all of its files completly?

hallow jackal
#

how do you install it?

sinful grail
#

thru kiauh

#

so deleting it in kiauh deletes octoprint totaly ?

hallow jackal
#

should be enough