I chose 1 to be my low mapped value, and 20 to be the high mapped value. Since Tinkercad can't do much with values this large, the first step is to translate them to a usable range. In the example ( project link) there are items 01 through 05, with values ranging from 1,000 to 16,000. I created an example in Codeblocks to fiddle with values, and give myself a reference to check back with. The map function takes a range of input values, and re-maps them to a user specific range of numbers. I use it in just about every sketch to translate raw sensor values to something easier to understand. One of my favorite functions from Arduino is map(). In each of the steps below, you'll see a clickable " project link" that links out to the unique project(s) showcased in that step. In the following steps, I'll go into more depth on what each of these element represent, and how I went about visualizing them (in both simple and complex manners). I ended up visualizing: planet size and orbit distance (both measured in kilometer), and for orbits I included eccentricity and inclination. One example of something I decided not to include was a planets obliquity to orbit, which would show the angle a planets axis of rotation is off from it's orbit ( read more here). I've seen many cool example of the solar system created with Tinkercad's 3D editor, and it got me wondering how accurately I could scale down the whole solar system.Īs I trudged through, I realized there were a lot of different elements that would need to be scaled, and quickly realized that I would need to decide what elements were most important and which I would skip. I enjoy looking at scaled models of the solar system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |