|
Click here for information on the
required hardware and where to purchase it.
* Tira2 not recognized when using latest driver
2/28/07
We have found that the latest available driver from Home Electro for the
Tira2 causes it to not be recognized by IRCommand2. At present the only solution
to this issue is to re-install the previous driver. If you updated to the latest
driver from a prior version you may be able to just "roll back" in
device manager. Otherwise, be sure to completely remove the new driver before
installing the older one. Check with Home Electro for the older driver download.
* Device Power-On/Off Issues with UIRT and MyBlaster
3/18/07
IRC2 now supports a signal repeat feature that should correct this
problem. Try updating to v3.85 before following any other instructions in this
note.
11/13/06
If you cannot get a trained button to toggle device power for a device
and you're using a USB-UIRT or MyBlaster dongle then try this:
- Go to the train dialog for the power command signal by clicking Set
in the property sheet for the Command or Button Action
property.
- If you haven't trained the signal yet then do so by clicking Train.
- After training is done, click Copy in the train dialog and then
click Paste. Do this one additional time. This step repeats the
trained signal burst so that multiple bursts are sent when the button is
clicked.
- Click Save to store the results.
UIRT and MyBlaster are designed to return a single "burst" of a
command signal when training a button. This can be observed by looking at the
resulting signal in the Scope. However, some devices require two or more
consecutive copies of the command signal burst before they will respond. This is
usually necessary only for the power command and is probably intended to avoid
accidental changes to power state. The method above will store multiple copies
of the signal burst in the command signal and may resolve the problem.
If you are using UEI codes with MyBlaster then a similar problem may occur.
In this case, just set the Repeat # field in the Set IR Code
dialog to a value of 2 or 3. This will cause the signal to be repeated.
* Toggle Bits
7/30/05
IRCommand2 v3.72 now includes support for toggle bit remotes. This is done by allowing both versions of the command signal to be trained
into a button. IRCommand2 can then alternate between the signals with each
button press.
1/5/05
Many remote control protocols have a toggle bit in the signal that toggles a bit
on and off with each button press of the remote. The toggle bit enables the
receiving device to detect and respond to each press and release of a button
even if this is done very rapidly (e.g., the button is tapped several times).
This basically means that there are two different codes that can be sent for
each command - one with the toggle bit on and one with it off.
The toggle bit protocol is a problem for learning remotes (like IRCommand2)
only if the receiving device requires the toggle bit and ignores
subsequent commands if the bit isn't toggled. The most common symptoms of this
problem are: the device responds to every other command sent, or you must send a
command to some other device to get the problem device to respond to another
command, or you cannot send duplicate commands (e.g., "22" only
registers as "2").
IRCommand2 will directly support toggle bit commands in the next release.
This will be done by allowing both versions of the command signal to be trained
into a button. IRCommand2 will then alternate between the signals with each
button press. Listen triggers already support a similar feature that enables
IRCommand2 to consistently respond to remotes that use a toggle bit.
Until the next release, you may be able to work around this problem for some
devices. IRCommand2's signal editing features for trimming and appending to
signals enable creation of arbitrary signal sequences. One approach to try is to
append a signal for another device to the end of the actual command signal. More
details to follow...
* USB-Serial Adapters
7/30/05
IRCommand2 Version 3.72 works well with USB-serial adapters and the IR200L.
Our testing so far shows that adapters using the Prolific chip set with
the Prolific driver seem to work best. The previously mentioned Sewell
SW-1301 uses this chip set, but quite a few other adapters also use
it.
5/12/04
IRCommand2 Version 3.50 appears to work much more reliably with USB-serial
adapters and the IR200L, though some adapters still seem to work better
than others. The best adapter tested so far is the SW-1301 from Sewell.
This adapter has only been tested under WinXP.
The CM11A/HD11A interface for X10 also works with USB-serial adapters. The
only limitation found so far in our testing is that the interface does not wake
the PC from standby on receipt of a command as it does using a serial port.
|
