Hello, good afternoon.
How can I handle spontaneous disconnections from a Notecard to NoteHub? I have a starter kit that was working and sending notes without problems for several hours, but suddenly this event occurred:
The card was still powered; in fact, I was keeping a log of events with the PIO Device Monitor, and the MCU continued to work correctly. The notes accumulated, and the connection wasn’t reestablished until I performed a hard reset of the card (disconnecting and restoring the power).
What can be done in this case?
Hi @Juan_Cossio,
I would recommend first looking at any _health.qo Notes that should appear after your Notecard reconnects. They may give some hints as to why the previous connection failed. It’s also important to understand the Notecard Penalty Boxes that will protect your device/battery in the event that Notecard is unable to establish a cellular connection.
Is your device in continuous mode (via the hub.set request)? Are you on a recent release of the Notecard firmware? If it happens again there are commands like hub.status, hub.sync.status, and card.wireless that can help diagnose the current status of the Notecard and its connection to Notehub.
Rob
Hi @RobLauer and @Juan_Cossio,
I have encountered this exact problem over the past two days, since updating my notecard firmware from an earlier version, probably 4.4.4, to 8.1.4.17149. The Notehub dashboard won’t let me go back to the old version to confirm that the problem has arisen since the update. The update to the old firmware just fails with the error “unable to get file ‘notecard-u5-4.4.4.4015707$20240926192723.bin’ from ‘/upload’ storage {dfu-dl}.”
The mode is set to continuous. The notecard just closes the connection and won’t respond to requests or firmware updates unless it is reset. I have worked around the problem for now by getting the MCU to call hub.sync every 10 minutes, which is not ideal.
This behaviour is the same with two Notecards I have; one NOTE-NBGLN and one NOTE-WBEX-500. Both have good cellular connections.
My problem is that I have a couple of units that will not respond to firmware update requests because they won’t initiate connections.
Thanks,
Rob
Hi @rlkeith,
I’m assuming this issue was addressed based on your response in the other post?
Re: the “missing” 4.4.4 firmware - what happened was you tried to update to a version that doesn’t exist for that particular Notecard (LTS 4.4.4 was only available for the legacy green cell Notecards and Notecard WiFi v1). I agree though that our error messaging could be improved there though!
Rob
Hi @RobLauer,
OK. That sounds right. In that case the previous version was a 7.something. That just worked.
I am still having the problem where notecards that are supposed to be continuous just shut down the connection and won’t respond to messages or update requests. The kludge of having the MCU request a sync regularly seems to work. They stay awake after the first few
I have at least one device is in another country, and it is not practical for the user to open it up and push the reset button. I am waiting until the battery runs down so I can ask him to power it up and I will try to catch it before it turns off before it goes unresponsive again.
Is there any way to force a notecard to reset if it is in such a state?
Regards,
Rob
Hi @rlkeith,
As mentioned in this thread, the first thing I would do is look at any _health.qo events that appear in Notehub after the Notecard reconnects. This behavior is definitely not expected, so it’ll be good to dig in to see what the problem could be.
Thanks,
Rob
