The ASC1 does not have a sleep function. It is always listening when placed in operate mode. If powering cycling the ASC1 causes the ASC1 to respond to a motor command, I would check if the sending device is initially issuing the DiSEqC command and if the signal path is correct with no pinches/kinks in the coax, corroded fittings, failing switches/splitters, and proper voltage levels. Deaf DiSEqC slaves are usually due to insufficient amplitude or missing 22KHz/DiSEqC signals. Power cycling the ASC1 will interrupt the satellite signal presented to the attached tuner and most tuner devices will reissue switch and motor commands to re-establish a signal path when it is interrupted.
A few months ago I experienced a similar problem with intermittent controller communication. It stumped me until I discovered that the coax had been kinked when I fished cables behind the test bench. Replaced the coax jumper between the receiver and the controller and the system started working again.
What tuner is connected to the ASC1? A STB, PCIE/USB tuner?
Do you have a meter or scope to verify the device is issuing 22/KHz DiSEqC commands?
Are there any splitters or switches (22KHz or DiSEqC) inline between the tuner and the ASC1? If so, does the problem occur if removed?
Does this happen on both vertical and horizontal transponders or only when tuned to one polarity? If one polarity, which polarity?
Check the firmware version again to make sure it is the latest. This sounds like a glitch that was discovered and fixed with a late firmware update. The problem was if you used the power button on the unit or the remote to turn it off then the other buttons would not function when you turned it back on. You would need to power cycle the unit (switch on the back) to get the buttons on the front panel or remote to function again. However when the unit would not respond to the manual buttons it would still respond to DiSEqC calls.
What PC software is used for switch and motor control?
Did you reset the DiSEqC user settings to the software defaults? Try changing the repeat settings to different values? What 22KHz/DiSEqC command parameters does the software provide?
Do you have a STB to swap and compare operation?
Feel free to send the ASC! in for bench testing. We have never observed the "sleep" issue that you that you are experiencing, and would be happy to test. Have dozens of STBs, cards and software to test, but no Linux and Kaffeine. Unfortunately, not many use that solution, so not much documentation or discussion on the NA satellite forums.
Yes, It is a known issue that the AZboxes incorrectly issue commands to set limits on motors and controllers. Nothing unique to the ASC1.
As mentioned in previous posts, check the Kaffeine software DiSEqC control interface settings. I understand that Kaffeine has presented users set-up and configuration challenges. Have you checked with a Kaffeine user group for input on the DiSEqC command structure and settings?