ROBOT.LK

As I said in my last post, here is my 2nd post. No much words, just some images

First of all, you have to learn about, SIRC Protocol Below two images were created from my own data. Below is the mikroC code, I used...
(I switched to mikroC from hitechC, because of the lack of information and tutorial ) Video
[media]http://www.youtube.com/watch?v=W1QXHrYTnL0[/media]

Superb... This is a lesson to everyone

have you modeled your protocol with state machine model before start coding ?

However nice tutorial Risk. Teach me bro.

However , do not add labels like this when you drawing diagrams.



Instead the professional way to do this is to use bellow format ,
you could add your copyright info at the bottom boxes.


And I have revived your diagram too, Nothing much to fix I could see from here on it.
The only thing that I see is it's better to add a 10uF 10V capacitor near the PIC IC.
Because there may be current spikes when it receiving data. And your IR sensor not
just a sensor, so I think you are right we don't need a voltage follower circuit or schematic
trigger there.



and this is a question for you,
What software you used to draw the waveforms , I have asked this question on meta.electronics.stackexchange.com/
and according to them they use inkspace. Matlab is also a good choice if you got the money.I'm curious to know which
software is you using.
http://meta.electronics.stackexchange.c ... -waveforms

Thanks.
Good luck Risk , keep reading the source code and keep writing blogs.

SemiconductorCat wrote:do not add labels like this when you drawing diagrams.

Sorry for poor diagram. I just edited a simple diagram which was in my MCU downloads directory . Didn't thought to draw a professional diagram.

SemiconductorCat wrote: What software you used to draw the waveforms

No, I didn't draw this. It is the output of PICkit2's logic tool.

Thank you.

Sorry for poor diagram. I just edited a simple diagram which was in my MCU downloads directory . Didn't thought to draw a professional diagram.

No risk , I'm not ask you to say me sorry.
It's not the point, the point is this. See: http://electronics.stackexchange.com/qu ... schematics

Read the olin guidline.When it comes to an engineering drawing, it should be clear and neat. So other engineers who read
it will save their time too. You may think it's a simple thing. But avoid it is more better.
Reason why:

When you give someone a sloppy schematic (or any other work from you), the first thing they're going to think is "What a jerk". Everything else they think of you and your work will be colored by that initial impression. Don't be that loser.

--Olin lanthrop.

[/quote]

There are no rules here. And I'm not the admin. But why we need to be that loser?

There are no rules here. And I'm not the admin. But why we need to be that loser?

I'm the admin here and there is only one rule. Just respect everyone, that's all

Rksk (it's not Risk Sandun BTW ) is doing very well with electronic and embedded. And as Semi stated, I agree it would be great to use a nice schematic tool which will produce a clear diagram for everyone's interest.

Here I have started a topic where you can contribute as well.
Best Online circuit diagram tools for free