Mindboards

I am having no success at getting the HT IRLink to communicate with the PF IR Receivers. Is there some trick I forgot about? I know it used to work, but it doesn't seem to at all now. I tried using something as simple as HTPFSingleOutputPWM(S2, PF_CHANNEL_1, PF_OUT_A, PF_PWM_FWD7); but the IR Receivers' lights didn't even flicker. And yes, I did remember to SetSensorLowspeed(S2);

I know the HT IRLink is transmitting, because I can see the IR with a camera. I also know that the PF IR Receiver is working, because it receives commands from the remote.

I will get out my IRLink and PF receiver for a quick test tonight but I'd be surprised if it doesn't work. But it is conceivable that I broke something somewhere along the line. Hopefully that is not the case.

John Hansen

I'm not sure what might be going wrong in your situation but I just tested my IRLink and the current test release of BricxCC/NBC/NXC and it worked great with my PF receiver/motors/battery box.

I ran the attached program.
John Hansen

Yeah, no response from that either. Again, I can see the IR from the LED. I guess I should call customer support.

I remember reading something about the different LEGO sets using different frequencies for the carry signal. Not sure if it makes any sense in this case.

You are probably thinking about the RCXs. Other than the RCX 2.0, all lego IR devices have been 38kHz AFAIK. The RCX 2.0 used a 76kHz TSOP (IR Receiver), and I think the FW allowed it to optionally modulate the IR LED at 76kHz. However, it was completely backwards and forwards compatible with the 38kHz RCXs.

I don't know of any revisions to the PF receivers, and I am currently using one receiver from years ago, that has always worked fine with the HT IR Link (the other receiver I got new from S@H less than 5 months ago).

I guess you double checked the channel on the receiver (all the way up) and tried it with brand new batteries in the battery box? Maybe you could post a picture of your test setup? Mine had two small motors attached to the receiver, channel selector at the top, battery box with fully charged nimhs, IRLink attached to port 1 pointed directly at the receiver about an inch away. Not sure what else could go wrong with the device still emitting IR and the receiver functional when used with a PF remote but it not responding to the IRLink device.

John Hansen

I have two systems set up for testing. One of them has 2 IR Receivers, on channels 1 and 2, and a 7.2v RC battery pack for power. The other has one receiver on channel 1, powered by the PF AA battery pack with some-what low batteries. Both of the systems respond properly with the hand-held PF remote, so I'm quite sure that it is the IR Link's fault. I tried with the IR Link anywhere from 0 to 10 cm away, pointed directly at the top of the PF IR Receiver.

I too am at a loss. Probably the only way to tell for sure what the problem is, would be to use a logic analyzer on an IR Diode or transistor, but I don't have a logic analyzer.

BTW, what range works for you? To ensure reliability, I have always had to keep it within about 8 cm for PF and RCX (I don't have IR trains). It did work up to 15cm, but it got patchy.