Author Topic: Protocol flow chart  (Read 1589 times)

Offline grampus

  • IceTV Beta
  • Guru
  • *
  • Posts: 350
    • View Profile
Protocol flow chart
« on: August 03, 2010, 09:35:27 AM »
Is there a publicly available generic or device specific flow chart.
Not after the bits 'n bytes, but just a block diagram type.
BeyonWiz, T3

Offline prl

  • Guru
  • *****
  • Posts: 3157
    • View Profile
Re: Protocol flow chart
« Reply #1 on: August 03, 2010, 10:44:56 AM »
Is there a publicly available generic or device specific flow chart.
Not after the bits 'n bytes, but just a block diagram type.
Ewww... flowcharts are so 1960's... Though I'm sure if I dig deep enough in my junk I can probably dig out a flowchart stencil :)

Anyway, something like this, on Beyonwiz at least:
Code: [Select]
if IceTV_config.enabled then
    config_info = request_config_info(login_credentials);
    if exists config_info.devicename(IceTV_config.device_name) then
        start IceEPG(config_info.devicename(IceTV_config.device_name));
        start IceTimers(config_info.devicename(IceTV_config.device_name));
    fi
fi

thread IceEPG(device_config) {
    while true do
        accepted = request_EPG_update(device_config, next_update_wait);
if accepted then
    send_current_EPG_state();
    receive_EPG_update();
fi
sleep(next_update_wait);
    done
}

thread IceTimers(device_config) {
    while true do
        accepted = request_timer_update(device_config, next_update_wait);
if accepted then
    send_current_timer_state(); // Includes sending timers created on PVR
    receive_timer_update();
fi
sleep(next_update_wait);
    done
}
The server may not honour an update request even if you've waited the specified wait time. If this happens, you'll be given a new wait time.

There are optimisations that allow only changes in state of the EPG and Timers to be transmitted, but not much is known about them except that they exist.
Peter
Beyonwiz T4 in-use
Beyonwiz T2, T3 & T4 for testing

Offline grampus

  • IceTV Beta
  • Guru
  • *
  • Posts: 350
    • View Profile
Re: Protocol flow chart
« Reply #2 on: August 03, 2010, 11:33:49 AM »
Ewww... flowcharts are so 1960's... Though I'm sure if I dig deep enough in my junk I can probably dig out a flowchart stencil :)
Well, I guess I never got much past DTR, DSR, enq, ack. ;D

Quote
The server may not honour an update request even if you've waited the specified wait time. If this happens, you'll be given a new wait time.

There are optimisations that allow only changes in state of the EPG and Timers to be transmitted, but not much is known about them except that they exist.
At the moment I'm trying to figure out who does what to whom and when.
One example.
I have a minor problem, that goes something like this. I scheduled the midday movie. I did this around 8:15 AM,  then turned on my device.
Checked the BW a few minutes later, and the timer was set in the timer list.
Left the BW on, and I've been checking IceTV ever since.  Refreshing the page every time.
3 hours later, I still have a red doughnut which tells me its queued, but not scheduled.
After all that time, I would expect that the BW should have acknowledged receipt (?) and the doughnut becomes solid to show that it was scheduled.

Or is the fact that Ice has sent the update suffice to have the doughnut become solid.
So the question comes to mind.
Who's problem is it.
Ice?  Sent, doesn't require and acknowledgment of receipt but didn't update its own table.
BW? it didn't acknowledge the fact that it received it?
Network?, the ack was sent by the BW as a UDP packet (blast and pray) and it got lost?

Haven't got much to do have I, to be able to do a bit of woolgathering like that?




Offline prl

  • Guru
  • *****
  • Posts: 3157
    • View Profile
Re: Protocol flow chart
« Reply #3 on: August 03, 2010, 11:51:49 AM »
Unfortunately, the details you're asking about aren't known, but the exchange of timer information us usually enough to update the recording status from queued to scheduled on the IceTV Web pages. I occasionally get programs that are scheduled on the Beyonwiz, but never change state from queued to scheduled in the IceTV Web pages. I've posted about the problem a couple of times on this forum, and the frequency that it happens seems a lot less now, but I'm not surprised that it has happened to someone else.

I get the impression that it's a problem confined to Beyonwiz, which would suggest that the problem is in the Beyonwiz, but I don't know for sure.

The IceTV Widget is one solution to this problem. It only shows the solid icon, whether the status is actually queued or scheduled.


Share via facebook Share via twitter

xx
New XML Protocol & Channel Data Inconsistencies

Started by DeltaMikeCharlie on XMLTV (General)

3 Replies
811 Views
Last post February 20, 2018, 06:12:29 AM
by DeltaMikeCharlie
xx
Unable to record mission impossible ghost protocol

Started by simoncasey on Beyonwiz

21 Replies
2968 Views
Last post August 08, 2017, 11:48:18 AM
by prl