They are for different purposes:

Detector 1:

This is a precise detector for accurate sampling (or learning) of raw remote control signal data. It has a short range (only 1 to 2m), but the sampled data can be used for reliable signal output and signal recognition.

Detector 2:

For applications where you want to control the PC with a remote control this standard long-range remote control detector is used. It has a reception range of 10m or more with sufficient accuracy for signal recognition, but not for reproduction.

Yes! For performance reasons, there is currently a software limit of 32 RedRat3s, but in principle this could be increased to the USB limit of 127 devices.

Yes, the RedRat3 works well in both directions with PowerMid, so it is assumed that there should be no problem with other types of IR extender.

OUT - From the RedRat3 can be sent via an IR extender to another room.

IN - The computer can be controlled from another room by using an IR extender to send IR signals to the RedRat3. (Developer Note: In this situation you may see additional spurious signal input from the RedRat3 as IR extenders tend to detect and transmit any IR noise in the source room, adding to the IR noise in the target room.)

Yes. Telewest cable set-top boxes (STBs) use an IrDa-like remote control signal protocol. NTL boxes either use standard remote control signals or the same IrDa-like signals as used by Telewest. If your NTL STB uses normal remote control signals, then the RedRat3 will learn and output these signals without problem. If your Telewest/NTL STB uses IrDa-like signals, then the RedRat3 can now output these signals (from firmware version V0.17 onwards). Please look here for more info....

This is an indication that the initial pulse of the IR signal from the remote control is pretty short, so not long enough for the RedRat to measure the carrier frequency using its default settings. What the RedRat tries to do is measure the carrier frequency of the IR signal in this first pulse of IR by counting 8 cycles of the IR carrier wave. If the pulse is short, it may not have sufficient cycles of the carrier wave, so the RedRat generates this error message.

To get round this, the number of cycles that the RedRat measure can be reduced. Using the Signal DB Utility, go to the 'View -> Signal Capture Parameters' menu item. The third field down is 'Mod. Freq. Periods to Count', so change this to '4' and see whether that helps. If you still get the problem, then reduce further to '2' and then '1'. If this does allow you to capture the IR signal, then it may mean that measurement of the carrier frequency is not quite as accurate, but this can be manually adjusted late if necessary.

The most usual cause of this error is interference with the IR signal, e.g. sunlight or other light sources shining directly on the RedRat3. Try covering the RedRat3 while capturing the signals.

When the RedRat3 is plugged in, it transfers firmware from external memory to the microcontroller's RAM. This process takes one to two seconds, during which time Windows XP is not sure what kind of device it is. Once the firmware has been transferred, the RedRat3 starts and XP then recognizes it correctly.