Possible defective BeadaPanel 5P (or bad firmware)

[esky-sh]

A new drop of v715 firmware uploaded. You can have a regression test for the picture stream latency issue.

https://www.nxelec.com/service/download ... 131.tar.gz
MD5: E8EF5B45D9644DC4AA6D33D52C91A724

[bobg2222]

The firmware I got is beadapanel-i6-v715-202403112.tar.gz (note 3112 vs 3121 in your post).

Also, I tried it on AIDA64 version 7.20.6800 which just updated a day or two before I tested. Which version of AIDA were you testing against?

I will try the latest firmware--but it's a busy day for me, so it will be late in the day or tomorrow.

[esky-sh]

We use build date to name the tarball for each drop, and 3131 is the latest one. Both 3112 and 3121 had a timing issue which get solved in 3131, so you can go directly to test with it.

For AIDA64, we use AIDA64 EXTREME 7.00.6700. But I do not think it will be an issue for any later version. I will install a newer version in our lab and test with it. I will post result in this thread if anything goes to wrong.

[bobg2222]

I haven't had a chance to update the firmware yet. But late this afternoon, AIDA64 popped up an "Update is available" message so I hit OK and it updated to version 7.20.6802. The release notes include: "fixed: Preferences / crash at open." (I always get a 1-year license, so I get these maintenance release update notices periodically. But I've NEVER seen two this close together--2 or 3 days apart--before.)

So, a little later, I tried adding the BeadaPanel 5P (but with the ...3112.tar firmware still). And, indeed, the Preferences screen now behaves itself! I noticed this time that after the initial screen is displayed by AIDA64, there is an update after about 10 seconds--and then just one more update after about 30 seconds. And then if you bring up the Preferences screen again and REMOVE the BeadaPanel, there's one more update! This also happens if you exit from AIDA64 and restart it.

So, you can safely ignore the part of my previous post regarding the AIDA64 Preferences screen. But be sure to update your AIDA64 to version 7.20.6802.

Sorry I didn't get a chance today to try the new firmware; presumably it will work better with AIDA64 (and my app?). I'll try it for sure tomorrow.

[bobg2222]

I downloaded https://www.nxelec.com/service/download ... 131.tar.gz and unzipped the tarball. I used the BeadaPanel service tool just like before, pointing it at the tarball, but got a "download failed" after the progress bar had got all the way across. So, I downloaded again--and the same thing happened. Then I power cycled the 5P and tried once more. Same problem.

NOTE: I tried downloading https://www.nxelec.com/service/download ... 121.tar.gz to see if I could install that, but the same thing happened: "download failed."

What's going on?

[esky-sh]

PS, you do not need to unzip the tarball at all, just point the beadatools to the tarball --"beadapanel-i6-v715-202403131.tar.gz" itself and then click 'update'.

[bobg2222]

I pointed the service tool at beadapanel-i6-v715-202403131.tar.gz and it updated fine. And I think you have a winner!

1. I didn't let it run for very long, but with the 5P and my AX206 display both running on AIDA64, both displays update simultaneously and the 5P never stops updating.

2. With my app both the Start tag -- image -- End tag and continuous PNG work flawlessly with the seconds display updating exactly on time. And, significantly, with continuous PNG, if I only send just one image, it displays immediately (without an End tag).

3. I've seen no freezes with my app regardless of which protocol I use.

[esky-sh]

That is result what we were expecting. Thanks for your diligent working and dramatic contribution!

[bobg2222]

In return, perhaps you could answer a couple of questions for me.

I'm kind of short of room for the weather data my app displays on the 5P--so I've been looking at the black BeadaPanel 6P as a possibly better fit.

1. Is the 6P display itself (excluding bezel) as wide in inches/mm in the 480-pixel dimension as the 5P?

2. With 60% more pixels to update, is the 6P as fast--or nearly as fast--as the 5P? I've been able to measure about 1 millisecond for the actual data send with the PanelLink protocol on the 5P, but I have no way to measure the update time--or refresh rate--of the display itself. Note: the app sends a full 800x480 PNG to the 5P on every update and would be sending a 1280x480 PNG on every update to the 6P.

Thanks!

[esky-sh]

1. The dimensions are different.
For 5" LCD screen, it is 108mmx64.8mm. And for 6.8" LCD, it is 160.5mmx60.2mm

dx.jpg (109.9 KiB) Viewed 2291 times

2. For the process time of panelLink protocol.
The timing may vary depending on which video/picture format is chosen. The another factor may be taken into account is hardware platform which can support kinds of hardware accelerating. So best way to get this timing is a test program on host machine. panelLink will be blocked on USB endpoint to receive new data when it is under processing of a previous image. You can write a test program to send continuous picture/stream to BeadaPanel on USB endpoint and then get a calculation of FPS inside your program.