andin
About
- Username
- andin
- Joined
- Visits
- 39
- Last Active
- Roles
- Member
Comments
-
I have downloaded the newest version and was able to finish some prints without issues using advance - and quality is finally good Thank you for the update! One thing that still looks weird, but doesn't make much of a problem: Z-axis moves a few mm…
-
Advance has improved my print quality significantly before - and I really hope it will also work soon with RADDS. Thanks in advance for looking into this! Best,Andi.
-
I believe this bug relates to the changes described in this post:http://forum.repetier.com/discussion/comment/2733/#Comment_2733
-
Hi, It's been a while, but a managed to test the firmware's advance algorithm... and it fails. Here's what happens: - If advance is enabled, the extruder driver (in my case RAPS128) fails after a few layers causing the extruder motor to stop turning…
-
The same test with advance_L = 10. Interestingly, this problem does not appear now - the X/Y motion is not decelerating during speed increase.
-
Hello Repetier, I have just downloaded the new firmare with the ALTERNATIVE_JERK implemented. As you suggested, I included this in the configuration.h: #define ALTERNATIVE_JERK However, I am observing same issues here. I performed the test again. Th…
-
Hi, Could you elaborate on how to use the new direction filtering in the firmware? Is there a flag or parameter that needs to be set? Another question: What do you recommend for #define STEP_DOUBLER_FREQUENCY ? Since I am using an ARM, this value co…
-
I can't wait to test the new release. When are you planning to release the update? Many thanks,Andi.
-
Sounds wonderful, thank you! I will try the get the buffer full to see how the path planner does acceleration/deceleration and get back with some results. But I guess you are right, let's see... Best,Andi.
-
and here are the results for the test where advance was enabled (advance_L = 10): Best,Andi.
-
I have performed the same tests as in the above post - and now measured the STEP and DIR signals of the XY-motors. However, XY is probably not the best way to call them since I am using CoreXY, so I named them A- and B- motors on the charts: 1) WITH…
-
Hi Repetier, Here are my EEPROM settings relevant to movements and extrusion; these settings were used for the above tests (advance factor was set to either 0 or 10 depending on the test). High values for step p. mm for the Z- and E-axis are due to …
-
Hello, Here are some interesting results I observed using the latest update of Repetier FW (0.92.3). I measured the step and direction signals of the extruder using my logic analyzer and here are the results. In particular, I looked at how the signa…
-
Many thanks for the quick response!I will download the updated version and report back if the problem was solved.
-
I am indeed using RAPS128 stepper drivers with a 1.8deg stepper motor in direct drive. However, I have installed the stepper drivers in a 1/64 uStepping mode - this yields around 550 steps per mm in my extruder. The rest of the machine (XYZ) is driv…
-
Anyone?
-
Follow-up: The problem persists and is definitely a bug in the firmware: The issues with X-Y movements appear with DRIVE_SYSTEM 2 and after the function setAdvanceActivated() is called. Hardware related problems are out of the question: everything w…
-
Ok, problem found: Repetier Host does not load the EXT0_ADVANCE_L to EEPROM correctly. I assume the parameter is loaded as int and not as float as it is supposed to be, but not sure... Anyway, I have tested saving EXT0_ADVANCE_L 40 to EEPROM using m…
-
Thanks for your quick responses, repetier! The heater was disabled during the test. I also take specific cautions to EMI-related issues by making sure that cables do not radiate and the signals are robust. Crosstalk is minimal on all lines - checke…
-
I was confused as well - there should be no relation between both. always checking endstops is disabled. However, there is no such problem with version 0.91.7. There must be something in 0.92 which creates such problems. Configurations I used for te…
-
Correct:In my previous post, I made a mistake:It should say EXT0_ADVANCE_L, not EXT0_ADVANCE_K obviously.