Author: mcbasse

Day 9: Wednesday – Connecting dots…

mcbasseLeave a comment

It’s time to wrap things up and get the subfeatures working together. This has proven to require a lot of thinking, coding and designing. The goal since day 1 has been to have a functioning prototype by tomorrow leaving the report, nice to haves and exam preparation for the remaining days.

The initial test of the day was to get stepper and waterpump working to dose flour and water into the mixing container. With a few adjustments we found a stepper speed optimized for dosing flour. In this test we ran into a new problem of preventing uncontrolled spill of flour when demounting the flour container. This was solved in plenum as we went through this test.

Todays jobs were distributed among the members of the group:

  • Coding screen text and pictures
  • Connecting motors and sensors (to a functioning circuit and main code)
  • Mechanical features … (TB explained)
  • Fine tuning Node Red interface with ‘nice to haves’ and nodeMCU/Arduino connectivity.

OLED display (Overly Lousy and Evil Display

Coding text to OLED has proven to be harder than anticipated. Some faulty code keeps disrupting the screen display when printing messages in several lines to the screen. So only 1/3 of the screen could show text, which was highly frustrating. We had no problems printing an image as an xbm file, so we planned on uploading an image with text when we needed multiple lines and then we made a drawing for every mode.

Later in the day we finally had a break through and found the error in the code, so now it works as it should. Then we tried connecting a SR-HC 4 ultrasonic sensor to the circuit and made a code which displays on the OLED when a refill of flour or water is needed.

Node RED

Today we changed some details in NodeRED. The link to the dashboard will now take you to a page with a button, and clicking this button will either take you to the sign up page or the main dashboard if you already have signed up. We also managed to clear the different inputs on the dashboard after you save the information as a flow or global variable. We also added a count down function which counts down the amount of days left on travel or baking mode. To make sure that the user will not stop the mode by mistake, we added a pop up window, which asks if you are sure you want to stop the current mode. If you try to overwrite the travel mode with baking mode or vice versa, you will get a pop up window telling you that this is not possible, because of the current mode. To change mode you would have to stop the current mode and then activate the new mode. 

The lids

We laser cut the different part of the lid for the containers today. The lid is made from 5 acrylic parts. The first two parts are made to fit the ultrasonic sensor, and the tube. One of the these part have a space to mount a hinge. There also are two plates to lay around the tube and the wires, with at hole to get the wires out. At last we have the top part of the lid. 

Day 1: Thursday – Auger screw prototyping

mcbasseLeave a comment

Today, the first day of 3 week course in mechatronics we have already begun prototyping. Essential to the machine is dosage of flour. We’ve brainstormed several ideas and a simple, versatile solution to control dosage amount is accomblished with the auger screw. This method of controlling dry powder is already well known and established in many machines.

We have to construct our own and have it accostumed to the material attributes of flour. this will require propor testing. From thingyverse we have downloaded an Auger screw as STL file. We modified the file to our liking and begun printing.

Project 3 – FOOD

mcbasseLeave a comment

The subjekt “FOOD” was presented to the mechatronics team. Initially, the group had to adjust to the new topic and the divergent process should be launched. Loosely and firmly, the talk crossed the table with crazy ideas.

Aksel and Sebastian go on their way to Skylab Food and get in touch with Ruberto early. He is open, helpful and comes with some key points to the topic: It is important to find a new topic. A new way of doing things. In the world, there are many alternative ways of processing foodstuffs, which are considered either exclusive, industrial processes or consumed. New technologies need to find their way to the everyday kitchen. In Skylab FOOD, we were shown technologies to cook without heating and an ultrasonic device to evaporate liquid without heating. Common to the technologies is that they have no everyday use – and are therefore an example of what has a potential in the consumer market.

POWER to the Group

We decided to go on an excursion to get new inputs. In power, we asked the staff for new products and technologies within food. First we were shown new product releases, for example a m-hood that is on the table. Next, the group searched the other department’s stores, which offered:

Various coffee machines, blenders, ergonomics, visual design user-friendliness and more. Many products are conventional, as one expects them. Few new products dominate the market, just new models and new designs. In fact, the visit could help us find possible categories, but it is difficult to pinpoint the concrete input.

The project must be based on a user group and an existing problem field. This is the basis and must above all be applied. We returned to skylab and wrapped up the day, by assigning a hometask: Everyone will look into and present an idea that we can work on in the 3-week period.

Buzzer completion = Success

mcbasseLeave a comment

A code has been completed which outputs little custom melodies to the Piezo buzzer (passive).

In the process of determining which melodies was relevant, we also discussed a lot of overall functions about the locker so that the product produces clear feedback to the user and acts accordingly. As result we came to 5 unique sounds for 5 unique scenarios:

“SUCCESS” = When the closet has been succesfully accessed via email pincode, an anthem plays.

“LOCKED” = When the locker has been locked, a short confirmation tone will be played.

“FAILED” = If accessing the locker fails (wrong password) or timer runs out when the door is open, a failed tone plays to alert the user.

“PING” = When the locker has been open for 30 seconds, a reminder will alert the user that the locker is still open.

“KIM POSSIBLE” = When the rental time has run out (after 48 hours) the Kim Possible signature plays, hopefully to deter any nearby thieves; as thieves fear Kim Possible. It’s common knowledge.

The code was initially set up from code originating from:
https://pastebin.com/jdhs9LXB

The melodies were created and customised within the sketch. Rearrangements and shortening made it ready for implementing it in the main code.

NodeRed and MQTT Connect – week 4

mcbasseLeave a comment

NodeRed is an online coding platform accessed via Cloud IBM (BlueMix). The coding form is to connect the wanted node functions and specify their behavior via programming and various inputs ( such as perhaps Topic, Passcode and Port for MQTT input/output ). Initially NodeRed has been programmed with two functioning “button messages”, so that when they’re clicked on the UI message strings are sent to the MQTT.

Our nodeMCU is subscribed to the Topic and will receive the strings. Now our web client will show the text current on the OLED, now you can know from our web client is the lock is lock or not.

We also set up the web client with to form so it remembers the Email for the confirmation and remember the password. The next step is to set up NodeRed so it remember the password and check the password, when you need to unlock the lock.

Flow model of the communication between the MQTT broker, the NodeRed and the NodeMCU


The fuzz about the buzz – week 2

mcbasseLeave a comment

Initially I examined the buzzer on my own. The passive buzzer would make it possible to generate pitching noises while the active buzzer would have a constant tone. With PWM tonegeneration and pitching is somewhat possible but the end result is not as clear. The Active buzzer does show to be louder and it is much easier to program.

The base-function of the active buzzer is easy. Plug it to power and it will generate it’s own oscillating signal. It can now be manipulated with Arduino builtin tone. With the frequency [Hz] and an assigned duration it’s possible to compose melodies. With an appropriate setup we can now proceed to write melodies.