Telemetry to IOT Hub Stops after 45 minutes

[Angelia Thompkins]

Posted on August 18, 2017 at 18:09

I am working with a Cloud Jam L4.  It sucessfully connects and sends messages to the iot hub but disconnects after 45 minutes.  I need it to run continuously.

[waclawek.jan]

Posted on August 21, 2017 at 11:15

Cloud Jam L4

What is it?

JW

[AvaTar]

Posted on August 21, 2017 at 11:27

Cloud Jam L4

What is it?

Me too.

Sounds like some high-level (script-based ?) firmware package.

And '...stops after 45 minutes' sounds like a yet undiscovered bug in this firmware.

I hardly see a way around inspecting/debugging your application ...

[John F.]

Posted on August 22, 2017 at 09:08

This is the Cloud application board of JAM family and then is capable of connecting the motion & environmental sensors to the cloud throught Wi-Fi network using SSID, Password and web authentication stored in the dynamic NFC.

JAM is a family of boards that embeds the most used STM32 Nucleo functional packs. Develop with STM32ODE environment, test with STM32-Nucleo and start immediately with Cloud-JAM. No firmware or software development needed, simple use the .bin file created for the Nucleo. STM32-Nucleo FW plug & play on Cloud-JAM.

I think you'll need to contact the manufacture about their product!

https://community.st.com/external-link.jspa?url=https%3A%2F%2Fwww.rushup.tech%2Fjam%2F

https://community.st.com/external-link.jspa?url=https%3A%2F%2Fgithub.com%2Frushup

[c_]

Posted on September 06, 2017 at 22:42

Hello Angelia, I'm Christian from RushUp.

Cloud-JAM L4 is the industrialized version of the P-NUCLEO-AZURE1 function pack

http://www.st.com/en/evaluation-tools/p-nucleo-azure1.html

 

The FW developed on the Nucleo function pack can be dowloaded into the Cloud-JAM L4 and thanks to the presence of the ST-Link V2, it's also possible to develop and debug code ditecty on JAM board.

Are you using the ST Nucleo demo code?

[Angelia Thompkins]

Posted on September 07, 2017 at 13:11

I am using en.fp-cld-azure1 /AZURE1_V3.0.1

[Matteo Fumagalli]

Posted on September 08, 2017 at 17:30

Hi Angelia,

It seems related to the expiration of the SAS_TOKEN.

It should at least reconnect after 4 minutes as stated in this 

https://github.com/Azure/azure-iot-arduino/issues/60

 but that doesn't happend with 

en.fp-cld-azure1 and the connection remains stuck. 

We are currently investigating further.As a workaround you can increase the SAS_TOKEN_DEFAULT_LIFETIME in iothubtransport_mqtt_common.c for now.