Desperate for a bit of feedback here.....

[christoph]

Benj or team member or anyone.....

Is there any reason with this VERY simple circuit and my having 'checked it to death' for over a week now hardware-wise , why it simulates perfectly but doesn't work. I have noticed in a couple of posts that this can happen and there has ALWAYS been an explanation or a way round it. Would it be possible for you or someone on the Matrix team to suggest something 'cos I been stuck for the last week on this and need to find a way round it or an alternative approach....

Does any one know why my 'No 1 first up alarm' works perfectly in simulation but not in hardware??

I have modified Bens original RX - attached, so that it 'holds' the very first signal it sees regardless of any different ones following. (see the attachments below for reference).

Can you see what is wrong and how to achieve that?. I have checked wiring, supply and chips and all is OK in those respects.

Cheers,

Chris

[Benj]

Hi Chris,

Sorry for the delay in replying, its all very hectic at the moment what with getting everything ready for v5 AVR, ARM and dsPIC.

Do you need the connection points in your program? I don't really see why they are required.

Also might be worth only calling the output_to_leds macro when you have received the second byte rather then after the first and again after the second.

Maybe also run a quick 1 second flasher test to confirm your clock speed on the hardware is correct and matches the Flowcode settings.

[christoph]

Many thanks Benj,

Sorry to have badgered you cos I know you lads are busy but I have got the rest all sorted and this is the only problem I have left but couldn't sort out.

I can work with that and apply to another two of my variants which also simulate but wont run - does look like a timing issue therefore!

Thanks for your prompt reply,

Cheers,

Chris