Read device serial number

[mungewell]

Not sure, but looking through logs this looks like it might be a serial number....

[mungewell]

My unit returns:

ep.write('\x81\x00\xaa\x08\x80\x00\x00\x00\x00\x00\x00\x00')
...
8000aa30
0a00320100000002000053104d503136
4d5030303638333031313638b11f0000
b11f0000240800000000000000000000

[edit to reformat data block]

[gusmanb]

Will check with mine tomorrow. Also, not sure but it's a possibility, if this is the serial number there also can be the firmware version, as mine is in V2.0 and yours in 1.5 we will have both versions to compare.

[gusmanb]

I'm testing this now. This is my result:

8000aa303200000200000002000053104d5031364d5030303637313030373239fd29000062120000000000000000000000000000

And I'm going to "interlace" yours and mine to show some things (upper is mine, lower is yours)

8000aa303200000200000002000053104d5031364d5030303637
8000aa300a00320100000002000053104d5031364d5030303638

333031313638b11f0000b11f0000240800000000000000000000
313030373239fd29000062120000000000000000000000000000

Look at the first block, yours have a "3201" and mine "0002", that seems to be our firmwares, 1.50 yours (32 should be minor and 01 major revision) and 2.0 mine, this seems to match.

Next I can see the serial number, it starts from "3136" to "3638" so my serial must be MP16MP0067100729 and yours MP16MP0068301168.

After these I can see two integers, fd290000, 62120000. Why two integers? well, yours has b11f0000 b11f0000 on these positions so these boundaries match perfectly an int or uint. What they mean? no clue for now :) Values are 10749, 11142 on mine and 8113, 8113 on ours. May be a mask with some settings or a hardware revision (I don't think it would be a HW revision, my device has a lower S/N and these values are higher than yours so doesn't make sense).

I will try to understand some more these bytes as they must have more info, there are some bytes left with data on yours and not in mine, for now I'm going to show this info on the toolbox as to know the FW is necessary to avoid problems with different versions.

[mungewell]

Good observations, just need one or more examples.... step up folks!

BTW I recoment 'meld' for looking for deltas, can even do '3 way comparisons'. http://meldmerge.org/

[gusmanb]

I usually use WinMerge but will try this. Thanks for the recomendation :)

[mungewell]

Mention of new firmware coming for PSVR to fix known issues. https://www.reddit.com/r/PSVR/comments/5cenp5/processing_unit_stays_running_during_rest_mode/

[gusmanb]

Hmmmm, I'm thinking something... @mungewell could you post a sensor report as a new issue? Maybe I'm getting crazy with the sensor fusion because the fields are wrongly mapped, it's just a supposition, but may be the case after FW2.0 the report has changed since 1.50 and the code for report sensor parsing may come from a 1.50 unit.

[gusmanb]

Also, something curious, the people talking about the new firmware exposes something that happened to me, if you put the PS4 on sleep the black box didn't powered off, but, it works correctly now, when I put the PS4 to sleep the box shuts down. Maybe something we sent to the box has changed it's behavior?

[mungewell]

If you have been changing the cabling, you might have a HDMI cable without CEC capability. I think you previously said 'tvpower' can shut down the PU via CEC.

[mungewell]

Mon Nov 14 20:52:04 2016, re-read to see if it changes over time. It doesn't....

8000aa30
0a00320100000002000053104d503136
4d5030303638333031313638b11f0000
b11f0000240800000000000000000000`