Forum Replies Created
-
Posts
-
Thanks for contacting FDI, but this product is not supported or sold by FDI. Please contact Aladdin Light Lift directly.
Toll Free Support: +1 877-287-4601(8am – 4:30pm central)
Phone: +1 256-429-9700
Fax: +1 256-429-9708
Email: [email protected]’),
(161, ‘Please contact Aladdin Light Lift directly for support.
https://aladdinlightlift.com/contact/ <- Support linkSandeep,
Please see the software tab here on the product page for the SD card files.
https://www.teamfdi.com/product-details/uezgui-1788-70wvt#softwareFor the touch screen issue please confirm the following:
uEZGUI Rev number (printed on backside of unit in silkscreen)uEZ version used
Did you compile the uEZ/Build/Generic/NXP/LPC1788/FreeRTOS/CrossWorks library in debug mode with no changes to the code?
Did you compile the uEZDemos/Build/FDI/uEZGUI/uEZGUI-1788-70WVT/CrossWorks demo project in debug mode with no changes to the code?
Do you see any visible cut or puncture in the touchscreen tail? They are fragile so please be careful.
Is the touchscreen \”tail\” fully seated in the 4-pin connector?
When you boot up the newly compiled software, please hold your finger down on the touchscreen, them attempt to complete the calibration procedure when it appears on the screen.
Bill
Thank you for your interest in our product. I am sorry that you are running into difficulty.
We have not seen any difficulty driving the display using an Intel Atom (this is what is inside your Versalogic (Raven board)). We used Compute Sticks for our tests.
We use industry standard EDID to provide the required timing to the SBC. This allows us to work with every SBC that we have come across and both Windows 7/10 and Linux.
We do not have a Raven Board here. If you were to send us a board we could take a look at what it is doing and possibly get you up and running.
Thank you for your interest in our product. Fortunately, we also see the value in the Tinker Board S and have a few here at FDI. We were able to connect the ELI43-CP to the Tinker Board S and confirm the problem you are having. We then used the Xorg config file to set the correct EDID settings for the ELI43-CP. The display came up, but the image was not shown correctly. Appears to be a timing problem.
We have identified an issue where the Intel Graphics Processing Unit (GPU) cannot run the pixel clock slow enough. As you can imagine a display this small uses a fairly slow pixel clock when compared to normal laptop/computer displays. The Intel GPU can support 200+Mhz but cannot clock below 20MHz. The spec for our display limits the input clock to 12MHz. In testing, we run the pixel clock at 22.0MHz and the display functions as expected. This verifies our assumption that the problem is in the Tinker Board S GPU.
NOTE: You should not run the ELI43-CP with timing that is outside the specification of the display. This would void the warranty with FDI and our display manufacturer.
But, we have good news. We recently tested the performance of the Tinker Board S against the Raspberry Pi 4B. The Raspberry Pi 4B WON in almost every category. And it is cheaper and more available.
Thank you for your interest in our product. Fortunately, we also see the value in the Tinker Board S and have a few here at FDI. We were able to connect the ELI43-CP to the Tinker Board S and confirm the problem you are having. We then used the Xorg config file to set the correct EDID settings for the ELI43-CP. The display came up, but the image was not shown correctly. Appears to be a timing problem.
We have identified an issue where the Intel Graphics Processing Unit (GPU) cannot run the pixel clock slow enough. As you can imagine a display this small uses a fairly slow pixel clock when compared to normal laptop/computer displays. The Intel GPU can support 200+Mhz but cannot clock below 20MHz. The spec for our display limits the input clock to 12MHz. In testing, we run the pixel clock at 22.0MHz and the display functions as expected. This verifies our assumption that the problem is in the Tinker Board S GPU.
NOTE: You should not run the ELI43-CP with timing that is outside the specification of the display. This would void the warranty with FDI and our display manufacturer.
But, we have good news. We recently tested the performance of the Tinker Board S against the Raspberry Pi 4B. The Raspberry Pi 4B WON in almost every category. And it is cheaper and more available.
1. We can get around this doing the following:
a. Using a Windows 7 machine, follow this procedure to change the AR1100 into digitizer mode: ar1100-calibration-and-setup-guide.pdf. (Sorry, this software does not work repeatedly in Windows 10, we are working with Microchip to fix this.)
b. Inside the procedure you will download this software: ARConfigurationUtilityV2.20.zip
c. In Step 3.a.5 you will need to put the AR1100 into AR1100 USB Digitizer mode.
i. Change settings on the right for Digitizer.
ii. Click “Use These Settings”
iii. Some dialogs will pop up confirming it has changed.
2. You could do device level calibration using the AR Configuration Utility Sowftware (better calibration as it moves between OSs).
3. Now, use USBView (software download from Microsoft) to see how the digitizer is reporting within Windows.
a. You will need to find the USB Input Device connected to your IoT device.
4. Once ELI is reporting as a Digitizer (as above), you should be able to calibrate in Windows 10.
a. You may have to run the setup to define the screen to calibrate.
5. Windows has a bug. If you try to run calibration by selecting the display like below and the Calibrate option is grayed out, run the calibration on another display (you do not need to finish), then you should be able to run calibration on the ELI device.
