Changes between Version 1 and Version 2 of Debugging-UI4


Ignore:
Timestamp:
2011-04-18 03:21:18 (14 years ago)
Author:
guessed
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Debugging-UI4

    v1 v2  
    1 == General Health == 
    2 The SQBlaster Plugin periodically wakes up and emits the following output in the `LuaUPnP.log` file.  This is used to test that the Puck is contactable, and show the corresponding ''Up'' or ''Down'' status on the Dashboard UI 
     1== Debugging == 
     2[[PageOutline]] 
     3 
     4This page contains shows various forms of log output that occur during execution of the IR components in MiOS, specifically those using the SQBlaster Plugin. 
     5 
     6The examples shown include both successful requests and executions, along with un-successful executions for the common cases.  They are intended as a guide to debugging a particular configuration, since there are many things that may prevent an environment from working correctly. 
     7 
     8In most cases, the samples provided will require you to have access to the `LuaUPnP.log` file.  This can be done by logging into your Vera using `ssh`.  Alternatively, on new MiOS Firmware versions, you can view the log files ''online'' using the URL: 
     9 
     10    http://192.168.x.xxx/cgi-bin/cmh/log.sh?Device=LuaUPnP 
     11 
     12 
     13Note: The log output below may be trimmed in order to make it more readable. 
     14 
     15 
     16=== General Health === 
     17The SQBlaster Plugin periodically wakes up and emits the following output in the `LuaUPnP.log` file.  This is used to test that the Puck is contactable, and show the corresponding ''Up'' or ''Down'' status on the Dashboard UI, along with the details show in the Dashboard Dialog. 
    318 
    419{{{ 
    … …  
    1025}}} 
    1126 
    12 == Request to Send an IR Code from the IR Device == 
     27=== Request to Send an IR Code from the IR Device === 
     28The following example shows a ''DiscretePower1::On'' action being requested against MiOS Device ''202''.  This request came from a SQRemote AV Control request. 
     29 
     30Internally, at the end of this request, MiOS will determine the correct IR ''!ProntoCode'' to send, and push it through to the associated ''IRTransmitter'' (see below) 
    1331{{{ 
    143212 04/17/11 ... luvd_get_info_data_request starting /data_request?id=lu_action&DeviceNum=202 
    … …  
    2442}}} 
    2543 
    26 == Request to Send an IR Code from the IR Transmitter == 
     44=== Request to Send an IR Code from the IR Transmitter === 
     45The following example shows an IR ''!ProntoCode'' being passed through from a MiOS ''IRDevice'', to the attached MiOS ''IRTransmitter'' device. 
    2746{{{ 
    284708 04/17/11 ... JobHandler_LuaUPnP::HandleActionRequest device: 90 
    … …  
    3756}}} 
    3857 
    39 == IR Transmitter succeeded in sending IR Code == 
     58=== IR Transmitter succeeded in sending IR Code === 
    4059{{{ 
    416050 04/17/11 ... luup_log:90: Web request returned status=200 response= 
    … …  
    4362}}} 
    4463 
    45 == IR Transmitter failed in sending IR Code, SQBlaster not contactable == 
     64=== IR Transmitter failing to send an IR Code, SQBlaster not contactable === 
    4665{{{ 
    476601 04/17/11 ... luup_log:90: Web request returned no response ProntoCode=P44c0 301c 17b6 7ca4 6e8a 7b96