No IR control from NI3100?
vegastech
Posts: 369
I recently uploaded a new src and tkn to a 3100, and I'm having trouble getting the NI to output IR. I am using an 8400 panel, and when I push a button, I see the activity led light up on the NI, but no IR lights flash. I went into Diagnostics-Control a device, and can select the port (5001:1:0) and see the led light up, but nothing from my program. Originally I was using a set of dev arrays and variables, and when that didn't work (although it worked at my house last night), I went the P1 style:
button_event[bluray,1] { PUSH: { PULSE[bluray,1] } }and still no response from the NI. I recently loaded an IR file to that port(5001:1:0), so I know it's there, and I can see the port available in the online tree. What am I doing wrong?
0
Comments
i had a similar problem with an NI-2100 once. I was able to see the IR led lit but no actual IR data was
transmited from the port. I tried to set and re set the properties of the IR port and yet nothing.
BUT when i used the send commands it worked. So try to use the SP and CP commands to see if works.
Remember that the SP command works like a string buffer. That said it is best used when you want to pulse a sequence of IR numbers.
Here is an example on how to send the sequence of 142 with the CP command (assuming standard AMX/DUET channel numbers):
The CP command on the other hand CLEARS that buffer before the IR command.
Use CTON and CTOF to send the pulse (CTON) time and the idle (CTOF) time.
If you have AMX-PI installed try to search for these functions.
Yes, and even though it's a serial port, you can turn a channel on and off. So, diagnostic is not lying to you. I believe the IR ports on an NI-3100 start on port 9.
i never get anything from diagnostics when I use system 0. I can only get a response when I give it the real system number. Have you tried 5001:1:1?
I guess I should always verify what I am copying from other parts of my code....It seems that non-AMX devices don't exactly like the send_command code! Duh...hello, send_string. Hopefully this fixes my non-responsive switcher issue for tomorrow's return!
Easy mistake to make. Everyone gets caught by that one