• State Verified Answer
  • Replies 16 replies
  • Subscribers 2 subscribers
  • Views 5412 views
  • Users 0 members are here
Options
Related

DA16200 MQTT DPM (reopened)

premsai

Hi,

Somehow the thread " https://www.dialog-semiconductor.com/support-posts/da16200-mqtt-dpm " was bricked.

So opening this new one.

"""PM_Dialog 

Hi Premsai, 

According to our Team internally, we need some extra info regarding that issue. Please check below. 

1. dpm status

 

2. mqtt configuration

 

Can you please share that screenshots from your side? 

Regards, 

PM_Dialog"""

Reply:

Since i'm not allowed to share confidential information some of the info are masked.Please find the snapshots.

Regards,

Prem Sai

13468.zip
Parents
  • 0

    Hi,

    Thanks for the response.

    Test Scenario:

    Initially we have used UART1_TXD(GPIOA4 of DA16200MOD DVK) as the wake up of HOST MCU since the HOST MCU was not able to detect the interrupt provided by GPIOA11 of DA16200MOD. At that time we observed the 1hr wakeup of HOST MCU since some data is transmitted via UART1_TXD. In the custom board we used GPIO 11 as the wake up source so now the HOST MCU wakes every 10 min.

    Once the DA16200 MOD wakes HOST MCU, it RESETS the DA16200 MOD using RTC_PWR_KEY and sends the AT sequence(already shared) and HOST MCU does its operation and once the operations are complete it puts the DA16200 MOD again in DPM mode.

    What we were expecting was that once DA16200 MOD receives message via MQTT only then it generates interrupt at GPIO11 but every time it pings the server (keep alive maybe) it generates interrupt.

    Q1 : Do you know if the host controls the power of DA16200 or not? and Q2 : Are they using those wake up source?

    Once the HOST MCU gets woken up from sleep mode it RESETS the DA16200 MOD using RTC_PWR_KEY and AT+DPM=0 is send.

     

    "DA16200 sends a packet every hour normally." Could you please provide some  info on this.

    Thanks and Regard

    Prem Sai

Reply
  • 0

    Hi,

    Thanks for the response.

    Test Scenario:

    Initially we have used UART1_TXD(GPIOA4 of DA16200MOD DVK) as the wake up of HOST MCU since the HOST MCU was not able to detect the interrupt provided by GPIOA11 of DA16200MOD. At that time we observed the 1hr wakeup of HOST MCU since some data is transmitted via UART1_TXD. In the custom board we used GPIO 11 as the wake up source so now the HOST MCU wakes every 10 min.

    Once the DA16200 MOD wakes HOST MCU, it RESETS the DA16200 MOD using RTC_PWR_KEY and sends the AT sequence(already shared) and HOST MCU does its operation and once the operations are complete it puts the DA16200 MOD again in DPM mode.

    What we were expecting was that once DA16200 MOD receives message via MQTT only then it generates interrupt at GPIO11 but every time it pings the server (keep alive maybe) it generates interrupt.

    Q1 : Do you know if the host controls the power of DA16200 or not? and Q2 : Are they using those wake up source?

    Once the HOST MCU gets woken up from sleep mode it RESETS the DA16200 MOD using RTC_PWR_KEY and AT+DPM=0 is send.

     

    "DA16200 sends a packet every hour normally." Could you please provide some  info on this.

    Thanks and Regard

    Prem Sai

Children
No Data