Repetier Firmware

[Flateric]

I don't feel you should adjust your values to correct for Onyx bow. This bow will be different for different temperatures and will change over the age of the machine and also be affected by ambiant tempuratures.

Rather I think you should try to correct the bowing issue through the use of an aluminium plate or glass and do everything you can to adjust for a flat surface and calibrate assuming the surface is flat.

Trying to calibrate to the bow of the Onyx will be un-realistic for the reasons I list above and make you crazy going in and out of the firmware endlessly trying to compansate for something that will never stay the same from day to day or even print to print for that matter.

This is my thinking anyways. Correct the bow rather than try to work with it.

[Polygonhell]

I don't think that's true, but I may have missed it in the firmware.
There are literally only 3 values that matter, steps per, delta radius and whatever repetier calls arm length. There are a lot of other values that go into delta radius, but it's the only vaue used in the calculation, the other values as far as I can tell are used directly.

I take this back.
I looked at the code this morning and AXIS_STEPS_PER_MM is used directly (rather than the stored EEPROM value) to calculate a constant used in the delta motion.
That means that it MUST be correct in the firmware, not just the EEPROM.
This is probably the issue people seeing odd motion at the edge of travel are seeing.

[Polygonhell]

I don't feel you should adjust your values to correct for Onyx bow. This bow will be different for different temperatures and will change over the age of the machine and also be affected by ambiant tempuratures.

Rather I think you should try to correct the bowing issue through the use of an aluminium plate or glass and do everything you can to adjust for a flat surface and calibrate assuming the surface is flat.

Trying to calibrate to the bow of the Onyx will be un-realistic for the reasons I list above and make you crazy going in and out of the firmware endlessly trying to compansate for something that will never stay the same from day to day or even print to print for that matter.

This is my thinking anyways. Correct the bow rather than try to work with it.

DELTA RADIUS is not designed to correct for bow in the onyx. You should have a glass sheet or similar flat surface to calibrate against.
It 's to correct for manufacturing variances, if it is not exactly right the head will move in an arc over the build plate rather than horizontally.
Mine has a correction of 0.6mm in it, but it's likely everyones is slightly different.

[x95braat]

The 'other' Kevin here (Kevin Wixom started the thread). John had adjusted the firmware as mentioned. We could not alter just the delta values to fix the issue. We were seeing an excessive amount of convex motion before the new firmware and the adjustments. I now have the build platform leveled out and all is good. I spent some time with the extruder adjustments on Sunday and should be ready to further my test prints this evening.

I was going to review the code to better familiarize myself with what is going on to create the issue once I had the rest of the settings worked out.

Kevin - maybe we should get together again with the machines side by side and compare the firmware and Repetier settings.

[cambo3d]

there seems to be a lot of discrepancies in comparing johnoly's repetier firmware that's having trouble, compared to polygonhells repetier firmware that works.

using winmerge, I found several mistakes. is john starting from scratch here? other than the pulley thing, there's a lot of mismatch.

[Polygonhell]

there seems to be a lot of discrepancies in comparing johnoly's repetier firmware that's having trouble, compared to polygonhells repetier firmware that works.

using winmerge, I found several mistakes. is john starting from scratch here? other than the pulley thing, there's a lot of mismatch.

He might be pulling from the current release I haven't merged the 0.82 changes in (I couldn't see anything worth the effort when I looked at the changes), I also manually configure the LCD, since there was no direct support for the rostock LCD when I first set it up. I think there is now.

The having to have the steps match in the Firmware and in the EEPROM is an issue for both builds, I filed a bug on git hub this morning, he's going to try and fix it for the 0.90 release.

[Flateric]

Poly, you don't get this enough, Thanks!

I appreciate your puttig up with my endless stupid questions and cannot say eough how much you have helped me through all this as you have others too.

Seriously your effort make a huge difference in this community.

I have no clue what you do in real life but I figure you for some kinda genius type tech guy, lol.

[Eaglezsoar]

Poly, you don't get this enough, Thanks!

I appreciate your puttig up with my endless stupid questions and cannot say eough how much you have helped me through all this as you have others too.

Seriously your effort make a huge difference in this community.

I have no clue what you do in real life but I figure you for some kinda genius type tech guy, lol.

I'll second that.