Changes between Version 32 and Version 33 of expansion/gw16122


Ignore:
Timestamp:
04/16/2018 07:40:56 PM (18 months ago)
Author:
Ryan Erbstoesser
Comment:

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

Legend:

Unmodified
Added
Removed
Modified
  • expansion/gw16122

    v32 v33  
    5151 1. GW16122 firmware: '''pre-installed (so you can skip this step)''' is called the !CoProcessor firmware
    5252  * Download the SDK here: [http://www.ti.com/tool/download/SIMPLELINK-CC13X0-SDK SIMPLELINK-CC13X0-SDK]
     53   * Gateworks tested with SDK version 1.40.xx
    5354  * There is a precompiled binary in the SDK here:
    5455    * /usr/src/ti/simplelink_cc13x0_sdk_xxx/examples/rtos/CC1350_LAUNCHXL/ti154stack/hexfiles/coprocessor_cc13x0_lp.hex
     
    5859   * There is a precompiled binary .hex file in the [http://www.ti.com/tool/download/SIMPLELINK-CC13X0-SDK SIMPLELINK-CC13X0-SDK] from step 1:
    5960    * /usr/src/ti/simplelink_cc13x0_sdk_xxx/examples/rtos/CC1350_LAUNCHXL/ti154stack/hexfiles/default/sensor_default.hex
     61     * Gateworks tested with SDK version 1.40.xx
    6062    * Install firmware to Sensor !LaunchPad with [#HostProgrammingSoftware this information]
    6163    * Additional TI Links here:
     
    8991* Install the collector application software on the Gateworks SBC as described above in the software requirements section
    9092
    91 ==== Running the Application ====
     93==== Running the Collector Application ====
    9294
    9395* To start the collector application, run the script on the Gateworks command line:
     
    117119}}}
    118120* Observe the IP address printed out in the script output
     121
     122* 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:
     123 * * '''IMPORTANT''' Click the grey button in the !WebGui on the left to open the network for new devices
     124 * [[Image(gw16122webgui.png,400px)]]
    119125* Power on the sensor node that should then connect to the collector.
    120  * 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.
    121 * 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:
    122 [[Image(gw16122webgui.png,400px)]]
    123 * '''IMPORTANT''' Click the grey button in the WebGui on the left to open the network for new devices
    124 
     126 * 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]
     127* 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.
     128
     129==== Troubleshooting ====
     130* Be sure any GW16122 boards have an antenna installed
     131* 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
     132* 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.
     133* 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.
    125134
    126135=== What's Next? ===