FYI.
You should see the prompt when the start the Editor, but new Nextion Editor version available.
"For Legacy Nextion devices, please consult FAQ BEFORE Upgrade
V1.62.1 Update List
(Items marked with * are for Intelligent Series only)"
Couple additional bits of info:
- Enhance page component background/vis
That was actually a bug I reported on their forums a few months ago. Except for some comments towards âtoo stupid to use the thing the way itâs intendedâ Patrick was quite helpful - offering more support than I expected or asked for. Aaaand then someone wrote my username in the UNUF discord and Iâve been banned 
Anyways, the bug was that if you hide a component with vis it would fill the area with the compile-time color of the underlying object. If you change f.ex. the page background color from white to black, youâd always get a white rectangle at the place of the hidden component - very annoying if your HMI app includes a dark mode like mine.
Another nice change is that they finally updated the bootloader colors from red on white to light gray on black. Even added a nice progress bar. Buuut⌠after the upload is done you still get a red/white update successful screen 
Kind regards,
Max
Anyone else having issues when attempting update?
Iâm running 1.61.2
It keeps nagging, reminding of an update 1.62.1
No problem.
Auto Update.
Nope, fails.
No problem.
Manual update downloads the latest nextion-setup .exe.
Run that.
Fails.
Now youâre [incorrectly] telling me this latest update isnât as recent as what I already have?
Another Nextion disaster, for something that should be quite straightforward.
Whatâs the help line number in Canada we can telephone ? 
What did work:
Uninstall the existing version 1.61.2 via Win Control panel.
Run the same latest 1.62.1 setup.exe file downloaded that failed to install as above.
Edit: Turns out itâs not the fault of v1.62.1. Details below.
Original Post
Bad news for v1.62.1. I just compiled my project with the new version and itâs become unusable. Framerate has severely dropped; around 50% from a first view. Similarly, page loading time pretty much doubled from 1 to 2 seconds.
Maybe even worse, the serial coms are completely hit and miss. Half of the commands fail. Either no response at all from Nextion, or 0x1a (invalid variable), or 0x00 (instruction failed). I canât even update the firmware with the upload function from the editor because it doesnât even connect 9/10 times. And the one other time it just gets stuck at 1% - probably because Nextion doesnât acknowledge. Honestly, at that point I couldnât be bothered investigating it.
I havenât done any precise benchmark tests yet, so no âhard factsâ I could provide, but the difference is obvious enough without.
Can anyone confirm those observations?
Technical details:
Kind regards,
Max
Ouch, that doesnât absolutely not sound good. Will try to reproduce in the next days and write back.
I did program a NX4832T035 (3.5" basic) two days ago with v1.62.1 and nothing unusual observed here.
The HMI worked and communicated with the MCU just fine, with no inkling there was anything different.
Perhaps what you are seeing is HMI variant dependent?
Iâm currently updating another project that uses Enhanced HMIs of various sizes.
Will report if anything unusual is found.
Thanks for the feedback. I forgot to mention but it actually did not start right at the beginning. It worked fine for a couple uploads and then suddenly it didnât anymore. In retrospective I canât tell anymore what I did before the issues started. Mostly just playing around, testing stuff for my application. I do remember that I aborted some of the uploads; which is probably the only âabnormalâ thing.
I also reported the issue to Nextion and so far it looks like they canât reproduce it either.
All of this looks like it was something faulty on my side but I honestly donât know where that would come from⌠I can go back and forth between v1.61.1 and v1.62.1, consistently getting perfect results with the first one and crap results with the latter one - while not changing anything else to the setup.
Unfortunately I donât have a second screen to test.
Edit: Hereâs the link to the specific HMI file I used for testing (and the source code as text): Syntherrupter/Syntherrupter_Nextion at v4.1.3 ¡ MMMZZZZ/Syntherrupter ¡ GitHub
Kind regards,
Max
Issue solved. It was a power issue, not a firmware issue.
My device (microcontroller plus Nextion) is powered by my notebooks USB3 port. I donât know if itâs capable of 1A, 1.5A or more but it is the âchargingâ port for charging phones, etc and certainly fulfills the minimum requirement of 500mA. Iâm using a thick, good quality USB cable. I havenât cut it open but itâs certainly not a thin cheapo one.
Although this setup should be good enough, itâs not. Measuring the 3.3V and 5V rail on the Nextion PCB itself I can see a high ripple caused by the background LED PWM. The lower peak on the 5V rail goes as low as 3.7V, which the 3.3V reg canât compensate anymore, making the 3.3V line sag to 2.6V for a short time.
These results are visible on the attached scope image, C1 (yellow) measures the 3.3V rail, C3 the 5V rail. The white traces are explained below.
When increasing the backlight intensity to 100% everything is okay, and indeed, the application immediately runs faster again. Very weird how you can switch between fast and slow while itâs running. At 100% backlight the 5V line sits at 4.5V which is well in spec (USB hardware - Wikipedia ).
The 100% backlight test proves that my USB port, the cable, the connections, ⌠is well capable of handling the full LED current. However, the transient response is bad - likely caused by cable inductance. This cannot really be solved by a better cable, since inductance isnât much dependent on the wire diameter. With 1m the cable isnât exceptionally long, but rather a pretty common size.
As every PCB designer probably knows, the solution is local decoupling. Therefore I soldered a 220uF 63V low-ESR capacitor to the connector on the Nextion screen itself. Sure enough the voltage rating is way too high but I didnât have anything else at hand.
Result: The excessive dips are gone. Except for noise the 5V rail stays above 4.45V which makes it USB compliant. The 3.3V line is perfectly stable. All issues are gone no matter the Nextion firmware version.
These observations are again visible in the scope screenshot. R1 and R3 show the 3.3 and 5V rail.
Iâm not the first one who added a decoupling capacitor. Apparently it also helps a lot with reducing noise that the Nextion screen injects into the rest of the system - which totally makes sense to me after seeing these scope shots. Possibly much less than 220uF would already be sufficient. This is not a big BOM item but it would certainly make the screen more reliable - which for industrial clients is probably well worth the extra 0.2$ costs.
I also measured the 3.3V rail on my microcontroller board (Tiva TM4C1294XL) and it doesnât experience any sagging. Apparently they do use a proper LDO regultator. Price difference between LDO and standard 3.3V reg shouldnât be significant, making this a low hanging fruit for more robustness.
Finally, I still wonder what v1.62.1 has to do with all this. Why did it suddenly start to become picky about that voltage dip or why wasnât any previous version sensitive to this. I donât know. Also, Iâd have expected crashes and similar things, but not that its execution speed drops by 50%. Did v1.62.1 potentially include some kind of power management? If a brown out is detected, reduce CPU clock? That would be fancy, but rather unlikely I think.
Anyways, I donât think v1.62.1 is the one to blame here. Handling voltage drops like this isnât the job of a firmware IMO.
Kind regards,
Max
Hello Max,
i very much enjoyed your solution, but since I am not a PCB designer I would like some further assistance if possible.
My company also uses the Nextion enhanced 4,3" for the same 2 producs for years now and lately (last 3 months) weâve had some serious inconsistent problems with them.
Mainly cutouts of other pages beeing shown where they are not supposed to, or number glitches like temperature 23°C which for a split second shows 33°C and so on.
Is there any way we can talk so I can better understand your decoupling solution as in what and exactly where needs to be soddered?
E-Mail, whatsap, telegram or whatever, just please help me on this one cause Iâve been busting my head with this 
Hi and welcome @Sebastian,
Sorry to hear that.
Best thing to do is join the UNUF Discord chat we can discuss everything there or switch to private conversation if required/desired. But be warned, unless itâs a really easy fix, some equipment and knowledge on how to use it will be required. I (and all the other members) can only guide you, not do it for you.
Kind regards,
Max
Hello, have you already found a solution?
It canât be that â.tftâ is to be saved all the time, plug in/unplug because direct uploading doesnât work.
I donât think itâs the USB port, because if you can install/flash ESP32/ArduinoMega on the same port+cable, then it has nothing to do with the USB port, they also use the corresponding 3.3V / 5V
This forum is in no way affiliated with NEXTIONÂŽ, ITEAD STUDIOÂŽ, TJCÂŽ, or anyone else really. All product names, logos, and brands are property of their respective owners. All company, product, and service names used in this website are for identification purposes only. Use of these names, logos, and brands does not imply endorsement from the respective rights holder(s).
