karl_ranseier
About
- Username
- karl_ranseier
- Joined
- Visits
- 18
- Last Active
- Roles
- Member
Comments
-
Looks again like rounding. Scroll down to three bold lines in the protocol. Recv:18:21:40.592: Z-Test failed:160.000015Recv:18:21:40.592: zmax:160.000000Recv:18:21:40.592: Warning:Move to illegal position prevented! Position should not be trusted a…
-
Again, thanks a lot!
-
I can confirm that it is removed now. Level of dir is constant low or high for both directions
-
First the result: It seems to be solved! Thank you very much! I add the protocol downwards.1. trying with your first version: Failed2. Trying with Epsilon Z = 10.01: SUCCESS3. Tryiung with Epsilon Z=0.01: SUCCESS4. Removing rotMax[i] += 10.01; and r…
-
I tried it with replacing the lines a)for (fast8_t i = 0; i
-
I checked wit the version downloaded some minutes ago, but it still looks like this:https://drive.google.com/file/d/1Hdvo_YqRPVS3UWuN2CMw4BlyNHMiyQ0u/view?usp=sharing
-
Sorry for forgetting to activate debug output. Can I activate this permanently? I added the line in the config and changed the homeAxes as you described. Upload and M111 S7: Autolevel enabled: Send:22:19:16.504: N22 G28Recv:22:19:16.504: minPosOff:…
-
I found it in motionlevel1 and changed it. Without correction:Send:12:06:39.985: N18 G28Recv:12:06:39.985: Info:Autoleveling disabledRecv:12:06:39.985: X:0.00 Y:0.00 Z:0.000 E:0.0000Recv:12:06:42.764: Info:Autoleveling disabledRecv:12:06:42.764: X:-…
-
AbsoluteCatalyst said: It happens during interpolated moves/direction changes/corners. https://tinyurl.com/y3ynkj5y I think it always happens, but if the steps are very close to each other, it is still in the other state and one does no…
-
Repetier said: SLOW_DIRECTION_CHANGE 1 makes a timer interrupt call pause = 1/STEPPER_FREQUENCY seconds. This is for drivers that don't see the changed direction when step follows very quickly. The drivers datasheet normally has a timing diag…
-
Sorry. DC= direct/constant current (or voltage) AC= alternating current (or voltage) Normally AC is for +/- current, so therefore I used a wrong term. Here I meant with "not DC" a "not constant" voltage, so an alternating voltage between 0 and 3.3 …
-
These are the values named in the EEPROM: via repetier server: * axis distance after homing 2 with *={x,y,z} ENDTSOP_*_BACK_MOVE is in my opinion not what shows the last movement. In my setup it looks like this:- Homing z axis, with retesting. At …
-
I thought I already did it, but only NOW I have set #define RAISE_Z_ON_TOOLCHANGE 0 (it was 2mm) So if in my upper post something was misleading, it is my fault. Sorry for that. In addition I changed #define ZHOME_HEIGHT 160 (it was 159) After the…
-
I changed in EEPROM via repetier server the "auto level active" value from 1 to 0. Result: Send:11:11:58.600: N21 G28Recv:11:11:58.600: Info:Autoleveling disabledRecv:11:11:58.600: X:35.00 Y:0.00 Z:160.000 E:0.0000Recv:11:12:12.613: Info:Autoleveli…
-
I assume, that ENDSTOP_Z_BACK_ON_HOME 2 is the same like setting in the EEPROM "z axis distance after homing =2". In addition to reducing z-axis max position by 2, so to 157 it gives the following: Send:20:07:46.379: N31 G28 Recv:20:07:46.379: Info…
-
I downloaded the new version and replaced configuration.h and configuration_io.h by my old versions. --> problem is still existingSend:18:22:00.930: N24 G28 Recv:18:22:00.930: Info:Autoleveling disabled Recv:18:22:00.930: X:-65.09 Y:399.92 Z:15…
-
Sure, here it is with "endstop distance after moving" for all axis with positive value 10mm: Send:15:23:41.118: N48 G28 Recv:15:23:41.118: Info:Autoleveling disabled Recv:15:23:41.118: X:-65.09 Y:399.92 Z:159.167 E:0.0000 Recv:15:23:45.488: Info…
-
Repetier said: Yes, Recv:11:55:23.232: SelectTool:0 Recv:11:55:23.232: Warning:Move to illegal position prevented! Position should not be trusted any more! is a problem. Selecting tool 0 causes a illegal position which invalides homing. Is…
-
Quick and dirty sketch: https://drive.google.com/file/d/18lus9RrsjyiOURupdu7FEb0IzOQ6kqa3/view?usp=sharing
-
The last changes were Fix closestPosition, fix servo off for STM32 boards. After that I downloaded from github. My Offsets are x:-108, y:-8Homing direction: x to negative y to positivez to positive
-
Thanks!
-
RAyWB said: Die Frage ist nur warum er bei Dir trotz homing x und/oder y als nicht gehomed sieht.falls Du ein Display drann hast müsste das ja an den koordinaten ersichtlich sein The display shows the right values, but switches every s…
-
I would even not block the operation. Or at least give a parameter like "G30 S1" to allow an override of the blocking.
-
Repetier said: I assumed you homed first and then you send G30. G30 does not move to any position - it probes where you are only the offset for z probe is added. You should make sure it is only called above the bed. Firmware just checks if i…
-
I downloaded the complete files from github. Than I put back my config files, compile and run as above. It is still homing first. During compilation I do get plenty of warnings. Here are the first ones:In file included from src\Repetier.h:220, …
-
Repetier said: Where do you see a upload function? Because we have none and in my interface I also see none. Easiest solution is dropbox or google drive and share a file. But I thought your problem is solved using x max pin instead. Here a…
-
Both were Rumba32, but different pins were broken. I think we should not waste time on that. I have a working solution. I will contact the company which produced the board.
-
Ok, I tried G30 P1. The description is the same as above. It homes, than moves the distance given in "z-probe xaxis offset" and moves down. But it is not performing a probe at the position where it is/was, so not at the current position. I do not f…
-
You can simply drag & drop a file to the Editor. At least in Firefox. Yes, it is solved. But still I Wonder If I am so unlucky to have two broken Boards in a row.
-
second try: failed. The uploaded files are not shown. Email would be the easiest way.