Repetier
About
- Username
- Repetier
- Joined
- Visits
- 2,088
- Last Active
- Roles
- Administrator
Comments
-
Yes. At start e speed is 0 and with start speed 1 it allows 1mm/s from the start and that is jerk.
-
G29 only works for leveled bed or you will have only a average height but not real value. Easy solution is run G32, check error correct and G32 again until you are satisfied. That is what you thought about G29 just working as rotation is also consi…
-
You mean after z homing it is 15mm away from bed? Fix homing in your firmware/hardware depending on the source of 15mm. Endstop may be too high to you have set to move up 15 mm after homing which should be 0 for z min homing. If using repetier-firmw…
-
#define ENDSTOP_X_BACK_ON_HOME 1 #define ENDSTOP_Y_BACK_ON_HOME 1 might be a bit low for your endstop type. Test how much you need to go back to uncheck the endstops.
-
The problem here is caused by N49 M109 S200.000000 which is a slow command taking longer then timeout seconds. Server knows this and as long as it thinks it is not finished will not cause the timeout. It is not that visible now if the M109 got a mat…
-
Maybe you can explain exactly when and where. The frontend filament change had some errors, so I hope you are using the normal web frontend. Or are you using a firmware version of toolchange?
-
Extruder start speed is equivalent to extruder jerk, so reduce that value.
-
If you check the board plan sensors use a 4,7k resistor to get split voltage. Have already heard about boards with wrong resistors. If you find them, you could check if they have 4.7k. Different values cause other voltages and hence wrong temperatur…
-
Firmware setting is not relevant here. We do not use G10/G11 which would use firmware settings. Important fact is that you set values per extruder and only when you insert/remove filament changed values get stored. So setting 0 a nd leaving does no…
-
G30 includes the z probe height already in output. But G30 with known height is a way to correct a wrong value. That is exactly how the menu correction in 1.0 works. There you run from known height and firmware computes the corrected value.
-
So newer then my testing devices that worked:-) But yes finish first print before testing if you expect a problem.
-
Als heater pin kannst du übrigens jeden anderen pin nehmen der nicht genutzt wird. Es muss ja keine Heizung dranhängen. Aber der Heitzungs PWM setzt den wert halt ständig auf 0 zurück von der Heizungssteuerung.
-
Ok, I'm officially confused as I do not have xy gantry myself and do not see what you are doing wrong. If no endstop is hit and your xy length are good (no software endstop triggered) you should be able to move in all directions. For pure directions…
-
3 possible mistakes. 1. D10 is ok but if heater is also set to D10 (default) it will override every setting. 2. Laser turns only on when you move with G1 if using M3. Imagine a laser always being on is inherently unsafe. So add a G1 move. G0 moves w…
-
The one I gave you has your changes already included. YOu should just replace it.
-
It might be a connection speed problem. The webcam output gets buffered if connection is too slow and that could maybe eat up all memory causing a stall. But only when viewing webcam, so not when you are on the start page not seeing it. Maybe you …
-
I see no reason why it should not work. In fact the new eeprom editor in repetier-host even uses exactly these commands, so you should be able to use the eeprom editor. I will test if M501 now hides the informations or sets them as ack (so you might…
-
It's a bit tricky but we could store z on connect and add a server side command @restoreZ that does this. G92 is not enough here as G92 does not change the coordinates you see. But with a server command that you could add in connect script or send m…
-
You can have z min as safety below bed level as long as you home to z max. As long as you make sure that it is lower then every point so it never triggers early stopping a move. Your "fast" G32 is homing. G32 is autoleveling. That is a different op…
-
Check resistance for room temperature. Should be 100K for 25°C. Also since E1 works put it in E0 sensor and see if it reports right temperature. If it does the sensor is defect.
-
You mean for slicing? In slicer settings is a filament section to set temperatures. Manually in manual control tab.
-
Precision depends not on height of limit switch. at z = 0 it has same precision as ob Z = 1000. The only real constrains is that you can not have z min limit switch and z probe. limit switch limits moves so for z min it MUST be at lowest position. …
-
Ist M119 not M199 to report endstop status! Steps per mm from pulley computed * 2 is what you enter I think, or it was sqrt(2). With fast corexy it is factor 1, but then you should use dev version.
-
No in object placement you can modify it all the time in position, composition and extruder assignment. Just needs to reslice to take effect. And as said use both extruders for dual extrusion or use slic3r.
-
You need to slice the object before you print or load a sliced model. Otherwise your print contains no g-code (the commands to control printer) and print is in deed directly finished.
-
This is also extremely uncomfortable. Different firmwares use different commands so we would end up with maybe 300 commands and masks. Entering them by hand is much quicker and more flexible as every week some firmware also gets new commands but hos…
-
While there are boards that have a shared enable signal for all extruders, the RAMPS 1.4 board does not do this. So there should be no problem unless you have 2 extruders selected so that 2 code parts use same extruder. That can cause strange behavi…
-
Make sure you have not changed the extruder in object placement. Especially with curaEngine you can only use extruder 2 if Extruder 1 is also used or it will always fall back to extruder 1. With slic3r this does not happen.
-
That function should only be turned on when you had a successfull G32 S2. In fact G32 will turn it on anyway if successfull.