#printer hits bed temp then mainsail changes it to 110
1 messages · Page 1 of 1 (latest)
Mainsail doesn't change your bed temp it's a klipper thing
Mainsail is only running inside your browser
Besides a log also send a sliced gcode, most likely you have a small error in there
Ahoi @obtuse pewter!
It looks like you did not provide all the necessary information we need to help you.
Please upload your logfiles and a detailed description of your problem.
For further information see: https://docs.mainsail.xyz/faq/getting-help/discord#provide-information
Note: We only accept .log and .txt files as log files.
@obtuse pewter Please stop deleting your original messages and abandon your threads. If you have found the solution, then just go ahead and say so, maybe with a small explanation what the error was for future reference, and close the post afterwards (top right on the 3 dots)
If you are annoyed by the bot, just read the #readme, but again, this was an issue were we needed the logs. If you want our help, you just have to accept what we are asking for.
A small reaction on if you have understand this, would be nice.
Sure, so far as I know this is the only one I've deleted as it is the only one i've resolved.. Further the issue was with a G29 macro, kiauh macros imported their own macros instead of my custom G29. Their g29 forced a 110 bed temp.
Sure, so far as I know this is the only one I've deleted as it is the only one i've resolved.
Oh, sry, might have got confused from something 🙈
kiauh macros imported their own macros instead of my custom G29
afaik kiauh doesn't set macros itself. Might have come from one of the installations that kiauh can do, but a 110 default bed temp seems pretty strange for an overwrite of a broadly available software, as some beds cannot even heat up that far or loose their magnetic force at that temperature
well I don't know how else that macro would have gotten there but I can assure you it was there in its g29 lol