Welcome to the SeeMeCNC Community

Polygonhell wrote:You have to put the error in context of the machine..
If the reading is off by say 0.05mm it really only impacts the first layer since every subsequent layer is relative to it. You can see this when you level by hand, the limit switches probably aren't repeatable to better than 0.05mm, so you work with that much error on every run.

Apparently 0.05mm is considered by others to be an acceptable target. In the post hercek describes that within 3 attempts of the hall-effect leveling probe on Johann's Kossel they were within 0.05mm. He also describes the general method for measuring the bed and adjusting tower positions in the firmware (which I hope might help with my issues).

http://forums.reprap.org/read.php?178,2 ... msg-238009

8020 Inc. sells t-slot nuts that pop in from the side. They work well, I have used them on my MM.

If I have to choose between LEDs and a probe, I'm picking the probe. My printer knows how to run in the dark. But I'm glad you guys are working on getting both to work happy together.

Is there any further development with the easy probe?

foshon wrote:8020 Inc. sells t-slot nuts that pop in from the side. They work well, I have used them on my MM.

On my MM I have different colors and man do they taste good!

I've got my version of the probe (a Kossel-style probe mounted to the effector) working with the Marlin firmware. It does the deploy/probe/store sequence, but I'm left with a huge dish shape (like PRINTER_RADIUS has gone way wrong). As soon as I have that issue resolved, I'll modify the code to use Steve's "tool changer" probe and publish my results along with instructions on what to do.

I don't have time table for this however, I'm awaiting answers from folks that know WAY more about this than I do in order to get help with the dish/dome error I'm seeing after the G29 sequence completes.

g.

I dont know what modifications you have made to it, but the Kossel has a much, much smaller effector, and that may be were you are encountering issues possibly. I also plan on trying to get it running, the RMAX I worked on a few months ago is returning to me and I'll try to cut out the EZ mount and stuff for it and get that running as well. You may beat me to it though, and I will be sad.... but oh well, nothing I can do about that

It handles the bed size properly - it will probe nearly the entire bed while it does its thing. I've emailed Johann about the issue I'm seeing and I'm hoping he can help. The nozzle will strike the bed within 20mm of center as it moves. I haven't had a chance to verify the delta_radius behavior before the G29, but I'll get that done this week. The machine was tuned perfectly with Repetier and I'm using the same delta parameters with Marlin, but I've obviously missed something.

g.

I wish PRINTER_RADIUS was an EEPROM variable rather than a #define. Converting that to a float might be part of the solution. I remember reading Johann saying something about how his probing algorithm would figure out ALL that stuff, implying that modifying that variable is part of the solution.

I agree completely. I think my primary issue has more to do with a missed setting than anything else.

BTW, the DELTA_RADIUS (PRINTER_RADIUS in Rep.) ARE floats.

g.

The next repetier .90 in alpha right now allows you to mod it from within the repetier host without reflashing or disconnecting nonesense.

Flateric wrote:The next repetier .90 in alpha right now allows you to mod it from within the repetier host without reflashing or disconnecting nonesense.

Flateric, do you have a link where it discusses this alpha version, searching with google did not find anything.
I also wonder how long the average wait period is to go from alpha to beta to release.

I haven't seen any discussion about it. I grabbed the development branch and then emailed Roland questions about it.

g.

geneb wrote:I haven't seen any discussion about it. I grabbed the development branch and then emailed Roland questions about it.

g.

Same here, there is some discussion on the github itself. But more limited to suggstions and bugs.

I just keep an eye on the dev branch for changes and updates personally.

I am not sure if you guys are aware or not of this so I thought I would post anyways.

Did you know that you can adjust the extruder steps per mm, delta radius and many other critical tweaks in real time during your print to get things "Just right".

I find this in particular very very handy when tuning my delta radius to absolute perfection.

I get things as close as I can the old way and then when it is at an acceptable level for a print to actually complete. I will load up a very large flat object, cylinder, box, etc.

Set the infill to 100% and then watch the machine closely.

You can clearly see even the slightest dip or doming effect happening as you print. If it is doming go into your firmware adjust option from the menu without pausing your print.

And tweak you delta radius up ever so slightly.

Only works with v0.90. But you can get your delta so perfect, only your mother will ever know it was printed on a delta reprap!

Works well for extruder steps per mm fine tunign atc.

The secret is to wait for 10 seconds or so after hitting ok for your changes to filter down through the cache to your print and rinse repeat.

flateric, I'm working with the alpha branch right now and I'm not getting any temperature readings (bed or hot end). I've got the board type set right and I can move the effector around without issue. I copied the RAMBo pin definitions straight from the RepetierMAX pins.h file and I've checked to make sure that the temp pins defined in Configuration.h are identical.

RepetierMAX works without issue, but Repeteir .90 alpha doesn't.

Suggestions?

tnx.

g.

I had the same issue, the generic thermistor table wouldn't work for me, but all the predefined and even user defined would. I spent longer than I should have trying to solve it without getting anywhere. I eventually just gave up and used a thermistor profile that was "good enough" and compensate for the difference in the temp setting. In retrospect it would have been quicker for me to just take the data sheet and make a user defined table from it.

I've also had the alpha version lock up twice so far, although there are more settings to toy with. Overall I really like some of the changes but if I don't solve the lockup fix I'm back to the stable version (hopefully taking my fine tuned settings with me ).

The issue I'm getting is a 0c reading for both the hot end thermistor an the heated bed. Are you saying this is due to a dodgy thermistor table?

tnx.
g.

I have had far less issues with it than any other version....ever. I did go through it with a super fine tooth text editor every time I compiled to be sure every setting was perfect however. So god knows how much I changed and tweaked overall in the hours of nit picking it.

I really like it alot though. It is also the most perfect delta radius I have ever seen due to the quick adjustability during printing it offers.

It finally pulled me off Marlin even. And marlin always just simply "worked" for me every time. Now repetier does too. And no more lockups. Even when forcing binary. (I think I finally have the whole story behind that adventure, will know by morning for sure) stay tuned.

Let me know how I can help you guys with the alpha however. I have Ramps 1.4, Rambo, Azteeg (best board ever here with best drivers, thermocop support and 4 hotends with drivers and the works, and so clean and neat, really impressed with it. Also doesn't get the stuttering I get with all other variants, perhaps due to different usb chip comms?)

geneb wrote:The issue I'm getting is a 0c reading for both the hot end thermistor an the heated bed. Are you saying this is due to a dodgy thermistor table?

Exactly what I had going on. I may have missed something, but after a couple hours I decided to move on.

Did you consider copying the Type 97 table from the RepetierMAX branch?

g.

geneb wrote:flateric, I'm working with the alpha branch right now and I'm not getting any temperature readings (bed or hot end). I've got the board type set right and I can move the effector around without issue. I copied the RAMBo pin definitions straight from the RepetierMAX pins.h file and I've checked to make sure that the temp pins defined in Configuration.h are identical.

RepetierMAX works without issue, but Repeteir .90 alpha doesn't.

Suggestions?

tnx.

g.

This may appear to be a question from a stupid person but I must ask it.
I know that the Repetier host is now at .90c but what is the .90 alpha that you keep discussing?
I went to the public Repetier Github and see no .90 alpha under Master or Development of the firmware.
To play with the very latest host I believe that I should get the .90c host.
What about the firmware, should not the very latest be on the public Github or am I missing something.
For what it is worth, there seems to be two separate and distinct divisions of this Forum. The general public and the
those who are the very experienced. Sometimes the very experienced talk about things such as the .90 alpha that make
it difficult for the general public to understand. Perhaps someday we can all be experienced enough to understand.
I know I talk to much...shutting up.

If you go to the Github repository and hit the branch drop-down menu, choose development, and click on the 'changelog.txt' file you will see the version numbers flateric et. al. are referring to. The latest development branch is called 0.90alpha.

As far as Repetier-Host goes, 0.91 was recently issued (again, seen in the changelog), but has hot yet been declared stable or released on the main website.

flateric, what version of Repetier-Host are you using?

Thank you edward, now it makes sense.

Sorry about that, yes, I was referring to the firmware revision number not the host version number which are both very confusingly similar in numbering.

I was running 0.90 alpha FIRMWARE, and the commonly available 90c HOST.

But you mention that the 0.91 has just been issued. Are you referring to host or firmware now?