Instructions for sniffing HTTPPost(), HTTPPut(), and HTTPGet() from the terminal mode in Device Configuration Utility

One way to catch errors such as "Is my header formatted correctly?" and "Does it contain the right type of information?" is to monitor your traffic using a terminal or a terminal emulator.

  1. Launch Device Configuration Utility and connect to your data logger.

  2. Click the Terminal tab.

  3. Type capital letter W, and press Enter.

  4. Enter the number that corresponds to IP Trace (for the CR1000X, it’s 23), then press Enter.

  5. Enter the number that corresponds to HTTP (800), then press Enter.

  6. You should now see the press ESC to exit, any other key to renew timeout message. To create an export of the results, click the Start Export button.

  7. On the Choose an export file window, select a location where you can find the file and give it a name (For example, “mysniff.txt”). Click Save.

  8. Wait for your HTTPPost() instruction to trigger in your data logger program, or trigger it manually. For best results, let the HTTPPost() instruction complete or fail twice for redundancy before clicking the End Export button. If the HTTPPost() instruction only runs once per day at midnight, testing may be difficult without a way to trigger it manually.