FOVE SUPPORT CENTER

Fove setup v 12 - No HMD connected and Cant upgrade firmware

Comments

6 comments

  • Avatar
    Paul Gomes

    Ok, so now i cant even use the 11_3 setup. I cant calibrate the headset anymore. See the log output below. Has anyone else had this? I really need to fix this as i am using the Fove for my thesis and its due in August.

     

    New log client 0.11.3 C:/Program Files\FOVE\bin\FoveServiceHost.exe
    Service started. Initialising FoveVR
    Loaded config file at C:\ProgramData\FOVE\FoveVR.config
    COMPANION_IPC_PORT: 8317
    COMPOSITOR_CLIENT_PORT: 8307
    CURRENT_USER_PROFILE: 604713
    EYE_TRACKING_EYES: 3
    FoveVR ctor
    Loaded module PositionTracking
    Loaded module EyeTracking
    Connected to headset with fw50
    Launched FoveCompositorApplication.exe
    Launched FoveCompanion.exe
    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General
    New log client 0.11.3 C:/Program Files\FOVE\bin\FoveCompanion.exe
    Companion starting
    Loaded config file at C:\ProgramData\FOVE\FoveVR.config
    COMPANION_IPC_PORT: 8317
    COMPOSITOR_CLIENT_PORT: 8307
    CURRENT_USER_PROFILE: 604713
    EYE_TRACKING_EYES: 3
    Creating a compositor client (00000216A89AC9F0) of type 196608
    [RNDR] Acquiring rendering backend...
    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server
    New log client 0.11.3 C:/Program Files\FOVE\bin\FoveCompositorApplication.exe
    Loaded config file at C:\ProgramData\FOVE\FoveVR.config
    COMPANION_IPC_PORT: 8317
    COMPOSITOR_CLIENT_PORT: 8307
    CURRENT_USER_PROFILE: 604713
    EYE_TRACKING_EYES: 3
    [RNDR] Acquiring rendering backend...
    [RNDR] Nvidia not found
    Creating FVRHeadset object (00000216AA8BC110)
    ClientCap final: EFVR_ClientCapabilities(2, Orientation)
    Trying to connect to service as 992c7284-bf08-4e4b-a035-ce731db7e117
    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General
    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server
    [RNDR] AMD API found
    Perm: N:FOVE HMD M:FOV P:0x1 <-- [[ This one ]]
    [RNDR] Backend display was found
    Creating FVRHeadset object (000001F41308D870)
    ClientCap final: EFVR_ClientCapabilities(2, Orientation)
    Compositor found HMD display
    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server
    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General
    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server
    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General
    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server
    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General
    RemoteRequester(tcp://127.0.0.1:8307) error: EFVR_RemoteRequester_Result::Timeout: No response from server
    InitiateConnection: Unable to send heartbeat
    RemoteRequester(tcp://127.0.0.1:8307) error: EFVR_RemoteRequester_Result::Timeout: No response from server
    Destroying compositor client (00000216A89AC9F0) of type 196608
    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General
    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server
    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General
    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server
    Trying to connect to service as b5ac6e33-11e0-46b6-9b53-8c9d1b6dd2b6
    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General
    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server
    Constants struct size: 80
    Constants struct size: 80
    Constants struct size: 80
    Recommended zoom factor: 1.230600
    Constants struct size: 80
    Recommended zoom factor: 1.230600
    Constants struct size: 80
    Recommended zoom factor: 1.230600
    Constants struct size: 80
    Recommended zoom factor: 1.230600
    Constants struct size: 80
    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server
    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General
    REPORT: New client accepted b5ac6e33-11e0-46b6-9b53-8c9d1b6dd2b6
    Connection to service succeeded!
    Destroying FVRHeadset object (00000216AA8BC110)
    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General
    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server
    RemoteRequester(tcp://127.0.0.1:8317) error: EFVR_RemoteRequester_Result::Timeout: No response from server
    Unable to determine IsEyeTrackingCalibrating: EFVR_ErrorCode::Server_General
    Critical error in companion: Unable to send heartbeat
    Marking client stale: b5ac6e33-11e0-46b6-9b53-8c9d1b6dd2b6
    REPORT: dropping stale client: b5ac6e33-11e0-46b6-9b53-8c9d1b6dd2b6
    Loaded calibration data for profile: 604713

  • Avatar
    Paul Gomes

    Forgot to add the error i get when trying to upgrade my firmware

     

    Found FOVE HMD with firmware 50
    Entering DFU mode
    Waiting for device reboot
    Waiting for device reboot
    Waiting for device reboot
    Waiting for device reboot
    Waiting for device reboot
    Timeout waiting for reboot, will attempt to progress anyway
    Uploading new firmware
    0 Device(s) found. Plug your DFU Device !

    Target 00: Error Code: Unknown error 0x12340005.
    Target: 00
    Error Code: Unknown error 0x12340005.
    TransferSize: 0
    DFU State: STATE_IDLE
    DFU Status: STATUS_OK
    Request: (unknown 0x00000000).
    CurrentNBlock: 0x0000
    CurrentLength: 0x0000
    Percent: 0

  • Avatar
    Jeff

    Hi Paul,

    Sorry that you're running into trouble!

    The AMD RX480 and Firmware 50 will work 0.12.0 (ignore the warning/update message for now). I'm not seeing any particular root issue in the log. Would you mind if we hop on skype and debug this in real time w/ a screen share? I want to make sure you can get back to your thesis as soon as possible.

  • Avatar
    Paul Gomes

    Hi Jeff
    Many thanks for your response. I seem to have fixed this last night. I plugged the usb 3 cable into a USB 2 port. Now it is working as usual. Will this interfere with performance of the Fove?

  • Avatar
    Jeff

    Hi Paul,

    Glad to hear you got it working. In theory, the combined video streams require a more than the bandwidth of USB2, but some ports provide enough bandwidth anyway.

    I am curious why your USB3 port did not work - were you using any sort of usb hub or extension cable? What motherboard are you using?

    As long as you're getting the data coming through, it's should be fine to proceed with your USB2 port.

  • Avatar
    Paul Gomes

    I am plugging into the motherboard directly via a USB 3 port. The motherboard is a MSI Gaming 970. It's funny because it worked before I did the update. Happy to do a Skype call to show the behave using the USB 3 port.

Please sign in to leave a comment.