I have job that we did last year with DPI Titan LED Projector installed into a projector enclosure with a cooling fan, the projector cpu runs 24/7, so we installed a snap av switched outlet as the customer did not want the external cooling fan and projector running all the time. In the savant programming, it turns the switched outlet on and 3 mins later it issues the power on command to the projector. About 1 in 50 times the projector will not power on, it is connected RS232. Of course I am never there when it happens, so I want to add a simple power on ir command but DPI does not have a simple power on command, it is a push and hold for 5 seconds. Any ideas?

I've worked with a couple of these together in an enclosure. Their power On is a bit squirrely.
A couple of things come to mind.
Simplest, is it possible that two RS232 commands might work in those rare instances?

Or, can hex code be copied into Savant? If so, there's a multi-step trick I used to use with the first generation of Prontos:
A. Learn the Power On code.
B. Learn the Power ON code holding down the button, not letting the IR learner see the first second of emitted code.

Then create a code that is A followed by as many as a dozen repetitions of B.
A starts the projector seeing the command. The second part, repeated, make a code extended in time. Your hex code, then is ABBBBBBBBBBB or something like that.

The Pronto software issued one command immediately after another, so there it was done as a macro. Later versions of Pronto software inserted a pause that broke up the command.

I never made a long single command ABBBBBBBB etc by copying several repetitions of B in the editor, though that may possible. It depends on your editor.

Our Titans are Crestron controlled and I'll get some more info for you if our programmer has the time to consult on this.

Are you having the RS-232 code sent a second time? I would just do another 10-15 second delay and send the ON code again.

It's being sent three times.

So you thought of repeating it already, huh?
In the middle of your pain, I'm kidding with you. Sorry.
So... with a delay between, maybe?

Anyway, we found the Titan required 50 seconds between restoral of power and any command.

At what interval? Sure seems odd that it happens so rarely and you cant reproduce it.

Have you talked to DPI about the power on code? Seems silly that they would not have a discrete on code that can be sent easily through a control system.

Have you tried this DPI On code?

0000 006D 0022 0000 0157 00AC 0015 0015 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0689

What does he do to get the projector to come on once the macro fails?

Regardless of the profile command structure, you could always create a trigger that is testing the state of the projector and if it goes to 0 then issue a power command. I understand there are some other timing things at play but it could be an additional way to ensure proper operation.

I have had issues with Denon and Yamaha AVR profiles where if the receiver hasn't been powered on for a while, the IP commands will not turn the device on. Turning the zone off and back on again will fix it. And the Denon or Yamaha app will turn it on. I also don't believe it's a profile issue because it's happening with different profiles and different brands.

Could you elaborate on how to issue this trigger?