This is a helpful start! We will attempt to replicate the time jump by scanning FoxHD on 99w.
GEOSATpro Micro Timer issues.
- Thread starter rgk
- Start date
- Latest activity Latest activity:
- Replies 171
- Views 25K
This is a helpful start! We will attempt to replicate the time jump by scanning FoxHD on 99w.
Poof! Timers disappeared overnight.
I had 4 timers set to record some programs on PBS at 125W and LPBS at 87W overnight. The MHD was left on standby last night. This morning the unit was on when I went to check the recordings. It was on a LPBS channel and the picture and sound was acting like it was a very weak signal. However the quality was 76%. I then turned the unit off and on again with the remote, the picture and sound became stable as it should be at Q 76%. However there were no recordings overnight. The timers had somehow all been switched off, even the timers I had set for future recording. All other settings had been retained. I am using the latest firmware. Has anyone else experienced this?
Thanks, iHenry
I had 4 timers set to record some programs on PBS at 125W and LPBS at 87W overnight. The MHD was left on standby last night. This morning the unit was on when I went to check the recordings. It was on a LPBS channel and the picture and sound was acting like it was a very weak signal. However the quality was 76%. I then turned the unit off and on again with the remote, the picture and sound became stable as it should be at Q 76%. However there were no recordings overnight. The timers had somehow all been switched off, even the timers I had set for future recording. All other settings had been retained. I am using the latest firmware. Has anyone else experienced this?
Thanks, iHenry
Last edited by a moderator:
Please review the previous posts in this thread. The more specifics that you can provide about the time mode selected, channel the system was parked on, number of timers, types of timers, etc would be helpful.
This could be the result of the time mode selection, a power loss, rebooting on a channel with incorrect time data, memory device not being recognized, signal being bad during the timer initiation, etc. Many possibilities for lost timers including a possibility of a firmware issue. The only time issue that we can verify and replicate is the reset of the seconds to the nearest minute when powering between standby and operation mode..
If this happens again, please document as much about the event as possible and post in this thread.
This could be the result of the time mode selection, a power loss, rebooting on a channel with incorrect time data, memory device not being recognized, signal being bad during the timer initiation, etc. Many possibilities for lost timers including a possibility of a firmware issue. The only time issue that we can verify and replicate is the reset of the seconds to the nearest minute when powering between standby and operation mode..
If this happens again, please document as much about the event as possible and post in this thread.
The only occasional "quirk" I've noticed of late with timers, well, actually two of them are the following:
1) If you "manually" record during a scheduled recording (I record MASH daily on ME TV) on a different channel, instead of ignoring the recording timer,
it pops on the screen says its recording, then when it can't, it apparently disables the usually scheduled ongoing timer. Mine did! I think I was on a fixed dish PBS doing a recording on the weekend when it did this. The ME is a 7-day setting (there are no "weekend only" settings, wish there were)...and the competing recording was started manually.
2) If you're listening on the "radio" side and have a video timer, the MicroHD won't make the switch across modes to video, and you simply don't get your
recording. This would be nice to have updated.
Shared with others for comparison, and with thanks! Maybe our collective input will help me correct these!
1) If you "manually" record during a scheduled recording (I record MASH daily on ME TV) on a different channel, instead of ignoring the recording timer,
it pops on the screen says its recording, then when it can't, it apparently disables the usually scheduled ongoing timer. Mine did! I think I was on a fixed dish PBS doing a recording on the weekend when it did this. The ME is a 7-day setting (there are no "weekend only" settings, wish there were)...and the competing recording was started manually.
2) If you're listening on the "radio" side and have a video timer, the MicroHD won't make the switch across modes to video, and you simply don't get your
recording. This would be nice to have updated.
Shared with others for comparison, and with thanks! Maybe our collective input will help me correct these!
I know that with my setup after installing the Digiwave 8x1 DiSeqC switch, that I must leave the unit on and not standby when setup to record. Many times, my recording for Mission Impossible at noon was missed after installing the switch because of a momentary "no signal" when the unit powers on. One day I sat there with the TV on to see what was happening when it was time.
I would have rather that it record a couple of seconds of the blank message screen than nothing at all. I may try a different brand of switch for an experiment to see how the receiver communicates with it.
I would have rather that it record a couple of seconds of the blank message screen than nothing at all. I may try a different brand of switch for an experiment to see how the receiver communicates with it.
Thanks Brian,
I should have taken the time to check out previous posts before posting myself but I was in a rush. The timers were working well for me over the last few days. Yesterday I whittled the channels on a favourite list to PBS (125W) and LPBS (87W). The manual set clock was lagging a half a minute so I did change the clock back to GMT mode because I thought I was safe with this choice of channels. I suspect the problem had something to do with that. I will go back manual clock and reprogram the timers. We'll see how that goes.
Cheers, iHenry
I should have taken the time to check out previous posts before posting myself but I was in a rush. The timers were working well for me over the last few days. Yesterday I whittled the channels on a favourite list to PBS (125W) and LPBS (87W). The manual set clock was lagging a half a minute so I did change the clock back to GMT mode because I thought I was safe with this choice of channels. I suspect the problem had something to do with that. I will go back manual clock and reprogram the timers. We'll see how that goes.
Cheers, iHenry
If you set the time to GMT, it is likely that your receiver tuned to a transponder that provides an incorrect date and your receiver calculated that the timers were no longer valid and deleted them.
As a side note: Maybe we (Satellite Guys and Gals) should create a database of transponders with incorrect TDT data and I could mention the inaccuracies to the uplinkers in our regular communications.
It almost would be easier to list the ones that are right, and if it is not on the list ------ it is wrong!
rv1pop said:
Seriously... Would that help when we communicate with the uplink centers? I am proposing a means for a solution not meant as a joke!
Sorry. I knew what I was thinking.... There probably is a master list . Take it and cross off those that are right... What is left is wrong. This was not a joke.
Since starting this thread I have switched to using only weekly timers. This has reduced the number of timers that disappear dramatically. it also provides more flexibility in having a different schedule for weekends. There are still two anomalies that occur. The timer is for Anik F1r @107.3w 4060V28346 810-802 (CTV2). I believe it has more to do with the fact that the dish has to move than the specific channel. When I come home from work the screen is all light blue. i press a button on the remote (don't know if it's any button or just certain buttons) the starting to record box pops up and the micro begins to record. I stop the recording and check the timers. That timer will be missing. This has happened about five times since it was originally reported. The second issue which seems to occur almost everytime is weekly timers on weekends. No matter what duration they are set to they stop at exactly 30 minutes. The timers are for This Tv and MEtv - 101w on Saturdays and Sundays.
Last edited:
The timers overnight ran perfectly. The MHD was on standby this morning as it should be. However the recordings last night were from different transponders on a single satellite (125W), so no motor action. Tonight I will program a few timers to switch back and forth between 87W and 125W. We'll see how that goes. The clock is still on manual set.
Cheers, iHenry
Cheers, iHenry
ihenry said:
If you run into problems with your c-band motor system moving too slowly and the record event times out before the satellite signal is locked, consider setting a non-recording timer to move the dish in advance of the recording timer.
Lack of signal is no reason to delete a timer. There really isn't anytime when the Micro should be deleting a weekly or daily timer without input from the user. It seems to be a problem with setting the timer up for the next date to be recorded. Maybe the Micro suffers from ADHD.
A single event timer will be deleted if there is no signal, the event recording cannot occur and the event passes. Single event timers are erased after the event is completed or there is an error.
If input were required from a user, future event timers would not execute until the user cleared the error. The ALI chipset is coded this way, and while not elegant... it makes sense not to prevent future events from occurring due to an error n a previous timer.
The suggestion that the microHD needs an error message requiring user input brings to mind the current DirecTV advertisement about the dreaded cable DVR reservation/ full error screens!
Last edited by a moderator:
The results are in early. Before going out this morning I set up 6 single event timers for this morning and afternoon and one which will record daily starting Monday. The timers alternated between OPBS on 125W and LPBS on 87W. When I arrived home this evening the MHD was on and playing the LPBS channel on 87W. I checked the recorded programs and found only two recorded. I then checked the timers and all were turned off except the daily timer. It would seem something occurred after the second timer to cause the remaining single timers to turn off and leave the unit playing the channel of the second timer. Is it the motor? Or is it looking for a signal before the motor gets to the desired satellite and that generating an error? There was at least a 10 or more minutes from the end of one timer to the beginning of the other. I'm puzzled as to what to try next.
Cheers, iHenry
Cheers, iHenry
The
The only thing I can agree upon is that the ALI code is not very elegant when it comes to recording. If my coolsat or Dish receivers fails to record a daily or weekly event for any reason it goes on with its' business and tries again next time. If I try to record anything that contradicts the current timers they both prompt as to which one to record. Neither receiver blows away a timer, they prioritize. while I like the micro it doesn't seem to follow best practices when it comes to the UI. Obviously a one time timer is going to be deleted after a failure. I specifically mentioned daily and weekly timers. This is not rocket science. A good programmer should have fixed this by now.
The only thing I can agree upon is that the ALI code is not very elegant when it comes to recording. If my coolsat or Dish receivers fails to record a daily or weekly event for any reason it goes on with its' business and tries again next time. If I try to record anything that contradicts the current timers they both prompt as to which one to record. Neither receiver blows away a timer, they prioritize. while I like the micro it doesn't seem to follow best practices when it comes to the UI. Obviously a one time timer is going to be deleted after a failure. I specifically mentioned daily and weekly timers. This is not rocket science. A good programmer should have fixed this by now.
Last edited by a moderator:
ihenry said:
How long does your system take to move from 125w to 87w? How long does it take your system to move between 87w and 125w?
Now try the suggestion of setting a non recording event timer on the new satellite prior to the recording event. This will move your dish into position and be ready without timeout risk when the recording command is issued.
I believe that your motor is taking to long to move the dish into position. When the recording start command is sent, no signal is present so the event is cancelled.
We could attempt to program the mIcroHD to record even if no signal is present (may not be possible as the TS information needs to be defined on the file) or increase the time before the motor move command times out. Either way, the routine won't satisfy the particular needs or wants of a user group.
Recording even if no signal is present will upset the feed hobbyist who prefer the recording to stop when the feed terminates and run the risk of a blank recording filling the drive.
Or
Increasing the time out on the motor move command would drive almost all motorized system users loco...
Or
Continue to attempt to start a recording every 30 seconds or 1 minute throughout the duration of the record timer event.
Last edited:
rgk said:
You evidently have never developed using the ALI SDK. Thanks for your kind words of encouragement!
So true, but I have and will continue to develop for manufacturing and food processing. If the vendors SDK has issues and they don't want to fix them, sometimes you have to get under the hood and roll your own SDK.You evidently have never developed using the ALI SDK. Thanks for your kind words of encouragement!
I don't mean to be harsh. I've been dealing with these same types of issues for over twenty years. I once had issues with a SDK that was causing $250,000 loads of composite materials at Boeing to be used to test drill bits to see how many holes you could drill with a single bit. The parts couldn't be used for their intended purpose because the functions in the vendors library were periodically failing. We finally had to write our own code to communicate with the vendors hardware. A year later they finally fixed their code and then admitted there was a problem.
The secret here is to not blame the user when the software doesn't work. Admit there is an issue and find a solution.
Last edited:
