to be added or removed depending on the company implementing the ACS will need. There will be two structures crated in the Asset Control System database. One will be structured on users, their roles, payments, and their account info. This is seen figure 3.8.1.1, this will be crucial for allowing general access and being able to invoice the user later. The other structure will be more information on the device identification, location, time used, and how it can be used. This structure can be seen in figure 3.8.1.2. Figure 3.8.1.1 – Database structure for the User Figure 3.8.1.2 – Database Structure for the Device Identification 3.8.2 Device communication network The type of network topology used for the Asset Control System will determine the minimum requirements for each individual asset controlling device station. This section will review some of the possible networking configurations that will ultimately allow for the same finished product, but achieve it in very different ways. The following figures 3.8.2.1 and 3.8.2.2 show how these different topologies would work. 3.8.2.1 STAR Topology
It is okay to have the same name as long as there are different inputs or outputs. Pointers Supported Not available Exception Handling A call to a function is made when an exception is thrown Exceptions are dealt with during runtime and are enforced at that time as well Hardware access Superior to Java because it can run and compile directly with hardware without excess code required Access to hardware is not a direct path Goto method Not Available Goto functionality exists and allows you to use it to go to other places in the code Table 3.9.2.1 - Java vs C++
C1 Report Designer Royalty Free with many design options, easily constructed detailed reports with from a database of records. Must purchase ComponentOne with a package, ComponentOne Ultimate or ComponentOne Studio Enterprise Visual Studio Report Designer Multiple forms of data can be displayed, integrated with Visual Studios Must use Visual Studios to develop code Pentaho Report Designer Strong online community for support. Multiple of data accepted. Java Software Platform InetSoft Diverse design capabilities, multiple sub reports supported product with a support system that is not fully developed Table 6.3.5.2 Advantages and Disadvantages Report Designers In summary, there are many inexpensive options for report designers. If the Asset Control System’s code will be developed in Visual Studios it may be advantageous to utilize the report designer that is coupled with visual studio, the
OVSTRGBB1CR8 LED RGB Mouser $1.82 3 $5.46 TE Connectivity RT314A03 Mouser $2.81 3 $8.43 1554U2GY Enclosure Mouser $24.12 3 $72.36 Mean Well AC-DC 12V Jameco $11.49 3 $34.47 RFID Tags Amazon $1.50 5 $7.50 Various circuit components: resisors, capacitors, breadboard, etc. Mouser $15.00 1 $15.00 Total $385.85 Table 7.1.1 – Bill of Materials for ACS 7.2 PCB Vendor and Assembly This section and its subsequent subsections will investigate pcb manufacturers based on the design and quantity of pcb we will require for this project. It should be noted that we will order more than is necessary in order to have spares. This is a precautionary in the event of board failure or damage. Cost is the primary concern here and the only real measure for the various producers. Assembly of the components to the pcb boards will be done by the team members. We will have to determine the values of components needed for the circuits. Such values are related to the type of component commonly known as: Capacitors Resistor (ohms) Inductor (henry’s) Diode (properties of this component are constant ) Depending on the design will determine the number of resistors used to create each pcb. As well as capacitors, diodes and inductors. It is not believed that we will need transistors for the circuit but that may change as development continues. We will utilize the university facilities to assemble the boards with components. The assemblage of the unit devices will also be done in facilities on campus. We do not expect to use outside companies to assemble any of this project except for printing of the boards.
Figure 7.3.1 – Final coding with REST service calls 8 Project Prototype Testing 8.1 Hardware Test Environment The environment for testing the ACS and its hardware components will initially be done in the controlled environment of the S.M.A.R.T Lab or the Senior Design lab on UCF campus. These are lab environments so there should be a limited number of variables that will cause interference with our testing. Once initial testing has been complete and successful, we will want to rerun the tests in an environment that will be less controlled and more noisy, like that of a machine or wood shop. Each member will be testing separate components of the ACS to verify that accurate and, more importantly, consistent results are achieved. Once all components have proven to be consistently successful in both environments we will then begin full prototype testing. 8.2 Hardware Specific Testing 8.2.1 LCD/Touch screen Testing Objective: Correctly be able to use the 3.2” screen to not only view the embedded computer GUI but also interface with it. Supplies: 3.2 Inch TFT LCD Display Module Touch Screen Compatible HDMI monitor Raspberry Pi DC power supply Preparation: the compatible monitor make sure all drivers needed for the touch screen are installed.