The Ortek VRC-1100 uses the OrtekMCE IR protocol, which can't be fully expressed in Pronto Hex.  Two bits of the IR stream take on 3 states:  the first frame (button down) sets these two bits to 00,  middle frames (button is being held down) are 01, and the final frame (button released) is 10.  Pronto Hex can only handle an initial state and a repeating state, so the final frame can't be sent. The IRP notation for OrtekMCE is {38.6k,480}<1,-1|-1,1>([P=0][P=1][P=2],4,-1,D:5,P:2,F:6,C:4,-48m)+{C=3+#D+#P+#F}.  The state variable is P.

Perhaps your equipment will ignore the lack of a final frame, or can TouchSquid handle such 3 state IR signals?

Here's Direction Up written in Pronto Hex, skipping the final frame
Arrow Up   Device Code: 21 Function: 21
0000 006B 000B 000B 004A 0025 0025 0025 0025 0025 0025 0013 0013 0025 0025 0025 0025 0025 0025 0025 0025 0013 0013 0025 0013 073D 004A 0025 0025 0025 0025 0025 0013 0013 0025 0025 0025 0025 0025 0025 0025 0013 0013 0025 0025 0025 0013 073D

Does it work?  If it does, I'll post the rest of the known signals.