AXB-IRS4 Initialization?
vegastech
Posts: 369
in AMX Hardware
Is there anything I need to do in my code to initialize an AXB-IRS4? I am testing some code with one, and I can't get the IR ports to light up. The IR works on my NI-700 port, but not the IRS4. I have set the ID(129) and uploaded IR files to each port, and have verified that it is listed in the online tree. Thanks!
0
Comments
That depends on what you call initialisation. You have to load some IR codes, which you've done.
You would then have to declare the device in your code and use that declaration as a reference.
Why don't you use 'control a device' in your diagnostics and pulse a channel that has a code in it?
You should get some lights happening then.
Cheers
You may already know this and just used the wrong terminology in the post. but, I'll post this anyway just in case.
The old AXB-IRS4 doesn't separate the IR emitters by ports. In other words, you don't have IR emitter 1 at 129:01:0, IR emitter 2 at 129:02:0, IR emitter 3 at 129:03:0, etc..
When you set the box's address, you're setting the address of the first device at 129:01:0. the 2nd IR emitter is addressed at 130:01:0, 3rd at 131:01:0 and 4th at 132:01:0. the remaining 3 IR emitters get the next three device addresses consecutively by default.
So, if you have other axlink devices addressed on top of those other addresses, they won't work.
Hope that helps.
BUTTON_EVENT[arrTPMB,nBtnArray] { PUSH: { local_var integer btn local_var integer src btn = get_last(nBtnArray) src = get_last(arrTPMB) TO[src,get_last(nBtnArray)] } }I'm specifically concerned about the new DirecTV HR24 box IR codes. Thanks in advance!I was gonna say this. I have several AXB-IRS4s on my personal system and they can send an IR code all day if you want them to.
I also note that I had to recapture the DirecTV codes due to their new 'feature' of using a hold time of .2 seconds now on Ch up/down and directionals that totally screws up control systems use of them. I had to capture the ir remote just flicking the codes and hoping the capture worked. It took several tried but I did get them. So, at least now the channels don't go racing up or down whenever you hit the buttons on the TP. But, it did jimmy up the ability to press and hold on the TPs.
BTW, if anyone want's this file, I'd happily share it.
e
could you post a code snippet with what you are doing with your IRS4s? I'll have to check diagnostics when I get home. I'm wondering if it's the way I wrote my code. Also, what works better on these - doing an ONLINE_EVENT setting the IR pulse time, or telling the IRS4 to set the time in the button press code?
hmmm...
sure, but I can assure you there's nothing magical about how I'm doing it.
something along the lines of:
button_event[dvTP_array,my_button_array] { push: { local_var integer button_id local_var integer tp_id button_id=get_last(my_button_array) tp_id=get_last(dvTP_array) to[dvTP_array[tp_id],my_button_array[button_id]] // for TP feedback to[dv_my_ir_box,my_IR_Box_Channels[button_id] } }On the set_pulse_time... I'm sure someone will pounce on me if I'm wrong, but I think that command actually effects pulse time system-wide. So, I'd do the command in the button event and then set it back to 'normal' (whatever that is) after the event has fired.
If I'm wrong, then I'd do it on the device online event.
I have an IRS4 configured as device IDs 132:1:0, 133:1:0, 134:1:0, and 135:1:0. If I go into Diagnostics-Control a Device, I can send IR commands via the pulse option (using exit currently). But when I try to send it in code using an R2, I get nothing. I am doing this:
DEFINE_DEVICE RFGUEST433 = 128:1:0 //433 Gateway in Guest 1 SAT_4 = 132:1:0 //NXB-IRS4 SAT_5 = 133:1:0 //NXB-IRS4 TV_OFFICE = 134:1:0 //On NXB-IRS4 DEFINE_EVENT BUTTON_EVENT[RFGUEST433,0] { PUSH: { PULSE[SAT_4,BUTTON.INPUT.CHANNEL] } }I have enabled diagnostics to see the button press/response from the RF, and see this: That is pressing button 0 on the R2, which should light up IR port 1 on my IRS4. However, it doesn't light up.Doing the same thing in Control A Device operates that Channel 10/IR Code 0 just fine. What did I do wrong?