Repetier
About
- Username
- Repetier
- Joined
- Visits
- 2,088
- Last Active
- Roles
- Administrator
Comments
-
If objects are send as separate objects slic3r does automatic rearrange of them. Use 2.0.5 host version. The bundled slic3r there can prevent this by command line so there it should not happen any more.
-
Check eeprom settings for extruder 2. Normally 20°C before target temp the heat controller takes over, so I assume the values set there lead to not heating.
-
Good. I have extended the install list for next update. The sRGB profile is just a warning so worst that can happen is wrong gamma correction. I have seen this also in my case. Gtk-Message: Failed to load module "canberra-gtk-module" No idea where …
-
First check set rectangle coordinates. Then also check log output for error messages that might give you a hint like probing outside allowed region.
-
I see. You need to add a z probe and define it on the same pin as z min endstop since you use it as z min. If you do this, it will add z probe height to the current position which you then would set to 20. Next trick would be to set homing order to…
-
Sie mal in der Konfiguration in Manuelle Steuerung und Druckerform nach. Eine der Bereichsparameter müsste zu klein gewählt sein, daher denkt er das er außerhalb des Bereichs druckt.
-
Looking in my code I think it should have nearly perfect correction in first pass. But to be that good you need to configure it correctly. I think your error might be no knowing the difference between probing points and BED_MOTOR_x. Probing points s…
-
When printer marker gets red that means the com port is gone. As a counter test you could also open hardware manager in windows. When green you should see a com port in serial connections. When server switches to red it tries to reconnect (orange). …
-
That interface is only for quick tasks at the printer. The configuration is done in the normal web frontend. So connect to one of the ip's you see in network and do the configuration there. There you can also upload gcodes. At the pi you could do th…
-
Currently not. For V2 I plan a new system that automatically detects available region and tests everything reachable. But until then I think it will not be possible.
-
It is correct to not move M1. This is taken as given height and M2/M3 are modified to go to same level. That is also why you only define these 2 motors for extra driver in addition. Have you tried repeated autoleveling? It should converge with each…
-
Make sure you can activate probe at the position you are. I guess you activated G30 at 0,0 and it has 20mm offset so required a move to -20 whcih is not allowed. SO just go to G1 X30 Y10 and then start and it should work. Same with the 3 points for…
-
I'd take 4.0 version as we compile for .NET 4
-
Why not G28 Z0 G0 Z20 M3 S255 As I understood M3 S255 is igniting for you so going first to position would be the logic consequence. If you want this all in M3 then it is not supported and you would have to edit the sources to do exactly that.
-
In most cases the start speed (z jerk) or z acceleration is then too high. For longer moves it seems then to start at one point but layer switches are small so here a short block is all needed to not move. Hope you already tested this as this was al…
-
If you are just skipping menu entries your encoder speed is simply set too fast, see this option: /* Normally cou want a next/previous actions with every click of your encoder. Unfortunately, the encoder have a different count of p…
-
It mainly depends on th ez probe speed. So if z-probe takes some time to trigger the speed will influence the distance. If it is very fest it only depends on printer being able to stop without loosing steps.
-
That was my propsed solution! extcommands.xml can define menu entries with commands to execute just like with execute as well. You can even assign them to a printer so they appear in printer context menu and not the global menu.
-
The extruder switch came along with checksum mismatch, so it looks like a communication error made firmware think it should switch extruder. The line numbers you see in script are not the line numbers you see in log. Host adds a new line for every …
-
Do you have selected Marlin as firmware type? Looks like you send commands in binary whcih happens if you have selected repetier-firmware.
-
Ok, first the bump map now looks like it shold be. Swinging around zero and small values. Never figured you did not autolevel before. As you now see your bed is rotated and you completely neglected that causing big corrections. You would never get s…
-
No command. It is a configuration option where you define the homing and endstops in config tool.
-
pins.h has pins set for radds sd card. You would need displaylis to not change them.
-
You mean it shows these coordinates in host? In that case it is simply the first layer height. That can differ from other layers and often it is good to have first layer 0.2 or 0.3mm height.
-
Adjust endstop to trigger at lower height. Endstops can prevent going lower depending on firmware and configuration.
-
First MartinH is correct with saying Zmax homing should use G32 S2 to autolevel and save. This will additionally measure distance to top and set z length accordingly. Of course only works with correct z probe height. Your idea to home go low until …
-
Default radds config activates this, but lcd config can overwrite to use an other one. There can only be one sd reader working.
-
Exactly that is the trick. Firmware measures distance to top based on z probe height, so this correction needs to be added. Or you have an other problem. Make sure to go back from max endstop so z homing is not at switch. If you move at top it will…
-
Bitte nur den Bereich des Zeitpunkts und den Zeitpunkt auch benennen. Sonst kann man die Ereignisse nicht zuordnen.
-
Yes, looks like your fault:-) Values should swing around 0 and not 2.2. After all you reduce correction in teh next millimeter to 0 from 2.2mm. So for 1mm up it needs to go 2.2mm down, just as you said. This happens normally if z probe height is wr…