Repetier
About
- Username
- Repetier
- Joined
- Visits
- 2,088
- Last Active
- Roles
- Administrator
Comments
-
Don't use fan2. Better see my comment and solution here https://forum.repetier.com/discussion/6363/laser-enable-pin-issue#latest
-
Don't you use config tool? That would have updated the file automatically. But as soon as you start changing settings manually they are not copied to config tool:-( Still not sure which menu shows the wrong temperature as there are quite some pages…
-
Looks like you use repetier firmware. As error says after 13 seconds of heating the extruder temperature did not rise. There are several typical errors causing it: 1) No power - test if motors move. 2) Wrong heater pin 3) Wrong sensor pin, e.g. bed …
-
In BedLeveling.cpp runBedLeveling steht #if BED_CORRECTION_METHOD == 1if (fabsf(plane.a) < 0.00025 && fabsf(plane.b) < 0.00025) {success = true;break; // we reached achievable precision so we can stop}} // for BED_LEVELING_REPETITIONS
-
If it happens frequently I would suggest having a ssh connection with putty and run top in that to see memory and cpu usage. That should give you early a warning when one of the components starts using more memory and even if you miss it you still …
-
Only due based boards work with V2. Development is using a RADDS board so that would be first choice. Switching is untested and the overtake of active value to other fan is not implemented. That is something I thought about during this discussion k…
-
No, heater i snot good for that. You want 100% output for main power. For my laser I used a fan output for enabling main power. You can use second fan for this which is not controlled by slicers. Laser is set in Drivers.cpp in this function void L…
-
Without analysis I can not say much here. Question is are you running out of memory so it swaps and slows down everything? If so which software increased memory usage to the limit? These are the main things to check to isolate the reason. The fact …
-
MKS TFT hab ich nicht aber ja zwei parallele Kommunikationen machen es sicherlich nicht besser. Sollte aber eigentlich trotzdem gut funktionieren. Gerade beim Verbinden sehe ich aber häufiger solche Fehler. Die würde ich daher nicht zu hoch bewerten…
-
Ok, now I understood what you said, thanks. Also I never have seen it. Which language are you using? I ask because output depends on special chars in text and if a translation has wrong char e.g. current temperature instead of temp 1/ temp 2 it woul…
-
Don't think you can use heater pins also as laser pins. They are controlled by temperature loop already. You can check the datasheet of mega2560 and see which pin uses which timer. As said timer 0-2 are reserved for firmware internal use. all you n…
-
In BedLeveling.cpp runBedLeveling steht #if BED_CORRECTION_METHOD == 1 if (fabsf(plane.a) < 0.00025 && fabsf(plane.b) < 0.00025) { success = true; break; // we reached achievable precision so we can stop } } // for BE…
-
For the dev version you get better handling in combination with Repetier-Server, better advance handling, less bugs and many small improvements. Also I do not fully understand what you tell with errors, if you come from a shared extruder config mak…
-
1) Yes, that is default behaviour of winform apps. 2) No, only shortkeys defined by default work. However the 5 scripts you can define have hotkeys Ctrl+Alt+ 1-5 3) Not in host. Repetier-Server can have any number. 4) No 5) No it is closed source co…
-
Yes, that is the default password. You can also connect with ethernet and check file /usr/local/Repetier-Setup/etc/server.conf which contains the password.
-
Yes, slicers only support one cooling fan so having one for both fans is the typical solution. Only V2 firmware supports what you want - mapping unnamed fan to active extruder cooling fan. But that version currently does not support 8 bit processor…
-
That is what I did and it worked. So can't say what is wrong here, but will soon make new image with next update including the lan setup as well, so maybe best is to use that image then (V15) when released.
-
Looks like missing the responses. They are filtered by host in log in view. You need to enable logging in host and check the log file which is complete. You also need to send the command to set the temperature so I see if it reacts correct not only …
-
Ok, see the wrong version. Thought you had 2.5S. For 2MKS the release notes to 3.1 even state: There’s a known bug using Repetier server, please wait for the next release if you’re using itAnd host behaves the same. Not sure the bug is where you pos…
-
I can tell you that you can add commands to be run in gcode with @execute so if you put that call in the gcode finished event you can trigger a script doing what ever you want including home automation. I only can not say how you call home automatis…
-
Ja der server verbindet sich automatisch neu. Problem könnte ja schon behoben sein. Mal sehen ob man das wenigstens drosseln kann. Alternative wäre deaktivieren aber dann muss man ihn manuell aktivieren damit er sich verbindet was dann einige nicht …
-
Such a solution need special hardware to keep firmware running until data is written. And then it would only work for sd prints.
-
https://www.prusa3d.com/drivers/#_ga=2.18187248.878759437.1553846541-1248160477.1553846541 it offers version 3.6 from 1. march 2019 for MK2S so there is a recent version that should work. Server works different and you can connect over host, but i…
-
This is speed in in mm/min so factor 60. Means 80mm/s. For travel it is ok, print speed is the critical thing. But we are not Cura support! Can't say anything to Cura only Repetier-Host.
-
Installiert ja aber webcam muss man schon noch in der Konfiguration eintragen. Es gibt Fälle da findet mjpg_streamer (die webcam software auf dem pi) keine passende Einstellung und stoppt wieder. Dazu nach dem start des webcam servers mal in linux …
-
So it works correctly except first move?
-
Stay below 60mm/s then you are normally not too fast. Once you get good prints you can try if faster works. What is clear is that you do not extrude enough. There are many factors that can go wrong: - Wrongs steps per mm in extruder - Wrong extrusio…
-
Looks like a firmware bug. Nothing delay related. There was a short time a bug in marlin handling N1 M110 wrong (expecting N0 and nothing else would work). For that reason setting it to line 1 causes the wrong line number error. Solution therefore…
-
Ah klipper. Dann kann der Pi den Drucker nicht ehr erreichen und sagt dem Host damit Bescheid das er Probleme hat. MCU ist bei denen ja der Teil der auf dem Drucker läuft.
-
In Commands.com you should have case 0: // G0 -> G1 case 1: // G1#if defined(SUPPORT_LASER) && SUPPORT_LASER { // disable laser for G0 moves bool laserOn = LaserDriver::laserOn; if (Printer::mode == PRINTER_MODE_LASER) { …