Okay - is the IR remote RC5 or NEC (which is more common)?

The transmitter program has 50% duty on the signal - which might be better reduced slightly (overloads the gain control on the receiver)?

Hope you get a good sleep!

The command line option if you want the PICKit to power the board is -W5.0 or try /W which sets the voltage.


Martin

What MCU do you want to use for transmit and receive?

That's odd - I see digits 3 and 4 use pins 2 and 3 as their CC pins. I would expect that the chips handles this invisibly - though all will be revealed.

I'm glad I don't have to do the wiring

Martin

Also note - I power the receiver from pins 4 and 5 - $D4 =1 , $D5 = 0.

... I couldn't get the IR transmission to work using the PWM component :-( Looking at the trace on the scope - the pulses had 'gaps' - each high pulse was made up of several short 38kHz lumps with a space between them.

I added a small lump of C to enable the PWM from TMR0 and some C - to enable ...

... and of course the PWM duty is 0..255 (not %) - so adjusting the duty cycle does work as expected...

It will be interesting to hear how it goes.

There are a few changes needed if you use a PIC, as I didn't have the part to test, I used an Arduino (it was the set-up at present) - if you have issues I'll try and help.

It's not a component as such - I'd probably need some matrix magic to make the ...

My first attempt at generating with a 38kHz carrier.

I used the PWM component - and toggle the PWM pin (in this case d6) and my current output pin on and off at the same time. The duty on the PWM pin looks a bit 'low' - but setdutycycle doesn't seem to alter this?

LabNation_Screenshot59.png

I ...

Yes, I'm in the UK. I can PM you my address...

Martin