Facility Control

 View Only

  • 1.  Responding to OGP_GET_DESCRIPTOR with PARM_NOTFOUND causes java.io.exception

    Posted 05-09-2016 20:46

    The Dashboard document mostly documents the format of a good response. However I do not know what Dashboard is expecting from the error response. Eg. I am responding with 0x11 PARAM_NOTFOUND to a OGP_GET_DESCRIPTor request and with no other data included in the response. I am working with Dashboard 7.0

    Could anyone tell me what does the response look like in case of error? Thanks

    Last Sent (15:38:29:582): S:0x00 D:0x11 T:0x47 C[3]: 00 29 06
    Last Received (15:38:29:682): S:0x11 D:0x00 T:0xc7 C[3]: 11 29 06
    java.io.IOException: Response code: 17
    at com.rossvideo.gear.ogp.ParamDescResponse.(Pa ramDescResponse.java:50)
    at com.rossvideo.gear.device.DeviceLink.requestAndBui ldParam(DeviceLink.java:454)
    at com.rossvideo.gear.device.DeviceLink.requestParamT able(DeviceLink.java:721)
    at com.rossvideo.gear.device.OgpDevice.initDevice(Ogp Device.java:889)
    at com.rossvideo.gear.device.monitor.DeviceMonitorPoo l$1.run(DeviceMonitorPool.java:84)
    at com.rossvideo.common.connection.util.RunnableInvoc ation.dispatch(RunnableInvocation.java:65)
    at com.rossvideo.common.connection.util.QueueThread$1 .run(QueueThread.java:142)
    at java.lang.Thread.run(Unknown Source)


  • 2.  RE: Responding to OGP_GET_DESCRIPTOR with PARM_NOTFOUND causes java.io.exception

    Posted 05-09-2016 20:51
    Hi Kto.
    The code in DashBoard is not checking the return code for that message during the initialization page (yes, it probably should, but it doesn't).
    During the initialization phase, it expects you to have all of the parameters you declare in your OID list (since it asks for this list moments before).

    Is there a reason you're declaring/returning and OID you don't actually have?


    #DashBoard


  • 3.  RE: Responding to OGP_GET_DESCRIPTOR with PARM_NOTFOUND causes java.io.exception

    Posted 05-09-2016 21:23
    I am using my declared OIDs just to make sure this is what Dashboard is complaining about. I have noted that whenever the Dashboard is requesting the reserved OIDs such as 0xFF01 and 0xFF09, Dashboard will throw an exception because I do not have such parameter oids defined. The request for such reserved oids are not consistent and therefore I am using my own declared parameter to verify why it is throwing the parameter not found response code

    #DashBoard


  • 4.  RE: Responding to OGP_GET_DESCRIPTOR with PARM_NOTFOUND causes java.io.exception

    Posted 05-10-2016 12:56
    0xFF09 should never be requested by DashBoard unless you declare it.
    Same goes with 0xFF01 unless your device fails to initialize multiple times for some other reason. In that case, it will attempt to request 0x105 and 0xFF01 so that it can at least show the device's name on its error page.
    #DashBoard