Click here to go to the forum index Click here for the home page
 
Author Message

<  Bugs  ~  Possible solution to prevent missed recordings

Page 1 of 8
Goto page 1, 2, 3, 4, 5, 6, 7, 8  Next
R2-D2
Posted: Sat Apr 07, 2007 7:22 pm Reply with quote
Frequent contributor Joined: 18 Dec 2006 Posts: 12149
After some research (see the FpLogger thread), DeadBeef has developed a firmware patch that might be a solution to the Toppy's rather elusive and most annoying problem of not waking up from standby to do a recording. (Note: this probably won't help in the case where the Toppy crashes as it shuts down and shows the "Four Dots of Doom".)

The patch is available here: TimerPatch V4. (And an updated version which applies to more firmwares, including TF5700.) You'll need to use Firebird's Firmware Patcher to apply this patch. Put the tfp file in the same directory as the FWPatcher.exe and run it, then browse to the firmware image you want to patch, tick the patch(es) you want to apply and then upload the new patched firmware to the Toppy in the normal way.

Technical summary: at very regular intervals the Toppy sends a stream of timer data to the front panel processor (FP) that is in charge of bringing the Toppy out of standby. DeadBeef postulated that the message buffers might at certain times overflow and cause the FP to have the wrong timer data (or none at all!). There is now very strong evidence to support this view -- incomplete data has been observed being sent to the FP, leaving small "danger" windows where if the Toppy had been turned into standby it would have failed to wake up at the correct time (if at all). The patch eliminates a redundant part of the timer data before it is queued to be sent to the FP, which drastically reduces the overall size of the data that is sent, and therefore reduces the possibility of overflowing the buffer or queue.


Last edited by R2-D2 on Sat Aug 25, 2007 11:11 am; edited 2 times in total
View user's profile Send private message Visit poster's website
tichtich
Posted: Sun Apr 08, 2007 7:56 am Reply with quote
Frequent contributor Joined: 08 May 2005 Posts: 1377 Location: Bristol, UK
I've been leaving my Toppy on 24/7 for the last week, but I'll go back to shutting down and try out this patch. I used to suffer from more failures to wake up than the average Toppy user, so I should make a good guinea pig. Wink

Thanks to you and DeadBeef for all your efforts.

_________________
Richard Wein
Firmware: 5.13.65 (patched). Auto Start TAPs: TapCommander 1.0.2, Power Down 0.6, DescriptionExtender 2.2, mei2archive 3.8I3, Automove 1.8, QuickJump 1.54, Improbox 2.1RC8, Jag's EPG 3.0b3 (TV & radio), Media Manager 1.5, MHEG Control A2g, Extend 1.7. PC apps: DGtoTop 1.1. Profile last updated 13/05/2009
View user's profile Send private message
tichtich
Posted: Sun Apr 08, 2007 8:23 am Reply with quote
Frequent contributor Joined: 08 May 2005 Posts: 1377 Location: Bristol, UK
Ah... when I went to install the patch into firmware version 5.12.88, I got the message "Not intended for this firmware". I suppose that means I'll need to upgrade to the latest firmware if I want to use the patch. But I was putting off upgrading until I was sure there were no problems with the new version.

OK, I'll bite the bullet and upgrade. But I'll go back to the old firmware at the first sign of any problems. Wink

_________________
Richard Wein
Firmware: 5.13.65 (patched). Auto Start TAPs: TapCommander 1.0.2, Power Down 0.6, DescriptionExtender 2.2, mei2archive 3.8I3, Automove 1.8, QuickJump 1.54, Improbox 2.1RC8, Jag's EPG 3.0b3 (TV & radio), Media Manager 1.5, MHEG Control A2g, Extend 1.7. PC apps: DGtoTop 1.1. Profile last updated 13/05/2009
View user's profile Send private message
R2-D2
Posted: Sun Apr 08, 2007 8:44 am Reply with quote
Frequent contributor Joined: 18 Dec 2006 Posts: 12149
tichtich wrote:
OK, I'll bite the bullet and upgrade. But I'll go back to the old firmware at the first sign of any problems. Wink

Good luck! I hoped you would be able to give it a try, since you had a lot of missed recordings/timers.
View user's profile Send private message Visit poster's website
DeadBeef
Posted: Sun Apr 08, 2007 8:56 am Reply with quote
Frequent contributor Joined: 09 Jan 2006 Posts: 264
tichtich wrote:
Ah... when I went to install the patch into firmware version 5.12.88, I got the message "Not intended for this firmware". I suppose that means I'll need to upgrade to the latest firmware if I want to use the patch. But I was putting off upgrading until I was sure there were no problems with the new version.

OK, I'll bite the bullet and upgrade. But I'll go back to the old firmware at the first sign of any problems. Wink
I have not tried patching that version. Obviously the FWPatcher cannot find the specified pattern. I will have to adjust the pattern in the patch.
View user's profile Send private message
tichtich
Posted: Sun Apr 08, 2007 9:24 am Reply with quote
Frequent contributor Joined: 08 May 2005 Posts: 1377 Location: Bristol, UK
OK, I've upgraded my firmware (and a couple of TAPs) as you can see from my sig. I've also set Media Manager to shut down the Toppy after its nightly batch job, as that seemed to be a significant contributor to my failures to wake up. Now we shall see what we shall see.

_________________
Richard Wein
Firmware: 5.13.65 (patched). Auto Start TAPs: TapCommander 1.0.2, Power Down 0.6, DescriptionExtender 2.2, mei2archive 3.8I3, Automove 1.8, QuickJump 1.54, Improbox 2.1RC8, Jag's EPG 3.0b3 (TV & radio), Media Manager 1.5, MHEG Control A2g, Extend 1.7. PC apps: DGtoTop 1.1. Profile last updated 13/05/2009
View user's profile Send private message
Andy K
Posted: Sun Apr 08, 2007 11:36 am Reply with quote
Frequent contributor Joined: 14 Jun 2005 Posts: 3497 Location: Owner of 3 Topfields
I would really appreciate it, if the patch would work with firmware 5.12.25 as well please, please, please, Smile (it's a lovely safe and stable firmware)

_________________
Autostart TAPs: Jags 3, Bookmark 2uk, Quickjump 1.71, Power Manager 1.1, Description Extender 1.5/2.1, MEI2Archive 3.8l6, Tap Launcher 3.5a, Tap Commander, AccurateBMExtend 0.3, RemoteExt 1.5, TunerRecAR.2
Launched during EPG scan: Crid, SeriesLink 0.35
TF5800 Version 5.13.65 PHT2UFXp5Xw3RpPcE2Bf2BqRsRh3Pf1Ec2ErEfHe1 Ra3Cf2Ct
Samsung 400Gb+Fan
View user's profile Send private message
DeadBeef
Posted: Sun Apr 08, 2007 12:33 pm Reply with quote
Frequent contributor Joined: 09 Jan 2006 Posts: 264
I uploaded a new version of the patch which can also be patched into 5.12.25 and 5.12.88.
View user's profile Send private message
Andy K
Posted: Sun Apr 08, 2007 2:52 pm Reply with quote
Frequent contributor Joined: 14 Jun 2005 Posts: 3497 Location: Owner of 3 Topfields
Much appreciated Smile

_________________
Autostart TAPs: Jags 3, Bookmark 2uk, Quickjump 1.71, Power Manager 1.1, Description Extender 1.5/2.1, MEI2Archive 3.8l6, Tap Launcher 3.5a, Tap Commander, AccurateBMExtend 0.3, RemoteExt 1.5, TunerRecAR.2
Launched during EPG scan: Crid, SeriesLink 0.35
TF5800 Version 5.13.65 PHT2UFXp5Xw3RpPcE2Bf2BqRsRh3Pf1Ec2ErEfHe1 Ra3Cf2Ct
Samsung 400Gb+Fan
View user's profile Send private message
tichtich
Posted: Mon Apr 09, 2007 7:51 am Reply with quote
Frequent contributor Joined: 08 May 2005 Posts: 1377 Location: Bristol, UK
Well, that didn't take long! I had a failed wake-up this morning. Here's the log...
Code:
FP hook installed at 21:57:18 (2007-04-08)
Wakeup due to a timer
#############################
21:57:34 Message: 35 8c c0 c0 99 ff 03   //Show LED string (shown only once)
21:57:39 Started sending timer : 05:00 (1, 2007-04-09)
21:57:39 Started sending timer : 23:57 (1, 2007-04-08)
21:57:39 Started sending timer : 21:59 (1, 2007-04-08)
21:58:04 Timer has been deleted: 2007-04-08 21:58 The Passion of the Christ.rec
21:58:19 Stopped sending timer : 21:59
22:00:00 New time: 22:00:00  (1, 2007-04-08)
22:02:00 New time: 22:02:00  (1, 2007-04-08)
22:02:59 New time: 22:02:59  (1, 2007-04-08)
22:04:00 New time: 22:04:00  (1, 2007-04-08)
22:04:59 New time: 22:04:59  (1, 2007-04-08)
22:06:00 New time: 22:06:00  (1, 2007-04-08)
22:06:59 New time: 22:06:59  (1, 2007-04-08)
22:08:00 New time: 22:08:00  (1, 2007-04-08)
22:08:59 New time: 22:08:59  (1, 2007-04-08)
22:10:00 New time: 22:10:00  (1, 2007-04-08)
22:10:59 New time: 22:10:59  (1, 2007-04-08)
22:13:00 New time: 22:13:00  (1, 2007-04-08)
23:25:00 New time: 23:25:00  (1, 2007-04-08)
23:26:01 New time: 23:26:01  (1, 2007-04-08)
23:27:51 Message: 40 03   //Return display control
23:27:51 Message: 99 00 c0 0e 0c 78 31 61 c2 08 03   //Show MP VFD string (shown only once)
23:27:51 Message: 40 03   //Return display control
23:27:51 Message: 40 03   //Return display control
23:27:51 Message: 40 03   //Return display control
23:27:59 New time: 23:27:59  (1, 2007-04-08)
23:30:11 Message: 40 03   //Return display control
23:30:11 Message: 40 03   //Return display control
23:30:11 Message: 40 03   //Return display control
23:33:59 New time: 23:33:59  (1, 2007-04-08)
23:34:06 Message: 40 03   //Return display control
23:34:06 Message: 40 03   //Return display control
23:34:06 Message: 40 03   //Return display control
23:35:00 New time: 23:35:00  (1, 2007-04-08)
23:35:59 New time: 23:35:59  (1, 2007-04-08)
23:37:00 New time: 23:37:00  (1, 2007-04-08)
23:39:00 New time: 23:39:00  (1, 2007-04-08)
23:39:59 New time: 23:39:59  (1, 2007-04-08)
23:41:00 New time: 23:41:00  (1, 2007-04-08)
23:41:59 New time: 23:41:59  (1, 2007-04-08)
23:43:00 New time: 23:43:00  (1, 2007-04-08)
23:45:00 New time: 23:45:00  (1, 2007-04-08)
23:45:59 New time: 23:45:59  (1, 2007-04-08)
23:47:00 New time: 23:47:00  (1, 2007-04-08)
23:47:59 New time: 23:47:59  (1, 2007-04-08)
23:49:00 New time: 23:49:00  (1, 2007-04-08)
23:51:00 New time: 23:51:00  (1, 2007-04-08)
23:51:59 New time: 23:51:59  (1, 2007-04-08)
23:53:00 New time: 23:53:00  (1, 2007-04-08)
23:53:59 New time: 23:53:59  (1, 2007-04-08)
23:55:00 New time: 23:55:00  (1, 2007-04-08)
23:57:00 Started sending timer : 23:59 (1, 2007-04-08)
23:57:15 Stopped sending timer : 23:57
23:58:06 Timer has been deleted: 2007-04-08 23:58 Office Space.rec
23:58:15 Stopped sending timer : 23:59
00:19:59 New time: 0:19:59  (1, 2007-04-09)
00:21:00 New time: 0:21:00  (1, 2007-04-09)
00:21:59 New time: 0:21:59  (1, 2007-04-09)
00:23:00 New time: 0:23:00  (1, 2007-04-09)
00:41:00 New time: 0:41:00  (1, 2007-04-09)
00:43:00 New time: 0:43:00  (1, 2007-04-09)
00:43:59 New time: 0:43:59  (1, 2007-04-09)
00:45:00 New time: 0:45:00  (1, 2007-04-09)
00:45:59 New time: 0:45:59  (1, 2007-04-09)
00:47:00 New time: 0:47:00  (1, 2007-04-09)
00:53:59 New time: 0:53:59  (1, 2007-04-09)
00:55:00 New time: 0:55:00  (1, 2007-04-09)
00:57:00 New time: 0:57:00  (1, 2007-04-09)
00:57:59 New time: 0:57:59  (1, 2007-04-09)
01:01:00 New time: 1:01:00  (1, 2007-04-09)
01:03:00 New time: 1:03:00  (1, 2007-04-09)
01:03:59 New time: 1:03:59  (1, 2007-04-09)
01:05:00 New time: 1:05:00  (1, 2007-04-09)
01:07:00 New time: 1:07:00  (1, 2007-04-09)
01:30:03 Timer has been added  : 2007-04-16 21:58 ER.rec

FP hook installed at 5:00:18 (2007-04-09)
Wakeup due to a timer
#############################
05:00:37 Message: 35 8c f9 c0 c0 ff 03   //Show LED string (shown only once)
05:00:37 Timer has been deleted: 2007-04-09 05:00 --- Daily Clean-up ---.rec
05:00:37 Timer has been added  : 2007-04-10 05:00 --- Daily Clean-up ---.rec

FP hook installed at 8:24:12 (2007-04-09)
#############################
08:24:27 Message: 35 8c f9 c0 c0 ff 03   //Show LED string (shown only once)
08:24:32 Started sending timer : 05:00 (1, 2007-04-10)
08:24:32 Started sending timer : 19:57 (1, 2007-04-09)
08:24:37 Timer has been deleted: 2007-04-09 06:00 TEST.rec  <<<<<<<<<<
08:24:45 Timer has been added  : 2007-04-10 06:00 TEST.rec
08:25:01 New time: 8:25:01  (1, 2007-04-09)

I had a couple of successful wake-ups yesterday. I used the Toppy during the evening, and then "shut down" using the Power Down TAP. There was a recording in progress at the time, so the TAP didn't actually power down until 01:40. Shortly before that, a Jag's EPG search created a new timer.

The Toppy woke up correctly for my 10 minute "Daily Clean-up" watch timer at 05:00. But then something seems to have gone wrong. It never started sending messages for my daily "TEST" record timer at 06:00. Also (and was this a coincidence?) Media Manager apparently failed to run its daily batch job at 05:05. (This batch job purges Media Manager's recycle bin and then shuts down. But the recycle bin has not been purged.) Of course, as the 06:00 timer was never sent, the Toppy failed to wake up at 06:00.

This is the first timer I've seen the Toppy fail to send a timer (or FpLogger fail to log it). So I wonder whether this failure was caused by the new patch (or the new firmware?). Any thoughts?

_________________
Richard Wein
Firmware: 5.13.65 (patched). Auto Start TAPs: TapCommander 1.0.2, Power Down 0.6, DescriptionExtender 2.2, mei2archive 3.8I3, Automove 1.8, QuickJump 1.54, Improbox 2.1RC8, Jag's EPG 3.0b3 (TV & radio), Media Manager 1.5, MHEG Control A2g, Extend 1.7. PC apps: DGtoTop 1.1. Profile last updated 13/05/2009
View user's profile Send private message
R2-D2
Posted: Mon Apr 09, 2007 8:33 am Reply with quote
Frequent contributor Joined: 18 Dec 2006 Posts: 12149
tichtich wrote:
Well, that didn't take long! I had a failed wake-up this morning. Here's the log...

That's a weird one (and I must admit that a number of your failures don't really fit the "large number of timers being sent" pattern of other failures). Are you able to do something like serial logging? That might help spot what is happening when your Toppy shuts down for these dummy timers.

Quote:
The Toppy woke up correctly for my 10 minute "Daily Clean-up" watch timer at 05:00. But then something seems to have gone wrong. It never started sending messages for my daily "TEST" record timer at 06:00.

It should (in my experience) have started sending this very soon after it stopped sending the 05:00 timer (and associated safety timers), but the fact your log shows no timers at all being sent at 05:00 leads me to think your Toppy crashed for some reason at that point, without enabling FpLogger to have an EVT_IDLE in order to log the activity. A serial log would have still been able to provide some information, so if you can try this it would be helpful.

Quote:
Also (and was this a coincidence?) Media Manager apparently failed to run its daily batch job at 05:05.

I don't think it's a coincidence. Something bad happened at 05:00. Are your TAPs fully compatible with the new firmware? Mind you, you've previously had failures linked to the 05:00 wakeup, haven't you?
View user's profile Send private message Visit poster's website
DeadBeef
Posted: Mon Apr 09, 2007 9:25 am Reply with quote
Frequent contributor Joined: 09 Jan 2006 Posts: 264
It looks like the Toppy was turned off within a very few seconds after start (i.e. before it could start sending timers to the FP).
View user's profile Send private message
tichtich
Posted: Mon Apr 09, 2007 3:32 pm Reply with quote
Frequent contributor Joined: 08 May 2005 Posts: 1377 Location: Bristol, UK
It turned out to be a problem with the latest version of the Power Down TAP (which doesn't like watch timers). So not specifically a wake-up problem, though it's useful to note that if anything causes a crash at start-up, then subsequent wake-ups may be missed.

_________________
Richard Wein
Firmware: 5.13.65 (patched). Auto Start TAPs: TapCommander 1.0.2, Power Down 0.6, DescriptionExtender 2.2, mei2archive 3.8I3, Automove 1.8, QuickJump 1.54, Improbox 2.1RC8, Jag's EPG 3.0b3 (TV & radio), Media Manager 1.5, MHEG Control A2g, Extend 1.7. PC apps: DGtoTop 1.1. Profile last updated 13/05/2009
View user's profile Send private message
DeadBeef
Posted: Sun Apr 15, 2007 3:01 pm Reply with quote
Frequent contributor Joined: 09 Jan 2006 Posts: 264
I created another version of the timer patch in cooperation with R2-D2. This version optimizes the timer list sent to the front panel (i.e. only the next earliest timer is sent). This version of the patch does not suppress timer deletion messages like the version 2. This should not be a problem because the patched timer processing cycle sends no more than 3 messages (2x timer deletion + the next earliest timer) no matter how many timers have been entered. In principle, the version 3 of the patch can be combined with version 2.

Download: TimerPatch V3
View user's profile Send private message
tichtich
Posted: Mon Apr 16, 2007 8:14 am Reply with quote
Frequent contributor Joined: 08 May 2005 Posts: 1377 Location: Bristol, UK
Thanks, DeadBeef. I've installed the new patch.

Since R2-D2 reported that the bug was triggered by having a lot of timers stored out of chronological order, I've already modified my DgtoJag script (which I use to export timers from DigiGuide to Toppy) so it exports them in chronological order. That would probably have been sufficient for me to avoid failed wake-ups in future even without any patch. However, for testing purposes I've temporarily changed the script to export timers in reverse chronological order!

_________________
Richard Wein
Firmware: 5.13.65 (patched). Auto Start TAPs: TapCommander 1.0.2, Power Down 0.6, DescriptionExtender 2.2, mei2archive 3.8I3, Automove 1.8, QuickJump 1.54, Improbox 2.1RC8, Jag's EPG 3.0b3 (TV & radio), Media Manager 1.5, MHEG Control A2g, Extend 1.7. PC apps: DGtoTop 1.1. Profile last updated 13/05/2009
View user's profile Send private message

Display posts from previous:  

All times are GMT
Page 1 of 8
Goto page 1, 2, 3, 4, 5, 6, 7, 8  Next

Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum