You are not logged in.
I guess (Shahin will know better) because what you are going to project to resin is an array of pixels (your projector resolution). So generating PNGs with the exact resolution of your projector should ensure projector pixels will match the slice image pixels. This enables to exploit at maximum your theoretical resolution.
If image resolution is readapted at the projection time, you will never know if pixel correspondence would be correct.
Great, thanks for the info. I will check it out next days and share back the solution.
I guess it was the main limitation, even though I was running some printer proprietary UI on the same RPi2 and it had live video option with no problem.
By the way, how about visualizing last photo at least?
It would be great to be able to update lamp hours through external command. Same as there is a similar option to switch projector on/off. I have a non serial model, but I can read the value through external program.
Similar usb/serial options might be useful, too, even if some might be worked around.
PS: is there a way to show output from a command in "confirmation window" arisen from customized buttons? Or, vice versa, to have a button open a "input value" window to take arguments for a command?
I agree, I would be interested, too, or at least have a way to show the last photo. When I hit "Take a photo", it makes an attempt to show "printing view" but then go back to normal dashboard with no photo shown.
Do it fails even with correct password? Otherwise it is the expected behavior.
That is what I meant, it fails even with correct password. Password seems to be stored correctly (I tried before setting different user names for admin and dashboard but same password and hashes do match in machine.json) but check always fails.
Please, try the beta version and let me know if it fixes the issue.
I was on build 1706. I updated to the latest [1734]; current behaviour is:
If I leave blank the "Dashboard" user and password:
I can access dashboard without password;
Password is asked for accessing any other tab;
If I put a "Dashboard" user and password:
Login is required even for dashboard;
Dashboard user login keeps failing.
I'm stuck with the same problem on a RPi2B and a Nextion Basic 3.5". I'm running v2. I think I tried all solution I saw online, but I can't find the issue.
I initially thought it was a permission/serial port issue, but after some checking I just realized it's should not.
I did find the problem. I just did not realized you need to change the url in config.json when using non-standard web interface port.
{
"url":"http://localhost",
....
to
{
"url":"http://localhost:PORT",
...
where PORT equals to your port number.
I am writing back in case someone else could find the same problem.
It might be nice to add this info in the README for other users, just in case. Or otherwise any kind of debug info when program cannot connect to the interface. I had been messing around a lot with the serial settings, thinking it was a pi serial configuration problem. Killing node process and running it from console with
DEBUG=* node /home/pi/nextion/bin/index.js
I could notice that program hang after successfully sending the first commands (sleep=0,bkcmd=3,etc) but there was no debug info like "cannot connect to url". It might be helpful to debug configuration.
PS: Thanks again for the great work!
I just noticed this msg in Terminal:
EPROM version mismatch (EEPROM=V09 Marlin=V41)
Is it something to be concerned about?
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.
I was using double user authentication (admin and viewonly) but the normal user login is not working.
It should be a bug on login check. Admin login works fine, normal user keeps failing and redirects to login page.
It seems that password for Viewonly user is stored correctly but the check fails. (I tried setting same password but different user, and hashing match on db/machine.json).
Thanks in advance for your help.
I recently submitted a Pull Request to the 1.1.x Marlin branch, so future releases could include G1 commands Z axis synchronization as an option in configuration.h.
PR is yet under revision, so if you want to try it meanwhile here you can find latest Marlin 1.1.6 release + z_sync addition.
https://github.com/robpower/Marlin/tree/1.1.x-NanoDLP
Info on how to enable the option and any feedback in the following thread:
https://www.nanodlp.com/forum/viewtopic.php?id=958
PS: of course it is stock Marlin, you need to also change configuration.h according to your printer requirements.
The output.log in Nextion folder says:
error opening port /dev/ttyAMA0 retry in 2 seconds
The cmdline.txt reads as follows:
dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=20bc60e1-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
I'm stuck with the same problem on a RPi2B and a Nextion Basic 3.5". I'm running v2. I think I tried all solution I saw online, but I can't find the issue.
I initially thought it was a permission/serial port issue, but after some checking I just realized it's should not.
/home/pi/nextion/output.log:
{ nextion: { port: '/dev/ttyAMA0', sleep: 30 },
pushbullet: { apiKey: null } } { apiKey: null }
connect to port /dev/ttyAMA0
list [ { comName: '/dev/ttyAMA0',
manufacturer: undefined,
serialNumber: undefined,
pnpId: undefined,
vendorId: undefined,
productId: undefined } ]
connected
On startup I have a root process running "node /home/pi/nextion/bin/index.js". Not sure if it should be root. I tested as user pi running the same process from command line and got the same output [connected].
Any hints? Is there any command I can try to send through minicom to completely exclude any communication-related problem? Like the command display is expecting to move to the main screen.
Great, thanks for the super fast response.
Is there any command to trigger "Ramps Reconnect" from GCODE boxes?
Our idea is to have the following setup for strict safety regulations:
-Raspberry Pi always on;
-RAMPS control board and projector power controlled through GPIO --> 230V 5V relays
This way we can have projector and RAMPS switched off while not using, without the need for the user to do it manually.
I would like to know: is there any command to use with [[Exec Command]] to trigger RAMPS reconnect? This way we can configure it to automatically switch everything on before printing, trigger reconnect and start all needed operations.
Thanks in advance for help!
I was just suggesting as I didn't know if it the timing behaviour just passed unnoticed; I understand priorities.
About embedding values in the mask, I agree it might be an interesting option.
If we can help somehow in development, please tell.
If you check it outputs both values: first mm, then pulses. Are you having any issue? Example (320pulses/mm):
X:0.00 Y:0.00 Z:180.00 E:0.00 Count X:0 Y:0 Z:57600
I had been printing a calibration plate (great tool, btw) and I noticed there is no real indication about print duration.
Once generated, it would be great to be able to check print time at least on the plates page.
Furthermore, while printing it only shows (in loop) ETA related to a single layer exposure. No info about the whole process percentage or remaining time.
Not sure if it might be complicated to calculate (print work a little different from normal models), but would be great to add the feature.
Thanks in advance for support.
Yianni-VJ,
I'm glad to see it was useful to someone else, too.
Hopefully it will be merged soon to the main codebase.
PS: I tested it myself, and it works ok. Anyway, in case you notice any possible improvement I'm open to feedbacks.
Thanks for the insight about nginx and for the quick response. I will investigate it further next week.
I understand the feature is not priority, by the way if I can found a nice solution I will share it back here.
Meanwhile any other suggestion by anyone is welcome.
[EDIT] Starting from version 1.1.7, Marlin now officially include Z_move_comp as an option, no need for using outdated patched firmware.
Download latest version from http://marlinfw.org/meta/download/.
[/EDIT]
Dear all,
In case someone might be interested, I branched Marlin 1.1.x and added NanoDLP Z axis synchronization ("Z_move_comp" output). This way you can use "Z_move_comp" output with latest Marlin features.
Compared to original MuveDLP patched firmware, I restricted the "Z_move_comp" output to G0/G1 commands which refers to Z axis. Commands related exclusively to other axis won't be affected.
I think this is a more correct implementation, it would be great if someone could confirm this.
You can clone it from here: https://github.com/robpower/Marlin/tree/1.1.x-NanoDLP.
Once downloaded, you should enable "NANODLP_Z_SYNC" option in "Configuration_adv.h" before compiling (uncomment line 1432: "//#define NANODLP_Z_SYNC" --> "#define NANODLP_Z_SYNC").
PS: I also branched the bugfix version and submitted a pull request to the main Marlin codebase. When accepted, the feature will be included in future releases so we could be able to upgrade and benefit other new Marlin features.
Hi,
First of all thanks for this great tool.
We run a DLP printer with multiple users. For management and security purpose it would be interesting an option to enable multiple users (non-admin level), so each one would have its own credentials.
It would be mainly of interest being able to check through logs who used the printer/changed resin profiles/etc.
Optionally it might also be interesting the possibility of more detailed privilege control (permission to edit profiles but not main configuration, print only, full admin) if not too complicated to implement.
Thanks in advance for any possible help.
PS: is there any way to actively contribute to the code?
Dear all,
I've been visiting the forum for a few months now and I finally registered to ask for some help and hopefully give back to the community.
I'm working on porting an existing custom bottom-up printer (projector below the VAT) to NanoDLP.
I would like to check if I got some basic concepts right.
My first step was change proprietary electronics to a RAMPS-compatible RUMBA board. I installed patched Marlin firmware.
Muve patched firmware is stuck at version 1.0. I saw there is also a patched version 1.0.2 by user WheresWaldo with less changes from original firmware.
1) What are necessary modifications to original Marlin to work with NanoDLP? I guess the main one is "Z_move_comp" message after G0/G1 Z axis move. Are there any other necessary or suggested?
2) Is there any chance to contribute this changes back to original Marlin as a configuration option? This way they might be inherited by newer versions (1.1.5 is out and many functions has been added/improved).
3) Was NanoDLP originally developed for top-down or bottom-up setup? I ask it to understand in which case modification have to be taken into account (Z axis and homing direction, etc).
4) What should be correct Z axis configuration for a bottom-up setup. Current config is Z+ direction downwards, Z- upwards, with a Z-min endstop placed at the top. It means moving Z in positive direction (i.e. G1 Z100) lowers the lift downward toward the VAT.
Not sure if this might generate confusion (seems counter-intuitive), so I would ask if is there any standard about Z axis definition. I know you can have same results flipping all settings, but I would like to follow the standard (if any).
Thanks in advance to all contributions. Hope I didn't mix too many questions in one post.