UP3216Q, initial testing

what about the 25 and 27 models? is there hdcp 2.2 available? have you tried any game or video? could you tell us a bit about this? thank you!

Too many models. You should look at the Technical specifications here. No gaming on the Optiplex 9020.

Chris,

You can still switch to the CAL1 and CAL2 preset modes without calibrating first. The blackout is the same at factory defaults and after calibration.

During calibration, I noticed that the step "Loading input data tables", where DUCCS loads data into the LUT took about 20 minutes, when it used to take less than 5 minutes on the U3014. Can you find out why it takes so long to read and write to the LUT compared to previous models? This could be why my screen blacks out for so long when switching to CAL1 and CAL2 because it is waiting to load the LUT.

is the up3216q flicker free? how accurate are the buildin colorspaces? thank you!

During calibration, I noticed that the step "Loading input data tables", where DUCCS loads data into the LUT took about 20 minutes, when it used to take less than 5 minutes on the U3014. Can you find out why it takes so long to read and write to the LUT compared to previous models? This could be why my screen blacks out for so long when switching to CAL1 and CAL2 because it is waiting to load the LUT.

Check application log un c:\Users\YOURNAME\AppData\SOMETHINGELSE\Dell
There should be a log file with raw & compressed LUT sent to monitor. Previous models reported 1024x3 x 3x3 matrix x 1024x3 (prelut , matrix, postlut). Check is this new model has different format.
There should be actual bytes sent for each command in connection.log.

Maybe if dell guys expose a "WRITE LUT3D API" people like Graeme Hill (ArgyllCMS creator) would make a proper calibration program for these monitors.
I'm not talking about make whole library public, I'm just talking about exposing an API in a C/C++ header & library like HP did for its HP Z27x:

http://h20564.www2.hp.com/hpsc/swd/public/detail?swItemId=vc_137687_1&swEnvOid=4063

Dell's library & API for DCC/CI and new models like UP2716D seems limited to OSD functions:

downloads.dell.com/.../DellMonitorSDK_1_01r2_FINAL.zip

HP Z27x API has read/write LUT3D functions in addition to OSD functions.

Hi yumichan,

I checked the logs for my new and old monitors, and they seem to be using different formats.

U3014 (using 1.5.3):

"_fnWriteI2C(0x6e) - Green Input Gamma (PreLUT) LUT data
[0] = 0x51
[1] = 0xea
[2] = 0xf1
[3] = 0x34
[4] = 0x11
[5] = 0x64
:emotion-14: = 0x0
[7] = 0x9
:emotion-29: = 0xe3
[9] = 0xf1
[10] = 0x4
[11] = 0xbf
[12] = 0x3c
[13] = 0x9f
[14] = 0x8f
[15] = 0xe7
[16] = 0xe3
[17] = 0xf1
[18] = 0xc8
[19] = 0xc2
[20] = 0x3e
[21] = 0x9f
[22] = 0xcf
[23] = 0xe7
[24] = 0xf3
[25] = 0xf9
[26] = 0x98
[27] = 0xc6
[28] = 0x40
[29] = 0x1f
[30] = 0xd0
[31] = 0xe7
[32] = 0x3
[33] = 0xfa
[34] = 0x78
[35] = 0xca
[36] = 0x40
[37] = 0x20
[38] = 0x10
[39] = 0xe8
[40] = 0x3
[41] = 0x2
[42] = 0x65
[43] = 0xce
[44] = 0x40
[45] = 0x21
[46] = 0x10
[47] = 0x8
[48] = 0x4
[49] = 0x2
[50] = 0x5d
[51] = 0xd2
[52] = 0x40
[53] = 0x21
[54] = 0x10
[55] = 0x28
[56] = 0x4
[57] = 0x2
[58] = 0x61
[59] = 0xd6
[60] = 0x42
[61] = 0x21
[62] = 0x50
[63] = 0x28
[64] = 0x4
[65] = 0xa
[66] = 0x6d
[67] = 0xda
[68] = 0x42
[69] = 0xa1
[70] = 0x50
[71] = 0x28
[72] = 0x4
[73] = 0xa
[74] = 0x85
[75] = 0xde
[76] = 0x42
[77] = 0x21
[78] = 0x51
[79] = 0x28
[80] = 0x14
[81] = 0xa
[82] = 0xa5
[83] = 0xe2
[84] = 0x44
[85] = 0x21
[86] = 0x91
[87] = 0x28
[88] = 0x24
[89] = 0xa
[90] = 0xcd
[91] = 0xe6
[92] = 0x44
[93] = 0x22
[94] = 0x91
[95] = 0x48
[96] = 0x24
[97] = 0xa
[98] = 0x1
[99] = 0xeb
[100] = 0x44
[101] = 0x22
[102] = 0xd1
[103] = 0x48
[104] = 0x24
[105] = 0x12
[106] = 0x3d
[107] = 0xef
[108] = 0x54"

and repeats 12 times.

UP3216Q (using 1.5.10):

"sendGreenPreLUT - WriteI2C(0x37): sent=41.
[0] = 0x51
[1] = 0xa6
[2] = 0xf0
[3] = 0x32
[4] = 0x01
[5] = 0x20
:emotion-14: = 0x06
[7] = 0x60
:emotion-29: = 0x26
[9] = 0x57
[10] = 0x26
[11] = 0x72
[12] = 0x26
[13] = 0x8d
[14] = 0x26
[15] = 0xa8
[16] = 0x26
[17] = 0xc3
[18] = 0x26
[19] = 0xdf
[20] = 0x26
[21] = 0xfa
[22] = 0x27
[23] = 0x15
[24] = 0x27
[25] = 0x31
[26] = 0x27
[27] = 0x4c
[28] = 0x27
[29] = 0x68
[30] = 0x27
[31] = 0x84
[32] = 0x27
[33] = 0x9f
[34] = 0x27
[35] = 0xbb
[36] = 0x27
[37] = 0xd7
[38] = 0x27
[39] = 0xf3
[40] = 0x7f

receiveUncompressedGammaChecksum [WRITE] - WriteI2C(0x37): sent=5.
[0] = 0x51
[1] = 0x82
[2] = 0xf0
[3] = 0x34
[4] = 0x79

receiveUncompressedGammaChecksum [READ] - ReadI2C(0x37): sent=5, read=5.
[0] = 0x6e
[1] = 0x82
[2] = 0x63
[3] = 0x00
[4] = 0xdf
Gamma Chunk : 53 of 64 (size = 16) -------------"

and repeats 64 times.

However, in PrismData.log, there is the pattern of 1024x3 prelut, 3x3 matrix, 1024x3 postlut.

I do not remember that my U2413 have operations for "checksum", I'll check it at home,

It my U2413 does not have this feature, seems that UP3216Q is validating data integrity of the LUT in order to verify if they were errors in USB LUT upload... so it seems OK that it takes some time. Nice feature.

Yes, I have seen this issue on two models now, and there is a great youtube video showing it too, on three screens tested, not just tested as in powered on but tested with a callibrator and there are significant issues with this screen's ability to display neutrals. They are afflicted with green and pink tints, in different proportions and areas for each screen tested (and mine) clearly show there is an issue with them.

en.community.dell.com/.../20892790


My replacement screen (Rev A01) is much worse than the initial screen (Rev A00) too.