7 posts / 0 new
Last post
rvempati
Data not getting fetched at the time of sending data to Milli.

Data not getting fetched at the time of sending data to Milli every 2 or 3 Minutes from the CoAP Server.

rchoubey
Data not getting fetched at the time of sending data to Milli.

When you say "If you send data to Milli every 2 minutes" do you mean send data from the CoAP server running on your renesas processor? 

Are you setting the max age with the message from the sensor CoAP server? If so, to what value?

Are you using the wake pin (J5 #4) on the Milli shield to send messages? If so, can what is the signal characteristics? Are you sending a pulse high or pulse low and for how long?

rvempati
Data not getting fetched at the time of sending data to Milli.

Yes, I send data from the CoAP server.

#define COAP_MSG_MAX_AGE_IN_SECS 1800

Yes. I am sending a 1 ms pulse LOW signal.

praghunath
Data not getting fetched at the time of sending data to Milli.

Be sure your device drives the the milli wake-up low then high, and that will wake up the milli.  A 1ms 3.3V level signal should work but you could try lengthening the pulse some to see if there is a timing issue.

rvempati
Data not getting fetched at the time of sending data to Milli.

I changed the pulse time(2ms,3ms), but the result was the same.  If you send data every two minutes from sub-cpu, it works correctly.  But in 3 minutes, it is not working.

rchoubey
Data not getting fetched at the time of sending data to Milli.

The root cause of this issue has been identified as being firewall UDP timeouts. The issue is that UDP "connections are closed if there are no messages exchanged for longer than the timeout. The CoAP Observe sets up such a UDP connection and if no Observe response occurs for a period longer than a configured timeout period then the connection gets closed and subsequent messages are not sent. There were 2 firewalls in the test setup causing issues:

1) The Starfish Stage firewall between Gateway and the internet. SSN has implemented a workaround to temporarily bypass the connection "state" logic and forward responses regardless of state. This is temporary fix and more permanent changes to Gateway are under investigation.

2) The Java CoAP client was run either in ConEd's guest network, at New Cosmos behind their corporate firewall, or in AWS. All 3 likely have UDP timeout settings. We are currently running the CoAP client in AWS and have configured the AWS firewall to eliminate  UDP timeouts on the ports we are using (ports 5683 and 6003).

rvempati
Data not getting fetched at the time of sending data to Milli.

Great !! that seems to solve the issue of milli Data Fetching Issues.