Good evening all,
Background:
I am final year Electrical & Electronic engineering student currently in the process of completing my undergraduate thesis. The thesis topic consists of making a low-cost, non-intrusive, battery powered electronic device that is small enough to fit in the punt (the under dome) of a wine bottle. This electronic device will be used to track the storage conditions (temperature, humidity, and ambient light) of luxury wine. A user-interface will be used to display the storage conditions. The aim of this device is to give confidence to the buyer that a wine has not been spoilt when bought at auction, wine retailers ect.
I am currently busy with the hardware design, and I’ve hit a roadblock. I feel as if I’m heading in the total wrong direction. Any guidance/advice will be appreciated. I have chosen to use the DF robot beetle (https://www.dfrobot.com/product-1075.html) as the micro-controlling unit (MCU). The 5V MCU will act as the master and communicate with sensors (which will act as slaves) via I2C. The sensors which I’ve chosen are:
The 9V battery will be connected to low dropout voltage 5V regulator to power the microcontroller. Voltage division will then be used to step down the 5V rail to 3.3V for the sensors. A PCB will be designed using Altium and housing with Autodesk inventor. UART will be used to communicate to the user-interface, or a removable SD card will be implemented on the PCB if there is enough space.
The questions I have are:
Any help/suggestions will be greatly appreciated Sorry for the long read!
Background:
I am final year Electrical & Electronic engineering student currently in the process of completing my undergraduate thesis. The thesis topic consists of making a low-cost, non-intrusive, battery powered electronic device that is small enough to fit in the punt (the under dome) of a wine bottle. This electronic device will be used to track the storage conditions (temperature, humidity, and ambient light) of luxury wine. A user-interface will be used to display the storage conditions. The aim of this device is to give confidence to the buyer that a wine has not been spoilt when bought at auction, wine retailers ect.
I am currently busy with the hardware design, and I’ve hit a roadblock. I feel as if I’m heading in the total wrong direction. Any guidance/advice will be appreciated. I have chosen to use the DF robot beetle (https://www.dfrobot.com/product-1075.html) as the micro-controlling unit (MCU). The 5V MCU will act as the master and communicate with sensors (which will act as slaves) via I2C. The sensors which I’ve chosen are:
- Contactless infrared temperature sensor - https://neotronics.co.za/index.php?route=product/product&product_id=608 which will act as the main temperature sensor and will be pointed upwards through the bottle from 3D printed housing.
- BH1750FVI digital ambient light sensor - https://www.elechouse.com/elechouse/images/product/Digital light Sensor/bh1750fvi-e.pdf
- SHT3x-DIS Humidity and temperature sensor - https://docs.rs-online.com/c777/0900766b816bf6ab.pdf the second temperature sensor will act as a backup and ensure the main sensor is operating correctly.
The 9V battery will be connected to low dropout voltage 5V regulator to power the microcontroller. Voltage division will then be used to step down the 5V rail to 3.3V for the sensors. A PCB will be designed using Altium and housing with Autodesk inventor. UART will be used to communicate to the user-interface, or a removable SD card will be implemented on the PCB if there is enough space.
The questions I have are:
- The battery solution feels inefficient, is there a better approach to solve this solution? Will making use of an Arduino Nano (a much larger board) which has an input voltage of 7-12V be a better solution? This MCU also offers both 5V and 3.3V pins. Will the battery be able to last as long as the beetle?
- How can I go about calculating the total power dissipation of the system which can then be used to calculate the potential battery life?
- Is there a totally different approach to take? An intrusive design is on the cards but the objective for now is keep the design non-intrusive.
Any help/suggestions will be greatly appreciated Sorry for the long read!
Attachments
-
748.1 KB Views: 0
-
386.3 KB Views: 1
-
4.6 MB Views: 3
-
1.8 MB Views: 0
-
919.8 KB Views: 0
-
999.6 KB Views: 0