Early Access participants

@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?

@MeneerJacco any news? Did you reach out to Simcom?

“Might be a different default setting for the UART slow clock control.”

@meneerjacco

What a strange and annoying problem! I think that it makes most sense to report this problem directly to Simcom. But in the meantime I have asked some colleagues if they recognize this behaviour.

Will let you know

@derko-drukker

I think you have been in touch with Roland already, right?

Just to be sure

@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?