Safari FAE Demo FAQ

1. How is the GUI getting the data to plot?
2. Why does there seem to be a delay in some of the temperature and pressure data timestamps?
3. Why MQTT and not REST?
4. What programming language was used to create the demo?
5. Why Python?

Q1

How is the GUI getting the data to plot?

A: When the demo kit is connected to Wi-Fi, the temperature and pressure data is sent to Arrow Connect using MQTT and the accelerometer data is sent to the GUI using the serial (UART) connection. The GUI plots the accelerometer data when it is received from the serial port, while the temperature and pressure data are plotted by subscribing to the same Arrow Connect MQTT topic to which the demo kit is publishing. In the case when the demo kit is not connected to Wi-Fi, all data is sent to the GUI using the serial connection.

Q2

Why does there seem to be a delay in some of the temperature and pressure data timestamps?

A: This is a result of network latency. The demo kit is sending data to Arrow Connect while the laptop is receiving data from Arrow Connect, if the network is slow or congested there will be delays. There should be no missed packets due to the MQTT quality of service (QoS) setting.

Q3

Why MQTT and not REST?

A: MQTT is lower power, allows for the device to always be connected to the cloud, and is faster than REST.

Q5

What programming language was used to create the demo?

A: Python.

Q5

Why Python?

A: Python was used because of it's portability across platforms, allowing the Safari demo to be run on any 96Boards platform with Python support.

Previous- Troubleshooting

Next- Modifying the Demo for Alternate Sensors

Return to Appendix Table of Contents