Data dump, please...

[mungewell]

Don't have PSVR, but worked on DS4 driver for Linux...

Please post a dump of multiple reports from the device. These are a LOT easier to view in Hex as the data will line up.

I suspect that you'll see that Gryo and Accels are 16bit. Due to HID byte order the low-byte comes first.

Also for the PS-Move and DS4 there is a time stamp associated with the reports. https://github.com/nitsch/moveonpc/wiki/Input-report http://www.psdevwiki.com/ps4/DS4-BT#HID_INPUT_reports

[zigen]

Thank you for telling me that. I don't know much about HID and DS4. it is so helpful.

Today, I found that time stamp is probably located at offset 33 and 34.

here is dump of input report, but this is not reliable. https://gist.github.com/hrl7/5fc8a372c5914846406441fefe72bd38 I will collect more dump and upload tomorrow.

[zigen]

this is dump of communication between PS4 and PSVR. https://drive.google.com/open?id=0B9k4M70SGKlAYWY3RVFEOVRETE0

and viewer is in this page (windows only). http://www.ellisys.com/products/usbex260/download.php

here is USB descriptor. this may be helpful. http://wiki.onakasuita.org/pukiwiki/?PlayStation%20VR%2FUSB

[mungewell]

Glad to help. :-)

For the PS4<->PSVR log (which will take some time to digest), was that a power on and into 'cinematic mode'? This is the trigger/handshake I think most people would be interested in replicating...

If you get the chance, can you do separate logs of:

1. Switching into different 'screen sizes' (cinematic mode)
2. Recentering cinematic mode.

Once the PS4 starts up a full VR game, I guess the log will get real busy with 3D audio data. Thanks, Simon.