nanoDLP

Rob,

With Marlin-mUVe1DLP firmware I had problems with not being able to increase acceleration, despite the values I used.
Not to mention that mUVe is a branded product and I wanted my custom build unit to be in line with a broader community.

I was about to switch to Repetier, which I had no familiarity with and then I saw your post.
I tweaked minimally to adjust for my steps per mm and endstops,  using default values mostly, and acceleration is off the roof now!
That's going to speed up my printing significantly.

I can't thank you enough for sharing your work with Marlin 1.1.x !

Last edited by Yianni-VJ (2017-11-12 01:23:13)

Just a question:
Is M114 reporting in step values now?
Is there a way to have it report in mm?

Oops, my eyes were tired last night and I jumped the gun
Thanks for the heads up.

Looks like you had some settings saved to eprom from previous firmware [V09]. (More info here).

If you have eprom disabled in configuration, this won't bother you (settings will remain the ones you configured in firmware). Otherwise, if you want EEPROM to be enabled, you will need to update the settings stored there.
This could be done once with:

M502;Revert to the default "factory settings(Stored in firmware configuration you flashed)
M500; Store current parameters in EEPROM.

This way EPROM should be updated to your firmware default. Version will now check and error should go away.

Last edited by rob (2017-11-20 17:31:34)

Glad to announce that first Marlin stable release (v 1.1.7) including NanoDLP is officially available for download from Marlin website.

The feature is officially part of Marlin and will be included in all releases >=1.1.7 (including future 2.0 version).

PS: I would suggest to put this info here: https://www.nanodlp.com/download/.

Last edited by rob (2017-12-16 10:10:20)

I will try adding it to the official marlin docs in the next days.
Short version:
To enable it, you need to enable a couple of options/flags in config_adv.h before compiling Marlin source code. (Other options should be configured according to your printer, please check your previous config).
At the end of config_adv.h you will find:

• define NANODLP_Z_SYNC : uncomment this one to enable Z_move_comp output for the following commands:

  • G1: only if command includes Z axis;

  • G4: always;

  • G28: only if homing Z or all axis;

• define NANODLP_ALL_AXIS: uncomment also this line if you want Z_move_comp output from the following commands:

  • G1: always;

  • G4: always;

  • G28: always.

PS: if it's not too much effort and cost to set up and maintain, have you considered the possibility of a wiki? This might help the community to contribute to documentation. You made a great work, but first approach is often a bit hard as there is no extended documentation. We have the forum, which is great, but sometimes you have to read though many topics to understand features. A wiki might help to resume all that info spread across the forums.

Last edited by rob (2017-12-18 11:16:28)

I spent today and yesterday moving from the patched version of Marlin to 1.1.8 which officially supports NanoDLP and the sync requirements. I must say, I feel piece of mind now - patches always feels unclean to me. Whilst doing this I also took the opportunity to install a TMC2100 and I cannot believe the difference! It actualle
made the setting up of Marlin difficult because I could not hear the ramping of the acceleration! It was a welcome problem to have!