Hello,
I am developing using the Arduino MKR NB 1500 - not a Telstra kit purchase. With a Telstra SIM on the "Telstra IOT Data Plan 10MB".
The development exercise has the aim of switching a light on/off controlled by the NB 1500. The commands come from an AWS server using a TCP socket connection on port 4000.
The system works. :) However, most of the commands can take around one minute to be received by the NB 1500, some are almost instantaneous. :( The commands are simple text e.g. "CMD:ON" followed by a newline character.
I've used an alernative test by connecting to the server with telnet from my desktop (which uses Telstra mobile broadband) and the commands are received without delay.
Here is a section of the code making the connection (works fine):
<code>
...
if ((nbAccess.begin(0, true, true) == NB_READY) && (gprs.attachGPRS() == GPRS_READY)) {
connected = true;
...
if (client.connect(server, port)) {
Serial.println("connected");
...
</code>
Any thoughts on what could be causing the network delays appreciated.
Thank you
Garry
Hi Garry,
Myself Vinodh from TelstraDev support. I will check internally with our experts to find the reasons for this issue,
Are there any specific commands that consistently take more time?
Regards
Vinodh
Hi Garry,
I have had our IoT experts look into your post and they have back with following questions and suggestions.
Did you have any power saving features (i.e. eDRX or PSM) turned on by default? it sounds like you are trying to use NB-IOT for downlink control which may explains the higher latency experiences. It also sounds like the issue is when commands are sent from AWS to the device rather than from device to AWS. Probably need to identify if the device is permanently connected or polling. If it is polling, that may explain why sometimes the message is quick and sometimes not.
Regards
Vinodh