Klipper to Repetier
Hello, i used Repetier with Marlin in the past, then went to Klipper but miss the power loss recovery Reptier saved me from so many times living in Florida..If I already have Klipper setup is it possible to migrate to Repetier front end? or do i have to go with Repetier firmware.
Comments
http://127.0.0.1:3344
in your linux browser (external access needs other ip) to configure server?
This site can’t be reached
127.0.0.1 refused to connect.
is what i get
ps aux | grep tier
show. It should not list server as that is most likely the reason website does not exist. Did you install Repetier-Server correctly? Meaning debian version matching your cpu with root permission?
sudo service RepetierServer status
should also show if server is running or if it has any problems.
ps aux | grep tier
9625 0.0 0.0 9076 2296 pts/0 S+ 10:26 0:00 grep --color=auto tier~
sudo -i
sudo -u repetierserver /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml
starts it as normal process in terminal so you see outputs directly. Post the end so maybe 50 lines before it crashes till end.
all i notice is RepetierServer.xml has a lock symbol on it, not sure it matters though.
export LC_ALL=C && sudo -u repetierserver /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml
that should select correct locale first.
ffmpeg?
cd /usr/bin
export LC_ALL=C && sudo -u repetierserver /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml
and if it starts go to global settings->Timelapse and enter full path /usr/bin/ffmpeg instead of ffmpeg
Hope it is the last issue and it starts then, otherwise you will get a new message where you fail.
export LC_ALL=C && sudo /usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml
then you start as root and can access everything. Then fix timelapse ffmpeg path for later start with service.
Alternatively delete settings.sql but then you loose all global settings you defined:
sudo rm /var/lib/Repetier-Server/database/settings.sql
This type of error is frequently caused by running an older
version of the firmware on the micro-controller (fix by
recompiling and flashing the firmware).
two, is a way to use IFTT for my Kasa TP Link smart plug to power on and off the printer, i did have this working in Klipper so i am sure it is just a matter of adapting the commands.
[gcode_macro POWEROFF]
and the Printer_plug is reached via Ip address
Kasa with ifttt is what I also have. I have it in server defined as webaction with url
https://maker.ifttt.com/trigger/delta_off/with/key/yourIFTTTWebactionKey
If you have it inside klipper I can not help as it is klipper specific. Sure it is a klipper function and does not come from mainsail?
For babystepping we have define
in klipper config. So if you go in our touchscreen interface you should be able to move it. You can modify firmwares(Klipper.xml and change the command if you like a different command executed on babystep.
also, is there a document for klipper specific commands? I was reading some of them and was really confused since commenting out a command in Marlin uses a #, but Klipper uses none and now Repetier uses the # to enable?
IFTTT Solution is quite simple if you know the logic. Actually you need to hava kasa registered there in your IFTTT gui. Then create a Webhook Action that triggers a Kasa action. You get a url that you enter in webhook and every time you call it (even from browser) it will execute it. You need one webhook to enable plug and one to disable it.
Just tested babystepping and it is always accessible in touch interface. It is in status as button "Babysteps" selectable with or without print running.
In RS i added a new Web Action as POST with
@webAction https://ifttt.com/applets/2Zf4a5ke-if-maker-event-power_off-then-turn-on-hornet-3d-ep10-us, in both the URL and POST DATA field and nothing happens. i figured it would be that simple but i guess not.
https://www.repetier-server.com/knowledgebase/web-action-to-control-a-remote-controlled-socket/
it is even done with KASA showing how to do. In @webAction you add the action name as defined in global settings->web actions not a url. Also hope the link is not for your action otherwise everyone can activate it now when you make it public.
No matter what i do, it won't work. I have corrected the link and included the key from the documentation page but still nothing. My guess is it is either being blocked by my router or Kasa removed the ability to trigger it from outside the app. Just not sure how Klipper is still able to trigger it via gcode and just its IP address