Anas:

I previously pointed out that some code that you linked to or posted here was really really bad. Recall this posting: http://www.8052.com/forum/read/178325 where in a reply you seemed to actually agree with me.

Do note that code posted into the code library is not vetted for quality. A contributor simply fills out a simple web form and then it later magically appears in the code library page listing. Just because you downloaded it from this site does not give it the Good Housekeeping seal of approval or quality.

You appear to be handicapped by not being proficient at writing assembly language code for an 8051 type of MCU. Finding code that you try to cut and paste together is the worst way to try to learn how to get what you need. You would be far far better off using a different approach. Here are some your options:

1) Start simple and build up your application one step at a time whilst doing the due diligence to learn what you are doing at each step. Simple means starting with something like turning an LED on and off. Progress to learning how to input a switch state. Grow from there. Write all your own code along the way so you understand how every instruction works. If you get into a bind with something you do not understand post the code snippet here and you will get help. (You will likely have to be able to enunciate the problem clearly and explain what is going wrong). Read data sheets at every step of the way. It is fine to look at other folks code snippets but use that only as a way to understand how they work and then re-apply the concepts to your own code.

1.5) Learn to leverage the MCU at things that compute engines are good at doing. If you find yourself making code that seems like you are doing the same simple minded thing over and over then be assured that there IS a BETTER way. The code to which you refer in this thread is fraught with the repetitive problem.

2) Partner with someone that has more direct experience in this area and collaborate 1::1 to find the solution.

3) Purchase ready made hardware that has the intrinsic capabilities you need and comes with decent documentation so that you can figure out how to use it.

4) Write up a decent specification for what you want and hire a consultant to write the code for you. This can even extend to having someone design the hardware as well. When finding a consultant to work with do some research to make sure you link up with the correct resource. Get recommendations, look at past work, meet with the person and study their nature to access if you are talking to a reasonable person and not someone who is a good bull manure artist.

Feel free to post any questions you may have.

Michael Karas