User Tools

Site Tools


isp-iot-challenge

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
isp-iot-challenge [2018/11/18 17:50] – [Stage 3: Raise the bar !] ooubejjaisp-iot-challenge [2018/11/22 14:17] (current) – [Stage 3: Raise the bar !] ooubejja
Line 18: Line 18:
 Before we start, you have to do the following: Before we start, you have to do the following:
  
-- Form teams and give them cool names  +- Form a team of **THREE**   
-- Give us the infos (team names, members' names & emails)+- Give us the infos (team number, members' names & emails)
  
-Only after validating your team you will be able to access the challenge. 
  
-Why do we need your email? Well, the winning team members will receive a **USRP device**, kindly given by our partner National Instruments. A "Certificate of Success" will be given too.+Why do we need your email? Well, the winning team members will receive a SigFox device and one **USRP device**, kindly given by our partners SigFox and National Instruments. 
  
 To verify your progress, there will be several checkpoints to be __**validated by one of the organizers**__ (Leo, Matthieu, Othmane, Cyrille, Pascal, Tanguy ...).  To verify your progress, there will be several checkpoints to be __**validated by one of the organizers**__ (Leo, Matthieu, Othmane, Cyrille, Pascal, Tanguy ...). 
Line 32: Line 32:
 Each team will have a group number and thus have access to specific nodes following this table : Each team will have a group number and thus have access to specific nodes following this table :
  
 +
 +/*
 ^ Group ^ SSH login ^ Nodes to use ^ Port ^ Assigned team     ^ Stage 1 ^ Stage 2 ^ Stage 3 ^ ^ Group ^ SSH login ^ Nodes to use ^ Port ^ Assigned team     ^ Stage 1 ^ Stage 2 ^ Stage 3 ^
-| //X //| //tutoY //| //node Z//   | XXXX | //RadIO Riders//  |                         | +| //X //| //tutoY //| //node Z//                      | XXXX | //RadIO Riders//  |                         | 
-| 1     | tuto1                  | 6661 |                                           | +| 1     | tuto1     node 3 and node 4               | 6661 |                                           | 
-| 2     | tuto2                  | 6662 |                                           | +| 2     | tuto2     node 7 and node 8               | 6662 |                                           | 
-| 3     | tuto3                  | 6663 |                                           | +| 3     | tuto3     node 13 and node 14             | 6663 |                                           | 
-| 4                            | 6666 |                                           | +| 4               node 17 and node 18             | 6666 |                                           | 
-| 5                            | 6667 |                                           | +| 5               node 23 and node 24             | 6667 |                                           | 
-| 6                            | 6668 |                                           | +| 6               node 23 and node 24             | 6668 |                                           | 
-| 7                            | 6669 |                                           | +| 7               node 23 and node 24             | 6669 |                                           | 
-| 8                            | 6670 |                                           | +| 8               node 23 and node 24             | 6670 |                                           | 
-| 9                            | 6671 |                                           |+| 9               node 23 and node 24             | 6671 |                                           | 
 +*/ 
 + 
 + 
 +^ Group      ^ SSH login       ^ Nodes to use          ^ Frequency ^ TCP Port ^  Connected ^ Leader ^ 
 +| 1          | tuto1           | node 3 and node 4     | 2.400GHz  | 6663            Djibrilla   | 
 +| 2          | cadjih          | node 7 and node 8     | 2.410GHz  | 6664            Cedric   | 
 +| 3          | hezzeddine      | node 13 and node 14   | 2.420GHz  | 6665            Ezzeddine 
 +| 4          | dadja           | node 17 and node 18   | 2.430GHz  | 6666            Dadja  | 
 +| 5          | tuto4           | node 23 and node 24   | 2.440GHz  | 6667            Satya   | 
 +| 6          | ymestrah        | node 25 and node 27   | 2.450GHz  | 6668            Yasser   | 
 +| 7          | tuto7           | node 28 and node 32   | 2.460GHz  | 6669            Thomas 
 +| 8          | amayouche       | node 33 and node 34   | 2.470GHz  | 6670            Abdou  |  
 +| 9          | aparis          | node 37 and node 38   | 2.480GHz  | 6671            Antoine 
 +| 10         | lmroueh         | node 16 and node 35   | 2.490GHz  | 6672            Lina  | 
 +| 11         | gcallebaut      | node 6 and node 9     | 2.500GHz  | 6673            Gilles   | 
  
 Refresh this page, when you see your team name assigned it means you can start the **Challenge!** Refresh this page, when you see your team name assigned it means you can start the **Challenge!**
Line 48: Line 66:
 Also refresh this page to see your progress and the progress of the other groups Also refresh this page to see your progress and the progress of the other groups
  
 + 
 ---- ----
  
Line 80: Line 98:
   * Detect beacon from BS, and estimate slots timing    * Detect beacon from BS, and estimate slots timing 
   * Transmit    * Transmit 
-  * Store UDP feedback results sent by the BS (if any)  
   * Repeat    * Repeat 
  
Line 100: Line 117:
  
 The goal is familiarize with the [[https://project.inria.fr/ephyl/|EPHYL Project]] GNU Radio framework, understand it, and try some stuffs. The goal is familiarize with the [[https://project.inria.fr/ephyl/|EPHYL Project]] GNU Radio framework, understand it, and try some stuffs.
 +
 +**REMINDER**: If you you have never used GNU Radio Companion (GRC), it is **HIGHLY** suggested that you go check some [[tutorials|tutorials]]. Especially Tutorial **3** and **6**
  
 When connected to CorteXlab (aka Airlock server), create a new directory "stage1", copy this folder and put it in your home : When connected to CorteXlab (aka Airlock server), create a new directory "stage1", copy this folder and put it in your home :
Line 200: Line 219:
 </code> </code>
  
-  * 2) Two time plotsRx signal, and decoded data:+  * 2) Two time plotsRx signal, and decoded data:
  
  
Line 248: Line 267:
   * etc   * etc
  
 +Start experimenting and try to get some results as in the local tests.
 +Maybe you'll have to strengthen the processing in the uplink transmission (modify some parameters, thresholds, etc)
  
-Start your experiment and evaluate the transmission quality.   +**UPDATE For Wednesday 21 :** 
-Maybe you'll have to strengthen the processing in the uplink transmission !+ 
 +If you have some difficulties creating GRC flowgraphs, you can get an example for each node here: 
 + 
 +<code> 
 +yourlogin@srvairlock:~$ mkdir stage2 
 +yourlogin@srvairlock:~$ cp /cortexlab/homes/ooubejja/ws/cxlb stage2/ 
 +yourlogin@srvairlock:~$ ls stage2/cxlb 
 +</code> 
 + 
 +In stage2/cxlb you should have these files now: 
 + 
 +<code> 
 +A.txt             ephyl_bs_core.py  ephyl_sensor.py           main_bs.grc      scenario.yaml 
 +B.txt             ephyl_bs.grc      ephyl_sn_sched.py         main_bs.py       tag2msg.py 
 +C.txt             ephyl_bs.py       example.txt               main_sensor.grc  tag2msg_sn.py 
 +data_slot_mux.py  ephyl_sensor.grc  file_source_slot_ctrl.py  main_sensor.py 
 +</code> 
 + 
 +Open ''main_bs.grc'' and ''main_sensor.grc'' in GNU Radio, some parameters are already set to match CorteXlab setting (UHD blocks, generation options, reference source,etc). However, you should verify RF parameters (Freq, gain, sample rate,etc). 
 + 
 +Also, don't forget to adapt ''scenario.yaml'' to your actual scenario. 
  
  
Line 264: Line 305:
 The proposals can be relevant to :  PHY/MAC layers, data compression, channel coding, throughput, interference management, etc. The proposals can be relevant to :  PHY/MAC layers, data compression, channel coding, throughput, interference management, etc.
  
-Finally, keep in mind that, even after the Winster school, you can continue working on the framework (or anything else) anywhere and anytime, since you have your personal FIT/CorteXlab account.  +Finally, keep in mind that, even after the Winter school, you can continue working on the framework (or anything else) anywhere and any time, since you have your personal FIT/CorteXlab account.  
 And, please, if you ever use the testbed in your research, don't forget to [[http://ieeexplore.ieee.org/abstract/document/6849176/|cite]] FIT/CorteXlab in your publications And, please, if you ever use the testbed in your research, don't forget to [[http://ieeexplore.ieee.org/abstract/document/6849176/|cite]] FIT/CorteXlab in your publications
 +
 +**THURSDAY 22 UPDATE :**
 +
 +2pm-3.30pm ->  Add final touch and prepare a presentation (if any) 
 +
 +3.30pm-4.30pm -> Present your contribution
 +
 +4.30pm-5pm -> Winners announcement
  
  
  
isp-iot-challenge.1542559838.txt.gz · Last modified: 2018/11/18 17:50 by ooubejja

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki