1028964 - SF0-154 Latte Crestron iPad unable to use arrows within Crestron UI.

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: AVOps: Conference Rooms, task)

Description

[Ruben Olaes]

SF0-154 Latte Crestron iPad unable to use arrows within Crestron UI.  Unable to scroll down to select CRs in the directory, as well as unable to type in letters using the iPad within the *Vidyo* interface.  However, I am able to do a room search using the Crestron UI.

Comment 1

[Aaron Obstfeld]

I bet the IR bug fell off the front of the Vidyo codec.  This would explain the arrows, but not the numbers - I'm not sure we've ever seen T9 on the number pad - I think the API just allows for digits.  This should be confirmed.

Comment 2

[Ruben Olaes]

OK, I'll take a look to see if the IR bug wanted to go for a walk, and let you know what I find out.

Comment 3

[Ruben Olaes]

IR bug is his normal locked and upright position.  Please advise if you want me to check anything else.  Thanks.

Comment 4

[Aaron Obstfeld]

This has to be something physical.  I just checked and the program appears to be running normally.  We need to verify that the IR bug from the MC3 is connected (stuck) to the USB IR receiver (there should be two emitters; one from the Xantech IR extender and one from the MC3), plugged in to the correct port on the MC3 (IR Port 1), and is properly working (blinks when directional buttons are pressed on the iPad).  We can also check that the USB IR receiver is plugged all the way into a USB port on the HD-50.

Ruben, take a look at as much of the above as you feel comfortable with and let us know if you find anything or if we need to send someone out.  I'll start coordinating with our team to see who can make it toward the end of the day if necessary.

Comment 5

[Jared Obstfeld]

I stopped by this morning and found the USB cable unplugged from both the Xantech and the Vidyo box. I plugged in the cable and rebooted the Vidyo box. The IR functions are now working properly for Vidyo control.

Comment 6

[Ruben Olaes]

Jared, thanks for fixing the problem! I'll definitely make sure to check these cable connections in the future.  The IR bug "stuck" location is usually what we've been told to check... guess we now know that it was more than one connection that was faulty / unplugged.

Thanks again!