Repetier
About
- Username
- Repetier
- Joined
- Visits
- 2,088
- Last Active
- Roles
- Administrator
Comments
-
Printer does not know how big a object will be so there is nothing special for smaller objects. More likely it is the problem not printing in big areas of your bed and if the small object is there it will not be printed. I guess the firmware has a d…
-
Make sure ALWAYS_CHECK_ENDSTOPS 0 since the sensor can trigger and prevent z down moves during z hops. That would be a typical reason when z increases during print.
-
In config tool you set the max. extrusion length in "Maximum extrusion length / EXTRUDE_MAXLENGTH". This is to protect for big rewinds/extrusions when you forget G92 E0 and have big E value from previous print.
-
Not sure where your frind has them from. Slic3r configs are stored in homedir/AppData/Roaming/Slic3r and you could simply copy them to get them as well.
-
You now need to define COOLER_PWM_SPEED 0 but I guess it is defined as empty from not updating the config tool when I added the new option.
-
Host can only connect to one system so it can not sync with a second. Server can connect to several printers at once but does not sync, which is also not easy since firmwares buffer moves so syncing them is generally not possible and would require p…
-
I do not understand exactly how it works since I do not speak the language, but I think it should be possible. Looks like 1 motor output is copied 3 times and only one is active depending on some state of pins. We have a select and deselect gcode pe…
-
I can not really say what part is wrong, especially for deltas it is the bounding circle that gets violated, but I added for next update the message: error: Activating z-probe would lead to forbidden xy position: -5, 0 before the fatal message. Tha…
-
Does not make much sense. If it reacts on the z probe trigger it should also show so with M119 especially if z probe shows the signal as well. Your homing procedure sounds like it is triggered directly when trying to go down, which is why you see on…
-
Your board configuration has no named pin FAN 2 - use the digital pin number of that output instead, that works always if get the right one. As for the display, I guess it has no pin setting defined in ui.h/DisplayList.h for that display/board combi…
-
Log says nothing in that problem. It never shows missed steps. More interesting is how many steps per mm and which speed did you use? Could it be that you have no microstepping in drivers enabled so speeds are 16x faster then expected?
-
Ok, but it should do. You should have set z min endstop to hardware with z min pin (assuming you used that pin for z probe). If that does not change in sync homing will never work correctly.
-
Any idea how to say that so any one will understand it and it is still short to reduce memory usage? It does say exactly what it meant but I agree that it is not so obvious without long explanations. BTW: I meant with preheat since that is the combi…
-
Ok, then I I do not see why. I mean it works on first case it works when doing manually so something must cause this, but I can't say what and why this happens to you and not others. Maybe something special in your hardware/software combination that…
-
It is no problem. In fact I have checked the code and max. was even 61Hz and not 122. Have updated dev version to now allow 244Hz and also added a setting for fan pwm to config tool directly below heater pwm speed. Hope that will do now.
-
Latest dev now tests for succes on repositioning. I guess you have not homing order XYPreheat Z with z probe pos at 100,100 so activating at that position works. You seem to z probe at 0,0 and this needs to move into negative coordinates to activate…
-
Does M119 now show same level for z min and z probe? Since you inverted both and not one of them I guess that is your error. It will stop the down moves as soon a z min triggers.
-
Actually print rite updates their software regularly, but for some reason all versions must have the version name 1.5.5. If you install latest from website you should see it appear in title as 1.6.2. With release 2.0 coming soon you will get a new …
-
They refer to your firmware not a host file. You need then to recompile and upload a new firmware with correct thermistor selected. Different thermistors use different temperature-resistance curves so it is important to compile with the one used.
-
Does this also happen with programming port? Normally the programming port connects more reliably as it resets the board while the other one does not reset and depending on state it might need a reset to reconnect (e.g. when it expects line resend o…
-
You are homing to z max? Make sure bead coating is set 0 as this changes result when homing. S2 computes new height by adding the difference between old and new z from z probing as this is the change measured. Where z probe triggers /high/low) is no…
-
Every doubling of frequency means only 50% of resolution. The higher frequencies were introduced to reduce flickering effects for led lights. Same code is used for fans. Main problem is that higher frequencies take more time in cpu so we can not pri…
-
I copied them from your config to show you which are relevant. I think you need to change either Z_PROBE_ON_HIGH or ENDSTOP_Z_MAX_INVERTING
-
You are not using repetier-firmware so check on your firmwares pages for how to change endstop settings. But yes, I think your endstops show triggered when not and that prevents move in triggered direction. That is quite normal and needs just a diff…
-
So your z probe height is 0 and you should increase sensitivity! Consider it is not the distance of bed to probe when it triggers but distance of nozzle to bed when it triggers.
-
You can set all eeprom values with a eeprom editor in repetier-host or server. It shows all values for you to change. Internally these use M205 and M206 for this as described in our documentation. Regarding offset I think there is a difference betwe…
-
Sounds good so far. Connection works and the sound is most probably a stepper loosing step hence not moving. Typical reasons are steps per mm too high, moving to fast, motion blocked and current for motor set to low. After enabling motor you should …
-
RAMPS is th emost widely used board so it is surely supported
-
That is not planned. This codec contains active patents and needs completely different handling.
-
You are simply not talking to printer. Getting green = connected means with serial->usb converter but does not mean host understands answers. Most probably you used wrong baud rate. Try 115200 and 250000. One of them normally works.