What is the problem?
Applying a check in the checkbox next to "Auto-connect on server startup" in the Connection side panel does not seem to work for me. The server starts up without connecting.
What did you already try to solve it?
I looked at the ~/.octoprint/config.yaml file and it includes the expected settings under the serial section.
serial:
autoconnect: true
Pressing the Connect button works as expected. What's unfortunate is that I have some pretty good away-from-home ability to control the printer but it's not auto-connecting on startup so that's a drag.
Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, octoprint.log, serial.log or output on terminal tab, ...)
OctoPrint 1.3.8 running on OctoPi 0.15.0
Robo C2
Marlin 1.1.7-C2 octoprint.log (9.5 KB)
There's nothing in the serial.log.
Hey guys. I´m playing a little bit with a few plugins, and between them there is one that powers on or off the printer. When I power off, there is an option that powers off and disconnect, but when it is turned on, it doesn´t reconnect.
I uderstand that this is the expect behavior, and the "auto connect" is for connecting the printer to octoprint when it´s already powered on when I start octoprint.
Is there a way to add a command to a script, to force this connection a few seconds after it´s powered on, once octoprint is already running?
Personally, the script I'd do would probably be JavaScript since that's my preference but I'm thinking that one could create the following shell script.
On the -F thing, I got that one from one of foosel's examples. I'm more of a -d sort of guy myself; I like to just create the body and send it like you did in your last example.
If it freezes from the GUI, then it's either not running (unlikely) or it's running but not returning immediately and it's faking out OctoPrint.
Try adding an ampersand to the end of the command that calls the script. In Bash terms this means "run this in the background".
Well, I´ve already tried that, and didn´t work. Ive found a temporary solution that I´m not proud of, once it´s creepy, but it´s workin for now. When I have more time I´ll investigate a little bit more.
Monitoring the processes, I´ve found that when running the script called from the GUI, curl freezes. I also realized, that killing that process after a few seconds, it works. So, I´ve created a 3rd script, that I´ke called kill.sh and did the following:
I´m not familiarized with raspian yet. Tryed this pkil and worked. It´s stil ugly, but it´s working.
I feel like I owe you a beer for all the help you gave me.
My printer is now almost the way I want. Just thinking about some firmware mods.
:laugh: Don't worry, that feeling will go away when you notice something else that needs to be modded. Honestly, I've completely changed my Robo 3D printer from the ground up. The only software that remains is the forked Marlin but I'll replace that as soon as I figure out how to successfully back that up and can restore it if I want to.
Replaced the TFT menu system with a Conky-based theme
Cantilever stability for the print bed platform
Filament run-out block replacement
Manual print bed leveling addition
About three filament-delivery upgrades from stock
Removed PTFE tubing
Added sound events
Samba
Node JS subsystem
Styrofoam boxing for heat control
Temperature monitoring in the box
Two additional webcams
(Touchless) Alexa control of almost all printer functions
TP-Link power control over printer and the octo-proxy for remotely controlling it
Repurposing the print spool passthrough for the stereo cable
It never ends. I'd like to make a pretty version of the styrofoam boxing but I'm still thinking about how to do this. And I've got the parts in hand for an upgrade to turn it into a 3D scanner as well. It just lacks the time for me to build that out.
I teach software development in case you were wondering. :cheers: