Using SpitFire III via Portal

My task was to schedule a script in the Portal to change the channel on a device (TV, DSS whatever). The script was ineffective. The cause was unexpected.

Here are some hints when configuring a scheduled script in the Portal employing a SpitFire III.

First, read the Portal Admin guide section on Scripts and Script devices. The information is very good. The following information augments the manual.

I was having trouble getting a script to run which would change a device (TV) channel number to a two-digit channel. A script for a single digit channel worked ok.

Please configure the VBrick PassThrough port controls as “Force Off” (Configuration > Passthrough > RTS Control & DTR Control both “Force Off”). The SpitFire documentation does not specify any requirements concerning RS-232 Control Signals. However, if the VBrick Control Signals are configured as “Automatic” or “Force On”.

In the process of using a protocol analyzer the 2-digit script started working. In fact, as long as I kept the PA cable between the brick and the SpitFire, it worked. Even when the PA was disconnected it worked. However, substituting other cables did not help. The difference was that for the PA cable, I was minus a gender-bender, and substituted a few patch wires. I was NOT connecting all pins.

When I reconnected just the VBrick supplied serial cable, and the null adapter between the brick and the Spitfire, and forced controls off – it works. If controls are at automatic, or are forced on, it does not work.

The SpitFire III manual does NOT mention anything about the serial port except to point it out in a picture.

Unfortunately, the Portal Admin manual shows a screen capture with controls at automatic, although the text doesn’t actually tell you to do this. We will modify the manual.

It may be that this was not an issue with Spitfire II. I haven’t tried that.

Here is my script with descriptions of the commands:
Script for a Toshiba TV with device code 359, changing to channel 54

<-script->
<-send binary 0xc1 0x0d-> AUX slot
<-receive 2->
<-send binary 0xc0 0x0d-> program setup (to set device code)
<-receive 2->
<-send binary 0x83 0x0d-> press 3
<-receive 2->
<-send binary 0x85 0x0d-> press 5
<-receive 2->
<-send binary 0x89 0x0d-> press 9
<-receive 2->
<-send binary 0xc0 0x0d-> program setup (end setting device code)
<-receive 2->
<-send binary 0xd3 0x0d-> repeat IR tx 3 times
<-receive 2->
<-send binary 0x85 0x0d-> press 5
<-receive 2->
<-send binary 0xcf 0x0d-> smart (effectively adds a pause)
<-receive 2->
<-send binary 0x84 0x0d-> press 4
<-receive 2->

Note** Changing the d3 to d1 to repeat IR only once instead of three times, made no difference. It works as long as the “smart” character is inserted between the channel digits.

After making these changes I found the manual channel clicking done with the “Control Device” was much more reliable. If I click 2 digits too quickly, I still get a “Device Programming Failed” message meaning the Portal couldn’t handle it. But if I waited even a half second or so between clicks, this also now works.