alessio9008/Thingsquare-Contiki-O.S-Porting-STM32F4-Discovery

Stars
6
Rank 2,539,965 (Top 51 %)
Language
C
License
Other
Created about 11 years ago
Updated over 10 years ago

alessio9008/Thingsquare-Contiki-O.S-Porting-STM32F4-Discovery

alessio9008

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

We have ported the Contiki Operating System to STM32F4 platform (http://www.st.com/stm32f4-discovery). We started with the work that was already done on an evaluation board based on STM32L1 platform (STEVAL-IKR001V1, http://www.st.com/web/en/catalog/tools/PF253893). The original project, called "Mist", was created by Thingsquare using Spirit1 radio transceiver (STEVAL-IKR001V8D, http://www.st.com/web/en/catalog/tools/FM116/SC1075/PF258319). We converted the system calls from the original platform to the target platform. We have adapted Spirit1 radio driver in order to work properly on STM32F4. Then, we created a Wireless Sensor Network and collected several communication and performance data. I worked on it with Daniele Saitta. To manage the entire work, we used IAR Embedded Workbench (http://www.iar.com/en/products/iar-embedded-workbench/arm/).

TrackMyself-Automatic-Tracking-Positioning-System-through-RESTful-webservices-and-Android-app

The project consists in the tracking of the user's location through an ANDROID app that communicates with a remote database (MySQL) through RESTful webservices built with JAVA Enterprise 7 (using the Glassfish 4 container). The Android app allows you to capture and collect, with various options, the datas about user's current location. The app can also show the map with the routes created with the points stored in the remote database. The app is designed to work offline: after the user has logged in, the app can collect the data in a local database (SQLite); when the device goes back online, all caches in the local database will be sent to the remote database through the RESTful webservices. The communication between the app and the webservices is done with messages formatted according to the JSON standard. The app has several working modes and can manage multiple users: when the app is started for the first time, a screen allows the user to log in to the service or sign up using an other screen. After logged in, the app runs with default preferences that the user can change. Options are divided into three groups: - Tracking: o Enable tracking o Position acquisition rate - Network: o Automatic map update o Output data-rate (to the server) o Show the route of the last xx minutes/hours (customizable) - Map: o Route drawing mode (driving, walking, free). o Default zoom level o Map Mode (Map, Earth, Hybrid) o Tracking color The app has also a Service that runs in background; it sends the data to the server and collects the data about the current location.

PLC-to-STM32F4-communication-through-PC-as-gateway

This project has been made using the STM32F4 accelerometer and a Siemens S7-300 unit. The microcontroller is programmed to send data to a PC by using a serial-port communication; these data are read from a C# program that forward them to the PLC memory. Then, the PLC unit, that recognizes the microcontroller position, moves a mechanical arm.

Traffic-Track-with-GPS-module-for-Arduino-and-Android-app-through-RESTful-webservices

The project consists in the tracking of the user's location through an ARDUINO board that communicates with a remote database (MySQL) through RESTful webservices built with JAVA Enterprise 7 (using the Glassfish 4 application server) and Android APP. The ARDUINO with GPS module allows you to capture and collect, with various options, the datas about user's current location. The app can also show the map with the routes created with the points stored in the remote database. The routes are created with different color according to the speed for traffic monitoring. The communication between the app and the webservices is done with messages formatted according to the JSON standard. The app runs with default preferences that the user can change. Options are divided into two groups: Network: • Automatic map update Map: • Default zoom level • Map Mode (Map, Earth, Hybrid) This project was developed by Alessio Oglialoro and Daniele Saitta.

Java-Enterprise-7-Glassfish-4-Netbeans-project-management-offices-callcenters-and-DB

The system was developed using Java Enterprise 7.0 and glassfish server 4.0. It consists of: -Two callcenters (B1,B2) made with WebServices and Enterprice Application Client, than communicate by jms/queue -Every callcenter controls five offices and the callcenter communicate with them by the same number (five) of jms/queue . Any request that may be send to the callcenter through Web Page and Servlet consists: Unique identifier (ID) List of signals, which indicates which offices we have need to contact. The request is handled in a transactional context through the "two-phase commit" protocol. Every request received to the office consists: Read from the database Resolve the signal Write to database. Every office has three active replicas of the same database and communicate with the databases by jms/Topic.

Java-RMI-Project--management-offices-callcenters--

The system have five callcenters and twenty offices, every callcenter can receive a signal that requires from one to four offices. Then every signal have one id and the list of required offices. When the user enters in the system, every callcenter does the operations: -lock offices with mutual exclusion -execute required operations -send the answer to the user. -unlock resources.

Java-Enterprise-7-Glassfish-4-Java-Database-EJB-3-Signal-Project

The system consist of: -A front-end web services (SOAP) that take the users' signals. -An application components (EJB 3.0). The application: - Makes the parsing of the signal. - Manages the insert, modify and delete of reservations in a database (Java DB). - At regular intervals, logs in a file the performed activities. - Keeps the statistics on the received signal. For each district, the application maintains the average: - Number of the week's signals. - Number of the month's signals. - Number of the high priority month's signals. - Age of the users that send the signals. The signals are built with: - Id. - Name, surname and age of the user. - Id district. - Priority (HIGH – LOW - AUTO). The system has been designed with a BPMN workflow and was deployed in a remote virtual machine (Amazon - AWS). The client through which the user communicate with the system in particular with the web services is built with a web page and one servlet.

TCPForwardPort

Java TCP Port Forwarding

Java-SSH-and-SFTP-server

SSH and SFTP server written in Java, compatible with all windows and unix systems.