Thermal Heat Transfer and Heat Exchanger Model
Heat generation is always an issue caused by
lithium batteries charging or wireless chagrin
plate on the bottom of our product. Thus we
introduced a micro heat exchanger and
orientated tubing with corresponding two
razer blade fans to build up a nice performed
exhaust installed on the back to make sure all
electric devices which got put in by our
precious users were safe and sound.
Following data were gathered by carefully
simulated results on our product, from a
performance test based on a well-baffled 1
case for flowing, two-tubes pass micro heat
exchanger.
Assume the liquid oil we put inside the tubes
for cooling purposes of Phonestraint has
following listed physical properties: Specific
heat capacity coefficient as 2100 J/kgK if and
only if it went as fully developed turbulent
flow at steady states of performance with
entering rate of 0.1 kg/s. The inlet temperature
was about 340 Kelvins and left with 300
Kelvins at the outlet, which are very common
temperature during normal operation of
Phonestraint to prevent overheat customers’
devices but also, our product itself.
On the other hand, cold air were
brought by our carefully oriented
razer blade fans to drop the cooling
oil temperature down to a reliable
range as we said, around 300 Kelvin
degrees. Our team took the
assumption that the air was able to
enter the case with a relatively low
temperature around 290 Kelvin, then
left it at 300 Kelvin.
By iterative processes, we found out
that our initial assumptions were
incorrectly listed. Apparently, the
inlet temperature of cooling liquid
(oil) could possibly hit up to 353
Kelvin, but also at the same time,
our tubes and weightness limitation
could not afford that quick fluid
flow to build up and fully developed
turbulent flow.
Thus, we decided to drop down the
entering speed to around 0.62 kg/s
but increased inlet temperature up to
360 Kelvin to make sure that our
product would do normal operations
even during charging of both,
lithium battery and inside devices.
Tcin = 290; Now the outlet temperature is about 304
Tcout = 300; degrees of Kelvin, which is around 30.85
Thin = 340; degrees of Celsius and it is relatively good to
Thout = 300; be handling. But the real performance of it
mdot = 0.1; % kg/s. could possibly drop a small amount. However,
Cp = 2100; % J/kgK. still, 31 - 35 degrees of constantly convective
C_h = mdot * Cp; cooling fluid should be proper enough for
C_c = C_h * ((Thin - Thout)/(Tcout - Tcin)); constructing a nice and cool container’s
disp(C_c); environment, especially with charging on.

P = ((Thout- Thin/(Thout - Tcin));

R = C_h/C_c;
vnew = 0.62 * mdot;
LMTD = (((Thout - Thin)-(Tcout - Tcin))/log((Thout - Thin)/(Tcout - Tcin)));
dTmean = 0.94 * LMTD;
q = mdot * Cp * (Thin - Thout);
UA = q/dTmean;
UAnew = UA * (vnew)^(0.8);
NTU = UA/(vnew * Cp);
Tout = 360 - P * (360 - 290);
disp(Tout)
Actuator Selection Model
 Our team chose to stick on with electric linear
actuator instead of hydraulic cylinders, because
of the serval following reasons.

● Purchasing ELA normally would cost a lot less money than hydraulic
cylinders. And our manufacturing suggested price is only around 30-50
dollars depends on the future marketing. So reducing that cost is very
necessary.

● ELA is often consuming less energy than hydraulic cylinders, but with
greater energy efficiency since it was built for light duty. And the cap of our
product, it lifted, is only around 400-450 grams. So ELA is a better choice.

● ELA needs less regular maintenance than hydraulic cylinders due to how it
is constructed, which also made it a better choice for us.

● Hydraulic cylinders commonly contained a high horsepower motor installed

inside of it, which caused it very noisy. We want to reduce noise made by
Phonestraint as much as possible. Because who wants a really loud lock
box?

● ELA is self-contained units mounted where the force or motion is required

and connected to the system controller with a small diameter cable.
Hydraulic Systems mount the cylinder where the force or motion is
required and are connected by at least two hoses to a reservoir equipped
with a motor, pump and filters which are remotely positioned close to the
cylinder. All those need a lot of space for organizing.
Material’s Performance due to Cyclic Loading Model
As presented in the previous page, the top closing of Phonstraint is connected to the electric
linear actuator with a AISI 1045 steel triangular piece for stabilizing the entire process. The
reason why we put that top piece flexible sliding through the entire cap is because we put the
electric linear actuator perfectly enclosed inside of cavity built in for preventing mechanical
failure, and also extended life cycle of the linear actuator. But whatever method we used, we
have to face that the AISI 1045 steel part got into a unavoidable cyclic loading process as
shown in the bottom right corner. So we need to figure out the material property of AISI steel so
that we could possibly reduce accumulated energy from plastic shakedown.
Our entire team is very grateful for
ME-108 team provided experimental
data for testing cyclic loading
processes on AISI 1045 steel
specimen so that we could be able to
plotted Matlab results as we shown in
the previous page. Apparently, AISI
1045 steel would start to start
ratcheting at least around 40-45 kN
controlled load. Our calculations on
loading due to the top cap is only
about 3.92 Newtons cyclic loading
back and forth, which is far away
from the experimental result
mentioned above. All in all, by only
considering the AISI steel part, it
could potentially gain infinite life
time to Phonstraint’s mechanical
features.

But even considering the life time

cycles of electric linear actuators, it
still is able to hit up to 10 - 12 yrs.
Now, we just need to pay attentions to
electric components so that
Phonstraint can have best
performances
 Coding
Structures
Our team constructed a very brief coding for reaching out our initial introduced
features of the platform on locking, unlocking mechanism, just like what we show
in the previous page. The operation of it went pretty smooth until we were
thinking of bringing in extra functionalities such like weather / temperature
checker, stretch reminder, healthy daily plans etc,. Because, firstly, the
microcontroller needs to connect to internet so that it could solving such features
that we need. So we need a protocol to send data to/from ESP32 to remote host
computer. We did try to use our old friend message queuing telemetry transport to
do the communication between PC to microcontroller. But it did not work
properly. So we might need to figure out another better method to receive date
online, then sending them to the microcontroller, finally to the LCD display panel.

Besides those initial features we planned to do, we’re also facing technical issues
on writing codes for the rewarding system we asked for. Because we never got
satisfied with the performance of the coding we did. We think that simple logistics
of giving wording or graphic rewards won’t be power enough to stimulate users’
productivity, and we’re still considering a stronger method to do that.