Comments on V0.96
|
Yes. The major difference is the Setup button. Previously, the code read byte address 0 in EEPROM. If that byte was not equal to EEPROMINITVALUE ("raw" EEPROM is set to 0xFF), then the setup routine for the display was called. That code is still in place, but once you've run the display setup, EEPROM address 0 is equal to EEPROMINITVALUE and the display calibration is bypassed. Now, you can press the Setup button on the main display and re-run the display calibration routine. In the DisplayCalibration.cpp file is a routine named InitDisplayCalibration() that starts the calibration process. You could insert a call to this function at the bottom of setup() to force a new pass through the display calibration process. Note at the bottom of InitDisplayCalibration() that the display values are written to EEPROM so they can be recalled the next time you run the program. I know I'm going to regret doing this, but I have attached a text file we used in the DisplayCalibration.cpp file early during testing. It has display offsets that we used to test various 5" and 7" displays. As you can see, each display has slightly different values. However, if you can't get your touch screen to work well enough to calibrate it, these values might give you an idea for hard-coding sample values until the display values get "close enough" for the calibration to work. Please note: This should only be necessary for displays that are really out of whack from the factory. As such, it should be viewed as a measure of last resort. Jack, W8TEE
On Monday, April 15, 2019, 8:48:01 AM EDT, Brian Bowling <bowlingb@...> wrote:
Does this also work for the V4 and V3 boards? On Mon, Apr 15, 2019 at 8:32 AM jjpurdum via Groups.Io <jjpurdum=[email protected]> wrote:
¡°si vis pacem, para bellum¡± --
Brian - N8BDB |
jjpurdum