Repetier

About

Username
Repetier
Joined
Visits
2,088
Last Active
Roles
Administrator

Comments

  • It activates extruder after probing so the offset from z probe gets undone which can be an extra y move. If it crashes your last probe point is at a bad y position not allowing activating extruder again.
  • There is always a maximum speed at which you can heat up filament. If you go faster it is not hot enough and requires more force so you get slippage and not the extrusion you want. You also need the right temperature so it extrudes with required spe…
  • MKS Base V1.4 is ramps compatible so that makes not much difference. I think it only has one more output for a fan. So all you need to go is go through our config tool and compare values with the configuration from your vendors firmware to select th…
  • What webcam software do you use? You have to watch out with the url - that it works in browser does not always mean it is the url for the mjpg stream. It could also be a html page containing the stream. And the stream must have mjpg format and not a…
  • Yes in deed. If autoreport temperatures causes other functions having corrupt output this is clearly a firmware bug. Repetier-firmware also has autoreport temperatures and does not do this.
  • Looks like at least one used component requires glibc version 3.4.20. This is part of your os and it seems to have a older version. I have tested it with 16.04LTS and it worked, so one solution is to update your quite old linux environment. Alterna…
  • It is only in start code when you hit the create default gcode button after having set extruder count correctly.
  • Can you clarify if host is showing z = 0.3mm when printing the first 0.3mm layer? It seems you start mixing different z values liek real z, measured z, send z so clearifying what z you have after home and G1 Z0.3 would help. Only if G28 G1 Z0.3 res…
  • I'm not sure how curaengine handles this. I never use a raft. Would make sense that it would be used for raft instead. You can see it in the generated gcode. Just open gcode editor and you can see the layer switches and compare the z positions and y…
  • Steps are steps send to extruder so going from 128 to 32 microstepping should give 1/4th of the steps. That it effective you would see in the need to reduce steps per mm in extruder settings as well. Of course you have to set the reduced steps in co…
  • Yes that is what I meant. If you use host to measure it sends a complete measurement script to test. Thats go to xy, measure, go,measure,... so if go fails it stays and does z probe. Then again so it measures several times same position until go is …
  • I deed you can not have z min and max at same pin! If min triggers it also triggers z max meaning it can not go up. If you tell firmware to move back after homing a axis so that the axis untriggers, you can use the same pin for x and y endstop. Tha…
  • Is it defect or did you not go up enough so that it untriggers? Function awaits that it is untriggered so we can go down until it triggers to have a measurement. Starting to low causes the same error.
  • Yes these angles I mean. Maybe think like having a circle with 3 bars below. If you move the bars one side of the bar goes up and the other down. But in the end it is try and error. Make a height map with repetier-host, store it as table over clipbo…
  • I see it never uses the names. Will fix that. Regarding board temperature - that was never really interesting and relevant. If build correctly it stays in good range and you can add a fan that gets enabled. I think we even do not measure this expli…
  • Check the start gcode in curaengine config, it should have a line like this: {IF_EXT1}M109 T1 S{TEMP1} to enable it if that extruder gets used.
  • If slic3r has a g1 Z0.63 move it is clearly in slic3r. Can be in your personal start gcode or first layer height is set to that.
  • You should use dev version. I‘m quite sure there we use 32 bit for step count on radds, so no overflow. sdss is dangerous as it could be used by spi and due has hardware comtrol of sdss in that case, so it might become an output instead of input and…
  • When homing to z min using z probe as well that sounds right, yes.
  • Maybe you have changed the flow rate in host to a lower value. That would cause under extrusion as you describe.
  • What does the log show as reason for the stop. Also config is not relevant if z probe is working. Important is what coordinates are stored in eeprom i guess. And i think it is a problem with one of the positions stored that causes the stop.
  • Server already supports this for quite a while. If you watch the moves in frontend you have a function to the right to exclude a reagion. All moves in that reactangle will be omited except z moves and e values will be afjusted on the fly.
  • What kind of z probe do you use. Negative values mean it triggers after the bed is hit by nozzle. Force feedback ond switches integrated in nozzle tip do this, all other probes have a positive values assince the probe triggers before nozzle hits bed…
  • On select you modify active coil and use same motor pins for all extruders. Guess that should work. Problem is more that the maximum number of supported extruders is 6 not 8. If you define more you have to add more copies of the extruder handlin pa…
  • Check eeprom where you defines probe points building the square. Modify them to cover only reachable rectangle with active z probe, so start with higher x and stop just normally.
  • Yes if the edges of the square can be reached with active probe this would be fine.
  • You set them in eeprom. Depening on measurement method the 3 points only are used or they build a parallelogram. P1 is one edge and p1-p2 and p1-p3 biod the 2 axis.
  • Most likely changing b or c angle will help here. But that alo has an effect on the other sectors, so be carefull. Normally only very small changes like 0.1-0.3are needed. G33 would also help here if you do not manage to optimize geometry further.
  • Don‘t think firmwares report this temperature on m105 or did i miss that?
  • That would require a mode type view which we currently do not have as we support different slicersand some don‘t types or only if comments enabled. And of course all do it differently. Might come in a later version if data is available.