You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<strong> Not working as expected and need help? </strong> <br /><br />
1
+
---
2
+
icon: material/help-circle-outline
3
+
---
4
4
5
-
If you need technical assistance and more information on a product that is not working as you expected, we recommend heading on over to the <a href="https://www.sparkfun.com/technical_assistance">SparkFun Technical Assistance</a> page for some initial troubleshooting. <br /><br />
If you don't find what you need there, the <a href="https://forum.sparkfun.com/index.php">SparkFun Forums</a> are a great place to find and ask for help. If this is your first visit, you'll need to <a href="https://forum.sparkfun.com/ucp.php?mode=register">create a Forum Account</a> to search product forums and post questions.<br /><br />
10
-
11
-
<div style="text-align: center"><a href="https://forum.sparkfun.com/ucp.php?mode=register" class="md-button">Create New Forum Account</a> <a href="https://forum.sparkfun.com/index.php" class="md-button md-button--primary">Log Into SparkFun Forums</a></div>
5
+
# Troubleshooting and Support
12
6
7
+
## Support
13
8
9
+
If you need technical assistance and more information on a product that is not working as you expected, visit the [SparkFun Community](https://community.sparkfun.com). The community forums are monitored by the SparkFun Technical Support Team and the SparkFun community as a whole.
14
10
15
11
### Issues Connecting to IoT Service
16
12
17
13
Having trouble connecting your DataLogger IoT to an IoT service? Make sure to check your credentials and ensure that the configuration matches the IoT Service (such as your WiFi network, port, server, topic, certificates, keys, etc. to name a few). Make sure to also include the associated certificates and keys in the microSD card as well. You may see an output similar to the following errors below.
18
14
19
-
20
-
21
15
#### AWS IoT Error
22
16
23
17
The following error occurred when the DataLogger IoT was initializing with AWS.
@@ -26,15 +20,10 @@ The following error occurred when the DataLogger IoT was initializing with AWS.
<imgsrc="../assets/Incorrect_Configuration_Connection_Failed_IoT_Service_AWS.JPG"width="600px"height="600px"alt="Configuration entered incorrectly, DataLogger not connecting to IoT Service"></a>
32
-
</div>
23
+
33
24
34
25
In this case, the DataLogger IoT failed to connect to AWS IoT service because the port was using the default value that was saved: `1883`. Ensure that the port is set to `8883` for your IoT service (e.g. AWS IoT, Azure, and ThingSpeak) and saved in persistent memory in order for the DataLogger IoT to successfully connect. As of firmware v01.00.04, the default is `8883`.
35
26
36
-
37
-
38
27
#### ThinkSpeak IoT Error
39
28
40
29
The following error occurred when the DataLogger IoT was initializing with ThingSpeak.
@@ -43,15 +32,10 @@ The following error occurred when the DataLogger IoT was initializing with Thing
<imgsrc="../assets/Incorrect_Configuration_Connection_Failed_IoT_Service_ThingSpeak.JPG"width="600px"height="600px"alt="Configuration entered incorrectly, DataLogger not connecting to IoT Service - ThingSpeak"></a>
49
-
</div>
35
+
50
36
51
37
In this case, the DataLogger IoT failed to connect to ThingSpeak service because the credentials were entered incorrectly. Ensure that the and saved in persistent memory in order for the DataLogger IoT to successfully connect.
52
38
53
-
54
-
55
39
#### Arduino Cloud Error 1
56
40
57
41
The following error was occurred when the DataLogger IoT was initializing with Arduino Cloud.
@@ -65,15 +49,10 @@ The following error was occurred when the DataLogger IoT was initializing with A
65
49
[E] Arduino IoT Cloud not available or account credentials incorrect
<imgsrc="../assets/Arduion_IoT_Error_Connecting_Incorrect_Configuration.JPG"width="600px"height="600px"alt="Configuration entered incorrectly, DataLogger not connecting to IoT Service"></a>
71
-
</div>
52
+
72
53
73
54
In this case, the DataLogger IoT failed to connect to the Arduino Cloud service because the credentials were incorrect. Ensure that the credentials (i.e. API client ID, API secret, device secret, device ID) are entered correctly and saved in persistent memory in order for the DataLogger IoT to successfully connect.
74
55
75
-
76
-
77
56
#### Arduino Cloud Error 2
78
57
79
58
The following error was occurred when the DataLogger IoT was initializing with Arduino Cloud.
@@ -84,11 +63,7 @@ The following error was occurred when the DataLogger IoT was initializing with A
84
63
85
64
In this case, the DataLogger IoT failed to connect to the Arduino Cloud service because the credentials were incorrect. The string was supposed to be the device ID. When copying and pasting the device ID from a PDF that was generated with the Arduino Cloud, a carriage return (`\r`) was also copied and entered in the serial terminal. By pasting the device ID into a text editor and then re-copying/pasting it into the serial terminal helped to ensure that the credentials were entered correctly.
86
65
87
-
88
-
!!! note
89
-
The device ID in this example was a randomly generated string. You will need to check to make sure that your device matches the one that the Arduino Cloud generated specifically for your account.
90
-
91
-
66
+
> **NOTE** The device ID in this example was a randomly generated string. You will need to check to make sure that your device matches the one that the Arduino Cloud generated specifically for your account.
92
67
93
68
#### Arduino Cloud Error 3
94
69
@@ -104,51 +79,34 @@ ArduinoIoTCloudTCP::handle_ConnectMqttBroker 2 connection attempt at tick time 3
104
79
105
80
In this case, the DataLogger IoT failed to connect to the Arduino Cloud service because there was already a Thing that was created. By deleting the Thing in the Arduino Cloud, the DataLogger IoT was able to automatically create another Thing and setup the variables.
106
81
107
-
108
-
109
82
### ThingSpeak Data Points Not Updating
110
83
111
-
If your DataLogger IoT is connected to ThingSpeak but you do not see any data, ensure that the device name matches the Qwiic device that is connect to the DataLogger IoT. For example, the DataLogger IoT and Qwiic-enabled ENS160 was able to connect to ThingSpeak as shown in the image on the bottom left. However, there were no data points in any of the graphs as shown on ThingSpeak as shown in the image on the bottom right.
84
+
If your DataLogger IoT is connected to ThingSpeak but you do not see any data, ensure that the device name matches the Qwiic device that is connect to the DataLogger IoT. For example, the DataLogger IoT and Qwiic-enabled ENS160 was able to connect to ThingSpeak as shown in the following image:
<td style="text-align: center; vertical-align: middle; border: none;"><a href="../assets/ThingSpeak_ENS160_No_Data.JPG"><img src="../assets/ThingSpeak_ENS160_No_Data.JPG" width="600px" height="600px" alt="No Data Points in ThingSpeak Channel"></a></td>
118
-
</tr>
119
-
</table>
120
-
</div>
86
+
121
87
122
-
If you head back into the configuration menu for the DataLogger's ThingSpeak channel, make sure that the _<devicename>_ matches the connected Qwiic device's name that was shown during initialization. In this case, the device that was loaded and detected was **ENS160**. Then add the channel ID before saving the system settings.
88
+
However, there were no data points in any of the graphs as shown on ThingSpeak:
123
89
124
-
<divstyle="text-align: center">
125
-
<ahref="../assets/Device_Name_ENS160.JPG">
126
-
<imgsrc="../assets/Device_Name_ENS160.JPG"width="600px"height="600px"alt="Matching Device Name with Qwiic-Enabled ENS160 Breakout Board"></a>
127
-
</div>
90
+
128
91
129
-
!!! note
130
-
Only one device can be loaded per channel! ThingSpeak is not able graph two different devices in the same channel.
92
+
If you head back into the configuration menu for the DataLogger's ThingSpeak channel, make sure that the ```<device name>``` matches the connected Qwiic device's name that was shown during initialization. In this case, the device that was loaded and detected was **ENS160**. Then add the channel ID before saving the system settings.
131
93
132
-
Head back to your ThingSpeak Channel to verify that data is being plotted on the graphs.
94
+
<imgsrc="../assets/ThingSpeak_ENS160_with_Data.JPG"width="600px"height="600px"alt="ThingSpeak Outputting ENS160 Sensor Data on Graphs"></a>
137
-
</div>
96
+
> **NOTE** Only one device can be loaded per channel! ThingSpeak is not able graph two different devices in the same channel.
138
97
98
+
Head back to your ThingSpeak Channel to verify that data is being plotted on the graphs.
139
99
100
+
140
101
141
-
### U-Blox I<sup>2</sup>C Device Disappears when IoT DataLogger Initializes
102
+
### U-Blox Device Disappears when IoT DataLogger Initializes
142
103
143
-
If you have issues where a u-blox device that is connected to the I<sup>2</sup>C port fails to connect a second time when the IoT DataLogger initializes, this is due to a bug in the firmware from an initial release. You may see an output similar to the following message and image shown below.
104
+
If you have issues where a u-blox device that is connected via qwiic fails to connect a second time when the IoT DataLogger initializes, this is due to a bug in the firmware from an initial release. You may see an output similar to the following message and image shown below.
144
105
145
106
```bash
146
107
[W] GNSS::isConnected no traffic seen (first attempt)
If you see the following output and the IoT DataLogger not loading your u-blox device, you will need to [update the firmware to v01.00.03 and above](https://github.com/sparkfun/SparkFun_DataLogger/releases). For more information, make sure to check out the [tutorial on updating your IoT DataLogger's firmware](https://docs.sparkfun.com/SparkFun_DataLogger/updating_firmware/).
0 commit comments