This is a duplicate of these three posts.
... and it's arguable that this post is essentially a duplicate as well. It's just that it's more incomplete than the others.
Pick one thread to keep. If you want to update a post, you should be able to edit it, that way you don't need to open another.
Post formatted code instead of pictures of code. Even though nobody is going to run the code in whole without the hardware, it's often helpful to run parts of it. After all, the purpose of having a computer is so that the programmer doesn't have to execute code in their head and risk all the potential mistakes that might involve. Observing outcomes is more certain than predicting outcomes.
You haven't asked a question. You've requested a complete explanation of a task involving hardware that few people have or will be familiar with. You shouldn't be surprised if people are unfamilar, and you shouldn't be surprised that the people who are familiar aren't going to spend an hour writing a walkthrough of code without knowing whether you're familiar enough with the subject to understand their explanation. This is why questions should be specific and one should be willing to describe their own efforts to answer their questions.
I am not familiar with this hardware or its use.
