The LCD node clears any line it writes to. It sounds like you are using 2 LCD nodes and they are fighting for control. You need to rewrite your code to only use 1 LCD node and change strings being fed to it. A select node could be used to feed the lcd input.
Thanks for the reply, that’s indeed what i did and what’s happening. i don’t know if a select node will do the job.
This needs to be part of the ui, welcoming menu. So the first message for example “welcome, press next to continue” when the next button is pressed, the next message is presented and the first is never shown again until the power is turned off and on again ofcourse.
Could you help me with this if it’s not to much to ask?
Sounds like a perfect use for select node. Select node defaults to displaying one message (I believe the far-right option), so that would be your welcome message. The next button would be tied to the pulse pin for the next message. You can expand the select node to add additional messages that receive pulses from other buttons, or timers, or logic code to count button presses, or…
i’m very sorry to bother you again, would you mind drafting it up and posting it here? I’m an absolute beginner when it comes to coding and i can’t seem to figure it out
I would expect “test page 2” is always shown… I think the button is not being read at all. Do you set up its PORT correctly? Also, does it have a pull-up resistor in hardware?
Anyway, to change the message on button click, link the PRS output to S2, not DONE.
Yes, when selecting the node for the button i put in the correct port no. And i pulled it up with a 10K resistor. After changing the output to prs it still doesn’t work… Any suggestions?
I have also read your comment on another topic. which is about 4051 multiplexing. and you recommend using the nth-input node. can you explain about that thanks
nth-input works very well but being a “node-patch variadic” resource consumption is very high and in my case I could not use it. I made one node whose name “dataselect” works the same and consumes less resources. It is a personal opinion, after doing many tests.
Ideally, use the native node in this case nth-input, now if it is limited in resources you can use dataselect, maybe later nth-input will change. They work the same, they are the same, but one is in patch mode of nodes and the other is in c ++