nanoDLP

Actually, my current code and board would cost less than $40 all in for the sensor and board and strip.

At the moment, the board accepts a list of commands:
     - ZERO: homes or zeros the position of the sensor (I recommend doing this at the "top" or starting point of your build, so that the count is accurate, but it's there so you can decide)
     - POS: responds with the current position of the axis expressed either as a number of clicks or a float equal to the mm distance traveled
     - SEEK: this will move the axis in one full step increment until it reaches the requested position (Be aware, this is currently in clicks not mm, I need to fix that)
     - STEP: this simply moves the axis by one full step increment (useful for determining the step to click count of your axis)

All communication is over USB serial interface, and is just shockingly smooth and accurate (which I wasn't expecting because let's be honest, the code is shit.)

How would you like me to proceed so that the project can be better integrated with NanoDLP?

Well, I'm offering to build and code it to your specifications. More than that, you provided NanoDLP to us, it wouldn't be very fitting for me to not reciprocate.

Honestly, I'm trying to make this a core feature of NanoDLP, because I really do think it'll make axis use and calibration easier and more reliable and repeatable for everyone (or at least everyone who chooses to use an encoder enabled axis).

So... you tell me what's best / easiest for NanoDLP

I hate to be a smartass, so if I'm coming off that way, I apologize in advance, but I'll wire it however you tell me to wire it. I'll work this weekend / next week on it, both as a standalone board as well as seeing what I can accomplish with the RPi's GPIO's alone and I guess we can go from there.

I'm a functional programmer, not a good one, by which I mean I'll get the job done and it'll work, but it may not be pretty or best practices. I'm more familiar with C / C++, but I have passing familiarity with Python, Java, Ruby, Perl, Bash, and whatever flavor of JS you want to write Node.JS apps in.

What's NanoDLP actually written in so maybe I can start with that? Otherwise we'll probably end up having to port Python code.

Sold. I'll get it done as soon as I can!

Stalled at the moment, I haven't had a chance to sit and work on it. I'll try to get it to the top of my list again here shortly. The real world has intruded a bit recently.

I know what I talk about

Last edited by DLprinter (2016-08-22 18:27:59)

for CNC yes it really useful , but for printer with one Z-axis , it is more than not necessary .
use micro-stepping and small lead in screw

backXslash,

For response as number of clicks, I believe format such as n+n could be prove useful. 
Lets say we send command to platform already on vat floor to go down 10 pulses down, after 5 pulses vat floor push the motor back for 5 pulses.

DLprinter,

Even if it does not help increase accuracy on one axis. It still could prove handy for mechanical and electronic fault detection and floor detection.

Can't say my time was wasted, after all, it was my time to spend. Nice that you've got a wax mill I suppose though... good for you? The ... is with you people telling me that encoder support is a bad idea or a waste of time? The ... do you care? It's my time, I think it's a worthy pursuit, and even if you don't happen to use it with NanoDLP, it'll probably end up being a useful feature to someone at a later date.

Jesus christ you entitled ...

End rant, I suppose, and thank you Shahin for your patience and support.

I don't care your .... time .
just advice from my experience
but seems is not for you ,
you can do whatever you want even use direct drive with 5 horse power
good luck with that
amen !

Shahin
is it  better like this ?