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 8:34 PM
#13586
Sara, this is really amazing support. Thank you very much for your contributions to the community.
Unfortunately, problems persist. As far as I can tell, switching to synchronous close did not improv
Sara, this is really amazing support. Thank you very much for your contributions to the community.
Unfortunately, problems persist. As far as I can tell, switching to synchronous close did not improve the situation. I’m attaching another log, this time with TINY_GSM_DEBUG enabled. We are still sometimes getting +CME ERROR: Operation not allowed with USOCL. Hopefully the TINY_GSM_DEBUG messages will help with tracking down what’s going on… I don’t really follow all the internals of the AT commands but I do wonder why it’s closing immediately after the Connecting to NIST daytime Server message.
|
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 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 |
Connecting to NIST daytime Server <--SodaqUBeeR410M [208889] ***** Doing synchronous close on 1 AT+USOCL=1 +CME ERROR: Operation not allowed AT+USOCR=6 +USOCR: 1 OK AT+USOSO=1,6,1,1 OK AT+USOCO=1,"time.nist.gov",37,1 OK [224096] ### Unhandled: OK AT+USORD=1,0 +USORD: 1,0 OK AT+USOCTL=1,10 +USOCTL: 1,10,4 OK [226238] ### AVAILABLE: 0 on 1 AT+USORD=1,0 +USORD: 1,0 OK AT+USOCTL=1,10 +USOCTL: 1,10,4 OK [226742] ### AVAILABLE: 0 on 1 AT+USORD=1,0 +USORD: 1,0 OK AT+USOCTL=1,10 +USOCTL: 1,10,4 OK [227244] ### AVAILABLE: 0 on 1 AT+USORD=1,0 +USORD: 1,0 OK AT+USOCTL=1,10 +USOCTL: 1,10,4 OK [227745] ### AVAILABLE: 0 on 1 AT+USORD=1,0 +USORD: 1,0 OK AT+USOCTL=1,10 +USOCTL: 1,10,4 OK [228247] ### AVAILABLE: 0 on 1 AT+USORD=1,0 +USORD: 1,0 OK AT+USOCTL=1,10 +USOCTL: 1,10,4 OK [228749] ### AVAILABLE: 0 on 1 AT+USORD=1,0 +USORD: 1,0 OK AT+USOCTL=1,10 +USOCTL: 1,10,4 OK [229251] ### AVAILABLE: 0 on 1 AT+USORD=1,0 +USORD: 1,0 OK AT+USOCTL=1,10 +USOCTL: 1,10,4 OK [229752] ### AVAILABLE: 0 on 1 AT+USORD=1,0 +USORD: 1,0 OK AT+USOCTL=1,10 +USOCTL: 1,10,4 OK [230254] ### AVAILABLE: 0 on 1 AT+USORD=1,0 +USORD: 1,0 OK AT+USOCTL=1,10 +USOCTL: 1,10,4 OK [230754] ### AVAILABLE: 0 on 1 NIST Time server did not respond! <--SodaqUBeeR410M [231108] ***** Doing synchronous close on 1 AT+USOCL=1 OK Connecting to NIST daytime Server <--SodaqUBeeR410M [265910] ***** Doing synchronous close on 1 AT+USOCL=1 +CME ERROR: Operation not allowed AT+USOCR=6 +USOCR: 1 OK AT+USOSO=1,6,1,1 OK AT+USOCO=1,"time.nist.gov",37,1 OK [281118] ### Unhandled: OK AT+USORD=1,0 +USORD: 1,0 OK AT+USOCTL=1,10 +USOCTL: 1,10,4 OK [283258] ### AVAILABLE: 0 on 1 AT+USORD=1,0 +USORD: 1,0 OK AT+USOCTL=1,10 +USOCTL: 1,10,4 OK [283760] ### AVAILABLE: 0 on 1 AT+USORD=1,0 +USORD: 1,4 OK [284194] ### AVAILABLE: 4 on 1 NIST responded after 1081 ms <--SodaqUBeeR410M AT+USORD=1,4 +USORD: 1,4,"��Q�" OK [284278] ### READ: 4 from 1 AT+USORD=1,0 +USORD: 1,0 OK AT+USOCTL=1,10 +USOCTL: 1,10,9 OK [284418] ### AVAILABLE: 0 on 1 [284424] ***** Doing synchronous close on 1 AT+USOCL=1 OK Response Byte 0 : � = 225 = 11100001 <--LoggerModem Response Byte 1 : � = 194 = 11000010 <--LoggerModem Response Byte 2 : Q = 81 = 1010001 <--LoggerModem Response Byte 3 : � = 245 = 11110101 <--LoggerModem Seconds from Jan 1, 1900 returned by NIST (UTC): 3787608565 = 11100001110000100101000111110101 <--LoggerModem Unix Timestamp returned by NIST (UTC): 1578619765 <--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-10.csv Putting modem to sleep AT+CGACT=0 ERROR AT+CGATT=0 OK Disconnected from cellular network after 368 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): 281.107 <--LoggerModem Waiting up to 15000 milliseconds for graceful shutdown as indicated by pin 19 going 0 ... <--LoggerModem ... shutdown complete after 66 ms. <--LoggerModem Total modem power-on time (s): 286.040 <--LoggerModem Turning off power to u-blox SARA-R410M-02B with pin 23 <--LoggerModem Putting processor to sleep ------------------------------------------ Powering u-blox SARA-R410M-02B with pin 23 <--SodaqUBeeR410M Skipping u-blox SARA-R410M-02B in sensor power up! <--LoggerModem 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 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 82 ms <--SodaqUBeeR410M Pulsed for 151 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 8��[294584] ### Unhandled: 8�� AT AT OK It's been 309 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT+CEREG? AT+CEREG? +CEREG: 0,2 OK AT+CSQ AT+CSQ +CSQ: 99,99 OK AT AT OK It's been 559 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT AT OK It's been 809 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 1059 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 1309 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT AT OK It's been 1561 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 1812 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 2062 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 2312 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 2562 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 2812 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 3062 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 3312 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT AT OK It's been 3563 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 3813 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 4063 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 4313 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 4563 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 4813 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 5063 ms, and u-blox SARA-R410M-02B is now responding to AT commands! <--LoggerModem AT AT OK It's been 5314 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 5564 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: 15,99 OK Asking modem to give signal quality: <--LoggerModem Getting signal quality: <--SodaqUBeeR410M AT+CSQ AT+CSQ +CSQ: 15,99 OK Raw signal quality: 15 <--SodaqUBeeR410M RSSI Estimated from CSQ: -83 <--SodaqUBeeR410M Signal percent calcuated from CSQ: 48 <--SodaqUBeeR410M RSSI: -83 <--LoggerModem Percent signal strength: 48 <--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: 281.107 <--LoggerModem PRIOR modem powered time: 286.040 <--LoggerModem Skipping u-blox SARA-R410M-02B in sensor power down! <--LoggerModem \/---- Line Saved to SD Card ----\/ 2020-01-10 01:30:00,2,4.761,23.75,48,-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 133 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 399 milliseconds. <--SodaqUBeeR410M Sending data to [ 0 ] cloudsocket.hologram.io RUNNING IN HOLOGRAM <--HologramPublisher Outgoing JSON size: 509 <--HologramPublisher Connecting client <--HologramPublisher [301012] ***** Doing synchronous close on 1 AT+USOCL=1 AT+USOCL=1 +CME ERROR: Operation not allowed 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 [376326] ### Unhandled: AT+USOCO=0,"cloudsocket.hologram.io",9999,1 OK [378329] WARNING: Mux number changed from 1 to 0 Client connected after 77319 ms <--HologramPublisher {"k":"xxxxxxxx","d":"time,2020-01-10T01:30:00Z,sample,2,boardbatt,4.761,boardtemp,23.75,signalpct,48,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 [378755] ### AVAILABLE: 0 on 0 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 [379262] ### AVAILABLE: 0 on 0 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 [379770] ### AVAILABLE: 0 on 0 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 [380276] ### AVAILABLE: 0 on 0 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 [380778] ### AVAILABLE: 0 on 0 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 [381288] ### AVAILABLE: 0 on 0 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 [381798] ### AVAILABLE: 0 on 0 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 [382308] ### AVAILABLE: 0 on 0 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 [382818] ### AVAILABLE: 0 on 0 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 [383324] ### AVAILABLE: 0 on 0 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 [383832] ### AVAILABLE: 0 on 0 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 [384339] ### AVAILABLE: 0 on 0 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 [384847] ### AVAILABLE: 0 on 0 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 [385355] ### AVAILABLE: 0 on 0 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 [385859] ### AVAILABLE: 0 on 0 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 [386369] ### AVAILABLE: 0 on 0 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 [386879] ### AVAILABLE: 0 on 0 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 [387389] ### AVAILABLE: 0 on 0 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 [387897] ### AVAILABLE: 0 on 0 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 [388403] ### AVAILABLE: 0 on 0 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 [388907] ### AVAILABLE: 0 on 0 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 [389406] ### AVAILABLE: 0 on 0 Stopping client <--HologramPublisher [389566] ***** Doing synchronous close on 0 AT+USOCL=0 AT+USOCL=0 +CME ERROR: Operation not allowed Client stopped after 88 ms <--HologramPublisher -- Response Code -- 504 AT+CGACT=0 AT+CGACT=0 ERROR AT+CGATT=0 AT+CGATT=0 OK Disconnected from cellular network after 479 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.838 <--LoggerModem Waiting up to 15000 milliseconds for graceful shutdown as indicated by pin 19 going 0 ... <--LoggerModem ... shutdown complete after 1305 ms. <--LoggerModem Total modem power-on time (s): 104.575 <--LoggerModem Turning off power to u-blox SARA-R410M-02B with pin 23 <--LoggerModem ------------------------------------------ |
