BG600L: QSSLRECV=0,0 Not Working as Expected

IoT Modules LPWA Module
#1

I have a BG600L and I am trying to use QSSLRECV=0,0 to retrieve the number of bytes available to read. According to “Quectel_BG95BG77BG600L_Series_SSL_Application_Note_V1.1-1”, p24, I can use

AT+QSSLRECV=clientID,0

and this should return

+QSSLRECV: <total_receive_length>,<have_read_length>,<unread_length>

However, it always returns

+QSSLRECV: 0

I issue

AT+QSSLRECV=0,0

after receiving the ‘recv’ URC in order to get the actual number of bytes available, as the SSL URC doesn’t tell me, unlike the regular TCP version.

Any ideas what could be wrong?

Thank you.

Charles Law

#2

I will feedback your request to R&D.

If you send “AT+QSSLRECV=0,0”, it will read the TCP Buffer , The the buffer is empty , will Return 0 ,

One point need to pay more attention to , the return of AT is different from URC .

#3

Thank you for the response. As this is a …SSL… command I would expect it to read from the TLS/SSL buffer rather than the TCP buffer. If it does not it I think the unexpected behaviour needs to be made clear in the application note. I would also expect it to comply with the stated response format, and return

+QSSLRECV: 0,0,0

Would you agree?

#4

Does anyone have experience of this command working as documented? I’d appreciate an answer to promote the conversation.

Thank you.