cropduster
About
- Username
- cropduster
- Joined
- Visits
- 26
- Last Active
- Roles
- Member
Comments
-
Auf einem Raspi 3B und deinem Image für Buster. Frisch aufgesetzt und alles erstmal aktualisiert, am Ende die Sicherungen eingespielt. Aber auch manuell erstellte Drucker lassen sich nicht löschen, nur deaktivieren.
-
any update on a better Klipper integration ?
-
Danke! Ich könnte doch theoretisch auch denselben Drucker einrichten, einmal mit Klipper und einmal mit Marlin, und jeweils den einen deaktivieren, wenn ich ihn in den einen oder anderen Modus laufen lasse, oder? Hintergrund: Wenn ich mit Klipper …
-
Frage: Kann ich mit Repetier Server Klipper mit einem Drucker betreiben und zwei oder mehrere weitere mit Marlin? Ich würde gerne an einem meiner drei Drucker Klipper ausprobieren. Alle drei Drucker laufen mit SKR1.4 Board.
-
Danke.... die Auswahl TCP/IP bei der Einrichtung hatte ich nicht nehr auf dem Schirm! Too
-
After upgrading to 1.0.1 I also did the comm rest and interestingly I had better results with 255 instead of the default 127, but I am using the SKR 1.4 Turbo board and the Pro version running on 32-bit Raaspberyy pi 3b.
-
So, I have solved my issues: The root cause for my inconsisent bltouch behaviour was a loose signal cable connection :-/ no software issue. Strange how some occurrences coincident.
-
So it really seems to be related to my Bear SKR printer. This has a BLtouch issue. The Ender 3 SKR with a Hemera and Bltouch works fine. Not sure where this Bltouch issue on my Bear comes from :-/
-
Repetier said: Server is just sending gcodes. So that sounds more like a firmware issue than a server problem. Except if you see in console extra commands like deploy being send. Enable commands in console to see what gets actually really sen…
-
I had it running well on 0.94.3, retried 1.0.1. and had already an issue with screen resolution, connectivity and strangely enough UBL bed probing. That should not be connected with UBL, but I am puzzled, just after the upgrade my printer behaves st…
-
Repetier said: Is this meant to happen with that firmware? I mean M119 should show status of pin but not stow/deploy a pin. That is correct in marlin and it just works when everything is fine. However, when I experience "my issue", the M1…
-
Repetier said: Is this meant to happen with that firmware? I mean M119 should show status of pin but not stow/deploy a pin. At least that is how we do it in repetier firmware. Have no marlin with that. We only deploy when we want to measure. …
-
Hi, I have a normal 1.4 and a 1.4 turbo, but it didn‘t work for me. I don‘t know here the file went, Repetier confirmed the upload, but checking the sd card, nothing was there.
-
I went back to 0.94.3, but on one of my printer, a Bear SKR printer, I have the issue, that ftare a successful print, a new print leads to the nozzle crashing into the bed. When sending M119 via the console, the pint deploys from stowed mode and the…
-
my ender seems to be better off... I run a SKR 1.4 on it, and in my crashed Bear the turbo version. I didn‘t get that severe issue son my Ender.
-
wow, that‘s bad.... I just have a punctured textured steelsheet. but not sure what cracks I got on my x ends .. they were severly bending. After similar issues I use to perform sone bltouch homing tests above the bed to make sure nothing is br…
-
I see from the change log that some communication timeout and resend optimzation might have contributed to my issues when I needed to stop the printer by power switch.
-
did you check on the console what happened? This does not happen every time, and it seems like my two printers produce more failed prints since the upgrade... Layer shifts... that‘s why I though there might be a communication / buffering issue.
-
So you just installed the previous version over with no issues?
-
There seems to be a buffer issue. I get my issues always when cancel a print. This seems to lead to the nozzle slamming into the bed. Last time, I cancelled a print because after some spaghetti disaster. When I started another print, the nozzle ran …
-
Ok, I just changed RTS / DTR from "LOW to HIGH" to "HIGH to LOW", and it could connect. Didn#t expect that to change between version
-
Thank you for the feedback. Yes, it stabilizes at a later stage. My filament settings are as such, that I have a fan percentage of 0 to 100 depending on the need, so the fan kicks in suddenly when there are overhangs, but goes to 0 on flat pieces.
-
Here on the right-hand skala you can see the % variation which seem way off..
-
Ok, Problem erledigt Ich hatte noch den 5V Pin am USB-Stecker abgeklemmt, ich hatte das Kabel vom Ender 3 SKR Mini e3 wiederverwendet. Beim Prusa ist das natürlich ungünstig.Also, alles gut.
-
I have Safe Homing enabled in the firmware, so it moves to bed size /2 position instead of 0, 0, 0. But somehow that should be detected by Repetier server, or?
-
But why does Repetier not take the values from the printer as home position? When I change my z offset for any reason (I am running bltouch), I have to adjust this in the Repetier settings, right? Why is this not a problem for the Prusa, or how do …
-
You are right... when I home the Repetier Server GUI says 0, 0, 0 while the LCD and console outputs 160, 114.5, 12.20
-
Btw, if I send a G91 before executing, then it instantly works, which leads me to the suggestion to have G91 as part of the end gcode, or is this weird?
-
Another thing: I pressed "move left 50 mm" on the toucscreen, and this happened: 12:39:37.963: N16 G2812:40:02.922: echo:busy: processing (12)12:40:03.562: X:160.00 Y:114.50 Z:12.20 E:0.00 Count X:12800 Y:9160 Z:488012:40:03.562: ok12:40:16.381: …
-
So, I started the printer, (standalone) not connected to the Pi. I rebooted the Pi with Repetier Server running, then I connected the printer and the Pi. Then I pressed "Home all" on the touchscreen with Repetier running: 12:28:56.028: N11 G2812:2…