Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • W Wiki
  • Project information
    • Project information
    • Activity
    • Members
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Wiki
    • Wiki
  • Activity
Collapse sidebar

To receive notifications about scheduled maintenance, please subscribe to the mailing-list gitlab-operations@sympa.ethz.ch. You can subscribe to the mailing-list at https://sympa.ethz.ch

  • TECTEC
  • Public
  • FlockLabFlockLab
  • Wiki
  • Wiki
  • Man
  • FAQ

FAQ · Changes

Page history
Update FAQ authored May 23, 2022 by Reto Da Forno's avatar Reto Da Forno
Hide whitespace changes
Inline Side-by-side
Man/FAQ.md
View page @ 7d9c02b5
......@@ -40,4 +40,12 @@ Note: by default, tracing only starts 1s after the test to avoid capturing many
<br />
## Where can I buy the DPP2 LoRa communication board for debugging on the desk?
The DPP2 LoRa comboard that is used on FlockLab is a custom board and not available as an off-the-shelf component. Since the [hardware design files](https://gitlab.ethz.ch/tec/public/dpp/dpp/-/tree/master/hardware/dpp2_sx1262) are open-source, you can manufacture your own boards (Gerber files available upon request). However, this is very cost-intensive for small batch sizes. Therefore, it may be a more economical option to buy a NUCLEO-L476RG and SX1262MB2CAS shield instead. The hardware is obviously slightly different, which necessitates adjustments to clock, GPIO and peripheral configuration. Our [LWB sample code](https://gitlab.ethz.ch/tec/public/flora/lwb) has a separate branch ([`nucleo-devkit`](https://gitlab.ethz.ch/tec/public/flora/lwb/-/tree/nucleo-devkit)) which is compatible with the mentioned nucleo board and SX1262 shield.
\ No newline at end of file
The DPP2 LoRa comboard that is used on FlockLab is a custom board and not available as an off-the-shelf component. Since the [hardware design files](https://gitlab.ethz.ch/tec/public/dpp/dpp/-/tree/master/hardware/dpp2_sx1262) are open-source, you can manufacture your own boards (Gerber files available upon request). However, this is very cost-intensive for small batch sizes. Therefore, it may be a more economical option to buy a NUCLEO-L476RG and SX1262MB2CAS shield instead. The hardware is obviously slightly different, which necessitates adjustments to clock, GPIO and peripheral configuration. Our [LWB sample code](https://gitlab.ethz.ch/tec/public/flora/lwb) has a separate branch ([`nucleo-devkit`](https://gitlab.ethz.ch/tec/public/flora/lwb/-/tree/nucleo-devkit)) which is compatible with the mentioned nucleo board and SX1262 shield.
<br />
## Why is the results plot generated with the FlockLab Tools so sluggish, and how can I make it more responsive?
The reason for slow plot is usually a large GPIO tracing or power profiling file. The only ways to make it more responsive is to use a more powerful machine to render the plot or to reduce the amount of tracing and profiling data, i.e.:
* Remove the power profiling file from the results directory before invoking `flocklab -x` if you don't need to visualize the power data.
* Try to reduce the number of pin toggles in your code (also watch for erratic toggles due to floating pins).
* If you can't reduce the number of pin toggles, you might consider to plot only part of the GPIO trace. Use [this script](https://gitlab.ethz.ch/tec/public/flocklab/server/-/blob/master/tools/extract_subtrace.py) to extract a certain time frame from the tracing data.
\ No newline at end of file
Clone repository
  • Man
    • CoojaPlugin
    • Description
    • Examples
    • FAQ
    • GpioAssignmentTargetAdapter
    • HowTo
    • QuickStart
    • Services
    • ServicesOld
    • SetupGuide
    • Targets
    • Tutorials
    • Tutorials
      • Tutorial1
      • Tutorial2
      • Tutorial3
View All Pages