I like to try some of the GCB-code with the Nextion displays.
I see a lot of Nextion displays to buy online mostly:
NX3224T024, NX3224T028, NX3224T032, NX4832T035
1) Are they all the same type and compatible with gcb code-files?
2) Are they all multi color, touchscreens?
3) Are these the correct ones ? NX3224T024 - NX4832T035
4) Are these "New Version" types supported with gcb? NX3224T024 - NX4832T035 New Version
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
2) Touch is supported with the Nextion GLCD driver but does gcb also get a notification that the screen is pressed on a specific coordinate system?
4) Sorry, I see that in my first post the type number "NX3224T024 - NX4832T035 New Version" isn't the same as my supplied link NX3224K024, NX3224K028, NX4024K032, NX4832K035.
Are these types "NX3224K024, NX3224K028, NX4024K032, NX4832K035" also compatible with gcb code-files?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
They don't read x,y pressed in gcb I think,
You have to use the nextion gui and design boxes on the screen which have numbers and gcb detects the box area pressed...but I may be wrong.
I have 2 nextions and using the gui is a pain and flashing the display.
What's in the gcb nextion demos about touch?
I'd read up on them before buying as they're not cheap.
Just look up a youtube experts video :)
I just spent ages getting a ssd1306 to work to find it was duff!
Look at the silly 2 colour version...that worked.
this is the nextion touch gcb
this line- GLCDSendOpInstruction_Nextion( "vis", "t0,1" )
Great work by Anobium sorting nextion for gcb but not like other displays to use.
The work is in the nextion gui which is where you create your screen.
I don't know if there's a way of not using it to even get a blank screen that gcb glcd
could work on. ..... and the displays look cool but it's a slow display...
well mine are drawing circles etc
' ----- Main programwait1s;Disable all the objects;Hide or Show component on current page;- show will refresh component and bring it to the forefront layer;- hide will remove component visually, touch events on the objects will be disabledGLCDSendOpInstruction_Nextion("vis", "255,0");Enable this object so we can show the values of the X, Y positionGLCDSendOpInstruction_Nextion("vis", "t0,1")
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Nextion display use in gcb is mostly in combination with the Nextion Editor?
The Nextion Editor looks and feels a lot like "Visual Basic" to me with placing control components and editing properties and code programming.
I think Nextion is for more complex pc-like projects versus ssd1306 is for simple projects to display values and some graphics.
The instructionset looks easy to do but time will tell.
"displays look cool but it's a slow display."
Maybe the Arduino is to slow to send as the master to the slave nextion display?
— The Enhanced Series hardware feature of 3.5″ and above is more powerful than Basic Series in terms of MCU, Flash Storage and SRAM.
— The Enhanced Series integrates RTC for keeping accurate time, EEPROM for users’ data storage and 8 digital GPIOs (4 PWM capable).
I hope the enhanced serie NX3224K024-NX4832K035 are compatible with gcb code-files, for faster displays.
Last edit: Haroen 2020-12-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Have a look at the video and I explain the relationship between the Nextion IDE and your code. You have two choices - 1) develop the solution using the Nextion IDE and serially send from the micro-controller to the required instructions - you need to learn the Nextion IDE and GCB serial or 2) Create a very simple solution in the Nextion IDE (I think I have published this already) and get the micro-controller to send GLCD commands.
I have a few Nextion displays - the NX4832T035 is similar.
The Nextion TFT board uses one serial port to communicate. It lets you avoid the hassle of wiring. Nextion editor has mass components such as button, text, progress bar, slider, instrument panel etc. to enrich your interface design. And, the drag-and-drop function ensures that you spend less time in programming
The Nextion displays are 2.4 to 7.0 inches and range from 320240 to 800480 pixels. The connections are 5v, 0v, SerialIn and SerialOut. Great Cow BASIC supports hardware and software serial connectivity.
See GITHUB for the set of Great Cow BASIC demonstrations for the Nextion displays. See Nextion demonstrations on GITHUB, or your local install.
The Great Cow BASIC Nextion library interfaces to the display via the serial port. The library enables a full set of GCLD commands (see the help ) and the library supports hardware and software serial communications.
The solution architecture is down the requirements. Is the Nextion as standalone solution (lots of logic operations in the Nextion are possible) with the micro-controller as the data feed? or, where the micro-controller the master with the Nextion a display device?
It may be best for you to describe your requirements - as a Nextion may be over-kill.. or it may be perfect.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I agree Anobium. Nice displays that you can just use glcd to use
or for their extra cost, use the gui to make very nice dials or display and scroll data.
This makes sense if you are going to use what you are paying for Haroeon.
You said you need a large touch display for a lathe.
I haven't looked up large touch screens. I don't know the biggest supported by gcb.
An android pad comes to mind.
What would you want the screen to look like, will there be sub screens?
nextion gui handles events for it working on it's own ie display
or is all that's needed a few virtual buttons?
It's a choice indeed,
if you just want a glcd with touch but large screen
then what's the biggest supported by gcb?
nextions are serial and so slow especially if you used gcb glcd to do everything.
but if you set up the display with the gui then not a problem just receiving data.
as I only have a low spec nextion I can say it was worth the cost just to try it.
They jump up in price for other models so think carefully.
By the way..if a nextion is connected rx to tx and tx to rx then avr usb don't flash.
got to disconnect tx to rx.
and you can't do touch unless you set the area in the gui
Last edit: stan cartwright 2020-12-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried the usual circles and lines and it was not as fast as other spi but worked!
Brill you sorted nextion for gcb glcd
I only got one to play with and thought there's a default serial speed and no faster.
I think the idea is sort the display with the gui and use the controller as little as possible,
but you could use a pc
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@Anobium, you have made great video's to show the Nextion IDE and gcb code relationship, thanks.
@Stan, your info, pics and video's show that it can be done, that's good for my motivation to give it a try.
In the past I decided in my projects to use less displays and more LED's, beeper and even speech modules as a way of user communication feedback. Yeah, I know that silly :)
But now I know that displays cost less, display drivers are made easy with simple (empty) microcontrollers, displays are smaller, with colour, choice OLED instead of LCD, multi lines, fonts choice, touchscreens, Nextion editor with mass components such as button, text, progress bar, slider, instrument panel etc. are all options to choose from for existing and future projects.
The projects that I have could use a display implementation or upgrade with some of the above!
Even if all that's needed are a few virtual buttons.
These two methods of design intent with the Nextion IDE and gcb that Anobium mentioned, I have to play with to know what and how to implement. It's a choice indeed!
I'm just scratching the surface with gcb possibilities here. I can learn a lot from you guy's.
nextions are serial and so slow especially if you used gcb glcd to do everything.
but if you set up the display with the gui then not a problem just receiving data.
I think the idea is sort the display with the gui and use the controller as little as possible,
Yes, true "Anobium: Nextion may be over-kill.. or it may be perfect", but also true "Stan: as I only have a low spec nextion I can say it was worth the cost just to try it". For some of my projects that can be sufficient.
Especially when the cost of an 20x4 OLED is €37 in comparison and with it's big pcb it's twice the size!
The Enhanced Nextion Series hardware feature of 3.5″ and above is more powerful than Basic Series in terms of MCU, Flash Storage and SRAM.
These enhanced K-serie up to 3.2" (NX3224K024, NX3224K028, NX4024K032) are less enhanced then the 3.5" and above (NX4832K035-NX4832K070).
I bought the 3.5" (NX4832K035) to try the enhanced speed to see what is maximum possible.
I will share my findings to help the GCB-community.
I need a large Nextion touch display for my lathe and there will be sub screens, yes.
I thought of the idea to add small pics tutorials screens with colour drawings as a jpg or video to display instead of drawing and writing the tutorials from code.
This can improve the users speed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My mate is an engineer in a chocolate bar factory and when got the job found lots of industrial touch screens but everything is rs232... ie old and no info. Just dumped .
You can get an android tablet for £50 but interfacing to a lathe ???
with just gcb and a dumb display, it would be draw coloured boxes with text
then using the gcb touch for display
is the touch x,y within any box
if so highlight it. if touched again then run command.
bit of a simplification but not many gcb users use glcd.
using nextion I would use the gui to place/colour/text boxes...pretty ones
but then have to define their attributes or what they do and it takes effort to learn.
You have not mentioned how these press screen buttons are going to control a "cnc" lathe.
What is wrong with real buttons with labels.....like a microwave oven?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes Stan, salvaged components are free but not always what we want or need.
Android for technics real-time, I have not done that and don't know how to interface with it.
The approach you mention could be the solution.
I don't know if the Nextion Editor has only the components placement screen configuration with subscreens or that it has it's own programming envirement too where some Nextion code also can be run.
You have not mentioned how these press screen buttons are going to control a "cnc" lathe.
The idea is to control the spindle speed of the lathe depending on the tool type, cooling, diameter, etc.
What is wrong with real buttons with labels.....like a microwave oven?
The buttons function (label text) will change as I browse through the (sub)screens. Rotary encoder could work but while working with the lathe I want to switch between options fast.
Rotary encoder is like working on the pc with the (shift)TAB-button instead of a mouse or a touch screen that is the fastest selection method.
P.s. Your mate is a lucky guy, instead of looking for touch screens in the factory, I would search for lost chocolate bars :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I liked Evans nextion video and the bit where he shows touch x,y in a box only.
I think learn/use the nextion gui for its open new screens from menus.
It's what you're paying for. and they are very clear and bright displays.
It's down to price and what's needed. I would see if the gui simulates events that you could use.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Based on Evans video I also found out that in the Nextion Editor these K-serie enhanced displays are not the latest or best models.
When I select "NEW" in the iconbar a setting-window opens where I first have to select the Device-model type "Basic = T-serie, "Enhanced = K-serie" or Intelligent = P-serie".
Then I have to select the Display orientation.
Based on the higher P-serie selection the toolbox will have all components to choose from like video, audio, combo-box etc.
Last edit: Haroen 2020-12-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is what I could find in the Intelligent = P-serie:
NX4827P043 (480x272)
NX8048P050 (800x480) NX8048P070 (800x480) for €79
NX1060P070 (1024x600) NX1060P101 (1024x600) for €137
They alle have audio and video options in the toolbox and for the larger ones instead of that price (>€79) I better take an old MS-tablet in combination with an (gcb) arduino to interface stuff!
How much faster than the T- & K-series this P-serie will communicate to gcb I don't know?
The smallest NX4827P043 with 4,3" and NX8048P050 with 5,0" could be an option to use but I couldn't find a price tag?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1) Did this P-serie Nextion display work on gcb?
2) In the Nextion Editor side menu "toolbox", are all the components to place selectable?
3) Was it faster over serial communication to the gcb chip than the T-serie and K-serie?
4) Is your NX8048P070-011 touch capacitive or resistive?
5) This is the 800x480 type of the 7" version?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for all the questions, it's all new to me.
1) The developed library works then on all Nextions T-K-P-series?
2) Let me rephrase that question. If I open the Nextion Editor then I see in the upper left corner a sub-window called "Toobox" with selections for Text, ScrollingText, Number, Xfloat, Button, ProgressBar, Picture, ComboBox, Video, Audio, etc. called components I think.
Are all these components (ComboBox, Video, Audio) selectable to place on the NX8048P070-011R display and do they actually work with gcb?
3) Datasheet reads 921600 bps max for P-serie! And T+K-serie 115200 bps max. So Nextion T+K serial speed to gcb chips are the same! Your P-serie version is very fast!
4) Resistive single touch.
5) Yes.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That is the intent. The library is extensible and you can add your own functions to add more functionality.
If the object in the Nextion Editor is addressable via the serial then yes.
The BPS is not critical. You are actually sending very little data to the display. Personally, I would use 9.6k BPS to ensure the quality and distance.
OK
OK
Want to buy the one I have here?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I like to try some of the GCB-code with the Nextion displays.
I see a lot of Nextion displays to buy online mostly:
NX3224T024, NX3224T028, NX3224T032, NX4832T035
1) Are they all the same type and compatible with gcb code-files?
2) Are they all multi color, touchscreens?
3) Are these the correct ones ?
NX3224T024 - NX4832T035
4) Are these "New Version" types supported with gcb?
NX3224T024 - NX4832T035 New Version
The design intent is have all GLCD operate using the same GCLD commands.
1) Yes
2) This Nextion product specific but the Nextion GLCD driver supports touch
3) It the two products are valid then yes.
4) Yes.
2) Touch is supported with the Nextion GLCD driver but does gcb also get a notification that the screen is pressed on a specific coordinate system?
4) Sorry, I see that in my first post the type number "NX3224T024 - NX4832T035 New Version" isn't the same as my supplied link NX3224K024, NX3224K028, NX4024K032, NX4832K035.
Are these types "NX3224K024, NX3224K028, NX4024K032, NX4832K035" also compatible with gcb code-files?
They don't read x,y pressed in gcb I think,
You have to use the nextion gui and design boxes on the screen which have numbers and gcb detects the box area pressed...but I may be wrong.
I have 2 nextions and using the gui is a pain and flashing the display.
What's in the gcb nextion demos about touch?
I'd read up on them before buying as they're not cheap.
Just look up a youtube experts video :)
I just spent ages getting a ssd1306 to work to find it was duff!
Look at the silly 2 colour version...that worked.
this is the nextion touch gcb
this line- GLCDSendOpInstruction_Nextion( "vis", "t0,1" )
Great work by Anobium sorting nextion for gcb but not like other displays to use.
The work is in the nextion gui which is where you create your screen.
I don't know if there's a way of not using it to even get a blank screen that gcb glcd
could work on. ..... and the displays look cool but it's a slow display...
well mine are drawing circles etc
I take it back that glcd needs gui cos here's the standard demo on nextion NX3224 T024.
I still think touch is not as easy. I COULD BE WRONG!
They are quite clear and brighter than cheaper displays,...but the simple glcd demo is slower
than other glcd displays.
Nextion display use in gcb is mostly in combination with the Nextion Editor?
The Nextion Editor looks and feels a lot like "Visual Basic" to me with placing control components and editing properties and code programming.
I think Nextion is for more complex pc-like projects versus ssd1306 is for simple projects to display values and some graphics.
The instructionset looks easy to do but time will tell.
Maybe the Arduino is to slow to send as the master to the slave nextion display?
I hope the enhanced serie NX3224K024-NX4832K035 are compatible with gcb code-files, for faster displays.
Last edit: Haroen 2020-12-27
Hareon - the Nextion are supported via GLCD see https://www.youtube.com/watch?v=1g3QHYfU04c or you can create you own serial interface.
Have a look at the video and I explain the relationship between the Nextion IDE and your code. You have two choices - 1) develop the solution using the Nextion IDE and serially send from the micro-controller to the required instructions - you need to learn the Nextion IDE and GCB serial or 2) Create a very simple solution in the Nextion IDE (I think I have published this already) and get the micro-controller to send GLCD commands.
I have a few Nextion displays - the NX4832T035 is similar.
The Nextion TFT board uses one serial port to communicate. It lets you avoid the hassle of wiring. Nextion editor has mass components such as button, text, progress bar, slider, instrument panel etc. to enrich your interface design. And, the drag-and-drop function ensures that you spend less time in programming
The Nextion displays are 2.4 to 7.0 inches and range from 320240 to 800480 pixels. The connections are 5v, 0v, SerialIn and SerialOut. Great Cow BASIC supports hardware and software serial connectivity.
See GITHUB for the set of Great Cow BASIC demonstrations for the Nextion displays. See Nextion demonstrations on GITHUB, or your local install.
The Great Cow BASIC Nextion library interfaces to the display via the serial port. The library enables a full set of GCLD commands (see the help ) and the library supports hardware and software serial communications.
The solution architecture is down the requirements. Is the Nextion as standalone solution (lots of logic operations in the Nextion are possible) with the micro-controller as the data feed? or, where the micro-controller the master with the Nextion a display device?
It may be best for you to describe your requirements - as a Nextion may be over-kill.. or it may be perfect.
I agree Anobium. Nice displays that you can just use glcd to use
or for their extra cost, use the gui to make very nice dials or display and scroll data.
This makes sense if you are going to use what you are paying for Haroeon.
You said you need a large touch display for a lathe.
I haven't looked up large touch screens. I don't know the biggest supported by gcb.
An android pad comes to mind.
What would you want the screen to look like, will there be sub screens?
nextion gui handles events for it working on it's own ie display
or is all that's needed a few virtual buttons?
It's a choice indeed,
if you just want a glcd with touch but large screen
then what's the biggest supported by gcb?
nextions are serial and so slow especially if you used gcb glcd to do everything.
but if you set up the display with the gui then not a problem just receiving data.
as I only have a low spec nextion I can say it was worth the cost just to try it.
They jump up in price for other models so think carefully.
By the way..if a nextion is connected rx to tx and tx to rx then avr usb don't flash.
got to disconnect tx to rx.
and you can't do touch unless you set the area in the gui
Last edit: stan cartwright 2020-12-26
speed comparison https://www.youtube.com/watch?v=ZwVSyxAuo2o
serial slows what is a fast display down it seems
Last edit: stan cartwright 2020-12-26
Nice video but it may not be a fair comparison, but, your video shows the issues to be address.
In the Nextion code there could be specific delays in the serial comms or other delays that could be optimized. Have a look at the delays.
I tried the usual circles and lines and it was not as fast as other spi but worked!
Brill you sorted nextion for gcb glcd
I only got one to play with and thought there's a default serial speed and no faster.
I think the idea is sort the display with the gui and use the controller as little as possible,
but you could use a pc
@Anobium, you have made great video's to show the Nextion IDE and gcb code relationship, thanks.
@Stan, your info, pics and video's show that it can be done, that's good for my motivation to give it a try.
In the past I decided in my projects to use less displays and more LED's, beeper and even speech modules as a way of user communication feedback. Yeah, I know that silly :)
But now I know that displays cost less, display drivers are made easy with simple (empty) microcontrollers, displays are smaller, with colour, choice OLED instead of LCD, multi lines, fonts choice, touchscreens, Nextion editor with mass components such as button, text, progress bar, slider, instrument panel etc. are all options to choose from for existing and future projects.
The projects that I have could use a display implementation or upgrade with some of the above!
Even if all that's needed are a few virtual buttons.
These two methods of design intent with the Nextion IDE and gcb that Anobium mentioned, I have to play with to know what and how to implement. It's a choice indeed!
I'm just scratching the surface with gcb possibilities here. I can learn a lot from you guy's.
Yes, true "Anobium: Nextion may be over-kill.. or it may be perfect", but also true "Stan: as I only have a low spec nextion I can say it was worth the cost just to try it". For some of my projects that can be sufficient.
Especially when the cost of an 20x4 OLED is €37 in comparison and with it's big pcb it's twice the size!
These enhanced K-serie up to 3.2" (NX3224K024, NX3224K028, NX4024K032) are less enhanced then the 3.5" and above (NX4832K035-NX4832K070).
I bought the 3.5" (NX4832K035) to try the enhanced speed to see what is maximum possible.
I will share my findings to help the GCB-community.
I need a large Nextion touch display for my lathe and there will be sub screens, yes.
I thought of the idea to add small pics tutorials screens with colour drawings as a jpg or video to display instead of drawing and writing the tutorials from code.
This can improve the users speed.
My mate is an engineer in a chocolate bar factory and when got the job found lots of industrial touch screens but everything is rs232... ie old and no info. Just dumped .
You can get an android tablet for £50 but interfacing to a lathe ???
with just gcb and a dumb display, it would be draw coloured boxes with text
then using the gcb touch for display
is the touch x,y within any box
if so highlight it. if touched again then run command.
bit of a simplification but not many gcb users use glcd.
using nextion I would use the gui to place/colour/text boxes...pretty ones
but then have to define their attributes or what they do and it takes effort to learn.
You have not mentioned how these press screen buttons are going to control a "cnc" lathe.
What is wrong with real buttons with labels.....like a microwave oven?
Yes Stan, salvaged components are free but not always what we want or need.
Android for technics real-time, I have not done that and don't know how to interface with it.
The approach you mention could be the solution.
I don't know if the Nextion Editor has only the components placement screen configuration with subscreens or that it has it's own programming envirement too where some Nextion code also can be run.
The idea is to control the spindle speed of the lathe depending on the tool type, cooling, diameter, etc.
The buttons function (label text) will change as I browse through the (sub)screens. Rotary encoder could work but while working with the lathe I want to switch between options fast.
Rotary encoder is like working on the pc with the (shift)TAB-button instead of a mouse or a touch screen that is the fastest selection method.
P.s. Your mate is a lucky guy, instead of looking for touch screens in the factory, I would search for lost chocolate bars :)
They give the test run failures to the staff. company called nakd.
He gives me loads.
Oooh man, now you did it Stan...
The 3 ladies at home saw your box of chocolate and now I have to buy that instead of my displays :)
In the companies where I worked technical run failures also where distributed to the staff that in my case where not compatible with my projects.
I liked Evans nextion video and the bit where he shows touch x,y in a box only.
I think learn/use the nextion gui for its open new screens from menus.
It's what you're paying for. and they are very clear and bright displays.
It's down to price and what's needed. I would see if the gui simulates events that you could use.
Based on Evans video I also found out that in the Nextion Editor these K-serie enhanced displays are not the latest or best models.
When I select "NEW" in the iconbar a setting-window opens where I first have to select the Device-model type "Basic = T-serie, "Enhanced = K-serie" or Intelligent = P-serie".
Then I have to select the Display orientation.
Based on the higher P-serie selection the toolbox will have all components to choose from like video, audio, combo-box etc.
Last edit: Haroen 2020-12-30
This is what I could find in the Intelligent = P-serie:
NX4827P043 (480x272)
NX8048P050 (800x480)
NX8048P070 (800x480) for €79
NX1060P070 (1024x600)
NX1060P101 (1024x600) for €137
They alle have audio and video options in the toolbox and for the larger ones instead of that price (>€79) I better take an old MS-tablet in combination with an (gcb) arduino to interface stuff!
How much faster than the T- & K-series this P-serie will communicate to gcb I don't know?
The smallest NX4827P043 with 4,3" and NX8048P050 with 5,0" could be an option to use but I couldn't find a price tag?
I have a new NX8048P070-011. This is available for re-selling.
1) Did this P-serie Nextion display work on gcb?
2) In the Nextion Editor side menu "toolbox", are all the components to place selectable?
3) Was it faster over serial communication to the gcb chip than the T-serie and K-serie?
4) Is your NX8048P070-011 touch capacitive or resistive?
5) This is the 800x480 type of the 7" version?
:-)
Sorry for all the questions, it's all new to me.
1) The developed library works then on all Nextions T-K-P-series?
2) Let me rephrase that question. If I open the Nextion Editor then I see in the upper left corner a sub-window called "Toobox" with selections for Text, ScrollingText, Number, Xfloat, Button, ProgressBar, Picture, ComboBox, Video, Audio, etc. called components I think.
Are all these components (ComboBox, Video, Audio) selectable to place on the NX8048P070-011R display and do they actually work with gcb?
3) Datasheet reads 921600 bps max for P-serie! And T+K-serie 115200 bps max. So Nextion T+K serial speed to gcb chips are the same! Your P-serie version is very fast!
4) Resistive single touch.
5) Yes.
@Haroen.
That is the intent. The library is extensible and you can add your own functions to add more functionality.
If the object in the Nextion Editor is addressable via the serial then yes.
The BPS is not critical. You are actually sending very little data to the display. Personally, I would use 9.6k BPS to ensure the quality and distance.
OK
OK
Want to buy the one I have here?