Welcome to the SeeMeCNC Community

Ok sorry. I didn't mean to sidetrack the topic. I made my comment based on what I interpreted 626's comment to mean "I looked through the file." I guess we all have tools that work for us.

Yes, I'm on Marlin. When I referenced Repetier, I was recalling 0.83; it *was* in that version.. I've never more than quickly looked at some specific segments of the 0.90 development branch. Maybe it's been moved to EEPROM, in which case this whole business would be easier because you wouldn't have to recompile and reflash after each change.

Maybe later tonight I'll be able to study the new Repetier branch. Until then, if someone wants to look, I'd start by understanding the function that contains the primary location for use of the tower positions in the calculateDelta() or that similarly named.

I've now spent a few minutes looking into the 0.90 development code, specifcally in motion.cpp, focusing on the transformCartesianStepsToDeltaSteps() routine.

It seems that Roland did indeed eliminate the preprocessor defines for the tower positions, instead assuming that they are always separated by 120 degrees and performing all of the necessary trigonometric calculations with only the sine and cosine of 60 degrees, as can be done.

So, for those on the newest Repetier, this is going to be a bit more difficult; however, given the amount of "stuff" that has been moved into the EEPROM for this release, I think that it would be great it these six parameters could be put in there, too (there's plenty of space - I think 1k). Instead of starting the work on it now, I will email him to begin a discussion. He has seemed to be quite open to changes and improvements in the past, so I'm sure that this is something we can work out. Since I'm not intending to change away from Marlin, I'll need some testers if and/or once some code changes begin.

It might actually be a feature that could set Repetier apart from Marlin in a significant manner, IMO.

Edward,

Unfortunately this did not work for me. I went through the process of stepping through different SIN and COS values in the DELTA_TOWER_STEPS equations, but nothing had an effect on the thin spots on the left and right side of my print. Maybe I'm doing something wrong?

I have the DELTA_TOWER code in Repetier Version 0.90C and I substituted decimal equivalents for the SIN and COS values in the equations shown below as I was incrementing by +/-0.1 degrees up to +/- 1 degree:
and the DELTA_TOWER values appear to be used in motion.cpp:
Please let me know if you have any suggestions. Thanks.

Mitch

I am having a similar issue. The positive directions for both X and for Y are too close to the bed, but the negative directions are just fine. I tried the solution that edward posted regarding moving the three towers without success. If anyone has insight into this problem, I will gladly print you a pony and ship it to you when my printer works.

inventabuild wrote:Please let me know if you have any suggestions. Thanks. Mitch

I'll spend some more time looking at your case probably tomorrow, more specifically the Repetier code. But to be sure, you were re-calibrating the end-stops with each adjustment of the tower positions, right? Along with that, possibly adjusting the DELTA_RADIUS as needed? Every parameter adjustment requires a full re-calibration from the beginning to ensure the full effect of the adjustment.

I had a sneaking feeling that this would turn out to be a "works for me" situation

Edit: Also, be careful with your version numbers. Your mention of 0.90C is likely the version of your Repetier Host (on your PC). You are most likely using v0.83 of Repetier-Firmware on your RAMBo or whatever.

It seems that the v0.83 Repetier-Firmware code should apply the tower position changes just fine.

I'm not really sure of what else to say without knowing the answers to the couple of questions in my previous post: were you re-calibrating the end-stops after each parameter adjustment?

Also, can you post exactly the modified #define statements that you used (at least one for example)?

edward wrote: I had a sneaking feeling that this would turn out to be a "works for me" situation

For anyone who was following this thread - it's not just Edward this works for! I fixed my printer by rotating the Y tower one degree CCW. I think this is the solution I've been looking for for months.

Edit: I'm trying to get this implemented on Repetier, but the newest version has been changed so that there's an assumption that the towers are all 60 degrees apart. I've filed an issue. If you're using Repetier and your printer acts weird near the edge of the build platform, that would be the place to chime in.