ITV1 Failed Recordings

[Peso]

I’ve just seen the same thing on two boxes at my parents. My mums was supposed be recording Gardeners World and Corry. It was half awake but not recording as I could see on web interface. I rang to tell her, she went to boot the box from the remote and I saw both recordings start.
My dads did the same an hour later with the Corry repeat and Scenic Counties. This time when I turned the box fully on from the web interface it started to record. But only Scenic Counties and only 24mb worth.
AR is active as it has been forever for them with little problem.
Will get my Dad to factory reset them as a first step.

 

[Black Hole]

Some general comments:

If the 'fox is in standby prior to recording, for AR it needs to transition to half-awake about 15 minutes before the scheduled start time so that it can monitor the now/next (AKA start flag). Problems can occur if it goes to half-awake and is looking at a mux from a different region than the target recording, the now/next might not match the pattern it is looking for.

If it does not transition to half-awake in time to start looking, it could be that the alarm clock isn't working (located in the front panel assembly). The "alarm clock" is a timer programmed during the shut-down housekeeping. I can well imagine that if the 'fox is failing to enter standby correctly (delinquent half-awake), the timer is not being programmed. My 'foxes are on all the time, so I don't get this risk. However, I have observed occasions when the unit does not switch to the desired service, but starts recording if I switch to the service manually (because it then sees the appropriate program "now" code).

It is possible to mix auto-padding and AR recordings using the CF multimode package, which I use to ensure only reliable services use AR and the rest are padded.

 

[prpr]

for AR it needs to transition to half-awake about 15 minutes before the scheduled start time

In general, the box wakes up 3 minutes before whatever the event is, so a scheduled wakeup for say 08:00 would happen at 07:57. For an AR event notionally at 14:00, it would wakeup at 13:42.

so that it can monitor the now/next (AKA start flag). Problems can occur if it goes to half-awake and is looking at a mux from a different region than the target recording, the now/next might not match the pattern it is looking for.

The really stupid thing is that the EPG info. for your region and all the surrounding ones is actually transmitted and therefore received by the unit. I don't know the reason but surmise it was to cope with out-of-area muxes. But the T2 completely fails to do anything with this data.
e.g. from Mendip's transmissions I receive data for the West region, and also the South West, South (Southampton), South (Oxford), West Midlands and Wales. The same principle applies to my other unit in Waltham-land and will therefore apply everywhere. I did not know this until I wrote my logger.
Here is a sample of BBC ONE (but the same applies to all regionalised services):

10/25 08:59:48 Event  4161:31342 4E:16 started 09:00:00 01:30:00 "Saturday Kitchen Live" "/m/1FE3L" "/b-3RHME"
10/25 08:59:49 Event  4162:31340 4F:16 started 09:00:00 01:30:00 "Saturday Kitchen Live" "/m/1FE3L" "/b-3RHME"
10/25 08:59:50 Event 17537:05399 4F:16 started 09:00:00 01:30:00 "Saturday Kitchen Live" "/m/1FE3L" "/b/3RHME"
10/25 08:59:50 Event  4165:31384 4F:16 started 09:00:00 01:30:00 "Saturday Kitchen Live" "/m/1FE3L" "/b-3RHME"
10/25 08:59:50 Event  4163:31341 4F:16 started 09:00:00 01:30:00 "Saturday Kitchen Live" "/m/1FE3L" "/b-3RHME"
10/25 08:59:50 Event  4171:31353 4F:16 started 09:00:00 01:30:00 "Saturday Kitchen Live" "/m/1FE3L" "/b-3RHME"
10/25 08:59:50 Event  4222:00415 4F:16 started 09:00:00 01:30:00 "Saturday Kitchen Live" "/m/1FE3L" "/b-3RHME"

10/25 09:00:03 Event 17542:05445 4F:12 started 09:00:00 01:30:00 "Saturday Kitchen Live" "/m/1FE3L" "/b/3RHME"
10/25 09:00:05 Event  4165:31384 4F:13 started 09:00:00 01:30:00 "Saturday Kitchen Live" "/m/1FE3L" "/b-3RHME"
10/25 09:00:05 Event  4166:31351 4F:14 started 09:00:00 01:30:00 "Saturday Kitchen Live" "/m/1FE3L" "/b-3RHME"
10/25 09:00:05 Event  4170:31417 4F:14 started 09:00:00 01:30:00 "Saturday Kitchen Live" "/m/1FE3L" "/b-3RHME"
10/25 09:00:05 Event  4173:31401 4F:13 started 09:00:00 01:30:00 "Saturday Kitchen Live" "/m/1FE3L" "/b-3RHME"
10/25 09:00:05 Event  4175:31435 4F:11 started 09:00:00 01:30:00 "Saturday Kitchen Live" "/m/1FE3L" "/b-3RHME"

The first unit is tuned to PSB1, the second (currently) to PSB2 (usually PSB3). Notice the lag on the latter - I guess the "ITV" mux. operator significantly prioritises their own services' data though, and possibly the BBC do the same.
PSB3 is more or less the same as PSB1. I haven't checked the COMs.

If it does not transition to half-awake in time to start looking, it could be that the alarm clock isn't working (located in the front panel assembly). The "alarm clock" is a timer programmed during the shut-down housekeeping. I can well imagine that if the 'fox is failing to enter standby correctly (delinquent half-awake)

I suggested that up-thread.