diff --git a/.gitbook/assets/01_aws_integration.png b/.gitbook/assets/01_aws_integration.png new file mode 100644 index 0000000..6be07ea Binary files /dev/null and b/.gitbook/assets/01_aws_integration.png differ diff --git a/.gitbook/assets/02_aws_integration.png b/.gitbook/assets/02_aws_integration.png new file mode 100644 index 0000000..087b6b0 Binary files /dev/null and b/.gitbook/assets/02_aws_integration.png differ diff --git a/.gitbook/assets/03_aws_integration.png b/.gitbook/assets/03_aws_integration.png new file mode 100644 index 0000000..c613482 Binary files /dev/null and b/.gitbook/assets/03_aws_integration.png differ diff --git a/.gitbook/assets/04_aws_integration.png b/.gitbook/assets/04_aws_integration.png new file mode 100644 index 0000000..108a735 Binary files /dev/null and b/.gitbook/assets/04_aws_integration.png differ diff --git a/.gitbook/assets/assets-2f-lifiulge6_ztmmvcuea-2f-lkmxk1kqvbgjpw04i3u-2f-liqbk7blltxqntvqzh_-2fpysense_lopy4.png b/.gitbook/assets/assets-2f-lifiulge6_ztmmvcuea-2f-lkmxk1kqvbgjpw04i3u-2f-liqbk7blltxqntvqzh_-2fpysense_lopy4.png new file mode 100644 index 0000000..45c5c57 Binary files /dev/null and b/.gitbook/assets/assets-2f-lifiulge6_ztmmvcuea-2f-lkmxk1kqvbgjpw04i3u-2f-liqbk7blltxqntvqzh_-2fpysense_lopy4.png differ diff --git a/.gitbook/assets/assets-2f-lifiulge6_ztmmvcuea-2f-lkmxk1kqvbgjpw04i3u-2f-liqbluw130dl1amaklt-2fpytrack_lopy4.png b/.gitbook/assets/assets-2f-lifiulge6_ztmmvcuea-2f-lkmxk1kqvbgjpw04i3u-2f-liqbluw130dl1amaklt-2fpytrack_lopy4.png new file mode 100644 index 0000000..6794c20 Binary files /dev/null and b/.gitbook/assets/assets-2f-lifiulge6_ztmmvcuea-2f-lkmxk1kqvbgjpw04i3u-2f-liqbluw130dl1amaklt-2fpytrack_lopy4.png differ diff --git a/gettingstarted/connection/lopy4.md b/gettingstarted/connection/lopy4.md index 1e384e8..996d308 100644 --- a/gettingstarted/connection/lopy4.md +++ b/gettingstarted/connection/lopy4.md @@ -2,23 +2,34 @@ ## Basic connection +{% tabs %} +{% tab title="Exp Board 2.0" %} * Look for the reset button on the module \(located at a corner of the board, next to the LED\). * Locate the USB connector on the expansion board. * Insert the LoPy4 module on the the expansion board with the reset button pointing towards the USB connector. It should firmly click into place and the pins should now no longer be visible. ![](../../.gitbook/assets/expansion_board_2_lopy4.png) +{% endtab %} +{% tab title="Exp Board 3.0" %} * Before connecting your module to an Expansion Board 3.0, you should update the firmware on the Expansion Board 3.0. Instructions on how to do this can be found [here](../../pytrackpysense/installation/firmware.md). * Look for the reset button on the module \(located at a corner of the board, next to the LED\). * Locate the USB connector on the expansion board. * Insert the LoPy4 module on the Expansion Board with the reset button pointing towards the USB connector. It should firmly click into place and the pins should now no longer be visible. ![](../../.gitbook/assets/expansion_board_3_lopy4.png) +{% endtab %} +{% tab title="Pytrack/Pysense/Pyscan" %} * Before connecting your module to a Pysense/Pytrack/Pyscan board, you should update the firmware on the Pysense/Pytrack/Pyscan. Instructions on how to do this can be found [here](../../pytrackpysense/installation/firmware.md). * Look for the reset button on the LoPy4 module \(located at a corner of the board, next to the LED\). * Locate the USB connector on the Pysense/Pytrack/Pyscan. -* Insert the module on the Pysense/Pytrack/Pyscan with the reset button pointing towards the USB connector. It should firmly click into place and the pins should now no longer be visible. ![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LIfiUlGe6_zTmmvcuEa%2F-LKMXk1KQvBgjpw04I3u%2F-LIqbk7blltxqNtvQzH_%2FPysense_LoPy4.png?generation=1534772087747503&alt=media)![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LIfiUlGe6_zTmmvcuEa%2F-LKMXk1KQvBgjpw04I3u%2F-LIqblUw130dL1aMAkLT%2FPytrack_LoPy4.png?generation=1534772079835788&alt=media) +* Insert the module on the Pysense/Pytrack/Pyscan with the reset button pointing towards the USB connector. It should firmly click into place and the pins should now no longer be visible. + +![](../../.gitbook/assets/assets-2f-lifiulge6_ztmmvcuea-2f-lkmxk1kqvbgjpw04i3u-2f-liqbk7blltxqntvqzh_-2fpysense_lopy4.png) ![](../../.gitbook/assets/assets-2f-lifiulge6_ztmmvcuea-2f-lkmxk1kqvbgjpw04i3u-2f-liqbluw130dl1amaklt-2fpytrack_lopy4.png) +{% endtab %} + +{% tab title="USB UART Adapter" %} * Firstly you will need to connect power to your LoPy4. You will need to supply `3.5v`-`5.5v` to the `Vin` pin. {% hint style="danger" %} @@ -34,7 +45,9 @@ Please ensure you have the signal level of the UART adapter set to `3.3v` before * In order to put the LoPy4 into bootloader mode to update the device firmware you will need to connect `P2` to `GND`. We recommend you connect a button between the two to make this simpler. ![](../../.gitbook/assets/uart_lopy4.png) +{% endtab %} +{% tab title="WiFi" %} **Note:** This method of connection is not recommended for first time users. It is possible to lock yourself out of the device, requiring a USB connection. * In order to access the LoPy4 via WiFi you only need to provide `3.5v` - `5.5v` on the `Vin` pin of the LoPy4: @@ -47,6 +60,8 @@ Please ensure you have the signal level of the UART adapter set to `3.3v` before * Once connected to this network you will be able to access the telnet and FTP servers running on the LoPy4. For both of these the login details are: * username: `micro` * password: `python` +{% endtab %} +{% endtabs %} ## Antennas