3D Scanner MRD Project Report: Abstract-As We Look Throughout History, The Wealthy
3D Scanner MRD Project Report: Abstract-As We Look Throughout History, The Wealthy
Camera
We ended up using the raspberry pi camera module. It is 5MP
camera module is capable of 1080p video and still images and it
can be connecting directly to the raspberry Pi. Here is some data
Fig 3. Object scanned with one laser we get from the software of how long it takes to scan when we
run a scanner on different resolution of the camera. The size of
file is about 2MB-100MB depends on the resolution the user
chooses.
Resolution time
5 Megapixel( 2592 X 1944) 55mins
1.9Megapixel( 1600 X 1200) 10 mins
1.2Megapixel ( 1280 X 960 ) 8 mins
1.2Megapixel ( 1280 X 960 ) 4 mins
making sure that it compiled. Vangjel made all the necessary expected! However, this strategy would only work for the lasers
changes corresponding to our 3D scanner project, including the because we knew that they would receive 3.3V or 1V (high or
use of WiringPi to which helps the software control the low). The stepper motor, however, had three different
hardware. Vangjel has gotten the software to do a full scan and components that needed to be wired correctly (the enable pin,
output an STL file. He also implemented the team website. the direction pin, and the step pin). Because they received the
Chenkai expressed interest in building a user-friendly voltage they needed from the 12V power source, finding the
graphical interface with start and how to button to guide the user right combination of the three pins was not as simple.
to use the software. Chenkai was able to demonstrated the user Considering there are forty pins on the RP2, finding the correct
interface on LCD to displace connectivity between GUI and three would be near impossible and inefficient.
However, being low on options and ideas, Siyan and
raspberry pi 2.
Chenkai, started using the voltmeter anyway to try and locate
As a team, we all took part in calibrating the lasers in order to
the correct pins. Meanwhile, Vangjel started to look into
take accurate scans. This was the most time consuming part of
WiringPi. Upon his research, we figured out that WiringPi had
the project. Until the lasers were correctly aligned, and the its own set of pins, which mapped to certain pins on the RP2.
software matched the distances of the laser accurately, the scans The pins for each of the lasers mapped to the same pins we
we were taking were of poor quality. discovered by using the voltmeter. We reconnected the
turntable by following this mapping and finally got all the
Team communication hardware components to work, after many days of
All the team members produced a schedule of their available troubleshooting.
times. We met at least once every week. Occasionally, team
members will meet with one another to clarify any question or
receive help and support. There was constant communication
though Facebook group chat. Weekly team meetings were
scheduled for Thursday and Sunday and meetings with our
Advisor, Professor Tessier were on Wednesday morning.
During each team meeting with our advisor, we each start off
with an overview of each member’s accomplishments. We had
different interactions depend on what stage of the project we
were in, and also what to try to improve on before the next
meeting. If we had any problems or concerns, we would discuss
how to move forward. We collaborate to share information as
well as work on PowerPoint presentations using Google drive.
III. CHALLENGES
Although we accomplished a huge milestone by being able to
output the STL file, it wasn’t without some serious challenges.
When we read through the code, we located the section that
assigned hardware components to certain pins (see Figure 6).
This code was written to be used by the original RP, so we
modified the pin numbers in the code, by looking up the pin
layout for the RP2. We connected the lasers and turntable to the
numbers that corresponded. However when we ran the software,
neither the turn table nor the lasers were working. At first we
considered that there might be something wrong with the
physical hardware of our system. We reran the python code for
the lasers and turntable, and they both worked fine. Our next Fig 7. The object we tried scanning
thought was that we weren’t getting the 3.3V that we needed to
operate the lasers.
By taking the voltmeter to the pins we thought were correct,
we realized that the voltage at this pin was constantly low. After
many attempts at debugging on the software level, we took a
new approach. We ran the code, and used the voltmeter on all
the pins to see which ones would toggle from low to high. Once
we found the pins, we hooked up the lasers and tried running the
code again. This time the lasers were working to the level we
Team 8 Midway Design Review Report 6
Once the structure new structure was in place, and the lasers
were calibrated, our results dramatically improved. Fig 9 shows
our results after these changes.
VI. CONCLUSION
By demo day, Siyan has successfully assembled all necessary
hardware and tested them. Vangjel has complied Freelss
software and Chenkai has written the user interface. The
calibration process was done, and the quality of the scans
greatly improved. We also managed to output an STL file
generated by Freelss. With the user interface completed, not
only is everything more user friendly but the speed at which you
can access the software improved dramatically. It also made the
Fig 8. Output STL file at MDR pre calibration system end to end with the incorporation of the shoot button.
With the incorporation of the soldering board, the wiring
The other challenge was calibrating the lasers. During MDR became much cleaner and out of sight. This also means it is less
likely that a wire will accidentally be disconnected.
we managed to get our system working, however we didn’t have
Most importantly we were able to not only scan our objects,
our lasers calibrated. We tried scanning a small white out (Fig 7),
but managed to print them too! (See figure 10)
and the results we received are shown in figure 8. This showed
that the hardware is working together with the software and
producing raw data. We can see there are many points
connected together to create the whole STL file. The big gray
part on the right is the surface of the turntable. The part on the
left is the object being scan. Since the calibration is off, we
didn't successful getting the exact shape of the object. We also
need to find a better way to hold or stabilize the part when
scanning the object.
In order to fix this, we changed our physical structure. We
attach the turn table to the component that holds the camera and
lasers. By doing so, the turntable was always a fixed distance
and the lasers could be angled properly. This also prevented the
turn table from vibrating which cause the object we are trying to
scan from moving. Fig 10. The object on the left is the original and the object on the
right is the print out of our scan.
REFERENCES
Fig 9. The scan once the calibration was done
Team 8 Midway Design Review Report 7