RF troubles

Go To Last Post
53 posts / 0 new

Pages

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

The point is that you made it clear to me that you are an expert 'c' programmer, but you got the code to accomplish this task without telling anyone what you are up to.

You asked questions, that is good. But be forthcomming and be honest. As I said before, if you are so good at programming in 'c' this was a no brainer.

I finished the code..and trying to get a pcb done for it.

I feel bad for bringin our tiff up again, but I was reading through this thread in the euphoria of a project well done, and i saw those lines..

I was asked to learn a new uC platform in a 2 week deadline while making my first polished device. I was no seasoned atmel guru with a treasurey of errata knowledge. I was ground up learning and programming.

So how in the freak was my C coding skills called into question for not knowing esotierc things specific to atmel uC usart transmission timing issues??? I did notice it in the datasheet after the fact...but I was working by the seat of my pants...

And all that other stuff (the motor control) (the temp sensor) I researched the datasheets and got em working in a week..MYSELF!...My first week ever programming a mega 128 and like my second time ever working with atmel uC's...so when I said I had those other subsystems working and having trouble with usarts, you straight cut me off...said i stole code to make the other parts work...and hung up..

On other forums i frequent, what you called me was a script kiddie..

Well let me tell you...you were what my forums call a 1337 bast@$% (leet bastage)...I mean come on...belittleing me because i didnt have a firm grasp on a specific topic that i was in the process of learning?? Think about it..

The only reason I bring this up is that I want everone to realise were all in it together so no reason to be nasty and tune out.

But no worries. Thank you for calling me back. It made a young engineer with a deadline feel alittle better. And I hold no ill will. I mean under other circumstances I could see where you could have gotten mad....but I dont care how smart anyone is, 3 min of phone conversation dosent give anyone a solid bead on a situation(espically enough to blow up)

I just needed to vent alittle myself..

sorry :-/

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The code says manchester encoding, but what I'm seeing is pulse width encoding. Manchester encoding uses edges to encode the data, not pulse widths. Basically the transition in the middle of a bit cell determines a '1' or '0'.

for example:

01 = '1'
10 = '0'
or vice versa

RC5 ( the infrared remote control protocol) uses manchester encoding as does DALI lighting protocol.

See http://www.clearwater.com.au/rc5/
I'm sure I posted some code some time ago for RC5/DALI manchester receive for a M128 using the input capture.

Also, rather than use flags for the receive state - use a finite state machine - much easier to write and debug. If I had to build logic to receive this, I'd be using a FSM

Pages