Quantcast
Channel: Reprap Forum - Controllers
Viewing all articles
Browse latest Browse all 10211

Re: Unusual stepper ratings - vref settings for new Melzi

$
0
0
Thanks for that reply - I appreciate the input :)

Yes it's been frustrating getting to this point with all the problems but only from the perspective that it was meant to be something that would have worked more or less straight away.
I do enjoy the learning, and getting a better idea of what's what by virtue of it not working until now. I would be very lazy about taking the time to learn though had this thing worked from day 1, so all this is to my advantage really.

Re' my two remaining issues I'm not at this point hugely concerned over the bed temperature reading.
As I say it's reading 15C above real temperature, but I'm wondering if I can cater (temporarily at least) for this by setting the working temp 15C higher than it currently is?


More importantly, the one issue I really have to address before I can do prints properly is the rate that the Z axis moves.

I realised that with all the corrections and faults I've had to look at and resolve I've actually overlooked the part of the commissioning/calibration process whereby I should measure how far each control moves, relative to the manual commands issued for a given distance.

I think most movements are close to being correct, but know for sure that when I tell the Z axis to move 10mm, it actually moves closer to 2mm!! So I assume from this that the step size setup for Z at the very least is incorrect. I've never looked at those settings so I will investigate tonight and look on the wiki for how I calculate all that stuff.

I will also look for the setting you described (DEFAULT_AXIS_STEPS_PER_UNIT) to see how mine is currently set!

Hopefully once that's done I'll be able to actually print something properly, but I'm still really pleased that I got it do 'something' anyway.

I get the point of the suggestion re' changing the firmware, but I think with getting this one so close I'm going to persist with it for now as it's so close to working correctly now. I don't want to potentially go back to square one again with different firmware if I can avoid it easily.

Cheers

Viewing all articles
Browse latest Browse all 10211

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>