Repetier_Support
About
- Username
- Repetier_Support
- Joined
- Visits
- 24
- Last Active
- Roles
- Member, Moderator
Comments
-
Hello. Are you still on windows or is this problem occuring on a pi?
-
Hello. If you used our install wizard for klipper the path will be: /opt/klipper//klippy/extras Please make be aware that those klipper folders are owned by the user repetierserver and the user pi doesn't have read and write permissions, so you hav…
-
Hello. Please select the devices beginning with /dev/serial/by-id or /dev/serial/by-path. Make sure that you always attach the printer to the same port when using the /dev/serial/by-path method For your disappearing issues: Please make sure that t…
-
This method you tried is for repetier-firmware only. However, you can use Geeetechs solution for your machine, see
-
Ok now I could reproduce it. It seems that there is a bug in Slic3r. Unfortunately, Slic3r seems discontinued, so I would recommend you to use PrusaSlicer instead. However, you can try to slice with layer height 0.2, there this error seems to not o…
-
Hello. What slicer and what methods do you use to switch the extruders? Could you provide me a example gcode?
-
Hello. Sorry I didn't understand your issue, could you explain it further for me?
-
We want to display the most exact number possible without rounding, so it can happen that float point errors will be displayed. float point errors are machine dependent miscalculations by the computer itself like the famous: 1+2 = 3.000000000000000…
-
Hello. Currently you can't limit it from Repetier-Server side. But have a look on examples and threads like this on home assistants side: https://community.home-assistant.io/t/howdoi-convert-mqtt-received-value-to-a-2-decimal-place-float/239368/5
-
Hello. Currently there is no support for inches, sorry.
-
Hello. There is A Gcode called M109 to wait until the extruder reaches the target temperature. Maybe you have missed using it?
-
hm strange I cant reproduce it. Could you share your slicer settings with me?
-
Yes, there is kind of. you can set a timer with @setTimer [value] and then wait for it to finish with @waitForTimer [value] So if you want to wait 3 seconds, this is what you want: @setTimer 3000 @waitForTimer 3000@echo "done waiting"
-
Those changings can happen if your printers have the same serial Id. See here for a detailed explanation and solution: https://www.repetier-server.com/knowledgebase/serial-association-changes-on-linux-system/
-
I looked up and if the printer is not connected, timedCalls wont be executed. I will discuss this in the team and will look forward to find a fix for this issue. Until then you can use sleep and a normal call to get the same result.
-
Hello, Repetier-Server should run fine on the P Zero W. Does your Windows installation went into sleep mode while printing?
-
Hello. Yes, alternative servers is project and resource sharing, however, if you have the pro version, you can use the Repetier-Server Monitor to get a combined view of all your printers on one screen. Currently, there is no support for SLA Printer…
-
Hello. Which slicer do you use in which version? You can upload images to https://imgur.com/ and post the link here.
-
Hallo. Nachdem du die STL gesliced hast geh auf G-Code bearbeiten. Danach hast du unten zwei Slider. Stelle den unteren so ein das dieser beim Layer ist bei dem du das Filament wechseln möchtest. Danach drücke auf den Buttnen links nebendran (Letzt…
-
hello. could you provide me your script in your events?
-
Hello. Did you have a look on your end gcode or in the server events after a print? Maybe there is a gcode to set te printer to absolute
-
You can add the FIRMWARE_RESTART command in the printer settings under G-Codes -> Event dependent -> Run on connect. Then the server will restart the firmware after the connection with Klipper was established.
-
Hello. It means that a print started from a SD Card was paused due to a manual command, a specific Gcode in your Gcode file or if a filament output sensor was triggered. Check if you can resume the print in your LCD menu
-
Hello. Is your printer powered off but your Pi isn't? Then that the normal behaviour of Klipper. Klipper needs to restart the firmware if your printer wasn't ready at start to establish the connection
-
Hello Stefan, Strange I can't reproduce it on my system. Which Klipper version do you use? Could you tell me the exact process to reproduce your issue? Meanwhile you could try to update the Server to 1.3.0 and give some informations from the log …
-
I tried a fresh install of Windows 7 to reproduce this behaviour. After installing all updates Repetier-Host worked flawlessy. Was your instance a new install without all updates?
-
Hallo. Steht denn irgendwas aufschlussreiches im Drucker Log?
-
Could you send us the section with the error messages?
-
This error shows clearly that the printers initialised a Firmware Stop / kill due to a security function buildin. Are your temperatures instable? Maybe you got a thermal runaway. However this is not the server log, this is the printer gcode log. yo…
-
I recommend the last acknowledged pos if there was a power loss of the printer. If there is a power loss of the pi itself but not the printer the last send pos however would be more suitable.