Changes between Version 32 and Version 33 of expansion/gw16122

Timestamp:

04/16/2018 07:40:56 PM (7 years ago)

Author:

Ryan Erbstoesser

Comment:

add troubleshooting steps. add link to talk about sensor nv ram. add sdk version tested version.

expansion/gw16122

@@ -51 +51 @@
  1. GW16122 firmware: '''pre-installed (so you can skip this step)''' is called the !CoProcessor firmware
   * Download the SDK here: [http://www.ti.com/tool/download/SIMPLELINK-CC13X0-SDK SIMPLELINK-CC13X0-SDK] 
+   * Gateworks tested with SDK version 1.40.xx
   * There is a precompiled binary in the SDK here: 
     * /usr/src/ti/simplelink_cc13x0_sdk_xxx/examples/rtos/CC1350_LAUNCHXL/ti154stack/hexfiles/coprocessor_cc13x0_lp.hex
@@ -58 +59 @@
    * There is a precompiled binary .hex file in the [http://www.ti.com/tool/download/SIMPLELINK-CC13X0-SDK SIMPLELINK-CC13X0-SDK] from step 1:
     * /usr/src/ti/simplelink_cc13x0_sdk_xxx/examples/rtos/CC1350_LAUNCHXL/ti154stack/hexfiles/default/sensor_default.hex
+     * Gateworks tested with SDK version 1.40.xx
     * Install firmware to Sensor !LaunchPad with [#HostProgrammingSoftware this information]
     * Additional TI Links here: 
@@ -89 +91 @@
 * Install the collector application software on the Gateworks SBC as described above in the software requirements section 
 
-==== Running the Application ====
+==== Running the Collector Application ====
 
 * To start the collector application, run the script on the Gateworks command line:
@@ -117 +119 @@
 }}}
 * Observe the IP address printed out in the script output
+
+* From a computer on the same network as the Gateworks board, open a web browser and type in the IP address including the port and observe the web gui shown below:
+ * * '''IMPORTANT''' Click the grey button in the !WebGui on the left to open the network for new devices
+ * [[Image(gw16122webgui.png,400px)]]
 * Power on the sensor node that should then connect to the collector. 
- * NOTE: The sensor node has NV Ram that stores the last network it was connected to. This must be reset every time the run_demo.sh script is ran. 
-* From a computer on the same network as the Gateworks board, open a web browser and type in the IP address including the port and observe the web gui shown below:
-[[Image(gw16122webgui.png,400px)]]
-* '''IMPORTANT''' Click the grey button in the WebGui on the left to open the network for new devices
-
+ * NOTE: The sensor node has NV Ram that stores the last network it was connected to. This must be reset every time the run_demo.sh script is ran. Read a TI Forum topic about this here: [https://e2e.ti.com/support/wireless_connectivity/proprietary_sub_1_ghz_simpliciti/f/156/t/641623]
+* You can test the connection by clicking the 'Toggle LED' on the sensor node. This often takes 10 seconds to transmit and will affect LED D2 on the GW16122 if it is being used as a sensor. 
+
+==== Troubleshooting ====
+* Be sure any GW16122 boards have an antenna installed
+* Be sure the collector network is an open network so that the sensors can joined. By default, the network is closed and no sensors can join
+* Be sure that the Gateworks board and collector are all setup and turned on and the WebGUI is live with the run_demo script running on the Gateworks board. After this, then try re-programming the sensor firmware. This usually will force the sensor to re-join and search for new networks.
+* On the Gateworks board, you can try deleting the file in the extracted bin folder called nv-simulation.bin. This file will erase all previously connected sensor entries. 
 
 === What's Next? ===