[OS-mio] 6.6.010 Power Option Menu Missing Redux

[ArloGuthrie]

Hopefully we can continue the previous closed discussion. Very dismayed it was considered a waste of time.

I will not waste any time with the request. Everyone has already voiced their opinions.

Firstly. Understand this. When the option is not available (ViX) or not selected (OpenATV).
Randomly and unpredictably when power would go out. I would come home and the dish was re-positioned from where it was parked when I left home.
And at 12' in diameter. It is pretty hard to not notice it.

The receiver would be on the same bouquet (Named per the satellite that the channels reside. ex: 127W Galaxy 13).
When the TV was turned on. My receiver showed the correct satellite it was aimed at when I left home. But, the dish had moved.

The scenario would repeat itself when the power would go out and the receiver was on. Which it usually is.
Unpredictable. As who knows when the power will flicker. Correct?

I know this for a fact. I do not fabricate things up. And the situation was an annoyance.
It was when I discovered the options in OpenATV to choose what should occur after a power failure.
After selection of putting the receiver in deep standby. The receiver would be off when I came home.
And after making the selection, after a supposed power failure. The dish would NEVER MOVE ON ITS OWN.

Upon moving over to OpenVix. I noticed that the situation started to repeat itself. Power failures only occur here during lightning season and when it shows heavily.
I live in a rural setting.

I have log files here. I performed a comparison in Notepad++. I see some things going on. But not versed is log diagnostics to check what is happening.
And. With unplugging the PSU or operating the power strip switch a few times fast.
The receiver boots and the dish did not move. Both receiver and dish mover are on the same Tripp Lite surge suppressor power strip.

It is real. Not fabricated. Not repeatable. But 100% has been prevented in OpenATV from ver. 6.2 to present by the Customization for power failure setting.
And manifested since using OpenViX.

View attachment OsMio4K_Unplug_PSU_Setting_For_Standby_After_Power_Failure.log
View attachment OsMio4K_Boot_From_PSU_Unplug_To_Deep_Standby.log
View attachment OsMio4k_Boot_From_Deep_Standby.log
View attachment OsMio_Normal_Boot_Setting_For_Standby_Ater_Power_Failure.log

 

[Joe_90]

I have looked at all for logs and I can't see the difference in the handling of your positioner box whether it is a boot after a controlled shutdown or a power failure. ATV pops a message on-screen to ask if you want to put the box in standby or deep standby after a power fail but it always sends a command to the positioner to go to a particular stored position (in each case position02).

11:53:12.4355 [eDVBResourceManager] allocate channel.. 0065:0065
11:53:12.4356 [eDVBSatelliteEquipmentControl] direct_connected 1
11:53:12.4357 [eDVBSatelliteEquipmentControl] canTune 1
11:53:12.4357 [eDVBSatelliteEquipmentControl] lnb 0 found
11:53:12.4357 [eDVBSatelliteEquipmentControl] 1 option(s) at position 2329
11:53:12.4357 [eDVBSatelliteEquipmentControl] sat 2329 found
11:53:12.4358 ret1 10000
11:53:12.4358 [eDVBSatelliteEquipmentControl] ret5 10000
11:53:12.4358 [eDVBSatelliteEquipmentControl] ret 10000, score old 0
11:53:12.4358 [eDVBSatelliteEquipmentControl] score new 10000
11:53:12.4358 [eDVBSatelliteEquipmentControl] final score 10003
11:53:12.4358 [eDVBFrontend] isCompatibleWith NON MULTISTREAM CHANNEL!!!!
11:53:12.4360 [eDVBFrontend] m_need_delivery_system_workaround = 0
11:53:12.4360 [eDVBFrontend] opening frontend 0
11:53:12.6528 [eDVBFrontend0] setVoltage FE_ENABLE_HIGH_LNB_VOLTAGE 0 FE_SET_VOLTAGE 2
11:53:12.6540 [eDVBFrontend0] tune
11:53:12.6541 [eDVBSatelliteEquipmentControl] direct_connected 1
11:53:12.6541 [eDVBSatelliteEquipmentControl] canTune 1
11:53:12.6541 [eDVBSatelliteEquipmentControl] lnb 0 found
11:53:12.6542 [eDVBSatelliteEquipmentControl] 1 option(s) at position 2329
11:53:12.6542 [eDVBSatelliteEquipmentControl] sat 2329 found
11:53:12.6542 ret1 10000
11:53:12.6542 [eDVBSatelliteEquipmentControl] ret5 10000
11:53:12.6542 [eDVBSatelliteEquipmentControl] ret 10000, score old 0
11:53:12.6543 [eDVBSatelliteEquipmentControl] score new 10000
11:53:12.6543 [eDVBSatelliteEquipmentControl] final score 10003
11:53:12.6543 has_external_rotor /home/root/rotor_0 no
11:53:12.6544 [eDVBSatelliteEquipmentControl] RotorCmd 02, lastRotorCmd ffffffff
11:53:12.6544 [eDVBSatelliteEquipmentControl] set rotor timeout to 360 seconds

This is similar to what OpenVix does, except in my case it sends an angular position goto to my motor as per my log example posted in the original thread. Maybe one of the devs will comment in more detail as they will have deeper knowledge of the DiSecQ command set.

It's unfortunate that you can't reproduce the error consistently but I'd suggest you leave the logging in place and if it happens again there may be more info to go on. I think, as part of the move to a newer version of the OpenAlliance code (OE-A), there may be more startup options available in the Power menus in any case. Whether this includes power fail options I do not know. In the PowerTimers menu in OpenVix there is an option to boot up into standby which I use in order to perform unattended EPG and bouquet refreshes of my test machines, but that wouldn't cater for your situation where you are subject to uncontrolled power cuts.

 

[Joe_90]

... I think, as part of the move to a newer version of the OpenAlliance code (OE-A), there may be more startup options available in the Power menus in any case. Whether this includes power fail options I do not know... .

To confirm - there will be more power-up options available in the OpenVix menu. I've just seen some changes posted which will be tested in upcoming development versions and will subsequently be included in the Release versions. Similar to those in OpenATV. But, as I posted in the log extracts, I wouldn't expect them to change the way the positioner code is used after a power failure, so I would be surprised if it fixes your fundamental issue. This is all enigma application-layer code and doesn't fundamentally alter the initial linux start-up.

 

[el bandido]

This is nothing more than a badly programmed dish positioner. I can't see it being anything else, and can only wonder what the designer/programmer of the ASC1 was thinking when the thing was being built. You are saying the dish loses sync, which should not happen regardless of receiver commands to move.

If the receiver is on the exact same channel as when you left it, then the receiver probably did not lose power. Looks like you were on the exact same channel from what you have written?

Randomly and unpredictably when power would go out. I would come home and the dish was re-positioned from where it was parked when I left home.
And at 12' in diameter. It is pretty hard to not notice it.

The receiver would be on the same bouquet (Named per the satellite that the channels reside. ex: 127W Galaxy 13).
When the TV was turned on. My receiver showed the correct satellite it was aimed at when I left home. But, the dish had moved.

Purchasing a decent Vbox type positioner should have been a better choice instead of an uninterrupted power supply (ups) if you wanted to fix this particular problem. But any way you look at it, the dish will not come out of sync as you describe during a crash or power loss unless something in the dish moving system is defective. I have never had a dish come out of sync during a power loss as you describe it. Yes, the dish may move during a power loss, but it does not lose sync. And at least you have a shiny new ups which everyone should have.

There is an easy way to keep the dish from moving during a crash or power loss in almost any enigma2 image. Select a channel or service as a start-up channel that does not require the dish to move. To do this, simply select a satellite that you do not use and copy channels or service into it by scanning an active transponder. Do not give this particular satellite dish moving permissions. Something like 177w should work nicely.

To select a channel or service for start-up, highlight the channel or service name, then press the menu button and follow onscreen menu. A very simple solution that requires no coding changes. To fix it proper, ditch the ailing ASC1 and replace it with something that actually works correctly. In the meantime, selecting a dummy start-up channel as previously described should work without issues.

 

[ArloGuthrie]

Just got home from an assignment out of town. Feeling a bit of remorse for the apparent needing to rally a desire to either have a feature added or a way that I could implement it myself.
It was already stressed. Trying ways to figure out why something happened and the simple way from poking around in menus. As a "let's try it and see what happens".

Pretty simple. I gave it a go. It worked. And didn't think anymore about it. My home experienced lightning damage and my satellite equipment was down for an extensive period.
Once moving exclusively to vix from openatv (which I used from day one). Making the decision to start using openvix for one reason and one reason only.
Because in Signal Finder. You have the ability to check what channels are available when tuned to a transponder.
If the closely matched remote control button arrangement to do the most common tasks could be another reason compared with the almost same mirror found in openatv. Then consider it reason two.

So. I guess some things that are important to some really don't matter to others. The plethora of plugin bloatware that is either included in an image by default. To the horrendous and furthest away method of simply moving to another satellite and changing channels. The learning curve of using openatv and openvix after being used to any television remote control is minutes versus some abominations like purE2 and tnap. And others.

I guess the suggestion to purchase a vbox to solve the issue isn't going to be a priority ever. I would rather have the guy over at satsUK build me a diseqc actuator controller and ship it from the UK.
I've gotten rather good at reverse engineering the ASC1 controller to perform repairs with sellf made schematics of the subsections of them. I have three right here.
And is a vbox able to control a skew servo like is found on chaparral feeds and others? Nope.

The how's and why's of why my particular linear actuator controller goes "wonky" when the described scenario occurs. Not really sure.
But I could swear to The Lord Above on a bible that once I made a selection in software that is currently unavailable in openvix (once discovered that it is actually unavailable).
The "glitch" never once happened again. Then. When migrating to openvix. And discovering the anomaly had happened again. Well. You make your decision.
I mean. I have a simple installation as far as the image goes. No pretty anime' chickie with smelling salts and a college degree to change channels.
It was a simple request as to if it were possible to add the feature. Because on the package feed. I could not find a hint.

So. Thanks.

 

[Joe_90]

For info. Coming soon.To a Release 6.7 version of OpenVix. Currently testing in Development versions:

See my previous post #3 in this thread...

 

[ArloGuthrie]

It would be a useful feature for some. If foresight when set for Deep Standby has pertinent bus communication inhibited in the code.

Appreciate it Joe. You're a good man.