Repetier
About
- Username
- Repetier
- Joined
- Visits
- 2,088
- Last Active
- Roles
- Administrator
Comments
-
I never did this by I think your problem is this: "beacon: klipper or klippy env doesn't exist" You must activate correct klipper environment. For server the klipper installations are all in /opt/klipper/ I guess after activating the env it would …
-
Can you make a screenshot from the position you mean so I also see which user interface you are using. The normal interfaces do not show it in condensed info bars and show it only on detailed views e.g. main ui in right sidebar under temperatures or…
-
Gruppen must du vorher erstellen - das sind keine Ordner nur eine Zuordnung. Du kannst keine Ordner beim Upload angeben. Nur den Namen unter dem sie in der Gruppe erscheinen soll. Wird demnächst etwas gelockert aber du must weiterhin dann das Verzei…
-
I can not say much since we are not producing the printer and firmware, so can not say anything about connectors and touch sensors working. The missing M80 is no problem as said and you did not show communication log around the halt message which mi…
-
M80 - Turn on power supply You can ignore that it is not supported. Your printer has no switchable power supply so does not need that command.
-
Sorry, there is no official list.
-
Normally I would expect linux to support the hub and show all devices on it. You can always see it in syslog if there is a problem. Easiest solution is to run tail -f /var/log/syslog and then connect extra devices. You see then if linux disconnects …
-
This is an error from your printer firmware. Disable easy mode so you see communication at the bottom. I hope for you that you see the reason why printer firmware stops running. Typical reason is an error with heaters ot temperature sensors which ca…
-
So you are using the printer on the same device as with octoprint? Our image (assuming you use raspberry pi) uses latest raspbian os so I would expect it to show all visible serial ports. Some printers require the printer to be powered to show usb p…
-
primt ... sollte das nicht print mit n sein? Sicher das da kommas am ende stehen sollen? Ist das nicht die yml Datei? Mein beispiel war ja json format. Bin aber auch nicht mehr ganz firm mit HomeAssistant was Syntax angeht. War froh es damals rausbe…
-
Möglich, du schreibst value_json.time/1000 aber wie ich geschrieben habe ist die gesamte Druckzeit value_json. printTime und die ist dann schon in sekunden. Bedenke auch das der Wert nur definiert ist wenn ein Druck aktiv ist.
-
Im MQTT Explorer siehst du die definitionen die existieren in Homeassistant/sensor zum beispiel. Beispiel für ete: { "device": { "name": "Felix", "sw": "Repetier-Server 1.4.11", "manufacturer": "Hot-World GmbH & …
-
Du must dich mit dem MQTT Server verbinden nicht mit Repetier-Server. Im Grund die gleichen Daten wie im Server zum Verbinden mit dem HomeAssistant MQTT Server eingeben.
-
You see it connected when port is opened independently of success for real communication. Typical baud rates are 115200 and 250000. In rare cases it depends on RTS/DTR end level. If you disable easy mode and disable all filters you see if there is …
-
Data is send as body content. So should be the same as your curl example, also we do not use curl. Did you check server.log for error messages from send? Which solution do you use for sendinf? webaction or computed expression http_post or http_pos…
-
Du kannst die Entity leicht selber einfügen. Nur die wichtigsten sind über discover vordefiniert, aber es werden viel mehr Infos angeboten. Wenn du mit MQTTexplorer zum Beispiel die Daten testest siehst du das unter state//basics im json ein Feld pr…
-
Ping-Pong, buffer size etc on server side will not help I think. The message you get causing fatal error which is important is: Recv:22:40:43.589: // Lost communication with MCU 'mcu' Here mcu is the printer board and the message comes from klipper…
-
Er nutzt Klipper wozu der Server aktuell lokal installiert sein muss. Voraussichtluch mit Version 1.5.0 die als nächstes kommt unterstützen wir auch Klipper Drucker über das Netzwerk, wenn sie die Onlinefunktionen über Moonraker zur verfügung stelle…
-
Last 3 devices are all the same, 2 are just links to the real device. With mk3 you must have main power enabled, but when you see lcd I assume you have. Also in prusa settings rpi must be turned off so it uses usb connection for communication. Enabl…
-
@make_snapshot is for making timelapse videos. Only direct solution to get messages with webcam image is using push messages with push over as receiver. In push message config you can select to also send a webcam image with the message for it.
-
Im Server das invertieren betrifft nur die Pfeile, aber was die Firmware macht ändert sich nicht. Und es macht nur sinn wenn die Firmware bei positiven E werten extrudiert, sonst kann man nicht mehr drucken auch wenn er im Server dann korrekt herum …
-
Das ist Sache der Druckerfirmware. Wenn der Stecker es erlaubt reicht es aber auch den Motorstecker um 180 grad zu drehen.
-
Ja das ist fast der maximal mögliche negative z Wert für int32 Zahlen. Es wird nichts ungewöhnliches gesendet vom Server, davon kommt es also nicht. Ich denke es kommt hierher: Send:21:38:52.348: N60689 M400 ; wait for finnised movesSend:21:38:5…
-
Did you have logging active to see afterwards which commands get send. What wonders me is M501 especially after homing. Normally you should not fiddle with firmware settings during print, can have negative results if it changes sizes. After all you …
-
If it happens after the print I would guess it is in the after print gcode hat it want to go down, so you should check that code if there is a command that would cause it under some conditions. It is a bit strange that it went away after restart. Wo…
-
Config can not fry them only if your current is too high I'd say. Maybe make sure ALWAYS_CHECK_ENDSTOPS is disabled. In this case cross talk can only make problems during homing. Also check with M119 if an endstop is high. Moves in endstop directio…
-
In install_dir/firmware/marlin.xml the command for babystep is defined like this: M290 S{f:babyz}Reading current doc https://marlinfw.org/docs/gcode/M290.html It can modify probe offset depending on BABYSTEP_ZPROBE_OFFSET when you compiled marlin. …
-
Logging in RepetierServer.xml is only for server.log. For logging of printer connection go to printer and in printer menu select logs and there you can activate it for next prints. Logs appear in same window for download then.
-
Could be that you have cross talk to z end stop causing early trigger. Use a host software with console and send M111 S71 to enable endstop debugging. Note that this can crash firmware so use that flag only for testing if it is z endstop. Then home …
-
The main reason for babysteps is to change z without changing official z. It is not directly connected to z probe offset. If that offset is changed or how depends on the firmware you are using and maybe even the version or configuration.