Thanks for the answers. I was just curious about the speed given commands are going via a serial interface which is slower than SPI.
Do you think it is stable enough to develop upon? I dismissed it back in October 15 as too new and have gone down a route with LCD display and plug-in keyboard when input required (initial WIFI setup onsite).
@peekay123 - more processing power on the display would allow/support fancier segue between screens - I just dim the LED and redraw the screen then re lite the LED. Cost is the real issue - I am using 1.8" and 2.2" TFT SPI displays ST7735 and ILI9341 which I can source for US$4-5 each, really looking at the Nextion for touchscreen with low GPIO use and at a reasonable price. The SPI based small touch displays all seem to be expensive - $27 for a touchscreen display to SPI controller plus the display.
If you want to draw rather than use the HMI components on the devices you'd definetly need to go with a high baudrate (115200 is supported).
If you want some feel for the speed I could shoot you a video of some drawing action.
Another option for some speed might be the onboard scripting which cuts away the transfer time but only works for simple drawing tasks (loops have to be emulated with timers or unrolled, only simple if conditions, ...)
About stability, it depends on your expectations, but I never had any issues for what I used them.
Hello friends,
if you want to try my photon-less MP3 player for 2.4" Nextion display, you can download this zip and give it a try.
Since there is no MCU involved, you might see some occasional timing issues and the play button doesnāt pop out once a file is played, but this might be a building block.
To play a specific song from the MP3 folder tap the SongNr input box (second top left) and type in the number and hit play.
If you want to try a folder loop (as discussed in the other thread) tap the FolderNr input box (first top left) and hit the loop button.
On the far right you have a volume control.
Update: With the new Enhanced Nextion displays you can use the BUSY pin of the DFplayer module to provide āfeedbackā about the playing state to the display.
The .HMI file is the āsourceā file for Nextion Editor.
If you open it with NE you can see how Iāve done the communication by clicking one any component and look at the āTouch release eventā. And this way you can also alter the appearance of the controls by replacing the two .PNG files in the editor.
The .TFT file is the ācompiledā output of NE which youād only put on an SD card (root directory), pop that into the displays SD slot, power the display up and wait till the display reports āUpdate successed!ā (yup, thatās what it says ).
Then you take the SD out again and repower the display.
The wiring is easy.
The pins on the display are well marked (+5V red, TX blue, RX yellow, GND black).
Just connect TX/RX to RX/TX on the MP3 module, +5V to the Vcc pin and a 5V supply, GND goes to one of the GND pins of the module and the supply again and thatās it.
First card (4Gb) contains a folder "Garmin", which I left in, because I need it later. Then I got this message.
Second (32Gb, overkill?) was still new, empty. I copied only your "MP3.tft" file onto it. Same result...
(PS: I do this on OS-X, which may create 'hidden files' in a volume/folder...)
YES! All works fantastically! Good job @ScruffR !!!
The problem was indeed the hidden files on the cardā¦
I removed them in VM Ware and tried again: āUpdate successed!ā
Update: Hereās a photo of the music machine:
The Photon is just there for good company and to enjoy good musicā¦
Itās still a bit fragile in places (e.g. sometimes a play command is not immediately accepted), maybe removing the unused connection MP3 -> display and/or playing with delays in the display macros could help with possible timing issues.
But this is mainly a proof of concept anyway
Having the Photon in there with only one () serial port available will be the next challenge.
It works without the moduleās blue wire (Tx) indeed, but I donāt see any change in behaviourā¦
As a proof of concept itās of course a success!
If the display could be permanently connected to the Photon, we could also use it for other touchscreen functions.
That would be great!
For my projects it would be sufficient if I can use the touchscreen with the Photon for common control tasks, and then perhaps let it switch the display to the MP3 page to loop one of the selected folders in the background. One extra button on the screen could give control back to the Photonā¦
Sounds easy, isnāt it?
But I have no idea how to do thisā¦
What are the most problematic points with the current state of the project for you?
That very much depends on the intended interaction between Photon and display for your common control tasks
For a full fledged GUI you'd need bi-directional communication between the, but you only have one interface (well, a second you could free up with an soldering iron ;-))