I have a Prodigy system I have programmed in SB with a few sources (Blueray, Cable TV). When you select each source it turns on the Receiver, the source, and the Samsung UN series TV. The receiever and source always turn on correctly, the Samsung TV occasionaly does not turn on, I would need to select the source a couple times before the TV finally turns on.

I am using the UN series IR from the Crestron Database using the Power_On and Power_Off functions. Does anyone have any suggestions?

Where do you have the IR bug located on the TV? I believe with these TV's I placed them directly over the power LED and have never had a problem where the TV wouldn't turn on

How is everything else controlled?

Even though there are 5 IR outputs there is only one IR driver. Meaning if you are trying to turn on the TV, AVR and anything else via IR at the SAME time not all the commands get sent.


If you DO have delays between commands, then if could be IR placement like SWO said.

I do have the IR bug over the power LED, but do not have any delays setup, is a 2 second delay adequate?

I assumed the IR driver would just go down the list of commands firing them one by one.

2s is more than enough.

It sends all the commands at once, so the only delay is on the CPUs clock speed. So fairly close to NO delay at all

How many commands can the IR driver send at the same time? I just want to see if I need to delay any of the other commands sent to the source player, AVR?

Since I've never had an issue with those turning on, I'm assuming I only need to delay the TV command.

1 command can be sent at a time. If you only have one device per IR port put a .2sec delay between your commands and you should be fine. If you have multiple devices on one IR port you may require a longer delay (say .5 seconds)

Also make sure your IR bug is completely pushed in on the processor.

Another troubleshooting step is to open toolbox and debugger (or run realtime in SB) and physically send the power on/power off commands to the TV, if they work every time then you need a longer delay between the previous command being sent and your power commands

Shoot, that is an even more important note than the delays or having the emitter in place!

Have gone crazy a few times with MC3s only to note whoopsie! its not plugged in all the way

Typically I use a .1s delay between commands, with the IR discretely being .2s pulse.

This is easier to accomplish in Simpl than SB if my memory serves me correctly. Also if he has more than one device on the IR port a longer delay may be required to allow the IR bug to transfer the multiple codes

I will give these all a try, I have 5 IR ports and each one is assigned to only 1 device (Samsung is IR1, Receiver is IR2, Cable TV is IR3, etc).

What was your findings? Out of the 3 or 4 things suggested one has to be the answer. My best guess is that it was either the IR not plugged into the back of the processor or you needed a delay before your TV power signal

I added in a delay of 1s before the TV is turned on and added a .2s pulse to the TV before, and for the most part the TV is much better about turning on. I checked the IR cable, and it is fully plugged in.

There are still some instances where the TV wont turn on and I have go back to the source screen, select the source again, and it would finally turn on.

I feel like I may need to move the programming from SB to Simpli to better suite what I'm doing. Anyone want to help out with this? You will be compensated, please PM me.

Have you tried setting the tv command first. Try a .05 delay as your first command and then add in the tv on command. Add other delays as necessary after the tv power on command for the rest of your macro. Some samsung tv's take like 5-8 seconds before you can send in a input command. Do you have the option of using ex link and 232 for that display?

I usually do a TV on at the beginning and then a TV on at the end of the macro as well. Usually overkill, but just helps me sleep better knowing it is going to turn on every single time.