Power On Delay

[GeekHawk14]

How do you correctly program Control4 for a  Power On Delay for a device?  I have a handshake issue between my projector and my AV Receiver.  I need to delay the power on of the Receiver for 30 seconds to allow the projector to be ready to see it.  Any sooner and the projector refuses to accept the signal from the Receiver.  I'm replacing the projector next year, but would like to get past this for now.  Dealer hasn't been able to figure it out.

[msgreenf]

what kind of driver is it? IR? if so you have to edit the power on delay

[Cyknight]

If serial/IP it may have that option in composer.

Worst case scenario, you could try programming to turn the receiver off, then back on 30 seconds later. Note though that receivers can be iffy for that sort of programming (long story, but short version is, the proxy/drivers for them don't always work for power on/off PROGRAMMING).

If delay can't be set, I would first check to see if manually switching inputs doesn't allow the hand shake to engage as well - that is something easily and reliably programmed.

[GeekHawk14]

1 hour ago, msgreenf said:

what kind of driver is it? IR? if so you have to edit the power on delay

IR.  My dealer has been trying to do that, unsuccessfully to this point.

[GeekHawk14]

50 minutes ago, Cyknight said:

If serial/IP it may have that option in composer.

Worst case scenario, you could try programming to turn the receiver off, then back on 30 seconds later. Note though that receivers can be iffy for that sort of programming (long story, but short version is, the proxy/drivers for them don't always work for power on/off PROGRAMMING).

If delay can't be set, I would first check to see if manually switching inputs doesn't allow the hand shake to engage as well - that is something easily and reliably programmed.

Maybe a dumb question - but why would a driver struggle to power on/off a device, but not struggle to power everything on at the start of a sequence to power on the home theater?

[GeekHawk14]

Just now, GeekHawk14 said:

Maybe a dumb question - but why would a driver struggle to power on/off a device, but not struggle to power everything on at the start of a sequence to power on the home theater?

and power everything off successfully when I'm done watching?

[msgreenf]

4 minutes ago, GeekHawk14 said:

IR.  My dealer has been trying to do that, unsuccessfully to this point.

did he try to open it in driver editor and edit the power on delay?  Or he can download the driver, open it in notepad and edit the power on property and re-install it

[GeekHawk14]

44 minutes ago, msgreenf said:

did he try to open it in driver editor and edit the power on delay?  Or he can download the driver, open it in notepad and edit the power on property and re-install it

Good question to ask.

[Cyknight]

1 hour ago, GeekHawk14 said:

Maybe a dumb question - but why would a driver struggle to power on/off a device, but not struggle to power everything on at the start of a sequence to power on the home theater?

It's not a dumb question as such, but the answer is not very simple.

Brief version, the driver doesn't have an issue turning something on/off - the issue comes when using programming to do so (vs standard setup). It's not that the driver has trouble sending the code, it's that due to how receivers drivers/proxies work/are written to use multiple zones on a receiver that cause the 'default' proxy program line 'turn on/off receiver' (which is what is shown to you face-front when selecting the receiver under 'actions' in programming) to not function the way you would logically assume it would because the the driver doesn't actually have that function implemented (and that's to allow the added function of turning on/off multiple zones on a receiver).

It's a matter of old proxy that got pushed beyond it's initial functions.

 

Note that many 'newer' (been years) drivers still allow you to program on/off options, but you have to do it using the driver's  'device commands' vs the default 'proxy commands' if you will.

 

Again, it's not the system struggling to do something, it's just how many receiver drivers are implemented that make it more of a struggle to program it 'manually' if you will.

[Cyknight]

1 hour ago, GeekHawk14 said:

Good question to ask.

Suspect he may not know the difference in 'power on delay' vs 'code delay on power on'

The latter is something a dealer edits in the built in driver wizard and is very basic to do, but it will only delay commands sent AFTER a power on command, and will do nothing to delay the the power on command itself.

The former is something that must be changed in driver editor or directly in the xml file as msgreenf mentioned above, and MANY dealers/programmer do not take that step as it goes above and beyond what standard C4 training encompasses.

Not saying it's difficult, but it's not 'standard practise' at least. Probably should be...but well there it is.

If you or your dealer knows the driver used (and it's a standard database driver), post the exact driver file name, maybe one of us can have a peek, edit and post a copy.