karl_ranseier
About
- Username
- karl_ranseier
- Joined
- Visits
- 18
- Last Active
- Roles
- Member
Comments
-
In configuration_io.h I changed IO_INPUT_INVERTED_PULLUP(IOEndstopXMin, ORIG_X_MAX_PIN) with replacing the endstop to that connector homing works without any problem. Looks like that x-Min connection is broken (or there is something w…
-
Sorry, I did not get what M111 S70 should behave like. I have send the command. Send:23:41:25.820: N24 M111 S70Recv:23:41:25.820: DebugLevel:70Recv:23:41:25.820: debug:Echo:OffRecv:23:41:25.820: debug:Info:OnRecv:23:41:25.820: debug:Errors:OnRecv:…
-
Thanks a lot! That solved the problem. You were right, it was for roughly a second in the right position, than it moves to a high ms value. With your change it works fine. After restart, it stays at the desired position. Adding R500 (300 was not e…
-
It's not stopping early, it is not stopping anyway or late. I understand where I was misleading. I wanted to say it stops 250-500ms AFTER it reached the end stop. IO_INPUT_INVERTED_PULLUP(IOEndstopXMin, ORIG_X_MIN_PIN)// IO_INPUT_INVERTED(IOEndstop…
-
Repetier said: Distance after homing is just to get away from the endstop so it is not triggered any more. It is independent of the position so think of it as a relative distance. Ok, handling it as a relative position change explains it. An…
-
Looks like the endstop is defined as 0 mm. If I set "x-axis distance after homing" to 0 it does not move. "x-axis min position" is set to -65mm. Therefore I thought I need to set "x-axis distance after homing"to -65mm. Where do I set the position…
-
Yes, I see that now. The typical way may be the following:- One installs repetier-server- One installs the formware- One plays around with his printer and changes many things, because doing everthing correct before having a reacting printer is nearl…
-
Thanks, I read that manual, but obviously too fast. I did not expect the need of entering two times the direction: Here: #define X_HOME_DIR -1 And here: ENDSTOP_SWITCH_HW(endstopXMin, IOEndstopXMin, X_AXIS, false) It might make sense …
-
Ok, I did not see that I have configured that position (I left it out). These values are all entered in the EEPROM settings, so why not read them from EEPROM instead of making the user entering it again? Maybe even wit a selection 1. enter manuall…
-
DELETED
-
Thanks! Another problem: When Homing Z with the following values in EEPROM: Z axis endstop distance after homing: 0Z axis min position: 0Z axis max position: 160 there is a problem: repetier server does not read the new position. The z-value is a…
-
Setting: STEPPER_SIMPLE(YMotor, IOX1Step, IOX1Dir, IOX1Enable, endstopNone, endstopNone)STEPPER_SIMPLE(XMotor, IOY1Step, IOY1Dir, IOY1Enable, endstopNone, endstopNone)STEPPER_SIMPLE(ZMotor, IOZ1Step, IOZ1Dir, IOZ1Enable, endstopNone, endstopNone)STE…
-
RAyWB said: as you wrote above: i guess you fried the Driver. DRV8825 die immediate when mounting in wrong direction.fried myself around 10 pieces the last two years while "ich probier kurz" It is a compatible driver which obvously is n…
-
4.: Steps per mm: 495.000 Yank: 5.00 mm/s max speed: 30mm/s acceleration: 300 mm/s²advance: 10steps/mm 3./2.: In configuration_io.h I found:STEPPER_SIMPLE(XMotor, IOX1Step, IOX1Dir, IOX1Enable, endstopNone, endstopNone)STEPPER_SIMPLE(YMotor, IOY1…
-
About EEPROM: Correct, I use repetier-server. Sorry that I did not mention this (clear enough). I thought I did. I would suggest that if you prefer this behaviour, that there should not be the message "stored" or "success". Back to the …
-
In this manual one can find the settings for the stepper drivers: https://raw.githubusercontent.com/Aus3D/RUMBA32/master/Resources/Manual/RUMBA32 V1.1 User Manual - REV A.pdf I do not use SPI yet. I used the 16times microstepping. I have set the j…
-
I reproduced the error with the EEPROM: If there was an error, like decoupling of temperature, one cannot write the EEPROM. This makes in my opinion no sense, because there might be errors, which might arise from wrong EEPROM settings. It should eit…
-
Scottty said: @ karl_ranseier Are you aware of the so called EEPROM trap? You'll find it several times here. E…
-
Now I am getting some results. The full graphic display from my Rumba works, the one delivered with the Rumba32 not. That may be a setting, but I prefer the full graphics display anyway. I connected heated bed and thermistor as the first test. Bec…
-
@RAyWB I followed the video instrictions. The devide is now found as USB-device instead of controller and is named "STM32 BOOTLOADER". Upload worked! BUT: Now I cannot find the device anymore. No LED is flashing. USB PWR Led is on, 5V and 3V LED…
-
It is found as a known device. Thanks for that hint, I do have a pi laying around which I may try after using google more intensive.
-
When I press RESET-BOOT and release RESET the LED1 flashes once, than nothing flashes. As I said, the COM16 disappears. What I had not recognized is that "STM Device in DFU Mode" at USB-Controller appears. Still Visual Studio says: Match vendor I…
-
Thanks for that advice. I already noted that issue. My drivers are a bit bigger than the others and do not fit. Anyway I can configure the drivers using USB, therefore the misconfigured pins don't matter.
-
I decided to change to Rumba32 instead of replacing the old one with the same version. So I think one can close this thread.
-
Thanks! I ordered Rumba32 because of a broken Rumba. I am a bit nervous about how long it will take to make it print again.
-
I tried to check the logfile, but failed. Now my RUMBA-board is broken. I touched a metal part with a cable, have seen a spark and need now some time to fix it :-( . Therefore I cannot send anything right now. I found in another, older topic, tha…
-
Thanks for the explanation. I will do another test in the evening. Do you really think the brown out can appear just because of the new firmware? Using the older version I had never any problems with restarts. I will try to add a resistor and capaci…
-
I checked the start and finish code from the console: Startcode runs without problems. After the line "M340 P0 S1865 R400 \n G4 P400 \n M114" the next command results in an error. 20:36:51.524 : N24 M340 P0 S1865 R400 \N G4 P400 \N M114*35 20:36:5…
-
This is the protocol from repetier-host:16:25:01.165 : Z-probe:19.008 X:220.00 Y:50.00 16:25:01.165 : plane: a = -0.0003 b = -0.0003 c = 19.0933 16:25:01.185 : Transformation matrix: 1.000000 0.000000 0.000322 -0.000000 1.000000 0.000294 -0.000322 -…
-
A missing information: There is a servo with a microswith attached. After the last measurement point it moves back, than the printer goes off. Probe start code:M340 P0 S1165 R400 Probe finished code:M340 P0 S1865 R400 \n G4 P400 \n M114