# MangOH Yellow OOB can't connect to octave using GettingStartedGuide **URL:** \ **Category:** mangOH Yellow\ **Created:** [March 24, 2020, 4:29pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-oob-cant-connect-to-octave-using-gettingstartedguide/4131 "2020-03-24T16:29:28Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![luisalbertoespinosa](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@luisalbertoespinosa](https://mangoh.discourse.group/u/luisalbertoespinosa)\ **Post date:** [March 24, 2020, 4:29pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-oob-cant-connect-to-octave-using-gettingstartedguide/4131/1 "2020-03-24T16:29:29Z")
Hi, I’m evaluating mangOH yellow with which I managed to follow the Getting Started Guide to connect the device and interact directly with it (step 4) without any problem. When I tried to connect to Octave to obtain sensor data (step 5.2) is when I started having problems as the device were never detected by Octave (device were not in Las Vegas mode). If I power cycle the device, the Network LED turns green as it starts, then after a moment, the Nwk yellow LED becomes ON (The green one remains on) as it is supposed to happen… right? After this I start digging on what might cause this for which I: - Attached the antenna to the connector labeled as ‘main’, same result. - Followed the guides indicating how to update the firmware (yellow\_wp77xx\_0.5.0-octave.spk) after which I the device did not connect to Octave, even when the procedure indicated success. - Investigate on the API to know what happen to the device (where is the list of commands that can be used in a ssh session with the device, so far I only use what I saw people using in the forums?) - Using ‘cm radio’ after a reset several times I notice that the radio was not being able to register to the LTE-M network, I notice 3 types of state: root@swi-mdm9x28-wp:~# cm radio Power: ON Current Network Operator: Current RAT: Module not registered on network, RAT not available Status: Not registered and not currently searching for new operator (LE\_MRC\_REG\_NONE) Signal: No signal strength (0) PS: Packet Switched Not registered (LE\_MRC\_REG\_NONE) root@swi-mdm9x28-wp:~# cm radio Power: ON Current Network Operator: Sierra Wireless Current RAT: Module not registered on network, RAT not available Status: Not registered but currently searching for a new operator (LE\_MRC\_REG\_SEARCHING) Signal: Very strong signal strength (5) PS: Packet Switched Not registered (LE\_MRC\_REG\_NONE) root@swi-mdm9x28-wp:~# cm radio Power: ON Current Network Operator: Current RAT: Module not registered on network, RAT not available Status: Registration was denied, usually because of invalid access credentials (LE\_MRC\_REG\_DENIED) Signal: No signal strength (0) PS: Packet Switched Not registered (LE\_MRC\_REG\_NONE) After this, I saw people communicating directly to the modem using AT commands, for which ‘microcom’ is used: ‘microcom -E /dev/ttyAT’ however, if I use this I get the following message: root@swi-mdm9x28-wp:~# microcom -E /dev/ttyAT microcom: invalid number ‘/dev/ttyAT’ I have been reading all day about how to know what my problem is to get the out of the box demo to work without success and at this point I think I need a bit of help. Additional info that might help: root@swi-mdm9x28-wp:~# cm info Device: WP7702 IMEI: 352653090210394 IMEISV: 4 FSN: 4L936370340610 Firmware Version: SWI9X06Y\_02.32.02.00 c2e98c jenkins 2019/08/30 07:28:21 Bootloader Version: SWI9X06Y\_02.32.02.00 c2e98c jenkins 2019/08/30 07:28:21 MCU Version: 002.013 PRI Part Number (PN): 9909138 PRI Revision: 001.001 Carrier PRI Name: SIERRA Carrier PRI Revision: 001.027\_000 SKU: 1104405 Last Reset Cause: Power Down Resets Count: Expected: 27 Unexpected: 0 root@swi-mdm9x28-wp:~# cm data Index: 1 APN: iot.swir PDP Type: IPV4V6 Connected: no root@swi-mdm9x28-wp:~# cm sim info Type: EMBEDDED ICCID: 89332401000010872485 Home Network Operator: Sierra Wireless EID: 89033240817620069918070003392558 IMSI: 234507089996147 Phone Number: I’m located in Mexico, Baja California, can the device be used in here? Please, let me know if more information is needed to know what is happening or what can I try to get the device to work. Any help is appreciated! ---
**Author:** ![luisalbertoespinosa](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@luisalbertoespinosa](https://mangoh.discourse.group/u/luisalbertoespinosa)\ **Post date:** [March 24, 2020, 4:34pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-oob-cant-connect-to-octave-using-gettingstartedguide/4131/2 "2020-03-24T16:34:15Z")
UPDATE: I got the same result using: [https://downloads.sierrawireless.com/mangOH/exe/yellow\_wp77xx\_0.5.0-octave.exe](https://downloads.sierrawireless.com/mangOH/exe/yellow_wp77xx_0.5.0-octave.exe) Log of radio state below, output of the .exe file at the end. root@swi-mdm9x28-wp:~# cm radio Power: ON Current Network Operator: Current RAT: Module not registered on network, RAT not available Status: Not registered and not currently searching for new operator (LE\_MRC\_REG\_NONE) Signal: No signal strength (0) PS: Packet Switched Not registered (LE\_MRC\_REG\_NONE) root@swi-mdm9x28-wp:~# cm radio Power: ON Current Network Operator: Sierra Wireless Current RAT: Module not registered on network, RAT not available Status: Not registered but currently searching for a new operator (LE\_MRC\_REG\_SEARCHING) Signal: Very strong signal strength (5) PS: Packet Switched Not registered (LE\_MRC\_REG\_NONE) root@swi-mdm9x28-wp:~# cm radio Power: ON Current Network Operator: Sierra Wireless Current RAT: Module not registered on network, RAT not available Status: Registration was denied, usually because of invalid access credentials (LE\_MRC\_REG\_DENIED) Signal: Strong signal strength (4) PS: Packet Switched Not registered (LE\_MRC\_REG\_NONE) **Output of yellow\_wp77xx\_0.5.0-octave.exe** FDT version: 1.0.1902.1 Awaiting adapter … Setting images preference … Resetting … Awaiting download port … Switching to streaming mode … Downloading images … Writing image / Flashing image \ Awaiting adapter … Checking update status … Enabling selective suspend … Firmware image download succeeded. Final Firmware update succeeded. Preexisting images information: ``` Current: Firmware: ImageId: 001.027_000 BuildId: 02.32.02.00_SIERRA Configuration: ImageId: 001.027_000 BuildId: 02.32.02.00_SIERRA ``` Final images information: ``` Current: Firmware: ImageId: 001.027_000 BuildId: 02.32.02.00_SIERRA Configuration: ImageId: 001.027_000 BuildId: 02.32.02.00_SIERRA ``` OEM PRI: 9909138 001.001 IMEI: 352653090210394 Total time elapsed: 125266 ms. Time to switch to boot mode: 31516 ms. Images downloaded: ``` Image ID: 001.027_000 Build ID: 02.32.02.00_SIERRA write time: 22297 ms additional flash time: 23063 ms ``` Time to reset to application mode: 44766 ms. Press Enter to continue … ---
**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\ **Post date:** [March 25, 2020, 10:00pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-oob-cant-connect-to-octave-using-gettingstartedguide/4131/3 "2020-03-25T22:00:03Z")
@thibs can you check this? ---
**Author:** ![luisalbertoespinosa](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@luisalbertoespinosa](https://mangoh.discourse.group/u/luisalbertoespinosa)\ **Post date:** [March 25, 2020, 10:24pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-oob-cant-connect-to-octave-using-gettingstartedguide/4131/4 "2020-03-25T22:24:36Z")
Hi Asyal, @thibs Sorry for forgetting to update on this… It was fixed today and I got exited to start testing it… the issue was solved by SierraWireless, seems like there was a problem with the activation… of the SIM I guess… As reference I put the post there… > **[MangOH Yellow OOB can’t connect to octave using GettingStartedGuide](https://forum.sierrawireless.com/t/mangoh-yellow-oob-can-t-connect-to-octave-using-gettingstartedguide/19869/2)** > > UPDATE: I got the same result using: https://downloads.sierrawireless.com/mangOH/exe/yellow\_wp77xx\_0.5.0-octave.exe Log of radio state below, output of the .exe file at the end. root@swi-mdm9x28-wp:~# cm radio Power: ON Current Network Operator: ... Thanks for the help!