Sometimes a project owner wants a feature implemented in their project that the developers somehow are unable to realize. The project was a website containing a form that customers would enter text data on. The project owner asked for a feature which allowed customers to attach files to this form.
+
As a "temporary" solution, I suggested creating a stand-alone server that would handle file uploads that would be linked to the ID number of the form. This consisted of 2 servers. One server would be a simple web interface, the other a database server that hosted a simple API.
The web server used the Nginx engine and the Django framework. Python handles the HTTP requests with Gunicorn, a WSGI gateway.
+
The database server used a MySQL server to host uploaded file data. To expose this data, Flask RESTful was used to serve a simple API.
+
This was the first separate project I created for the company, so I set up a GitLab server for version control.
+
-
-
-
Attachment Module
-
Solving the problem of someone else
-
Sometimes a project owner wants a feature implemented in their project that the developers somehow are unable to realize. The project was a website containing a form that customers would enter text data on. The project owner asked for a feature which allowed customers to attach files to this form.
-
As a "temporary" solution, I suggested creating a stand-alone server that would handle file uploads that would be linked to the ID number of the form. This consisted of 2 servers. One server would be a simple web interface, the other a database server that hosted a simple API.
The web server used the Nginx engine and the Django framework. Python handles the HTTP requests with Gunicorn, a WSGI gateway.
-
The database server used a MySQL server to host uploaded file data. To expose this data, Flask RESTful was used to serve a simple API.
-
This was the first separate project I created for the company, so I set up a GitLab server for version control.
-
-
-
-
Workflow
-
-
The website hosting the forms, would serve a hyperlink to the "attachment module", along with the form's ID.
-
The user is redirected to the website with a simple input field and browse button where a file can be uploaded.
-
The file is validated by type, size and upload time.
-
The file is copied to the database server.
-
The file is also cached for 2 weeks on the web server, for quicker access.
-
The database server creates a database entry.
-
A link to the file is created for access on the website.
-
-
After a file is uploaded, someone else will want to access it.
-
-
The user accesses the website and clicks on the link with the file name.
-
If the file is cached on the web server, then this file is opened.
-
If the file is not cached, the web server downloads the file from the database server and then opens it.
+
+
Workflow
+
+
The website hosting the forms, would serve a hyperlink to the "attachment module", along with the form's ID.
+
The user is redirected to the website with a simple input field and browse button where a file can be uploaded.
+
The file is validated by type, size and upload time.
+
The file is copied to the database server.
+
The file is also cached for 2 weeks on the web server, for quicker access.
+
The database server creates a database entry.
+
A link to the file is created for access on the website.
-
+
After a file is uploaded, someone else will want to access it.
+
+
The user accesses the website and clicks on the link with the file name.
+
If the file is cached on the web server, then this file is opened.
+
If the file is not cached, the web server downloads the file from the database server and then opens it.
+
+
-
-
Lessons learnt
-
The project owner did not want the users to separately log in to the web server of the attachment module. So a big security issue is that anyone with the link, can access uploaded files. At the time this was agreed to be a temporary solution. The project was deployed in 2017 and in 2021 this project was still running though. After all, the business must go on and if the problem's symptoms seems fixed, why bother with it further...
-
Because other users could access other uploaded files using the right link, it was decided that users could only upload and never delete any files.
-
A big learning point for me was that not to compromise security, even for projects that are considered temporary. A problem never occurred. This compromise caused silly decisions to not allow users to delete their own files. I will defend my standpoint much more and use this project as an example.
-
The actual problem here though, is why the other developers were not able to create a safe file upload feature.
-
-
+
+
Lessons learnt
+
The project owner did not want the users to separately log in to the web server of the attachment module. So a big security issue is that anyone with the link, can access uploaded files. At the time this was agreed to be a temporary solution. The project was deployed in 2017 and in 2021 this project was still running though. After all, the business must go on and if the problem's symptoms seems fixed, why bother with it further...
+
Because other users could access other uploaded files using the right link, it was decided that users could only upload and never delete any files.
+
A big learning point for me was that not to compromise security, even for projects that are considered temporary. A problem never occurred. This compromise caused silly decisions to not allow users to delete their own files. I will defend my standpoint much more and use this project as an example.
+
The actual problem here though, is why the other developers were not able to create a safe file upload feature.
The Board of education Robot is a development platform made by Parallax.
+
This school project was mainly to learn about basic electronics and programming for embedded devices. The BoeBot was created by Parallax and uses the Javelin stamp processor. This processor accepts the high-level programming language Java to control different pieces of hardware on the robot. The robot started as a simple prototype board with two servo motors. Sensors and actuators were later placed on the breadboard to allow sensory input and output. We created a GUI named "Robot at Work" which allowed the robot to follow a path using QPI linefollowers. The robot could also be controlled with an IR remote control.
+
+
+
+
+
+
+
+
-
The Board of education Robot is a development platform made by Parallax.
-
This school project was mainly to learn about basic electronics and programming for embedded devices. The BoeBot was created by Parallax and uses the Javelin stamp processor. This processor accepts the high-level programming language Java to control different pieces of hardware on the robot. The robot started as a simple prototype board with two servo motors. Sensors and actuators were later placed on the breadboard to allow sensory input and output. We created a GUI named "Robot at Work" which allowed the robot to follow a path using QPI linefollowers. The robot could also be controlled with an IR remote control.
At Hitachi Vantara I worked with other developers on automating a configuration process using Python and several external API.
+
Products would be picked, assembled, configured and finally packaged for shipping at the distribution centre where I collaborated on this project. Configuration happend by connecting a Windows laptop to the product and apply settings. This related to the product's operating system, network and storage settings.
-
-
-
Configuration automation
-
At Hitachi Vantara I worked with other developers on automating a configuration process using Python and several external API.
-
Products would be picked, assembled, configured and finally packaged for shipping at the distribution centre where I collaborated on this project. Configuration happend by connecting a Windows laptop to the product and apply settings. This related to the product's operating system, network and storage settings.
+
+
+
+
+
+
-
-
-
-
-
-
+
-
+
+
Development
+
This project started as a local Python 2 script when it started, to only automate very specific settings. It later moved to USB drives and eventually to a VM on a network.
+
It eventually grew to support multiple product lines and at this moment I joined the other programmer to further extend this software after my internship.
+
Here I learnt working properly with Git and designing software architecture. I also learnt how to create automation by interfacing by GUI automation with AutoHotkey and combine multiple APIs to achieve results.
+
The automation software also used other resources like Tera Term scripts.
+
Another fun thing I added was an iPDU where Python could safely powercycle 230 Volt AC power consumers. This was useful to power down devices when the distribution center was not operating at night to reduce costs.
-
-
Development
-
This project started as a local Python 2 script when it started, to only automate very specific settings. It later moved to USB drives and eventually to a VM on a network.
-
It eventually grew to support multiple product lines and at this moment I joined the other programmer to further extend this software after my internship.
-
Here I learnt working properly with Git and designing software architecture. I also learnt how to create automation by interfacing by GUI automation with AutoHotkey and combine multiple APIs to achieve results.
-
The automation software also used other resources like Tera Term scripts.
-
Another fun thing I added was an iPDU where Python could safely powercycle 230 Volt AC power consumers. This was useful to power down devices when the distribution center was not operating at night to reduce costs.
+
+
+
+
+
+
-
-
-
-
-
-
+
-
+
+
Deployment
+
Creating the release of this software had to be done by running a batch script to create a bundled set of Python files. These files were then uploaded to the VM located in a European distribution center in the Netherlands. This VM is then used to run the software from on a local network on which all configuration laptops were connected to. A WinSCP script would then sync the contents of all VM's in distribution centres located in Singapore, United States and China in 24 hours.
+
A script (stub) on the configuration laptop would connect to the VM and run Python locally to receive instructions. The technician selects the product through a CLI menu and automated configuration starts.
+
Dedicated storage managing software had to be installed, so communicating with the Japanese supplier was always important. This software and other assets were separately deployed to create a stable configuration process.
-
-
Deployment
-
Creating the release of this software had to be done by running a batch script to create a bundled set of Python files. These files were then uploaded to the VM located in a European distribution center in the Netherlands. This VM is then used to run the software from on a local network on which all configuration laptops were connected to. A WinSCP script would then sync the contents of all VM's in distribution centres located in Singapore, United States and China in 24 hours.
-
A script (stub) on the configuration laptop would connect to the VM and run Python locally to receive instructions. The technician selects the product through a CLI menu and automated configuration starts.
-
Dedicated storage managing software had to be installed, so communicating with the Japanese supplier was always important. This software and other assets were separately deployed to create a stable configuration process.
+
+
+
+
+
+
-
-
-
-
-
-
+
-
+
+
Feedback
+
The application generated log files with each configuration and then upload these back to the VM after configuration was complete or halted. These logs were sorted under product name and the order number. But quite often, I found it very productive to go to the configuration area and simply talk with the technician to figure out what went wrong. Depending on the severity of the problem, it would get documented in Gitlab issues. On a weekly basis, issues would get assigned among developers.
+
Communication is always important and essential for proper DevOps. The people who operate and configure these machines daily often know a lot more details that can be used to optimize the software. But be certain to make them realize that they also contribute to profit, rather than believing their job may become obsolete.
-
-
Feedback
-
The application generated log files with each configuration and then upload these back to the VM after configuration was complete or halted. These logs were sorted under product name and the order number. But quite often, I found it very productive to go to the configuration area and simply talk with the technician to figure out what went wrong. Depending on the severity of the problem, it would get documented in Gitlab issues. On a weekly basis, issues would get assigned among developers.
-
Communication is always important and essential for proper DevOps. The people who operate and configure these machines daily often know a lot more details that can be used to optimize the software. But be certain to make them realize that they also contribute to profit, rather than believing their job may become obsolete.
+
+
+
+
+
+
-
-
-
-
-
-
+
-
+
+
Lessons learnt
+
Being a programmer, I was mostly concerned with the software. But it requires hardware to run on. When the software does not work because of differences in the platform the software run on, what is there to do? I eventually started managing around 40 configuration laptops, using Clonezilla to create identical machines.
+
Docker would have been an ideal solution, but I did not know much of it at the time.
+
Also my many points of learning in git merges, creating release tags, deploying broken versions of the software and immediately needing to patch with hotfixes, all contributed to my learning of software development.
+
Automation demands an equalized platform to run on and once it is deployed, hundreds of products will be making use of it. So, thinking something over and propely design and architecture software is much more time-saving than quickly meeting deadlines.
-
-
Lessons learnt
-
Being a programmer, I was mostly concerned with the software. But it requires hardware to run on. When the software does not work because of differences in the platform the software run on, what is there to do? I eventually started managing around 40 configuration laptops, using Clonezilla to create identical machines.
-
Docker would have been an ideal solution, but I did not know much of it at the time.
-
Also my many points of learning in git merges, creating release tags, deploying broken versions of the software and immediately needing to patch with hotfixes, all contributed to my learning of software development.
-
Automation demands an equalized platform to run on and once it is deployed, hundreds of products will be making use of it. So, thinking something over and propely design and architecture software is much more time-saving than quickly meeting deadlines.
What is DXP? It stands for Digital Experience Platform and is basically interactive software where data can be maintained. One such DXP I loved working on was for OPPLE. They are a brand of lighting products and have over 14000 different items.
+
My contributions were taking ownership of their catalog generator tool and maintaining the data of their products in Drupal on their website.
All the data was supplied through an external API by Compano and through an uploaded XML file. This data had to be parsed and converged into a logical structure so that products and product families were matched along with their features, photographs, accessoires, dimensional drawings, sensor diagrams and more. And all data is multilingual. And of course data had to be exchanged through excel files for pricelists and tender texts. Data was used interchangably between different tools and websites.
+
+
The catalog generator makes use of the Drupal platform as an intranet portal where thousands of PDF's could be automatically generated in a single batch. The customer only has to alter the data and the layouts and appropriate sections appear.
+
-
-
-
DXP Development
-
OPPLE Catalog Generator
-
What is DXP? It stands for Digital Experience Platform and is basically interactive software where data can be maintained. One such DXP I loved working on was for OPPLE. They are a brand of lighting products and have over 14000 different items.
-
My contributions were taking ownership of their catalog generator tool and maintaining the data of their products in Drupal on their website.
All the data was supplied through an external API by Compano and through an uploaded XML file. This data had to be parsed and converged into a logical structure so that products and product families were matched along with their features, photographs, accessoires, dimensional drawings, sensor diagrams and more. And all data is multilingual. And of course data had to be exchanged through excel files for pricelists and tender texts. Data was used interchangably between different tools and websites.
-
-
The catalog generator makes use of the Drupal platform as an intranet portal where thousands of PDF's could be automatically generated in a single batch. The customer only has to alter the data and the layouts and appropriate sections appear.
-
-
-
-
Legacy
-
This project was handed to me as a monolithic source, with only 1 PHP file containing all the rendering logic and handling exceptions (as in, many products had their own unique, exceptional attributes). This was a project that had outgrown itself and was hard to scale further due to the current structure. I had to improve the code base, while retaining the legacy functions. But because everything was so tightly coupled I had to make sure a change did not break functionality elsewhere. The key is to write new code and provide "safety nets" for older code.
-
A common misconception is to think by creating quick code, is easy gain. Not much effort, just copy and paste the existing logic and adjust it a bit. Then put it in the same file, no need to document it. But by building up Technical Dept, you will either leave this code behind or you will forget how everything works. Making code scalable, is essential. Even for "small" or "temporary" projects. Do not take shortcuts, thinking it will save time or meet the deadline.
-
-
-
-
Improvement
-
Restructuring code built as such requires mostly patience. You cannot instantly restart everything, as this tool is used in production. You cannot create a new architecture complete with diagrams, there is currently no time. It is not the only project I work on, there are 20 other projects that also require attention. Instead, I started by moving functions around every time I worked on a new feature for the tool. Dedicating existing functions to separate module files was the start. Creating object-oriented code for new features was the next step. Applying unit tests came next. As long as a new feature request did not exceed in time, it could be slowly prepared to grow by having prework done every time.
-
Eventually, it became a tool with composed logic, making future maintenance and feature requests a lot more simple.
-
Moving forward with a structured tool, I am proud to have collaborated on this project!
-
-
+
+
Legacy
+
This project was handed to me as a monolithic source, with only 1 PHP file containing all the rendering logic and handling exceptions (as in, many products had their own unique, exceptional attributes). This was a project that had outgrown itself and was hard to scale further due to the current structure. I had to improve the code base, while retaining the legacy functions. But because everything was so tightly coupled I had to make sure a change did not break functionality elsewhere. The key is to write new code and provide "safety nets" for older code.
+
A common misconception is to think by creating quick code, is easy gain. Not much effort, just copy and paste the existing logic and adjust it a bit. Then put it in the same file, no need to document it. But by building up Technical Dept, you will either leave this code behind or you will forget how everything works. Making code scalable, is essential. Even for "small" or "temporary" projects. Do not take shortcuts, thinking it will save time or meet the deadline.
+
+
+
Improvement
+
Restructuring code built as such requires mostly patience. You cannot instantly restart everything, as this tool is used in production. You cannot create a new architecture complete with diagrams, there is currently no time. It is not the only project I work on, there are 20 other projects that also require attention. Instead, I started by moving functions around every time I worked on a new feature for the tool. Dedicating existing functions to separate module files was the start. Creating object-oriented code for new features was the next step. Applying unit tests came next. As long as a new feature request did not exceed in time, it could be slowly prepared to grow by having prework done every time.
+
Eventually, it became a tool with composed logic, making future maintenance and feature requests a lot more simple.
+
Moving forward with a structured tool, I am proud to have collaborated on this project!
This project gave me the opportunity to work with the SIR120 internet radio made by the company StreamIT. The radio involved connecting to exiting internet streams and interfacing with the LCD and buttons on the device. The code was written in C.
+
+
+
+
+
+
+
-
This project gave me the opportunity to work with the SIR120 internet radio made by the company StreamIT. The radio involved connecting to exiting internet streams and interfacing with the LCD and buttons on the device. The code was written in C.
-
-
-
-
-
-
-
+
+
Development
+
The radio had an existing operating system called Nut/OS, an open source OS. Nut/OS provided the TCP/IP stack we required to connect the device to the internet. The radio was able to play a select number of internet streams. The user could read the stream channel on the LCD and use the buttons to navigate between them.
+
This project often had code overhauls because our code kept moving towards a more OOP approach using structs rather than large chunks of produral code.
+
+
+
+
+
+
+
-
-
Development
-
The radio had an existing operating system called Nut/OS, an open source OS. Nut/OS provided the TCP/IP stack we required to connect the device to the internet. The radio was able to play a select number of internet streams. The user could read the stream channel on the LCD and use the buttons to navigate between them.
-
This project often had code overhauls because our code kept moving towards a more OOP approach using structs rather than large chunks of produral code.
-
-
-
-
-
-
-
-
-
-
Design
-
A simple flowchart was created to show how the user could navigate through the menu.
-
-
-
-
-
-
-
-
-
+
+
Design
+
A simple flowchart was created to show how the user could navigate through the menu.
A team project in which a festival can be simulated to view how crowds of people behave. The user can build festivals, roads, snackbars and assign time periods when a band plays at a stage. The project was programmed in Java. A school project made by four people. The software allows users to build their own festival grounds. Snackbarstands, toilets, roads and stages can be placed to view how people form crowds and bottlenecks in certain areas. The user can also assign a band that plays for a certain time at a stage using a scheduler.
-
The band has a timeperiod and popularity, which affects the amount of people visiting that stage. The goal of this software is create an overview of potential bottlenecks and overcrowded areas.
+
A team project in which a festival can be simulated to view how crowds of people behave. The user can build festivals, roads, snackbars and assign time periods when a band plays at a stage. The project was programmed in Java. A school project made by four people. The software allows users to build their own festival grounds. Snackbarstands, toilets, roads and stages can be placed to view how people form crowds and bottlenecks in certain areas. The user can also assign a band that plays for a certain time at a stage using a scheduler.
+
The band has a timeperiod and popularity, which affects the amount of people visiting that stage. The goal of this software is create an overview of potential bottlenecks and overcrowded areas.
A mobile iPhone application using a SQLite database to display airports around the world. With this project I got to experience working with Xcode and Swift to develop iOS mobile applications.
-
A mobile iPhone application using a SQLite database to display airports around the world. With this project I got to experience working with Xcode and Swift to develop iOS mobile applications.
+
+ Source code can be seen on my Github page:
+
+
+
+
-
- Source code can be seen on my Github page:
-
-
-
-
In my free time I like to learn Japanese. I am married with someone from Japan, so being able talk with her parents in their own language is nice! You also pick up much of the culture through learning the language.
+
I wanted a personalized way to learn Kanji. I keep track of the words I want to learn in a small SQLite database. If I come across a Japanese word, I can enter it in the database myself, because many language learning applications give you a preset of words, usually of the joyo Kanji. The database can also be exported and imported to a file from the application.
+
+
+
+
+
-
-
-
Kanji flashcard Android application
-
Personalized Japanese learning
-
In my free time I like to learn Japanese. I am married with someone from Japan, so being able talk with her parents in their own language is nice! You also pick up much of the culture through learning the language.
-
I wanted a personalized way to learn Kanji. I keep track of the words I want to learn in a small SQLite database. If I come across a Japanese word, I can enter it in the database myself, because many language learning applications give you a preset of words, usually of the joyo Kanji. The database can also be exported and imported to a file from the application.
By user input, the difficulty of a Kanji is determined. A Kanji that is often guessed wrong will increase in difficulty and can be asked more frequently. Questioning can be done based on time and certain aspects of the Kanji can be shown or hidden. Finally, a dark and light mode offers some more customizability, along with the sizes of the characters.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
Settings
+
By user input, the difficulty of a Kanji is determined. A Kanji that is often guessed wrong will increase in difficulty and can be asked more frequently. Questioning can be done based on time and certain aspects of the Kanji can be shown or hidden. Finally, a dark and light mode offers some more customizability, along with the sizes of the characters.
A simple Java 2D game using Nintendo's Metroid franchise sprites. This was a school project. This little game I made to practice programming with 2D graphics. It slowly gained more and more features like extra weapons and different levels, because I really enjoyed working on this project.
+
+
+
+
+
+
+
+
-
A simple Java 2D game using Nintendo's Metroid franchise sprites. This was a school project. This little game I made to practice programming with 2D graphics. It slowly gained more and more features like extra weapons and different levels, because I really enjoyed working on this project.
Here I used a Raspberry Pi to stream internet radio. Python and Flask were used to create a simple website interface that resided on the Raspberry Pi using the Apache web engine. This simple site had buttons to control the LEDs, the station to stream and to adjust the volume.
Here I used a Raspberry Pi to stream internet radio. Python and Flask were used to create a simple website interface that resided on the Raspberry Pi using the Apache web engine. This simple site had buttons to control the LEDs, the station to stream and to adjust the volume.
A simple vertical space shooter created for the Raspberry Pi. The game is played with regular keyboard and a custom joystick setup. The game was programmed in Python using the PyGame library. This project was mainly to create small game and interface it with a custom hardware setup. The setup uses an analog joystick to control the player's helicopter. An ADC (Analog Digital Converter) samples the analog data into digital data so that the Raspberry Pi (version 1, type B) could parse the data.
+
+
+
-
-
-
Embedded Game
-
Vertical shooter
-
A simple vertical space shooter created for the Raspberry Pi. The game is played with regular keyboard and a custom joystick setup. The game was programmed in Python using the PyGame library. This project was mainly to create small game and interface it with a custom hardware setup. The setup uses an analog joystick to control the player's helicopter. An ADC (Analog Digital Converter) samples the analog data into digital data so that the Raspberry Pi (version 1, type B) could parse the data.
-
-
-
+
+
Hardware
+
Simple components were placed onto a breadboard and the joystick's analog resistive data would be converted into digital data. This data would be read by the GPIO pins and used to determine how the helicopter moves over the X- and Y-axis. To help with understanding electronic logic, an oscilloscope was used.
+
+
+
+
+
+
-
-
Hardware
-
Simple components were placed onto a breadboard and the joystick's analog resistive data would be converted into digital data. This data would be read by the GPIO pins and used to determine how the helicopter moves over the X- and Y-axis. To help with understanding electronic logic, an oscilloscope was used.
A team project where the player must align pipes correctly using a Wii remote. The ingame goals would then have effect on a custom built wooden tower. The game was programmed in Java.
+
This project was made by four people working on both software and hardware. The game uses the Nintendo Wii remote to get input from the player.
+
+
+
Gameplay
+
The player must align pipes from the fictional tesla coil to "relay electricity" to a specific point in the game. The game communicates to the Arduino to power servomotors that operate three doors and an elevator.
-
A team project where the player must align pipes correctly using a Wii remote. The ingame goals would then have effect on a custom built wooden tower. The game was programmed in Java.
-
This project was made by four people working on both software and hardware. The game uses the Nintendo Wii remote to get input from the player.
-
-
-
Gameplay
-
The player must align pipes from the fictional tesla coil to "relay electricity" to a specific point in the game. The game communicates to the Arduino to power servomotors that operate three doors and an elevator.
The tower base is made of wood and has a metal screw elevator. A conductive metal ball has to be elevated up and then roll down three rails. One side of a rail is powered and the other is grounded. The metal ball conducts electricity to blue LED's on the rails when it passes by. Once the ball has reached the bottom of the tower within the time limit, a switch turns on the plasma globe on the top of the tower and the game is won.
-
-
-
Woodwork
-
The tower base is made of wood and has a metal screw elevator. A conductive metal ball has to be elevated up and then roll down three rails. One side of a rail is powered and the other is grounded. The metal ball conducts electricity to blue LED's on the rails when it passes by. Once the ball has reached the bottom of the tower within the time limit, a switch turns on the plasma globe on the top of the tower and the game is won.
This was actually my favourite project to work on! It combined the talent of everyone in our team. We had a very skilled woodworker (who doubled as a good project leader as well) and we all were coding. This project taught me that effective team work with good group synergy, produces great results.
-
-
-
-
-
-
-
-
+
+
Lessons learnt
+
This was actually my favourite project to work on! It combined the talent of everyone in our team. We had a very skilled woodworker (who doubled as a good project leader as well) and we all were coding. This project taught me that effective team work with good group synergy, produces great results.
This project was part of my internship at Dazzletek in Breda. They created intelligent lighting control solutions, but sadly the company no longer exists today. My assignment was to create a prototype that would allow a device to communicate over Wi-Fi. I worked with oscilloscopes and electronics to adjust the hardware on the prototype.
+
I developed a software program using C in the OpenAT framework. At the end of my internship the prototype was realized into a product. The purpose of this assignment was to provide a device which communicates over GPRS, with the ability to communicate that data over Wi-Fi.
+
Instead of using the Wi-Fi stack, I was encouraged to develop my own data transfer logic over SPI, which was then read over the oscilloscope.
-
-
-
Wi-Fi prototype board
-
Embedded internship project
-
This project was part of my internship at Dazzletek in Breda. They created intelligent lighting control solutions, but sadly the company no longer exists today. My assignment was to create a prototype that would allow a device to communicate over Wi-Fi. I worked with oscilloscopes and electronics to adjust the hardware on the prototype.
-
I developed a software program using C in the OpenAT framework. At the end of my internship the prototype was realized into a product. The purpose of this assignment was to provide a device which communicates over GPRS, with the ability to communicate that data over Wi-Fi.
-
Instead of using the Wi-Fi stack, I was encouraged to develop my own data transfer logic over SPI, which was then read over the oscilloscope.
The WF121 by BlueGiga, which used a PIC32 microcontroller, had to be programmed to accept and transfer data to a specific SSID. Also the AirPrime SL6087 by Sierra Wireless had to be programmed to relay the data to the Wi-Fi module.
+
I used Wireshark, commandline debug and an oscilloscope to monitor the datatranfers. I also built a little RJ45 connector that could be plugged on the prototype board so it could be easily programmed. Version control was done in Subversion.
-
-
Technique
-
The WF121 by BlueGiga, which used a PIC32 microcontroller, had to be programmed to accept and transfer data to a specific SSID. Also the AirPrime SL6087 by Sierra Wireless had to be programmed to relay the data to the Wi-Fi module.
-
I used Wireshark, commandline debug and an oscilloscope to monitor the datatranfers. I also built a little RJ45 connector that could be plugged on the prototype board so it could be easily programmed. Version control was done in Subversion.
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
- 
- 
- 
- 
- 
- 
- 
- 
+ 
+ 
+ 
+ 
+ 
- 
- 
+ 
+ 
+ 
+ 
+ 
- 
- 
- 
- 
+ 
+ 
+ 
- 
- 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
- 
+ 
+ 
- 
- 
+ 
+ 
+ 
-