Touch screen for NanoDLP

Yianni-VJ · 2017-11-01 04:14:37

My Nextion was connected and talking to the Pi but now it's not.
The only thing changed was unplugging the Logitech USB keyboard receiver.

I upgraded to the newer version but it did not change anything.

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

Any clues guys?

mickymax75 · 2017-11-01 09:36:45

I run rhe simply installation...i suppose it replace the older version

mickymax75 · 2017-11-02 20:51:05

Hi Julien I installed v2.0 and lcd after 30s turn it off...but when I start a printing from pc....lcd does'n t move....is still on the first screenshot

mickymax75 · 2017-11-03 15:25:28

if I click on plates button...all plates are "UNDEFINED" any help????

juliendelnatte · 2017-11-03 19:26:12

Will Check it this weekend. Could you tell me your nanodlp version?

mickymax75 · 2017-11-03 19:37:30

Upgraded at the lasy syable version.thanks a lot

mickymax75 · 2017-11-06 11:27:10

Hi Julien
This week I reinstalled all nanodlp image with the v2.0 of your sw.
Now it seams to work but when printing on nextion lcd I dont have the preview images of processing layer.
I mean the black rectangle on the left side

mickymax75 · 2017-11-07 13:13:18

Hi Julien...any news????

juliendelnatte · 2017-11-07 13:36:38

I'm working on it, there was some update on nanodlp that change the screen behavior, so I'm fixing this. there will be a V0.3 in few days!

mickymax75 · 2017-11-07 14:57:02

Ok
But we can use the v2.0...or is better use the v1.0?

juliendelnatte · 2017-11-07 15:32:14

V2.0 works but there is some bug. you can use it but maybe use V1.0 for now is better

mickymax75 · 2017-11-07 15:42:35

Ok...the beat way for downgrade veraion is simply delete folder and reinstall v1.0?

juliendelnatte · 2017-11-07 15:43:33

yes, but if you can wait 2hours, I will update the V2.0 on the github to remove bugs!

mickymax75 · 2017-11-07 15:44:12

Yes....perfect

mickymax75 · 2017-11-14 13:09:44

Hi julien
May I download the newer version?

sgraber · 2017-11-14 13:55:38

Would someone more knowledgeable care to look at my mods to the nextion 2.4" touchscreen?

https://github.com/sgraber/TouchScreen-For-NanoDLP

Based on what I can tell, I have modified it appropriately, but none of the 4 buttons I placed in the home.js file work. They show up on the Nextion screen and I can press them, but they don't call the proper URLs, which are /button/press/0 and /button/press/1. Thank you!!!

juliendelnatte · 2017-11-14 14:02:10

Hello, it's not the name software listen to but the id of the button. So you have to change

this.addListener("click_c0", () => this.nanoDLP.command("/button/press/0"));
this.addListener("click_c1", () => this.nanoDLP.command("/button/press/1"));
this.addListener("click_c2", () => this.nanoDLP.command("/printer/off"));
this.addListener("click_c3", () => this.nanoDLP.command("printer/restart"));

To

this.addListener("click_b4", () => this.nanoDLP.command("/button/press/0"));
this.addListener("click_b5", () => this.nanoDLP.command("/button/press/1"));
this.addListener("click_b6", () => this.nanoDLP.command("/printer/off"));
this.addListener("click_b7", () => this.nanoDLP.command("/printer/restart"));

sgraber · 2017-11-14 14:29:15

juliendelnatte:

Take a look at "2.4_LittleRP.HMI", which is the one I modified for my LittleRP resin printer. If you look at home.js, you will see four new buttons with objnames c0, c1, c2, and c3.

I then reference them as I did in the following two files:

https://github.com/sgraber/TouchScreen- … es/home.js

The /button/press/0 event calls an M8 gcode which disables my stepper. The /button/press/1 event calls M9 gcode which enables the stepper. Pressing either of those buttons do nothing to my stepper motor at all. If I log into http://localhost/ I can click the button on the webpage that calls these two urls and they work.

I'm at a loss why it's not working.

juliendelnatte · 2017-11-14 14:34:21

It's what I said, I looked at your HMI and your code. It's not the name of the component is sent to the program but the ID. and the event is "click_b"+id. So I sent you the fix

sgraber · 2017-11-14 15:08:30

juliendelnatte wrote:

It's what I said, I looked at your HMI and your code. It's not the name of the component is sent to the program but the ID. and the event is "click_b"+id. So I sent you the fix

Oh my goodness. Is that it? It uses the id instead of objname? /me smacks his head

juliendelnatte · 2017-11-14 15:09:09

Yep, the code I give you should work.

sgraber · 2017-11-14 15:23:23

Thank you so much!!!

Doug · 2017-11-14 15:30:50

Is the add from Usb working now?

juliendelnatte · 2017-11-14 15:31:48

Not yet, have a lot to do on my printer and not done the usb and new UX yet

rob · 2017-11-17 12:31:37

Yianni-VJ wrote:

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.

Last edited by rob (2017-11-17 14:12:09)

nanoDLP

#51 2017-11-01 04:14:37

Re: Touch screen for NanoDLP

#52 2017-11-01 09:36:45

Re: Touch screen for NanoDLP

#53 2017-11-02 20:51:05

Re: Touch screen for NanoDLP

#54 2017-11-03 15:25:28

Re: Touch screen for NanoDLP

#55 2017-11-03 19:26:12

Re: Touch screen for NanoDLP

#56 2017-11-03 19:37:30

Re: Touch screen for NanoDLP

#57 2017-11-06 11:27:10

Re: Touch screen for NanoDLP

#58 2017-11-07 13:13:18

Re: Touch screen for NanoDLP

#59 2017-11-07 13:36:38

Re: Touch screen for NanoDLP

#60 2017-11-07 14:57:02

Re: Touch screen for NanoDLP

#61 2017-11-07 15:32:14

Re: Touch screen for NanoDLP

#62 2017-11-07 15:42:35

Re: Touch screen for NanoDLP

#63 2017-11-07 15:43:33

Re: Touch screen for NanoDLP

#64 2017-11-07 15:44:12

Re: Touch screen for NanoDLP

#65 2017-11-14 13:09:44

Re: Touch screen for NanoDLP

#66 2017-11-14 13:55:38

Re: Touch screen for NanoDLP

#67 2017-11-14 14:02:10

Re: Touch screen for NanoDLP

#68 2017-11-14 14:29:15

Re: Touch screen for NanoDLP

#69 2017-11-14 14:34:21

Re: Touch screen for NanoDLP

#70 2017-11-14 15:08:30

Re: Touch screen for NanoDLP

#71 2017-11-14 15:09:09

Re: Touch screen for NanoDLP

#72 2017-11-14 15:23:23

Re: Touch screen for NanoDLP

#73 2017-11-14 15:30:50

Re: Touch screen for NanoDLP

#74 2017-11-14 15:31:48

Re: Touch screen for NanoDLP

#75 2017-11-17 12:31:37

Re: Touch screen for NanoDLP

Board footer