Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of Home › Forums › Mayfly Data Logger › uBee R410 setup issues › Reply To: uBee R410 setup issues
2020-01-09 at 1:03 PM
#13576
Thanks Sara. Some more info for you. First, the CGMR and GMR commands both result in the response ERROR, as you can see in the output below.
Additionally, it sometimes seems to struggle getting a con
Thanks Sara. Some more info for you. First, the CGMR and GMR commands both result in the response ERROR, as you can see in the output below.
Additionally, it sometimes seems to struggle getting a connection to NIST, also as in the example below. It took two tries before it finally connected, and this seems to be commonb. Note also the funkiness in the shutdown code.
No USOWRs with OK responses (only +CME ERROR: Operation not allowed), No UUSOCL anywhere, and the result of USOCR was variable. You can see the different USOCR responses in the NIST connection below.
Now, I am using a bit of a homebrew solution for sending data. I’m not using EnviroDIY publisher or any of the other built-in methods but instead am using the Hologram Cloudsocket API. I modified EnviroDIYPublisher.cpp and .h to create HologramPublisher.cpp, .h to send data to Hologram, which has been working quite well on the two other modems I have (Sodaq GPRSbee and uBee U201). It seems a bit weird that there are double AT commands echoed to the log when trying to send data.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 |
Powering unspecified modem with pin 23 <--SodaqUBeeR410M Running wake function for unspecified modem <--LoggerModem Sending a wake-up pulse on pin 20 for Sodaq UBee R410M <--SodaqUBeeR410M Status pin came on after 80 ms <--SodaqUBeeR410M Pulsed for 150 ms <--SodaqUBeeR410M Waiting for UART to become active and requesting a slower baud rate. <--SodaqUBeeR410M AT+IPR=9600 unspecified modem should be awake. <--LoggerModem Setting up the modem ... <--LoggerModem Modem was already awake and should be ready for setup. <--LoggerModem Running modem's begin function ... <--LoggerModem AT 8��AT OK ATE0 ATE0 OK AT+CMEE=0 OK AT+CGMI u-blox OK AT+GMM SARA-R410M-02B OK AT+CPIN? +CPIN: READY OK AT+CGMI u-blox OK AT+GMM SARA-R410M-02B OK AT+URAT=7 OK ... Complete! It's a u-blox SARA-R410M-02B <--LoggerModem u-blox SARA-R410M-02B warms up in 250 ms, indicates status in 0 ms, is responsive to AT commands in less than 4500 ms, and takes up to 15000 ms to close connections and shut down. <--LoggerModem Leaving modem on after setup ... <--LoggerModem AT+CGMR? ERROR AT+GMR? ERROR Attempting to connect to the internet and synchronize RTC with NIST Waiting for u-blox SARA-R410M-02B to respond to AT commands... <--SodaqUBeeR410M AT OK ... AT OK after 35 milliseconds! <--SodaqUBeeR410M Waiting up to 120 seconds for cellular network registration... <--SodaqUBeeR410M AT+CEREG? +CEREG: 0,2 OK AT+CEREG? +CEREG: 0,2 OK AT+CEREG? +CEREG: 0,5 OK ... Registered after 719 milliseconds. Connecting to GPRS... <--SodaqUBeeR410M AT+CGATT=1 OK AT+CGDCONT=1,"IP","hologram" OK AT+CGACT=1,1 OK ... Connected after 885 milliseconds. <--SodaqUBeeR410M AT+CGATT? +CGATT: 1 OK AT+CGPADDR +CGPADDR: 1,10.191.68.253 OK Connecting to NIST daytime Server <--SodaqUBeeR410M AT+USOCL=0,1 OK AT+USOCR=6 +USOCR: 0 OK AT+USOSO=0,6,1,1 OK AT+USOCO=0,"time.nist.gov",37,1 OK AT+USORD=0,0 ERROR AT+USOCTL=0,10 ERROR NIST Time server did not respond! <--SodaqUBeeR410M Connecting to NIST daytime Server <--SodaqUBeeR410M AT+USOCL=0,1 ERROR AT+USOCR=6 +USOCR: 1 OK AT+USOSO=1,6,1,1 OK AT+USOCO=1,"time.nist.gov",37,1 OK AT+USORD=1,0 +USORD: 1,4 OK NIST responded after 73 ms <--SodaqUBeeR410M AT+USORD=1,4 +USORD: 1,4,"���" OK AT+USORD=1,0 +USORD: 1,0 OK AT+USOCTL=1,10 +USOCTL: 1,10,9 OK AT+USOCL=1,1 OK Response Byte 0 : � = 225 = 11100001 <--LoggerModem Response Byte 1 : � = 193 = 11000001 <--LoggerModem Response Byte 2 : � = 229 = 11100101 <--LoggerModem Response Byte 3 : � = 128 = 10000000 <--LoggerModem Seconds from Jan 1, 1900 returned by NIST (UTC): 3787580800 = 11100001110000011110010110000000 <--LoggerModem Unix Timestamp returned by NIST (UTC): 1578592000 <--LoggerModem Clock already within 5 seconds of time. Setting up sensors... Enabling interrupts for SDI12 on pin 7 <--SDI12Sensors Asking for sensor acknowlegement <--SDI12Sensors >>> 0! <--SDI12Sensors <<< ␀ <--SDI12Sensors VaisalaWXT520 at SDI12-0_Pin7 did not reply! <--SDI12Sensors >>> 0! <--SDI12Sensors <<< <--SDI12Sensors VaisalaWXT520 at SDI12-0_Pin7 did not reply! <--SDI12Sensors >>> 0! <--SDI12Sensors <<< <--SDI12Sensors VaisalaWXT520 at SDI12-0_Pin7 did not reply! <--SDI12Sensors >>> 0! <--SDI12Sensors <<< <--SDI12Sensors VaisalaWXT520 at SDI12-0_Pin7 did not reply! <--SDI12Sensors >>> 0! <--SDI12Sensors <<< <--SDI12Sensors VaisalaWXT520 at SDI12-0_Pin7 did not reply! <--SDI12Sensors Setting up file on SD card Data will be saved as bel_2020-01-09.csv Putting modem to sleep AT+CGACT=0 ERROR AT+CGATT=0 OK Disconnected from cellular network after 428 milliseconds. <--SodaqUBeeR410M Turning u-blox SARA-R410M-02B off. <--LoggerModem Running given sleep function for u-blox SARA-R410M-02B <--LoggerModem Asking u-blox R410M to power down <--SodaqUBeeR410M AT+CPWROFF OK Total modem active time (s): 38.672 <--LoggerModem Waiting up to 15000 milliseconds for graceful shutdown as indicated by pin 19 going 0 ... <--LoggerModem ... shutdown complete after 68 ms. <--LoggerModem Total modem power-on time (s): 43.606 <--LoggerModem Turning off power to u-blox SARA-R410M-02B with pin 23 <--LoggerModem Putting processor to sleep |
and then sending data:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 |
Powering u-blox SARA-R410M-02B with pin 23 <--SodaqUBeeR410M Skipping u-blox SARA-R410M-02B in sensor power up! <--LoggerModem Running wake function for u-blox SARA-R410M-02B <--LoggerModem Sending a wake-up pulse on pin 20 for Sodaq UBee R410M <--SodaqUBeeR410M Status pin came on after 80 ms <--SodaqUBeeR410M Pulsed for 150 ms <--SodaqUBeeR410M Waiting for UART to become active and requesting a slower baud rate. <--SodaqUBeeR410M AT+IPR=9600 u-blox SARA-R410M-02B should be awake. <--LoggerModem AT #TH�Enabling interrupts for SDI12 on pin 7 <--SDI12Sensors Asking for sensor acknowlegement <--SDI12Sensors >>> 0! <--SDI12Sensors <<< <--SDI12Sensors VaisalaWXT520 at SDI12-0_Pin7 did not reply! <--SDI12Sensors >>> 0! <--SDI12Sensors <<< <--SDI12Sensors VaisalaWXT520 at SDI12-0_Pin7 did not reply! <--SDI12Sensors >>> 0! <--SDI12Sensors <<< <--SDI12Sensors VaisalaWXT520 at SDI12-0_Pin7 did not reply! <--SDI12Sensors >>> 0! <--SDI12Sensors <<< <--SDI12Sensors VaisalaWXT520 at SDI12-0_Pin7 did not reply! <--SDI12Sensors >>> 0! <--SDI12Sensors <<< <--SDI12Sensors VaisalaWXT520 at SDI12-0_Pin7 did not reply! <--SDI12Sensors Asking for sensor acknowlegement <--SDI12Sensors >>> 0! <--SDI12Sensors <<< <--SDI12Sensors VaisalaWXT520 at SDI12-0_Pin7 did not reply! <--SDI12Sensors >>> 0! <--SDI12Sensors <<< <--SDI12Sensors VaisalaWXT520 at SDI12-0_Pin7 did not reply! <--SDI12Sensors >>> 0! <--SDI12Sensors <<< <--SDI12Sensors VaisalaWXT520 at SDI12-0_Pin7 did not reply! <--SDI12Sensors >>> 0! <--SDI12Sensors <<< <--SDI12Sensors VaisalaWXT520 at SDI12-0_Pin7 did not reply! <--SDI12Sensors >>> 0! <--SDI12Sensors <<< <--SDI12Sensors VaisalaWXT520 at SDI12-0_Pin7 did not reply! <--SDI12Sensors VaisalaWXT520 at SDI12-0_Pin7 is not currently measuring! <--SDI12Sensors AT AT OK It's been 2454 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT+CEREG? AT+CEREG? +CEREG: 0,5 OK AT+CSQ AT+CSQ +CSQ: 99,99 OK AT AT OK It's been 2704 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT AT OK It's been 2954 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT+CEREG? AT+CEREG? +CEREG: 0,5 OK AT+CSQ AT+CSQ +CSQ: 99,99 OK AT AT OK It's been 3205 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT+CEREG? AT+CEREG? +CEREG: 0,5 OK AT+CSQ AT+CSQ +CSQ: 99,99 OK AT AT OK It's been 3455 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT AT OK It's been 3705 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT+CEREG? AT+CEREG? +CEREG: 0,5 OK AT+CSQ AT+CSQ +CSQ: 99,99 OK AT AT OK It's been 3955 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT+CEREG? AT+CEREG? +CEREG: 0,5 OK AT+CSQ AT+CSQ +CSQ: 99,99 OK AT AT OK It's been 4205 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT+CEREG? AT+CEREG? +CEREG: 0,5 OK AT+CSQ AT+CSQ +CSQ: 99,99 OK AT AT OK It's been 4455 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT+CEREG? AT+CEREG? +CEREG: 0,5 OK AT+CSQ AT+CSQ +CSQ: 99,99 OK AT AT OK It's been 4705 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT AT OK It's been 4956 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT+CEREG? AT+CEREG? +CEREG: 0,5 OK AT+CSQ AT+CSQ +CSQ: 99,99 OK AT AT OK It's been 5206 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT+CEREG? AT+CEREG? +CEREG: 0,5 OK AT+CSQ AT+CSQ +CSQ: 99,99 OK AT AT OK It's been 5456 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT+CEREG? AT+CEREG? +CEREG: 0,5 OK AT+CSQ AT+CSQ +CSQ: 13,99 OK Asking modem to give signal quality: <--LoggerModem Getting signal quality: <--SodaqUBeeR410M AT+CSQ AT+CSQ +CSQ: 13,99 OK Raw signal quality: 13 <--SodaqUBeeR410M RSSI Estimated from CSQ: -87 <--SodaqUBeeR410M Signal percent calcuated from CSQ: 42 <--SodaqUBeeR410M RSSI: -87 <--LoggerModem Percent signal strength: 42 <--LoggerModem Getting battery info, if possible: <--LoggerModem Getting modem battery data: <--SodaqUBeeR410M AT+CIND? AT+CIND? +CIND: 5,2,1,0,0,1,1,0,1,0,0,2 OK Modem battery charge state: 0.00 <--LoggerModem Modem battery percentage: 100.00 <--LoggerModem Modem battery voltage: 0.00 <--LoggerModem Getting chip temperature, if possible: <--LoggerModem Getting temperature: <--SodaqUBeeR410M AT+UTEMP=0 AT+UTEMP=0 ERROR Temperature: -9999.00 <--SodaqUBeeR410M Modem temperature: -9999.00 <--LoggerModem PRIOR modem active time: 96.359 <--LoggerModem PRIOR modem powered time: 105.386 <--LoggerModem Skipping u-blox SARA-R410M-02B in sensor power down! <--LoggerModem \/---- Line Saved to SD Card ----\/ 2020-01-09 17:55:00,3,4.745,23.00,42,-9999,-9999.0,-9999.0,-9999.0,-9999.0,-9999.00 Waiting for u-blox SARA-R410M-02B to respond to AT commands... <--SodaqUBeeR410M AT AT OK ... AT OK after 39 milliseconds! <--SodaqUBeeR410M Waiting up to 50 seconds for cellular network registration... <--SodaqUBeeR410M AT+CEREG? AT+CEREG? +CEREG: 0,5 OK ... Registered after 131 milliseconds. Connecting to GPRS... <--SodaqUBeeR410M AT+CGATT=1 AT+CGATT=1 OK AT+CGDCONT=1,"IP","hologram" AT+CGDCONT=1,"IP","hologram" OK AT+CGACT=1,1 AT+CGACT=1,1 OK ... Connected after 397 milliseconds. <--SodaqUBeeR410M Sending data to [ 0 ] cloudsocket.hologram.io RUNNING IN HOLOGRAM <--HologramPublisher Outgoing JSON size: 509 <--HologramPublisher Connecting client <--HologramPublisher AT+USOCL=0,1 AT+USOCL=0,1 OK AT+USOCR=6 AT+USOCR=6 +USOCR: 0 OK AT+USOSO=0,6,1,1 AT+USOSO=0,6,1,1 OK AT+USOCO=0,"cloudsocket.hologram.io",9999,1 AT+USOCO=0,"cloudsocket.hologram.io",9999,1 OK Client connected after 77302 ms <--HologramPublisher {"k":"xxxxxxxx","d":"time,2020-01-09T17:55:00Z,sample,3,boardbatt,4.745,boardtemp,23.00,signalpct,42,Dm,-9999,Sm,-9999.0,Pa,-9999.0,Ta,-9999.0,Ua,-9999.0,Rc,-9999.00"} AT+USOWR=0,167 AT+USOWR=0,167 +CME ERROR: Operation not allowed AT+USOWR=0,2 AT+USOWR=0,2 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed AT+USORD=0,0 AT+USORD=0,0 +CME ERROR: Operation not allowed AT+USOCTL=0,10 AT+USOCTL=0,10 +CME ERROR: Operation not allowed Stopping client <--HologramPublisher AT+USOCL=0,1 AT+USOCL=0,1 +CME ERROR: Operation not allowed Client stopped after 92 ms <--HologramPublisher -- Response Code -- 504 AT+CGACT=0 AT+CGACT=0 ERROR AT+CGATT=0 AT+CGATT=0 OK Disconnected from cellular network after 499 milliseconds. <--SodaqUBeeR410M Turning u-blox SARA-R410M-02B off. <--LoggerModem Running given sleep function for u-blox SARA-R410M-02B <--LoggerModem Asking u-blox R410M to power down <--SodaqUBeeR410M AT+CPWROFF AT+CPWROFF OK Total modem active time (s): 95.746 <--LoggerModem Waiting up to 15000 milliseconds for graceful shutdown as indicated by pin 19 going 0 ... <--LoggerModem ... shutdown complete after 1307 ms. <--LoggerModem Total modem power-on time (s): 102.850 <--LoggerModem Turning off power to u-blox SARA-R410M-02B with pin 23 <--LoggerModem |
