Sofie Havegeer & Stephanie Van Haecke

The guide to the bright side of the night.

2

CONTENTS INTRODUCTION

Introduction ......................................................................................................................................................... 4

Project .................................................................................................................................................................. 5

EXPLORATION

Quad Ind.—Modular ............................................................................................................................................ 8

Wishes and commands ..................................................................................................................................... 11

Inspiration ........................................................................................................................................................... 12

IDEA GENERATION, SELECTION & CONCEPT FINALISATION

Brainstorm .......................................................................................................................................................... 14

Concept 1 .............................................................................................................................................................. 15

Concept 2 ............................................................................................................................................................. 16

Concept 3 ............................................................................................................................................................. 17

Idea selection ...................................................................................................................................................... 18

Concept finalisation ........................................................................................................................................... 19

Quad Ind.—Modular ............................................................................................................................................ 21

Competitiors ........................................................................................................................................................ 22

Goals ...................................................................................................................................................................... 23

Deadlines & Planning ......................................................................................................................................... 24

ENGINEERING

Technical approach ........................................................................................................................... 27

Arduino test 1 ...................................................................................................................................... 28

Arduino test 2 ..................................................................................................................................... 29

Arduino test 3 ..................................................................................................................................... 30

Proximity—Capacitive sensor ........................................................................................................ 31

Wireless connection—XBEE ............................................................................................................. 32

Power supply ...................................................................................................................................... 34

Quad Ind.’s contribution ................................................................................................................... 25

RESULT - CAARS

Result .................................................................................................................................................... 37

Final code ............................................................................................................................................. 40

Electronics .......................................................................................................................................... 41

Assembly .............................................................................................................................................. 45

Cost ....................................................................................................................................................... 46

Interaction chart ............................................................................................................................... 47

Product identity ................................................................................................................................. 49

Packing ................................................................................................................................................. 50

CONCLUSION & REFLECTION

Past & Future ..................................................................................................................................... 52

Acknowledgments .............................................................................................................................. 54

3

INTRODUCTION

4

INTRODUCTION Our mechatronics project started with the mission statement: ‘ Demonstrator light integration—Quad Ind. & Modular’.

This formulation led to confusion as well as great opportunities...

The first thing we had to do was: make a gigantic brainstorm in wich no boundaries were considered. Second, we had to consult Quad Ind. and Modular to discover what they mean with this tiny line of

instruction. During this first information and exploration phase, the third thing on the list was: come up with some ideas that match all the wishes and commands of all stakeholders.

Before we could properly start, we had to know something about what Quad Ind. or Modular could mean. So we looked up the internet, catalogues, brochures, etc. to find out more about a demonstrator

or what could be meant by it. During this preparation phase we investigated Quad Ind. and Modular to the bottom . It is important to know who you are dealing with...

So, in the next pages you’ll find out everything about Quad Ind. and Modular; who they are, what they do, their product range , etc. Next, some moodboards and inspirational items are showed. Those views

indicate the depth of the little tub we had to dive in. After this, the first brainstorms should show what we first thought about. Off course the wishes and requirements of the two participating companies

will be listed too, while this section will be ended with the concept conclusion. We hope you’ll enjoy this first part of the ride, because the second one will be a tiny bit more harsh.

Once we decided what we wanted to do during the project we had to define the goals. What should we have realized at the end of the semester? Besides this, we had a concept, but we didn’t know yet

what properties, functions and other specifications our product would and should have. So some time to think about this was required. Anyway, those bumps in the road were easily taken and pretty

fast we could move on to the real job.

In the third part of the project, we started programming Arduino. A short overview of what tests and setups we tried, will be given. In this part Quad Ind. has proven to really support the idea. They came

up with some technologies, which we were able to use during the prototyping off our concept.

In a short, fourth segment in this record, we’ll summarize the steps required to produce our product. Let’s say, ‘The Sofie’s and Stephanie’s manual to the bright side of the night’...The components

needed, the programming of arduino, the build-up of the PCB’s and all other necessary production steps will be explained.

The last part of this writing will be dedicated to special remarks, further planning and some words to thank the helping hands.

We hope we can convince you to let you guide by Caars.

Sofie & Stephanie

5

INTRODUCTION—PROJECT

Mission Statement

‘Demonstrator light integration—Quad Ind. & Modular’.

This was all we got at the start of the project. Obviously

some problem definition, border provision and some

additional explanation were needed.

We started with our own problem definition while the

first meeting with Quad Ind. and Modular was arranged.

One way or another, it was clear that in this project the

main goal was to learn how to design interactions by

the use of sensors. Indeed, the TIII project stimulates

young designers to think about how we can connect, by

the use of electronics, old problems with new solutions.

6

Mission Statement according to Quad Ind. & Modular

The moment we got our challenge, we didn’t have any clue about what was expected of us. After our own

first problem definition, we met the two supporting companies to see whether our noses pointed the same

direction.

Their wishes and commands, strings and requirements were simple...

DO YOUR THING

MAKE IT SOMETHING WHERE ALL OF US CAN BE PROUD OF

SHOW AND SHINE

The only thing they both had in mind, was creating a new interaction linked to both industries.

INTRODUCTION—PROJECT

7

EXPLORATION

8

EXPLORATION—QUAD IND. After the first 2 weeks we could meet Quad Ind. and Modular.

Quad Industries is a Belgian company that produces everything that has to do with interfaces.

9

EXPLORATION—MODULAR

Modular is also a Belgian company, but makes part of the lighting industry. Modular is very known for their

quirky design, innovative technology and pricey quality. Conclusion this company is famous and notorious.

10

EXPLORATION—QUAD IND.—MODULAR

The challenge formulated by Quad Ind. was to develop ‘something’ in which their interfaces, in combination with light, would

‘shake up’ their current market and clients. In this way that they are surprised that Quad Ind. also can do something new,

something different. It doesn’t always have to be that stiff, simple, etc. Quad Ind. is open for some adventure and wants to show

that they are not a sleeping company, but constantly busy exploring new technologies on a new scope.

Also Modular said to us that the current formulation of the challenge wasn’t strict. They just want to be involved in ‘someth ing’

new. For such a company, it’s good to know and see how young designers see the lighting of tomorrow. Often they stand to

close to the current lighting technologies, which lead to little leaps and wholes in ‘the meeting’ of the client’s desires.

Conclusion, both companies think we should do our own thing. No limitations coming from them. They just want to give us their

approval and help when we come up with some concepts.

11

EXPLORATION—Wishes and commands Quad Ind.

Try to use interfaces we can provide you with.

The product or interaction should be something that we actually could use or add to our product range.

The manner in which people interact with the new product, tool, or whatever you come up with, is a priority.

If what you have in mind is not too exotic, Quad Ind. can help with the development of proper sensors.

Try to do something people do not expect of Quad Ind.

Make it produceable and reproduceable.

If possible, try to come up with a technology we can use in the future too.

Modular

You know the ‘typical’ design of Modular, try to maintain this in the product.

Make it fit in the product range.

Create a new interaction with light.

Try to design/develop something with white light. This is often ‘forgotten’ but very useful.

Keep in mind our market. We focus on the layer of the society that is willing to pay for useful quality design.

Anyway, the things mentioned above are some guidelines. Still we had ‘carte blanche’.

12

EXPLORATION—INSPIRATION

13

IDEA GENERATION, SELECTION &

CONCEPT FINALISATION

14

IDEA GENERATION—BRAINSTORM

15

IDEA GENERATION—CONCEPT 1

The first concept, the ‘Pinch pillow’, was formed out of the feeling

that people need something that can calm them down during a

dispute. The ‘Pinch pillow‘ is ment to be some kind of pillow that

can ‘sense’ stress, anger, tension, etc.

During a fight there has to be something that can distract the

attention of those who are discussing something. The ‘Pinch

pillow’ lights up and moves when the tension, more precise, the

volume during a conversation, rises. When the pinch pillow is fully

active the attention of the people will be attracted to it. To calm

the pillow down, the volume will have to decrease. On the other

hand, the ‘Pinch pillow’ could be made into some kind of, literally,

punchball. When a dispute is becoming to heavy, the fighters could

decide to let their anger by giving some punches on the ball. Such

a relief...

16

IDEA GENERATION—CONCEPT 2

‘Beat me’ is some kind of device which you wear

while you’re making a run. The idea is to push your

limits in beating yourself. The device would be able

to track and memorize your route. When you’re

running your second lap, the previous lap will be

projected. It would be nice if the projection could

be a print of feet, so you get the idea you’re

running against you’re own...feet.

17

IDEA GENERATION—CONCEPT 3 The last concept grew out of the need of light during the night.

Imagine:

During the night, you have to pee, or you want something small to eat or drink... You don’t

want to turn on your light, because you’re afraid you’ll waken everyone in the house. So

you have to sneak around in your own place. With your hand you palpate the wall, just to

get an indication of where you are, which door is closed, etc.

Wouldn’t it be practical to have some kind of light to help you around in the dark? A

flashlight...of course, but not really fancy, is it?

To solve this, we came up with something new. We discoverd there are some more

bedroom problems during the night that can be solved...Of course we can’t solve them all...

But for sure, you’ll recognize the problem in which you are touching around your little

cabinet in search of the button to turn your light on...

The third concept, right now known as the ‘Follow-me’, will be a night guide which can

interact with the hand and duplicate of itself. The idea is that you have a device in your

room and some other similar devices around the house.

As soon as your hand moves towards the device, the more it will light up. Then, take it with

you to go to the kitchen or bathroom and discover how it lightens your path. When you

approach your destination, the device put there, will lighten up accordingly to the distance

between the two devices.

As soon as you return to your bedroom, the light in the kitchen or bathroom will fade out.

From the moment you put your own device into it’s docking station and the distance

between your hand and the device is large enough, it will fade out as well.

18

IDEA SELECTION

After the brainstorming and interim presentation, we chose to work with the third concept. The concept, then named, ‘FOLLOW ME’, was selected above ‘BEAT ME’

or ‘PINCH PILLOW’, because of the actual problem-solving approach, usability, assumed compactness and realisability within the given time.

19

CONCEPT FINALISATION In the first phase of the concept, it wasn’t clear yet how it should look like, what functions it would have,

which specialties there would be, etc.. To come to a solution and answer, we brainstormed again about

some topics.

Little detail, in this phase we didn’t want to lose to much time and start prototyping as soon as possible.

We realised that a lot of functions and so, would depend on the ability to program them. So, during the

brainstorms we gathered some ideas of what the device could, should and has to do. We didn’t translate

those requirements in ‘musts’, but we decided to wait and see for what we are capable of when we

started to program with Arduino.

This way of thinking, designing and developing was maintained, because we realised that in this course it

was more important to deliver a working prototype rather than a great concept.

20

CONCEPT FINALISATION

21

CONCEPT FINALISATION—QUAD IND.—MODULAR

Once the concept was concrete, we returned to Quad Ind. and Modular. They have the knowledge,

experience, feeling and much more about how a concept can do it out there.

Quad Ind. really liked the concept of ‘portable light’. The combination of a ‘need’ (a light guide during

the night), an old solution (remember the oldfashioned candle holders) and today’s technology made

our concept strong, they believed.

Modular was also fond of it because they believed it actually could be marketed. ‘’It is a new concept/

product that can be a solution for many different situations. Not only in domestic scenarios, like little

childeren who have to go tinkle, but it also can be a solution for those who frequently have to stay in a

hotel and aren’t familiar with the switches yet’’.

22

CONCEPT FINALISATION—COMPETITORS

23

CONCEPT FINALISATION—GOALS

Goals

We had a global idea of what our device should be able to do. So, we put up a list with requirements, us being

aware of our capabilities.

1) We want that the ‘lightball’ lights up when a hand approaches it.

2) The light should become stronger in proportion to the hand coming closer.

3) The ‘lightball’ in your hand has to be able to communicate with another ‘lightball’ or object that can emit

light.

4) That other object has to light up as soon as the ‘lightball’ in the hand approaches.

5) The light has to be white.

6) Preferably, the ‘lightballs’ work identically, so there is no ‘master’ and no ‘slave’. The communication is

mutual and all devices work on 'proximity'.

7) When feasable, we want that the device can be used as a ‘reading lamp’.

At that point we didn’t really think about how the devices would be provided of power. As soon as the biggest

part of the programming was realised, we concentrated on the provision of energy.

24

CONCEPT FINALISATION—DEADLINES & PLANNING

We wanted to start as soon as possible with the prototyping and

testing with Arduino. Because, we couldn’t rely on another ICT– or

electronics student with the knowledge of writing programs.

During the programming phase, Ing. Ward Houdendycke, really helped

us out. Without him, we wouldn’t have been able to achieve the goals

we had in mind.

During the project there was only 1 deadline. Halfway we had to present

our 3 best concepts.

The deliverables were: (see specifications in the projectsheet of the

Mechatronics project)

The blog (potential design dossier)

Working Prototype

Presentation

Movie

25

CONCEPT FINALISATION—DEADLINES & PLANNING

BLOG

PROTOTYPE

CODE

ELECTRONICS

Stephanie Sofie

VIDEO

DOSSIER

PRESENTATION

26

ENGINEERING

27

ENGINEERING—TECHNICAL APPROACH PRODUCT

Caars, is a light emitting device, developed to assist during a nightwalk in the house. Caars is a solution to many problems and finds it’s origin in a well known phenomenon and old fashioned solution.

More specific, the well known problems:

Not lighting up the light in the bedroom or hallway to prevent that other persons in the house would awake.

Having troubles with finding the switch of the night lamp, with the result that every other thing on the cabinet ends up on the floor.

Not having a light to take with you during your translocation to the bathroom, kitchen, etc.

The well known phenomenon:

Touching the wall during your trip in the house, just to have an indication of where you are.

The (very) old fashioned solution:

A candle holder

Caars, is a light emitting device that lightens up as soon as a hand (or foot) approaches. This means that the problem of not finding the switch is already solved. Caars also happens to be a lightball that

can be taken away from it’s docking station. So you can take it with you during your night trip. Caars is especially designed to function as a night lamp. This means that the amount of emitted light, is

limited. You don’t have to be afraid that the light will disturb the other, sleeping, person in the room. Besides those characteristics, Caars can communicate with his 'twins'. This means that when you

have installed other Caars devices around the house, those will start to light up accordingly to the distance between the 2 elements.

Translated this all into reality, the result is that you will have a light as soon as you wake up, during your trip to the destination and sufficient light on the destination spot, thanks to the 2 lighting Caars

devices.

APPROACH

Technically, the development of ‘Caars’ was reduced to the designing of 2 functions. The first development was the lightning of the ball as soon as a hand came closer and a second part was the

development of a wireless connection between 2 elements.

Subsequently, we had to think about power consumption and supply. Caars had to be portable, so we had to find a suitable battery or other energy-system.

In short, the development of ‘Caars’ lapsed in different phases. In the next pages, those phases are briefly reviewed.

28

ENGINEERING—ARDUINO TESTS—TEST 1 A simulation of proximity by the use of a potentiometer

This first test was set up to get some feeling with the idea of ‘proximity’. We never

used this technology before, and for sure we didn’t know yet how to handle it. The

following test was performed by the simple use of a potentiometer. The

potentiometer equals the distance between the ‘lightball’ and the hand. So this

meant that turning the potentiometer to the one side was the same as the hand

that came closer to the ball, turning the potentiometer the other side, was the

same as the hand that moved away from the ball.

29

ENGINEERING—ARDUINO TESTS—TEST 2 Test 2: Making our own capacitive sensor by the use of aluminium paper

30

ENGINEERING—ARDUINO TESTS—TEST 3 Test 2 with a fading LED

31

ENGINEERING—PROXIMITY—CAPACITIVE SENSOR Capacitive proximity sensors can be used to detect metallic and also non metallic targets like paper, wood, plastic, glass, wood, powder, liquid..etc without physical contact. The capacitive proximity

sensor works on the capacitor principle. The main components of the capacitive proximity sensor are a plate, oscillator, threshold detector and an output circuit.

The plate inside the sensor acts as one plate of the capacitor and the target acts as another plate. The air between the two plates acts as the dielectric.

As the object comes close to the plate of the capacitor the capacitance increases and as the object moves away the capacitance decreases. The detector circuit checks the amplitude output from the

oscillator and based on that the output switches. Important to mention is that the capacitive sensor only can detect any targets whose dielectric constant is more than air.

Briefly, a capacitive (proximity) sensor measures the capacity between an active sensor electrode and the electric earth potential. The oscillator, oscillates corresponding to the space between the

sensor electrode and object to be recognized. Later on, the output signal is generated from the amplitude of the oscillator.

Arduino has it’s own capacitive sensing library. We

used this one during our tests. (See test 1, 2 and 3

above.)

As soon as this library and the simulation of a sensor

became to limited, we contacted Quad Ind.

They said they would help us where possible and since

interfaces and sensors is their core business, we

thought they might be interested in the approach.

32

ENGINEERING—WIRELESS CONNECTION—XBEE 2 Caars elements had to be able to ‘communicate’. By this was meant that the elements had to be able to ’measure’ the distance between them.

First we thought of infrared connection, like in remotes, but this didn’t fit in the concept. Imagine that the bathroom door is closed, then the ’Caars’ in there would never light up until you’re already inside

the bathroom and the door doesn’t interfere the connection.

We also thought about an ultrasonic sensor. Those sensors work on the same principal as sonar or radar, which evaluates attributes of a target by interpreting the echoes from radio or sound waves

respectively. Ultrasonic sensors generate high frequency sound waves and evaluate the echo which is received back by the sensor. Sensors calculate the time interval between sending the signal and

receiving the echo to determine the distance to an object.

Both principles weren’t 100%suitable for the concept, so we decided to go through with the wireless connection via a XBEE module. Those modules are perfect compatible with Arduino and ‘easier’ to

program in comparison with infrared or ultrasonic sensors.

33

ENGINEERING—WIRELESS CONNECTION—XBEE The programming of the XBEE’s didn’t go as smooth as hoped. A lot of problems occured. The first problem was getting 2 XBEE’s to recognize eachother. We did not want any problems with other XBEE

modules interfering with the ones we were using, so we had to adjust the XBEEs. This had to be done via a small program. Murphy wanted that this couldn’t be done by our computers, so we thought it

would never come to a happy ending. Fortunately, we had Ward to help us setting up this connection.

Furthermore, we had to continue with Arduino nano modules. In the meanwhile we had decided to prototype the concept with 2 balls, diameter 10cm. All the electronics had to fit in.

Eventually, we succeeded in creating small all-in-one packages. Those packages included an Arduino nano, an XBEE, an explorer regulated board and of course the breadboards.

34

ENGINEERING—POWER SUPPLY This topic got handled in the last weeks. The closer we got to the finish, the more we had to optimize the whole concept.

We had chosen to work with balls, because we believed this had an influence on the power supply and consumption. A round object can roll away, so we thought it would be a good idea to use this

‘disadvantage’ in our product too. People will be obliged to put ‘Caars’ back in its docking station as soon as it’s fullfilled it’s purpose.

There are all kind of batteries and energy-systems, but we chose a lipo-battery. Easy to charge via an USB-cable.

So, for 1 ‘Caars’, 1 lipo-battery and Lipo-charger/booster are needed. The charger/booster is necessary because of the difference in voltage required by the components. A Lipo-battery provides 3.7V,

while the Arduino components work on 5V.

35

ENGINEERING—QUAD IND.’S CONTRIBUTION The tests above were the only one we could do to come as close as possible to proximity and the wished interaction. Arduino is a nice and versatile thing, but not everything is quite as perfect as wanted

or hoped.

After those tests, we felt it was time to return to Quad Ind.. Modular wasn’t very much in the picture anymore, because they couldn’t help us with the translation of the concept into a working prototype.

In the company of Quad Ind. we explained what we had achieved and what we hoped Quad Ind. could do for us. We agreed that Quad Ind. would print a capacitive sensor for us, that could fit in the half of

a ball. Besides this agreement, they gave us some hints about a chip AT42QT1010, some PCB’s, and other interesting things to know about the possible right configuration.

After a while Quad Ind. contacted us back with the surprising message: ‘Hej girls, we have a working ball on proximity! Can you come and fetch it?’

The Quad-ball works without Arduino. Instead it is composed out of an AT42QT1010-chip and their own printed capacitive sensor. The chip is programmed especially for proximity– or capacitive

applications. They made an all-in-one PCB, consisting out of the chip, the leds and some other required components.

In this prototype, a simple battery-block was used. This prototype was a stand-alone device. It wasn’t designed yet to communicate with it’s ‘twin’.

36

RESULT: CAARS

37

RESULT

38

RESULT

39

RESULT

40

RESULT—FINAL CODE—Zender & Ontvanger

41

RESULT—ELECTRONICS—Battery

ARDUINO

42

RESULT—ELECTRONICS—Transmitter

PROXIMITY CLICK

43

RESULT—ELECTRONICS—Receiver

PROXIMITY CLICK

44

RESULT—ELECTRONICS—Receiver

PROXIMITY CLICK

45

RESULT—ASSEMBLY

46

RESULT—COST Price Arduino nano € 7.90 2x = € 15.80

Price X bee € 19.00 2x = € 38.00

Price plastic ball € 1.00 2x = € 2.00

Price wood recycled material

PCB Quad Ind. (unknown price)

LED Quad Ind. (unknown price)

Sensor Quad Ind. (unknown price)

Explorer board (Arduino board) € 7.50 2x = € 15.00

Battery € 5.95 2x = € 11.90

Charger € 3.30+€ 7.40 2x = € 21.40

Lipo Charger/Booster € 15.90 2x = € 31.80

Wiring € 1.00 (all) 2x = € 2.00

+_________________________________________________________________________________________

Total cost = € 137.90

47

RESULT—INTERACTION CHART—Go Scenario 1

Scenario 2

48

RESULT—INTERACTION CHART—Return Scenario 1

Scenario 2

49

RESULT—PRODUCT IDENTITY

The name ‘Caars’ comes from the flemish word ‘kaars’. The idea of ‘Caars’

was indeed shaped by the old fashioned candle holder. We chose to write

the name with a ‘C’, because this refers to the technical and electronic part

of the concept. We thought a ‘C’ brings that idea along.

Actually there is not really a restriction when it comes to the logo colors.

We have chosen to deliver this dossier in pink, as a statement of what we 2

girls are capable off. Of course, we have to mention we had a lot of help.

Therefore, Thank You!

Besides this, ‘Caars’ was initial meant as a night guide for kids. During the

project, it became clear to us, that many more people can benefit of ‘Caars’.

50

RESULT—PACKING

51

CONCLUSION AND REFLECTION

52

CONCLUSION AND REFLECTION—PAST & FUTURE If we knew in the beginning what we know now , we could not have dealt with problems differently. Most of our goals have been achieved.

Caars lights up as soon as a hand approaches close enough and a 2nd Caars activates as soon as the first (active) Caars approaches close enough. The balls can be used

wirelessly and a charging system is provided.

We are also satisied with the co-operation. The tasks were distributed evenly , each contribution was equally important and the approach of the programming we attacked

together. Admittedly, Ward supported us very much here .

It is true that we had to adjust our goals during the project. The initial goals we had set , were not realistic within the provided time. For example we wanted to make several

Caars'en . This, from the point of view, that Caars should be provided all around the house. However getting the wireless connection established between two elements , was

already challenging enough.

A short list of difficulties and disappointments is perhaps in place :

Programming wireless connection

Bring together the sensor and arduino ... These are not fully compatible

The chip (AT42QT1010) calibrates every 40 seconds

The Lipo-batteries may interfere the sensor

The life time of the batteries is limited

53

CONCLUSION AND REFLECTION—PAST & FUTURE

Plans for the future include especially optimization . Today CAARS is not 100 % reliable . This is because of the chip that is used to make proximity possible. This chip has a

built-in calibration function . This means that , once you a hold CAARS too long , the hand will eventually no longer be seen as an external trigger , but will be ' included ' in

the system. On the other hand , calibration is necessary because objects that are set up next to the docking station , should not be seen as 'something ' that may activate

Caars. In time, it would be a good thing if Caars calibrates only when it is set in the docking station.

Furthermore, we would like to optimize the charging system. Today Caars is charged via a USB cable , but we actually want it to charge wireless . Think of a

electric toothbrush for example, or an electric kettle . This principle is based on induction . However, we should take into account the impact of this method of charging

on the sensor.

As indicated earlier , we would like to enable communication between multiple Caars'en . And this is a ' modular ' way . Suppose that a family first purchases two Caars'en.

Then it should be possible that they add some Caars'en to this system after some time . These should be included in the ' circuit' and the wireless communication should also

work perfectly with the new elements .

Also, we would like to completely eliminate the master-slave mechanism. We strive to make the balls all "identical". In this way, the exchange of balls does not affect

the operation.

To make CAARS versatile, it would be a good thing to build in a ' stand-alone ' mechanism too. This means that it should be possible to use CAARS as a reading light.

Conclusion: CAARS is far from 'finished’ , but we can be satisfied with the results achieved in the last semester.

54

CONCLUSION AND REFLECTION—ACKNOWLEDGMENTS

‘CAARS’ has been realized with the help of a lot of people. Now it’s time to say ’thank you’ to those.

First of all we want to thank all of our docents and mentors. Thanks to their view on the learning proces of ‘becoming a (good) designer’, mechatronics,

interactions, etc. the course ’mechatronics’ is what it is. The process we’ve been ’pushed’ through, has been very fulfilling.

Next we want to thank Quad Ind. and Modular. Their courage to invest time in this project, led to our successes. We want to thank Quad Ind. especially for

their co-operation and contribution to the realisation of ’Caars’. Without their ’Quad-ball’ and capacitive sensor, we wouldn’t have been able to

translate our concept in what it is today.

We also wish to say to Ward Houdendycke: ‘Thank you!!!’. He was the man, who helped us with the configuration of the XBEE’s and who helped us to

assembly the all-in-one packages.

Of course, we’re forgetting to mention some names, but know that we’re only forgetting to mention them. All those who supported us during the project,

who fed our inspiration, who gave us the comments we needed to move on, etc.

To all of you,

‘Thank you!’

55

Sofie Havegeer & Stephanie Van Haecke

The guide to the bright side of the night.