IR into a controller

Garret

I assume that since there are AMX trigger commands that you can use these to get a master to do things. My question is what methods are used to get them into the controller and what kind of programming is needed to handle them once they are there. I would also love if there was a way to pass through any IR command and send it out a specific IR port or all IR ports of the controller.

Thanks for any advice.

ericmedley

Garret wrote: »

I assume that since there are AMX trigger commands that you can use these to get a master to do things. My question is what methods are used to get them into the controller and what kind of programming is needed to handle them once they are there. I would also love if there was a way to pass through any IR command and send it out a specific IR port or all IR ports of the controller.

Thanks for any advice.

the ways that come to mind are

using the I/O (binary on/off)
using the serial comm ports (this just involves creating an API for whatever device you're connected to.

using a IP com port. Same as above.

Master-to-master communication. This is a lot more 'netlinx' in feel. devices, real or virtual can be monitored on the other master(s) and all the typical state changes, strings and commands can go back and forth.

There's a number of ways to make one master talk to another. I suppose the most common is to make a virtual device and send string/commands back and forth through it. Also the channels work too for feedback as well as triggering routines from button pushes or level changes.

We might be able to suggest a good 'best practice' if you'll let us know what you're trying to do.

DHawthorne

There are native AMX IR receivers that can be added like any other device to a system, but they don't pass through non-AMX IR signals. They accept AMX IR codes and treat them like button presses. So you would have to trap those out and send the appropriate command to your device(s).

Garret

The intention is to use a URC remote or similar programmable remote to activate "macros" on a netlinx controller. The pass through portion is so I wouldn't have to write an event for every up down or number key i would use to control a device. Its not the end of the world if I have to It just could save me some time.

Can I use the I/O ports to get IR into the controller using an IR receiver if they are AMX commands? If so what would the code look like to get it to recognize that?

One final thing its probably not wise to post this as part of this thread but what is the command to send a button press to a touch panel? I assume its something like

SEND_COMMAND dvTP1, "'^some three letter comand goes here"

I have spent an hour reading the AMXPI for the MVP-5200i

ericmedley

Garret wrote: »

The intention is to use a URC remote or similar programmable remote to activate "macros" on a netlinx controller. The pass through portion is so I wouldn't have to write an event for every up down or number key i would use to control a device. Its not the end of the world if I have to It just could save me some time.

Can I use the I/O ports to get IR into the controller using an IR receiver if they are AMX commands? If so what would the code look like to get it to recognize that?

One final thing its probably not wise to post this as part of this thread but what is the command to send a button press to a touch panel? I assume its something like

SEND_COMMAND dvTP1, "'^some three letter comand goes here"

I have spent an hour reading the AMXPI for the MVP-5200i

To repeat what Dave said, the AMX IR reciever's name is a bit tricky.

It WILL receive only one IR file loaded into the remote. That being the IR capture of an AMX IR remote.

It WILL NOT recieve any other manufacturer's IR remote.

When the IR reciever recieves and AMX IR flash, it triggers a channel in the device as a button push. So, if you flash AMX IR code for 'Channel 5' you 'll see a buton push on the IR Reciever device's button 5.

We've done this in a quite a few systems. We put in a hand held remote and map it with AMX IR Codes. the client doesn't know the difference. they just see the stuff go and that makes them happy.

Youo will not be able to make the AMX system an IR Passthrough if that's what your asking. It just doesn't work that way.

Garret

ericmedley wrote: »

the ways that come to mind are

using the I/O (binary on/off)
using the serial comm ports (this just involves creating an API for whatever device you're connected to.

using a IP com port. Same as above.

In most cases I'll use 232 out of a MSC400 and write an API. I found a MIO-IRRX that is the only IR receiver that I have found for AMX, that doesn't mean others don't exist but there is a pretty massive AMX product line and for someone new to AMX its a lot to sort out. The IRRX i get, it sits on the ax link buss and sends out button presses when it gets an IR command it recognizes. Knowing of this things existence helps.

Some of my confusion comes from what you mean by using the I/O (binary on/off)
The sensible side of me figures you mean I could trigger a command when it turns on or off.
The optimistic side of me wonders how fast those I/O's can change state and if its fast enough, it could detect the high and low voltage pulses of an IR command.

So in summary the only likely answerable question in all this is there any options for IR in besides the IRRX? It looks like a good solution I just like to know all my options.

Thank you for all the help.