Okay,
The pic12 acts as a transmitter with one or multiple recipients. The rc5 protocol would work okay - the Manchester encoder should work okay - with some tweaks to the timing.
I'll find a transmitter and play tomorrow. See
https://flowcode.co.uk/forums/viewtopic.php?t=2944
The rc5 uses a very ...

That's maybe two problems then - can you try the transmitter that came with the receiver boards?

I'm using the same board ky-022 from a pack of sensors.

If you are using the rc5 component to transmit - the data out might be wrong?

Martin

I managed to find a lot of stuff for the NEC format - less for the RC5 :-(

However - having just done a Manchester format decoder for the wireless comms - I think I can pull the bits together fairly easily.

Couple of things...

Did you manage to get RC5_Receive to work?
Which MCU are you aiming ...

Hi Enrique,

Jan and I managed to get it to work very reliably on AVR and PIC (which didn't support an either edge interrupt). It's not quite the same as a component (no simulation) - but it might do the trick for you?

I'll try and find the latest version / topic....

Martin

Using the Rc5_Receive from the above link - the sensor does receive data correctly (not whilst using the component!)

Somewhere there is a better version that uses a pin change interrupt not the busy_wait as in this code.

There was a lot of discussion with Jan about this...

Something odd - if I do Rx available - the component toggles the Rx pin at 300us intervals.

If I set Tx available - then the pin behaves as expected (held high) and I can see the signal received (on a logic analyser) if I press a button on the control....

I found one of the sensors in the toybox and a small (hopefully RC5) transmitter.

First attempt - failed (error in Timer function).

Compiled the example which seems very similar (except it has a TimerCallback - that does nothing) - and it doesn't work (nothing output :-( )

Added a TimerCallback ...

The 'duplicated' by the compiler warning means that there are multiple instances of the code (the function Initialise_states) generated - which will give larger code. It 'shouldn't' (famous last words) cause an issue - but looks to be an issue with the component. The source isn't currently available ...

In STATE:

You have
FLASH = 0
LOOP count 7 TIMES using FLASH
...
FLASH = FLASH + 1

If you count using a variable - you don't need to set it to 0 (it does (for(flash = 0; flash < 7; flash++) { ... )

The increment means that the flash won't occur 7 times - so would be best removed (and the loop ...

The messages are warnings (not errors) - but are indication of something wrong in the code.

The problem seems to be in DIGIT_RC5 where you have (for one instance) 'if command < 9999' - however command is a byte (0..255) - so the comparison may give incorrect results (similarly with if command < 999 ...