Posts made by magnatron

Hi @Sunny8569,
Please be aware that the maintainers of this forum are hardly ever here anymore.

I’m very happy I received an announcement from Afzal yesterday. Not happy at all with the fact that you keep doing maintenance in the middle of the day and that you keep announcing way to short before the interruption. But hey, at least I received an email.

However, when I want to know more about the interruption and find out if it went as planned, where can I go??

There’s nothing on the forum and nothing on the discord. Not even the announcement.

Is there a new platform somewhere that I didn’t hear about?

@magnatron Ah, not here but in the mail. Thanks.

Any update on the update? Is it done? Did it go well?
Thanks

@afzal_m very happy to hear this. As there was no change in the announcement I could only respond to what was stated.

@Florian-Duecker Again: unacceptable the way this is handled. 1,5 working day ahead announcement. Not in the “Announcement” channel. Expecting understanding. No buffering.

Please explain how we should inform our customers their device won’t be working in the middle of a working day tomorrow?
Also please help us to deal with the anger and frustration our customers will show. Oh, and please tell where we can collect lost revenue because customers are walking out.

Thanks for your understanding

Hi @Ronan-Lacroix,

Thank you for your elaborate reply. I think I understand now. We produce a device which is aimed at staying in the same place so the choice for automatic selection seems most appropriate.
Kind regards, Maarten Wolzak

What is industry standard to select a band and an operator?
Should we leave it up to the network and the modem to negotiate or is there a standard process we should follow to iterate over bands and operators programmatically?

@Jeroen-van-Bussel
I experience the same issue. However, deleting and recreating the device doesn’t solve it. Can you share as what type you recreated the device?

There’s an announcement in the portal which is not shared here.
For those that only work via API and have a notification on the forum:

We’ll update our backend on Wednesday 8th December, 2021 from 8:30 to 9:30 am CET. During that time window we expect a short outage of all device communication for not longer than 5 minutes.

@florian-duecker The IMEI was still registered at a separate account (hw developer account)
So, there might be a small bug in the register-device procedure that the response is a successful one (green prompt) while the device cannot actually be registered.
(just a guess)

I’m’ trying to register a Quectel device in a project. First time I entered the IMEI it was successful and the response was green. But it doesn’t show up in the list of devices.
Could not enter it a second time.
What could be the problem?

@uta thanks.
The extract is really nice. More of these simplifications might be very useful for people that have ideas to try with IoT but do not have the nerdiness to go through those manuals.
However, I still cannot get it to work:

1. Sending over the portal.
2. Sending message from SARA-N2 device.
3. Running AT+NQMGR results in BUFFERED=0,RECEIVED=0,DROPPED=0

@roalnd-baldin I’m able to send downlinks with the portal but unable to receive them on the device.
Are there any examples available for the ublox AT command set?

Thanks

@Yassine-Amraue No, not yet. I’m doing some testing with the portal but it seems sending downlinks influences the time it takes to send an uplink. I’m trying to figure it out but I’m not getting good results yet.

Is there any instructions on reading the downlink messages on a ublox sara-n211? I only found the instructions for the BC66 kit which has different AT commands…

@Ederuiter @afzal_m
Thanks.
We were thinking in that direction (sending version)
Another reason why I asked is that since I started sending downlinks to a (devkit) device for testing purposes, the device now is extremely slow in sending messages. It takes minutes, sometimes hours to send a single message (uplink).
Could that be linked to not “collecting” the downlink messages?

@Stefan-de-Lange we only plan on being able to update our software when really needed without needing to get the devices back in store. This should not happen on a daily basis, or even monthly.
We just want to make sure we can.

@Stefan-de-Lange @afzal_m thanks.
But still: can we know if queued downlinks are retrieved? Does the platform know?

@Roalnd-Baldin thanks!
Good catch the 195/197. However, we still see hundreds on AWS. It’s probably us then. I’ll check the header.

Anybody? @Uta @Florian-Duecker ?

@Stefan-de-Lange then how come FOTA does work over NB-IoT? Modem fwpkg > 1MB

@Stefan-de-Lange why?

Is their a callback mechanism to tell the northbound application that downlinks are consumed by device?

We have to split up a file into several ±7,5K payloads to send as downlinks. When we have more than 75K to send to the devices, what is the way to go about this?

• Should the device send a message so the NB application knows?
• Does the IMPACT platform notify the NB application?