Regarding doubts in SL 8082 and OpenAT SL8082BTR

1

1.We have tried flashing the modem multiple times in short span of time, the modem is getting hung up in the middle of the execution. If we leave the modem in power OFF mode for 30 mins to 1 hour and powering it ON again, it works properly as it should. Could there be a specific issue causing this?

2.When a GPRS failure occurs, is there a particular reason behind it, we are getting error 36 and after manually the powering OFF and powering ON, the GPRS again reconnects but after few days the same error 36 happens. To resolve the issue, is there any error handling for GPRS error setup, other than powering ON and OFF the modem or soft reset in the modem.

3.Does “WIP_BEV_ME_UNREG” refer to an issue on the SIM server side or a code-related problem, in this context we are using GPRS bearer?

4.The RTC is responsible for the timestamp logging of the debug logs but the timing is not in order when it comes to timestamp. The timestamp is normal until an error occurs and after the error has occurred, the timestamp for logging the debug logs is not in order. Is there specific reason for this issue? For exmple, we are seeing the logs that should at 8:30 AM, are comming in between 9:00 AM to 9:30 AM.

  1. When the DCU (Data Concentrator Unit) is not able to connect to the server back, we usually remove the sim and insert it back, now the DCU will be able to connect to the MQTT server. But sometimes, though we remove and insert back the same sim in the same DCU, the DCU was not able to connect back to the server. So we have tried to insert a new sim in the DCU and it got connected to the server without any problem. The removed sim in inserted in a different modem, now both the modem and sim are working perfectly fine and the DCU is able to connect to the MQTT server. Because of this, we are unable to find whether the issue is with the modem, code, or sim. If possible, please let us know if there is any possible resolution for this issue. This issue is persisting almost for all the DCUs.
2

duplicate topic to

3

Hi

Thanks for the reply, we are working in the same team and same project. Please provide us with the proper guidance it will be very helpful for the project. Sorry for the inconvenience.

4

you can see in that thread, right?

5

Hi,
Yes, since we are both working together on this project, we kindly request your support in resolving these issues.

6
  1. Why do we encounter the -36 error every time? Is there a specific reason for this?
  2. Is it possible that the SL8082 modem is outdated?
  3. Why do two or more DCUs go offline every day, specifically failing to connect to the MQTT?
  4. After upgrading the firmware, the modem hangs. Is it possible that the modem does not support specific scenarios?
7
  1. -36 means the GPRS setup failure, probably you need to restart the GPRS connection routine. Is it location dependent?
  2. Do you mean in the past there was no -36problem?
  3. Did you capture wireshark log to investigate?
  4. Are you using exe or dwl file?
8

  1. Yes, GPRS setup failures can sometimes be location-dependent due to variations in network coverage, signal strength, or interference in different areas.

  2. If the issue did not occur in the past, it may indicate changes in the environment, firmware, or configuration.

  3. Capturing Wireshark logs is essential for troubleshooting this issue effectively.

  4. We are using a .dwl file, which is a common format for Sierra Wireless/SL8082 modules used to update firmware or load applications onto the module.

9

1,2: then you might need to restart the GPRS connection and see if there is any improvement.
This module has been end of life, I don’t think there will be FW fix.

  1. please do so then.

  2. is it 100% reproducible? I remember using AT+WDWL with dwl file should be quite stable