Home AMX User Forum NetLinx Studio

IR fail to Toshiba 52WV645U

I'm just doing IR control for an LCD TV; I capture the IR codes from the remote, map, upload to controller. I'm getting the pulses I expect from the emitter, but the TV won't respond. I've tried CTON/CTOF timings everywhere from 1-10. I've re-captured the IR from the remote, re-did everything else, still no love.

Not sure I've ever failed so miserably at something that should have been so simple. Any ideas out there?

Thanks,

Comments

  • Jorde_VJorde_V Posts: 393
    Can you post some of those IR codes? I'll have a look.
  • Are you sure the Emitter is over the IR Window? They're not always where they seem.

    Have you tried holding the emitter 1ft from the screen and see if if will respond?
  • Yes, I've tried the emitter just about everywhere. I can identify the IR pickup because I can block it and the remote won't work when I do. It's almost got to be something really stupid and simple, but I haven't figured it out yet.

    It will take me just a bit to get the IR codes out.
  • viningvining Posts: 4,368
    I would send the IR file directly to the IR port from IREdit and then actuate (send) commands from there. Also if you want to avoid the IREdit Monster as Joe Hebert puts it you can do this now via NS3.

    Also as mentioned in another current post ensure you have these in your IR port DATA_EVENT ONLINE handler:
    SEND_COMMAND dv_IR1,'SET MODE IR'  ;       // set IR port 1 to IR mode
    SEND_COMMAND dv_IR1, 'CARON' ;            // set IR port 1 to CARRIER ON
    
    Although they are the defaults things aren't often what they should be.
  • There was a batch of IR Emitters with the polarity reversed a while ago.

    Have you checked with a camera phone that the emitters are flashing?
  • ericmedleyericmedley Posts: 4,177
    I'm just doing IR control for an LCD TV; I capture the IR codes from the remote, map, upload to controller. I'm getting the pulses I expect from the emitter, but the TV won't respond. I've tried CTON/CTOF timings everywhere from 1-10. I've re-captured the IR from the remote, re-did everything else, still no love.

    Not sure I've ever failed so miserably at something that should have been so simple. Any ideas out there?

    Thanks,

    this might be outside odds...

    I ran into an issue recently with my IR stuff. I would capture a file and it would just flat not work. I'd see IR flashes on my cell phone camera and all that. It would just not work.

    then I noticed that susequent IR captures were not working as well. My IRIS seemed to be working just fine, but anything it capured wasn't working.

    I sent it in and they recalibrated it. Now it works fine.

    Have you tried to capture other working codes on another already working IR rig? Perhaps the IRIS you're using is not functioning properly.

    Just a thought...
  • I'm using a Xantech "visible" IR emitter, but I've tried 2 of them so far. Haven't tried an AMX one yet.

    Attached is the IR file I captured. The only IR code I actually need is Power, but I've tried 5 different codes so far and the TV won't pick up any of them.

    A failure in the IRIS box is a fair guess; I don't have another one to try right now. I'll poke around on that some more.

    Here's the code I'm using:
    dvdisp21	=	5001:10:0 //Monitor Rm 21
    
    data_event[dvdisp21] { //Toshiba Monitor
        online: {
    	SEND_COMMAND DATA.DEVICE, "'CTON',2"
    	SEND_COMMAND DATA.DEVICE, "'CTOF',2"
        }
        string: {
    	// IR device, no strings from it
        }
    }
    
    //21 display power
    button_event[dvtp3_display21,31] { //POWER ON
        push: { 
    	send_command dvdisp21,"'SP',9"
        }
    }
    

    Thanks for the help everyone!
  • You can try adding these to your IR file:

    Power On:
    0000 0069 0022 0002 0161 00B1 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0042 0016 0016 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0016 0016 0042 0016 0016 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0016 0016 0042 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0042 0016 00FB 0161 0058 0016 00B1
    

    Power Off:
    0000 0069 0022 0002 0161 00B1 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0042 0016 0016 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0016 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0042 0016 00FB 0161 0058 0016 00B1
    
  • KennyKenny Posts: 209
    I recently had a similar issue where the IR just did not work. I could see it with my phone camera but the tv would not respond.
    I swapped the Xantech emitter for a very old AMX one and that fixed issue.
    I know the AMX emitters are pricey but they seemed to work better than the Xantech ones.
  • And the winner is... Kenny!

    An AMX IR emitter works fine. None of the Xantech "blinker" emitters do. This is the first time I've ever run across a difference in functionality between the two, besides the visible light in the Xantech ones. Fascinating.

    I've got a whole drawer full of the AMX emitters because we always just use the Xantech ones instead. The visible blink is a godsend during installation and troubleshooting. Or, used to be, more like.

    Thanks!
  • KennyKenny Posts: 209
    Woohoo!!!
    Look at that, I'm the winner and I still don't get a prize. :(
    Glad I could help. Hopefully no one else on these forums will have to spend the time that it took me to figure this one out. A dealer and I were beating ours heads against the wall for several hours trying get the Xantech to work.
Sign In or Register to comment.