You are not logged in.
- Topics: Active | Unanswered
#2 2016-03-26 22:04:50
- adam
- Member
- Registered: 2016-02-18
- Posts: 100
Re: nanoDLP User Interface on Github
Big thumbs up!
Offline
#3 2016-04-25 21:27:11
- adam
- Member
- Registered: 2016-02-18
- Posts: 100
Re: nanoDLP User Interface on Github
I have now forked the interface, already did some small changes to make it a little more convenient for me.
I don't know what your (or the general) workflow for this would be, but if you like some of them i'd be happy to submit pull requests.
I'm a bit rusty with web development but i know some good people who will help me out if i need something, so those changes could make their way into your version.
just let me know what you think:
Offline
#4 2016-04-25 21:44:14
- Shahin
- Administrator
- Registered: 2016-02-17
- Posts: 3,541
Re: nanoDLP User Interface on Github
I could not understand how displaying white frame helps stuck removal.
Other commit is fine please submit pull request, thank you for the help.
p.s. Was it hard to setup dev environment?
Offline
#5 2016-04-25 22:29:28
- adam
- Member
- Registered: 2016-02-18
- Posts: 100
Re: nanoDLP User Interface on Github
I use FEP Vat.
if parts of the print break off in the beginning due to small supports they of course get stuck to the vat. Especially if i print overnight and the broken off parts are small it's really hard to remove them from the vat without damaging the FEP film because they need to be scraped off .
Also it's easy to have floating debris while trying to remove.
In those cases i simply expose the whole area for 3 to 5 seconds. This fuses all small broken off parts together to form one layer, that layer is fairly stable and easily removed taking all shrapnel with it.
I remember reading on the forum about someone who does the same thing. I've been doing it by manually replacing the red calibration with a white PNG until now.
It's alright if you don't find it useful, that's why i try to split all commits to fairly granular features to cherrypick.
Let me know if you have any questions.
Cheers^^
Offline
#6 2016-04-25 22:30:31
- adam
- Member
- Registered: 2016-02-18
- Posts: 100
Re: nanoDLP User Interface on Github
oh and about the dev environment: I use windows and it was really easy, just copy files and run server. perfect.
Offline
#7 2016-04-26 07:15:28
- Shahin
- Administrator
- Registered: 2016-02-17
- Posts: 3,541
Re: nanoDLP User Interface on Github
Adam,
I just did not know how it works. It is very smart. Please, submit it too.
Offline
#8 2016-04-28 18:20:27
- adam
- Member
- Registered: 2016-02-18
- Posts: 100
Re: nanoDLP User Interface on Github
Hi,
Is there a way i can get the current layer totalArea and largestArea via JS to display it in UI? I'm finally getting around to implementing dynamic lift and having those values displayed in the frontend would help me a lot. Maybe also the number of filled areas?
Offline
#9 2016-04-28 20:26:20
- Shahin
- Administrator
- Registered: 2016-02-17
- Posts: 3,541
Re: nanoDLP User Interface on Github
Hi Adam,
What is your plan for those data on interface? Could it be useful to everyone?
You can have access to data through.
/static/plates/[plate_id]/info.jsonOffline
#10 2016-04-28 20:46:53
- adam
- Member
- Registered: 2016-02-18
- Posts: 100
Re: nanoDLP User Interface on Github
I don't believe this will be useful for others. I would have used it for collecting data about release times versus area to generate a formula for dynamic lift.
I have solved it now by reading the JSON into an excel sheet and collecting sample data over the whole print for graphiing.
Hopefully i can deduce some type of formula. I will keep you informed about the progress.
What would be helpful to me (maybe also others) would be a display of average layer time (maybe right next to the ETA)
Cheers^^
Offline
#11 2016-04-28 21:46:21
- Shahin
- Administrator
- Registered: 2016-02-17
- Posts: 3,541
Re: nanoDLP User Interface on Github
I am not sure if it worth it but we have it as LayerTime key on /status
Offline
#12 2016-04-29 07:41:59
- adam
- Member
- Registered: 2016-02-18
- Posts: 100
Re: nanoDLP User Interface on Github
got it, thanks. I'm gonna use it internally to judge the performance of dynamic lift.
Offline
#13 2016-04-29 08:42:23
- Shahin
- Administrator
- Registered: 2016-02-17
- Posts: 3,541
Re: nanoDLP User Interface on Github
Then, I am not sure if the current LayerTime would be useful to you as it average layers time since start of a plate.
Offline
#14 2016-04-29 13:23:56
- adam
- Member
- Registered: 2016-02-18
- Posts: 100
Re: nanoDLP User Interface on Github
It is, so i can evaluate it at the end of a print and see if there was any positive influence of dynamic lift. For now it's proven kind of complicated to accurately predict peeling time because not only exposed area, but also number of areas and placement have an influence. I'm diving into finding some kind of metric of weighing in all those factors via image processing.
Offline
#16 2016-07-16 15:48:13
Re: nanoDLP User Interface on Github
let me slightly join discussion , I would like to modified some buttons , a specialty in z calibration page , I have bottom up printer and I use arduino sheald for G cod .
I instal homing / Z-0 limit switch in bottom of Z axis . I make my buttons for colibration Z-0 and all work fine .
So question is how to remove the default buttons ?
I try to download zip from https://github.com/nanodlp/ui
follow this step :
1 Clone this repo
2 Download and extract Linux 32bit or Windows 32bit zip file into cloned repo folder
3 Run program by executing webserver.exe or ./webserver
I Run webserver.exe but I get black window with some warning and error ?
I use windows 7 .
what I do wrong ?
and second how to post picture in this forum ?
I need to upload it to somewhere first after just post link or have some direct way to post it ?
Offline
#18 2016-07-16 20:49:03
- Shahin
- Administrator
- Registered: 2016-02-17
- Posts: 3,541
Re: nanoDLP User Interface on Github
you can change buttons on z-calibration.html file.
It is fine if you see the black screen, just open http://127.0.0.1:8080 on your browser.
Offline
