• State Verified Answer
  • Replies 8 replies
  • Subscribers 87 subscribers
  • Views 1107 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 257278
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Thingy91 skipped orange breathing during setup

cachro2

Hi,

I received a Thingy91 and am unable to commission it to nrFCloud.

The Thingy91 skipped orange breathing as mentioned in the manual here (step 4). It went directly to cyan breathing which is weird since I believe it thinks it is associated to the cloud..

It was purchased brand new a few days ago and SIM card is activated through the nRF Cloud portal.

Before I go ahead and update modem firmware and the such, any thoughts?

Thanks,

Robert

  • 0 in reply to Heidi

    Thank you Heidi, we ended up salvaging two GPIO pins by cutting traces running from the Thingy accelerometers to nrf9160 P0.07 and P0.08. (TP37 and TP38). We are now soldering wires directly to these two test points and using them as inputs for our external rotation device which tracks counts. 

    We also decided to use the mqtt_simple firmware on the Thingy91 from the nRF SDK to push raw data to our AWS instance via MQTT. For our MVP prototypes, we did not yet need all the bells and whistles included in the Thingy91 firmware.

    That being said, I've got a few questions. Do you see any issues with us running mqtt_simple on this device?

    I ran a power draw test over the weekend and noticed that every 22 hours or so the Thingy stopped publishing data to our instance. Unfortunately, I needed to power cycle the unit with the on/off switch before it resumed posting. Do you know why this could be? I hope this is not an issue related to the inherent functionality of the PMIC.. Based on the schematic, it looks like the ADP5360 PMIC is controlled by I2C which is obviously not part of the mqtt_simple firmware. Perhaps, if possible, we need to reset the radio in the mqtt firmware every so often?

    Time Voltage (V) Data Used (Mb)
    11/6/2020 3:30pm 4.14 0.26
    11/7/2020 2:52pm 3.99 1.95
    11/8/2020 6:30pm 3.87 3.73
    11/9/2020 8:10am 3.80 4.70

    Also according to the documentation, the EEPROM onboard the Thingy apparently is critical for correct operation and should not be changed. Can you please elaborate what information is there and if it will affect our prototype units running the mqtt_simple firmware in the field?

    Thank you again Heidi, your support is much appreciated.

    Robert

  • 0 in reply to cachro2

    Hi!

    Would you mind making a new ticket for this issue?

    Best regards,

    Heidi

Related
Terms of service